Lon Xml files describe specific Lonworks device properties to the system. The file name extension for these files is .lnml. Each device requires its own Lon Xml file.
.jar files), for example, lonHoneywell. Each module contains numerous Lon Xml files for specific devices. You may also create additional Lon Xml files for devices
that are not included in the standard modules.
Each Lon Xml file includes data to describe the device itself (derived from an .xif file), as well as manufacturer-specific datatypes for nvs, ncis, and cps (derived from resource files). By convention, a
device’s Lon Xml file has the same name as its xif file (except for extension). For example, a device with a T7350Cs.xif file has a T7350Cs.lnml file.
During a Lon Device Manager discover, the driver automatically searches each Lon Xml file from which it displays the Program Id for each device. Or, when the needed lonVendor modules are installed on the host platform, a Quik Learn automatically uses the matching Lon Xml file to create Lon devices.
You may need to make your own Lon Xml file if:
Learn Nv action.In general, using the Lon Xml Tool independently integrates Lonworks devices without depending on the framework manufacturer to issue updated lonVendor modules.
For specific low-level details about Lon Xml, see to the Lon Markup Language section in the Developer Guide.
The device manufacturer provides the .xif and resource files for Lonworks devices. To create a Lon Xml file for any Lonworks device, you must have this .xif file. If the device contains manufacturer-defined datatypes, and you want this data for any Lon components, you must also
get the related resource files from the manufacturer.
Resource files include the following types:
Before creating a Lon Xml file, place all related resource files in a single directory.