Lon Xml file overview

Lon Xml (lnml) files are used to describe specific Lonworks devices to NiagaraAX. This includes data to describe the device itself (typically derived from an xif file), as well as manufacturer-specific datatypes for nvs, ncis, and cps (typically derived from resource files). For specific low-level details about Lon Xml, see the “Lon Markup Language” section in the Developer Guide.

By convention, any device’s lnml file is named identically as its xif file (except for extension). Meaning, a device that has a “T7350Cs.xif” file will have a “T7350Cs.lnml” file.

By default, Workbench installs with many “standard” lnml files for various Lon devices, all of which are distributed among various lon<Vendor> module jars (for example, lonHoneywell). During a Lon Device Manager “Discover”, these lnml files are automatically searched and defaulted, according to the Program Id returned by each device.

Or, if the needed lon<Vendor> modules are installed on the host JACE platform, a “Quik Learn” automatically uses the matching lnml file to create Lon devices, in much the same manner. For related details, see Lon Device Manager key points, and Quik Learn.

Note that Lon Xml file source data is required to make lnml files.

Lon Xml file source data

Xif and resource files for any Lonworks device are provided by the manufacturer. To create an lnml file for any Lonworks device, you must have its xif file. If the device contains manufacturer-defined datatypes, and you want this data for any LonComponents, you must also supply related resource files.

Resource files typically include the following types:

vendor.ENU — Language resource file (in this case, English).
vendor.FMT — Format selector file.
vendor.FPT — Functional profile file.
vendor.TYP —Type and enum file.

Before using this tool, place all related resource files in a single directory.