XIF to XML conversion

You can enter all of the necessary object mapping information manually using any BACnet object browser type tool or the XLConfig tool provided by Control Solutions. Along with the XLConfig tool, you received two utility programs that will allow conversion of a LonWorks XIF file to an XLConfig XML file. This permits fast and easy integration of an entire collection of network variables from a LonWorks device.

To begin with, you need to obtain a copy of the XIF file for the LonWorks device you are going to integrate. If you do not have a copy, you can export it from the device itself using the Nodeutil.exe tool available for free download at www.echelon.com.

The first step is to convert the XIF file to a CSV file. The purpose of this intermediate step is to allow you to review the mapping in "bulk" form using Excel or equivalent spread sheet program.

Open a command prompt (start->Programs->Accessories->Command Prompt) and type in this command:

xif2csv mynode.xif

where "mynode.xif" is the XIF file for your LonWorks device. If the XIF file is not in the same directory as the program, you will need to provide the full path. The program will create a new file named <file>.csv where <file> is the name of the original file excluding suffix. In the above example, we would get mynode.csv.

At this point, you should open the csv file and make any changes you want. The file will look like the following if the XIF for AddMe II is processed. Editing this CSV file can be an in-depth exercise, and is described here.
The second step is to convert the CSV file to an XML file. This XML file is what you will read into the XLConfig tool for subsequent uploading to the Babel Buster 485XL.

Open a command prompt (start->Programs->Accessories->Command Prompt) and type in this command:

csv2xml mynode.csv

where "mynode.csv" is the CSV file created above. This program will create a new file named <file>.xml where <file> is the name of the original file excluding suffix. In the above example, we would get mynode.xml. The resulting XML file will be a text file that looks like the following (only a small portion illustrated). When you click the Read Config from File button in XLConfig.exe, select the XML file you just created.
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!-- Babel Buster 485XL Configuration -->

<Babel_Buster_Configuration>
<BacnetObject>
<ObjectNumber>1</ObjectNumber>
<ObjectMapUse>1</ObjectMapUse>
<ServiceRequest>0</ServiceRequest>
<NodeIndex>1</NodeIndex>
<NvIndex>5</NvIndex>
<SNVTindex>66</SNVTindex>
<NvRawCat>0</NvRawCat>
<NvOffset>0</NvOffset>
<NvBitOffset>0</NvBitOffset>
<NvScaleA>0</NvScaleA>
<NvScaleB>0</NvScaleB>
<NvScaleC>0</NvScaleC>
<DefaultValue>0.000000</DefaultValue>
<ReferenceString>"nvoAnalogIn_1"</ReferenceString>
</BacnetObject>
Notes about importing this XML file: 

Simply reading the XML file into XLConfig.exe does not send these object maps to the Babel Buster 485XL gateway. You need to click the "Write All to Device" button to begin this process (which will take a little time).

The program ID (SPID) found in the XIF file will be imported into the device table in XLConfig, but this device is not installed until you complete the node installation process. You will note that a program ID will be shown, but the Neuron ID will be all zeroes until a node matching this program ID is actually found on the network.