Chipkin LonWorks XIF -> QuickServer Converter

1. Drop your .xif here

Drag & drop a .xif file, or click to browse.

Single file. Parsing happens locally in your browser. Don't have a XIF? Most manufacturers ship one with the device, but if the file is missing you can extract one live from the device. See How To Obtain A XIF for the four practical methods (commissioning database export, manufacturer request, NodeUtil live extraction, gateway-based extraction).

2. Parsed XIF summary

File: -; Name of the uploaded XIF file.
Format version: -; XIF text-format revision declared on line 1 (LonMark DIF Reference Guide). Current revision is 4.402.
Program ID: -; 12-byte device-interface identifier. Binding compatibility depends on this matching across nodes. See LonWorks XIF Files.
Self-doc: -; Device-level self-documentation string. May encode functional-block layout per the LonMark Interoperability Guidelines.
Network variables: -; Count of VAR records in the XIF. Compared against the header's declared static-NV count for a sanity check.

Network variable table

One row per VAR record in the file. Slots is the number of consecutive data-array slots the variable consumes; complex SNVTs like SNVT_switch (2 slots), SNVT_chlr_status (3), SNVT_time_stamp (6), and SNVT_str_asc (31) consume more than one. See SNVT Reference and XIF Mapping Guide.

Name	Index	Dir	SNVT idx	SNVT name	Slots

3. Site configuration

Most defaults below are safe. Always set the Neuron ID from the actual device label or a live XIF extract. Replace the trailing FSE##### in the title with your project's FSE number.

FieldServer title Appears in the Bridge.Title column and in the generated filename. Use the project's FSE number. System Node ID Internal node identifier for the FieldServer itself on the LonWorks bus. Default 97 is the Chipkin convention. LonWorks node name Human-readable label for the source LonWorks device. Used in the Nodes and Map_Descriptors sections. Neuron ID (12 hex chars) Required 48-bit hardware identifier burned into the Neuron chip at manufacture. 12 hex characters with no separators (e.g. 048BC8914800). Without this, the gateway will not bind to the real device. How to get it: see Finding the Neuron ID of a LonWorks Device for the four practical methods (device label, service-pin press, NodeUtil, LonMaker). LonWorks Subnet ID Subnet portion of the device's logical (domain/subnet/node) address. Look up in the commissioning database. LonWorks Node ID Node portion of the logical address. Each device on a subnet has a unique node number. BACnet server node name Name of the BACnet/IP server node the gateway exposes downstream. Appears in the server-side Nodes table. BACnet device instance BACnet device-instance number (0–4,194,303) used by the BMS to address this gateway. See BACnet Device Instance. BACnet adapter Network adapter name on the QuickServer for the BACnet/IP connection. Default N1 is the Ethernet port. Modbus server node name Name of the Modbus/TCP server node the gateway exposes downstream. Used in the alternate CSV output. Modbus Unit ID Modbus slave/unit ID (1–247) that Modbus/TCP clients use to address this gateway. Modbus adapter Network adapter on the QuickServer for the Modbus/TCP connection. Usually the same Ethernet port (N1) as BACnet.

Chipkin LonWorks XIF -> QuickServer Converter v—

1. Drop your .xif here

2. Parsed XIF summary

Network variable table

3. Site configuration

4. Output preview