Finding the Neuron ID of a LonWorks Device

What A Neuron ID Is

Every LonWorks device has a unique 48-bit identifier burned into its Neuron chip at manufacture. That identifier is the Neuron ID. It is the equivalent of a MAC address: globally unique, hardware-bound, and unchangeable. It is used to bootstrap commissioning, to bind variables to a specific physical device, and to replace a failed device while preserving the rest of the network database.

A Neuron ID is 12 hex characters long, written without separators (for example 048BC8914800). Some tools display it with colons or spaces; the canonical form for FieldServer configurations is the 12-character bare-hex string.

[!NOTE] The Neuron ID is not the same as the device’s domain/subnet/node address. The Neuron ID is hardware identity. The domain/subnet/node is the logical address assigned during commissioning. Routine traffic uses the logical address; commissioning and binding use the Neuron ID. See LonWorks for the full identity model.

Why It Matters

You cannot configure a QuickServer LonWorks gateway against a real device without the Neuron ID. The driver needs it to identify which physical device on the bus is being addressed. The configuration file’s Nodes section has a Neuron_ID column, and a wrong or missing value means the gateway will not bind even if every other parameter is right.

Five practical methods exist for obtaining a Neuron ID. They are listed below in order of reliability and convenience. The first method that works for your site is the right one.

Method 1: Read The Device Label

Most LonWorks devices print the Neuron ID on a sticker affixed to the housing. Look for one of these formats:

• Neuron ID: 04 8B C8 91 48 00
• NID: 048BC8914800
• A 12-character hex string under a small bar code

When the label is intact and legible, this is the fastest method. Strip any spaces or colons and use the 12 hex characters as-is.

[!TIP] Photograph the label during the site walk-through, even if you do not need the value immediately. Labels fade, get painted over, or end up behind cable trays once equipment is in service.

Method 2: Service-Pin Press

Every LonWorks device has a momentary service pin — a small recessed button or a pad you short with a jumper. When pressed, the device broadcasts a service-pin message containing its Neuron ID and Program ID on the LonTalk network.

To capture the broadcast:

1. Attach a network management tool (LonMaker, IzoT CT, or NodeUtil) to the LonWorks segment.
2. Set the tool to listen for service-pin messages.
3. Press the service pin on the target device.
4. The tool displays the Neuron ID and Program ID of the device that pressed.

This is the canonical method for commissioning a new device whose label cannot be read. It is also the only method that works for devices behind sealed enclosures whose label is not accessible.

[!CAUTION] A service-pin press on a commissioned device does not change the device’s state. It only sends a broadcast. Confirm with the controls team before pressing on a device that is currently in service, because some site policies treat any physical interaction with running equipment as a planned-maintenance activity.

Method 3: NodeUtil Discovery

Echelon NodeUtil is a command-line tool that discovers LonWorks devices on a network interface and reports their Neuron IDs. Useful when the device is already commissioned and the original database is unavailable.

Steps:

1. Connect a USB network interface (U10 / U20) or PC-card interface (PCLTA-21) to the LonWorks segment.
2. Run NodeUtil and select the network interface.
3. Use the Find devices option to scan the segment. NodeUtil will report each responding device’s Neuron ID, Program ID, and address.
4. Match the displayed list against the panel labels or the device count expected on the trunk.

NodeUtil works even when the original LonMaker database is missing, so it is often the recovery method for retrofit jobs where the commissioning records were lost.

[!TIP] NodeUtil can also extract the XIF file from each discovered device. Once you have both the Neuron ID and the XIF in hand, you are ready to run the LonWorks XIF -> QuickServer Converter and produce a gateway configuration.

For the related discovery workflow, see Interpreting and Generating LonWorks XIF Files.

Method 4: Read From The Commissioning Database

If the site still has its original LonMaker or IzoT CT database, every commissioned device’s Neuron ID is recorded there.

Steps for LonMaker:

1. Open the LonMaker workspace for the site.
2. In the device tree, right-click the target device and choose Properties.
3. The Neuron ID appears under the Identifiers tab.

Steps for IzoT CT:

1. Open the IzoT Commissioning Tool against the site’s network database.
2. Navigate to the device in the network browser.
3. The Neuron ID is shown in the device’s properties panel.

This is the most reliable source when the database is intact, because it tells you which Neuron ID is currently associated with each named device — including replacements where the original label no longer matches.

Method 5: Protocol-Analyzer Capture

A LonWorks protocol analyzer (LonScanner, or a packet capture from a USB network interface) records the service-pin broadcasts and the source Neuron IDs of every transaction on the bus.

This is the fallback when the device label is illegible, the service pin is inaccessible, and no commissioning database survives. Capture a few minutes of network traffic with the device active, then filter the trace for messages originating from the suspected device’s logical address. The Neuron ID appears in the link-layer source field of those packets.

This method requires more LonWorks expertise than the other four. It is mostly useful in forensic situations or when verifying that two devices with the same label really do have different Neuron IDs.

Common Pitfalls

Pitfall	Symptom	Action
Label was photographed but transcribed wrong	Gateway will not bind despite a plausible-looking ID	Re-read the label or service-pin press; check for O vs 0 and B vs 8 transcription errors
Two devices share the same label	Inventory mismatch; both labels read the same	Service-pin press both devices individually to confirm distinct Neuron IDs
Database Neuron ID does not match the label	Recent device replacement was not recorded on the label	The database value is authoritative if the device responds to it on the bus; update the label
Neuron ID looks valid but device does not respond	Wrong physical segment, or device unpowered	Verify the FT-10 segment, power, and termination before re-collecting the ID
ID was entered with spaces or colons	Configuration tool rejects the value	Strip separators: 04:8B:C8:91:48:00 → 048BC8914800

What To Do With The Neuron ID

Once you have the Neuron ID, you can:

• Configure a Chipkin QuickServer gateway to bind to the device. The Neuron ID goes in the Nodes section’s Neuron_ID column.
• Generate the gateway configuration automatically from the device’s XIF using the LonWorks XIF -> QuickServer Converter — drop the XIF on the page, paste the Neuron ID into the highlighted field, and download the CSV.
• Add the device to a LonMaker or IzoT CT network database for ongoing commissioning.
• Bind variables on the device to peers on other LonWorks nodes.

Related Pages

• LonWorks
• LonWorks XIF Files
• LonWorks Troubleshooting Guide
• Interpreting and Generating LonWorks XIF Files
• LonWorks SNVT Reference and XIF Mapping Guide
• LonWorks XIF -> QuickServer Converter — interactive browser tool that consumes the Neuron ID
• QuickServer Platform Overview