Although Workbench installs with many lon<Vendor> modules, where each one contains numerous lnml files for specific devices, in some cases you may need an lnml file for a
device not included. Typically, this need arises because:
-
The device includes one or more manufacturer-defined nvs (otherwise, you could simply use a DynamicDevice to represent it, then perform a Learn Nv action).
-
The device is newer or otherwise different than the one represented by the closest “standard” lnml file, or Tridium has not yet released a standard lnml version for this device.
Lon Xml supports “default” (init) values for a device’s ncis and cps, providing that the source .xif file is version 4.0 or
later, and “init” data values other than all zeros exist.
In general, using the Lon Xml Tool allows you to independently integrate Lonworks devices without depending on Tridium to issue updated lon<Vendor> modules.