When using the Lon Xml Tool tool to make an lnml file, you specify the following, by clicking the folder icon beside each input field (see Figure A.2):
-
Working Dir — where the device lnml file is to be made (Directory Chooser appears).
-
Xif File — the manufacturer’s xif for that device (File Chooser appears).
-
Resource Dir (if applicable) — the directory that contains associated resource files (as listed in the previous section, Lon Xml file source data) (Directory Chooser appears).
In the Directory Chooser or File Chooser dialogs, you can specify the complete path (inclusive of drive letter) for the working directory, *.xif file, and resource
files directory. Or, use the “Sys Home” (“!”) path if you are working under the Niagara-3. installation directory.
n.n
Starting in build 3.3.25 and in AX-3.4, a “Zero Based Arrays” checkbox can be used to force the use of “zero-based” names
for the unique name of each element in an arrayed nv, nci, and cp in the lnml file. Names of arrayed elements are created
by appending the array index to the array name. Note the default behavior (unchecked) continues to use “one-based” indices
for arrayed nvs, ncis, and cps.
When you click , the xif file for that device is parsed, along with the resource files (if applicable), and an *.lnml file for the device is created in the working directory. If using resource files, a “datatypes” subdirectory is also created under that working directory, with a child lnml file. See Storing lnml files.
If using resource files, a popup Engineering Unit Select dialog may appear before the lnml files are created. This dialog lets you review unit strings in the “language resource file” that may need association
with Niagara engineering units. See Engineering Unit Select.
Engineering units may be specified for elements in some of the datatypes. Unit descriptor strings are specified in the language resource file (*.enu for English). Strings for units in the resource files are intended for “display only,” and do not have a defined format. Whereas, units specified in the lnml file correspond to Niagara units (BUnits), and as such, must map to a specific set of strings.
If, when compiling, an exact match is not found, a popup dialog shows the original string and lets you pick a new unit from the approved “New Text” list. A “best guess” entry often exists (Figure A.3).
In this dialog, the “Scope/Index” field shows the mapping within the language resource file to the unit string, and the “Original” field shows the found string. Typically, the original string is “close” to an approved Niagara unit in the list (possibly the “best guess”), which you select and click (Figure A.4).
After clicking , if other unit strings are found that need specifying, the dialog remains open—you repeat selections until all unit strings are associated. The device lnml file is then created, along with a datatypes lnml file under the “datatypes” subdirectory of the working directory.
In a few cases, selection of a Niagara unit based on the “Original” text string may be difficult (does not suggest a normal
engineering unit). In this case, you can leave the “New Text” field blank and click to go to the next unit. No units will be applied to elements using this string.
If you are creating lnml files for multiple devices by the same vendor, after doing this process for the first device, you might not be prompted again with an Engineering Unit Select popup, unless another device (xif) points to a new unit string.