
What is LonWorks? LonTalk, FT-10, SNVTs and practical commissioning
LonWorks is a control-networking platform that lets sensors, controllers and actuators exchange information. It is particularly familiar in building automation, including heating, ventilation, air conditioning and lighting. LON stands for Local Operating Network. The name describes more than a cable or a particular processor: a working installation also needs compatible device interfaces, engineering tools and a defined control application. [1]
This guide places LonWorks within industrial communication and focuses on the TP/FT-10 channel often encountered in installed systems. Keep three acceptance checks separate: discovering a device, receiving the right information, and making the equipment respond correctly. Passing the first does not establish the other two.
On this page: Names and standards · SNVTs and binding · Wiring and termination · Commissioning · Temperature example · Troubleshooting · Related reading
LonWorks, LonTalk, Neuron and LonMark: what is the difference?
LonWorks is the platform name; LonTalk is the established protocol name. The Control Network Protocol specified in the ISO/IEC 14908 series provides its standards framework. Neuron refers to the processor/core family associated with traditional implementations, not a different name for the protocol. LonMark also lists implementations for other hardware and software environments, so one particular Neuron chip should not be treated as mandatory for every LON device. [2] [20]
LonMark addresses interoperability through standard data types, functional profiles and certification. A profile may contain both mandatory and optional features. Two devices carrying a LonWorks label therefore need not be interchangeable in every application. Nor is a supplier’s statement that a product is compatible the same as evidence of LonMark certification. [3] [4]
ISO/IEC 14908-1 covers the protocol from the data-link layer through the application layer. Part 2 addresses twisted-pair communication, while Part 4 covers IP transport. When reading a device’s standards references, check the particular part, physical medium and implemented features. A protocol reference alone does not certify an entire installation. [2] [8] [15] [21]
How does a LonWorks network operate?
In a distributed application, one device can supply a measurement directly to another device that uses it for control. Every exchange does not have to pass through a central computer. However, the protocol accommodates different communication arrangements; saying that a LON system never uses a central controller would also be misleading. A building-management system or SCADA system may provide schedules, supervision and records. Which local functions survive its loss depends on the application and its data dependencies. [1] [2]
A pressure sensor used in a LonWorks installation is not necessarily a native LON device. For example, a transmitter with a 4–20 mA or 0–10 V output could feed a suitable controller input, with that controller publishing the measurement on the network. In this illustrative arrangement, the sensor range, input scaling and network data type all need to agree. It is not a claim that an ordinary analog transmitter includes a LonWorks interface.
What do SNVTs, SCPTs and binding actually do?
A network variable, or NV, exposes application data to the network. The prefixes nvo and nvi conventionally indicate outputs and inputs. A Standard Network Variable Type, or SNVT, defines how the value is represented and interpreted. A temperature, a pressure and a switch state are not interchangeable simply because each can contain a number. [3]
Binding creates a logical connection from an output network variable to one or more compatible inputs. Installing the cable does not establish that relationship by itself. A Standard Configuration Property Type, or SCPT, defines a standard type for configuration data. Manufacturer-specific types may also require the appropriate resource files in the engineering tool. [3] [11]
A change threshold, a minimum send interval and a maximum update interval serve different purposes. A threshold can reduce traffic caused by small fluctuations. A periodic update, often described as a heartbeat, can help establish that the source is still active. The receiving application still needs an explicit timeout and a policy for stale data. There is no single interval that is correct for every device and process. [11]
How are a Neuron ID, a network address and an XIF file different?
The 48-bit Neuron ID identifies a traditional LON device. It is distinct from its configured domain/subnet/node addressing. A Program ID identifies the application interface. When replacing a device, reusing its plant label or logical address does not prove that the replacement exposes the same application data. [9] [10]
An XIF file describes the device’s network-visible interface; it is not its firmware or control program. Match it to the device application, Program ID and required resource files. Obtaining an XIF does not reconstruct a lost network project, its bindings or its configuration. Keep the engineering project and configuration backups as well as the interface files. [10]
FT-10 wiring: speed, distance and termination
TP/FT-10 denotes a free-topology twisted-pair channel running at 78.125 kbit/s. That is a physical-channel rate, not a universal LonWorks speed or a guaranteed application update time. A two-wire connection does not make it equivalent to RS-485. An ordinary USB–RS-485 converter cannot replace a suitable LON interface. Check both the electrical interface and the protocol when identifying a communication port. [8]
On the specified FTT-10 interfaces, the LON data pair is polarity-insensitive. Do not extend that rule to power inputs or other terminals. Keep the data pair separate from supply connections: a two-wire interface is not an invitation to inject 24 V into it. Link Power is a specific supported device-and-power arrangement, not an assumption applicable to every FT device. [6] [5]
Free topology does not mean unrestricted cable length. The following classic FTT-10/FTT-10A examples show why cable selection matters. They are not common limits for every LON product. [7]
Belden 85102: a maximum 500 m between nodes and 500 m total cable. TIA Category 5: a maximum 250 m between nodes and 450 m total cable. A short individual branch does not establish that the sum of all branches is acceptable. [7]
The FTT-10A guide specifies 64 transceivers per electrical segment, not 64 devices across the entire network. Its doubly terminated bus using Belden 85102 allows 2,700 m with stubs no longer than 3 m. Do not transfer that bus-length figure to a free-topology layout. [5]
Termination: the FTT-10A arrangement uses one terminator for free topology, or terminators at both ends of a doubly terminated bus. Use the specified RC termination network, not a resistor selected from an unrelated RS-485 rule. Cable distance, segment loading and termination must be checked as one design. [5]
A practical commissioning sequence
The following is an engineering checklist, not a menu-by-menu procedure for a particular software package. Obtain authorization, use the device documentation and establish a safe test window before changing a working control network. [18]
Capture the existing system first. Back up the network project and record the software version, license arrangements, device models, application versions, XIFs and resource files. Mark the cable routes and terminators. Screenshots may help document an installation, but they are not a substitute for a project that can actually be restored.
Verify the channel and identify each device. Select the correct LON interface and check power, wiring and segment layout. Use discovery or the manufacturer’s documented service-pin procedure to associate the physical device with its project record. Do not mistake an identification function for a factory-reset command or a way to restart the whole network. [9]
Match the application before connecting the data. Load the appropriate device interface, configure addressing where required, and check input/output types, bindings and update settings. Confirm the device is in the required operating state. Begin with reads: verify engineering units, valid values and actual updates before enabling control writes. [10] [11]
Test the intended function under controlled conditions. Once authorized, issue a suitable command and verify real field feedback, not just a network response. Check the specified timeout, alarm and safe response to loss of communication without creating an uncontrolled outage. Save the accepted configuration and a change record. [18]
Worked example: communicating a temperature of 23.50 °C
LonMark’s Temperature Sensor functional profile 1040, version 1.0 defines an nvoHVACTemp output of type SNVT_temp_p. The illustrative room-control scenario below uses that published data type to show what correct interpretation looks like; it is not executable code for a particular controller. [12]
SNVT_temp_p is a two-byte signed temperature representation with a 0.01 °C resolution. A raw value of 2350 represents 23.50 °C. Raw 32767 is the invalid-value code, not a normal temperature. The 0.01 °C increment describes data resolution; it does not establish the sensor’s measurement accuracy. [13]
Illustrative signal path: nvoHVACTemp sensor output → compatible temperature input → local control logic → appropriate valve or fan command. Suppose the measured temperature is 23.50 °C and the setpoint is 22.00 °C. The controller’s PID or other control algorithm determines the response. The temperature must not be treated as a “23.5% fan speed” command.
An acceptance test should confirm that both ends show the same engineering value, that stale data is detected, and that an invalid input produces the intended quality indication or alarm. With a datalogger or supervisory system, track freshness and validity as well as the number itself. Measurement accuracy and calibration remain separate questions: accurate communication can faithfully transmit an inaccurate measurement.
A real equipment example: ABB ACH580 with FLON-01
ABB’s official LonWorks documentation identifies FLON-01 support for the ACH580 and ACH480. The ACH580-01-09A5-4 model listed on AVM illustrates the ACH580 drive family, but that listing does not prove a particular unit includes the adapter. Check the exact drive type, installed hardware, firmware and adapter documentation; do not turn an optional communication feature into an assumed standard inclusion. [14]
Start by identifying readable status and measurement points, then establish command ownership and the required control source. A command accepted on the network is not proof that the motor will run. Local/remote selection, run permission, faults and application interlocks are separate control conditions. Defeating a safety circuit is not an acceptable method of testing a communication link. [18]
Connecting LonWorks to BACnet, Modbus or an IP network
A router can carry LON traffic between suitable channels. A gateway maps application information between different protocols. Transport over an IP network using Ethernet does not automatically turn a LON variable into a BACnet object or Modbus register. The IP transport covered by ISO/IEC 14908-4 is a different task from translating application data. [15]
Documented examples include Control Solutions’ BB2-7020-NB for mapping LonWorks information to BACnet/IP objects and BB2-2011-NB for Modbus RTU integration. Review direction, units, scaling, structured fields and invalid or stale values for every mapped point. Some gateways support non-bound polling; do not assume that every integration uses the same binding method. [16] [17]
Troubleshooting: start with the symptom
These are diagnostic checks derived from the interface and application distinctions above, not proof of any particular fault. Record what has changed and narrow the affected area before disturbing a live network. Avoid indiscriminate cable removal or a mass reset of working devices.
No devices are visible. Check the selected network interface/channel, device supplies, connections and electrical segment. If only one device is missing, focus on its branch, identity and state before blaming the entire network.
The device is visible, but its values do not update. Verify the XIF/application match, variable direction, binding or polling method, and operating state. Discovery demonstrates a degree of communication; it does not demonstrate correct application-data delivery.
A value is wrong by a factor of 100, or makes no sense. Check the SNVT, the distinction between raw and engineering values, units and invalid codes. At a gateway, look for scaling that has accidentally been applied twice.
Communication deteriorates under load. Review wiring and termination, possible electrical interference, update rates and available error records together. A traffic problem will not necessarily be fixed by changing a cable; increasing a timeout will not remove a physical-layer fault.
The command appears, but the equipment does not respond. Separate communication from control authorization. Verify actual feedback, local/remote selection, alarms and interlocks without bypassing protective functions.
Maintenance, security and the case for a new installation
A non-IP field channel is not automatically secure. The gateway, service laptop and engineering software are also part of industrial cybersecurity. Plan authorized access, controlled remote connectivity, segmentation and recoverable backups together. Cybersecurity measures and the equipment’s functional-safety provisions address different requirements; neither substitutes for the other. [18]
As of 18 September 2026, LonMark’s published notice discusses Renesas leaving the LonWorks component business and points to alternative supply routes. That is not a declaration that every LON product is unsupported or the standard has become unusable. Its development resources also list different hardware/software implementations. The useful project question is whether the selected devices and engineering tools have a maintainable support path. [19] [20]
For an installed system, assess recoverable projects, software licenses, operating-system compatibility, spare parts and local engineering knowledge. For a new design, compare the actual control duties, integration needs and support commitments. The practical value lies in a documented, maintainable control system—not in the protocol name alone.
Related AVM guides
Start with the system: Industrial communication · Building automation · Communication-port terminology.
Integration paths: BACnet · Modbus guide · Ethernet fundamentals.
Measurement and operation: PID control · 0–10 V and 4–20 mA · Datalogger accuracy and calibration · Industrial cybersecurity.
References and technical documents
The standards links lead to the publisher’s public scope pages; manual links lead to the technical documents. Limits taken from legacy manuals apply to the hardware identified, not every LON installation. Web references were checked on 18 September 2026.
[1] LonMark International — LON Technology. Applications and the distributed-control model.
[2] ISO/IEC 14908-1:2012 — Control network protocol specification. Official scope: protocol layers and communication models. This link is to the public abstract, not the full standard.
[3] LonMark — Functional Profiles and Online Resource Files. SNVTs, SCPTs, functional profiles, and mandatory versus optional features.
[4] LonMark — Certification. The distinction between certification and a general compatibility claim.
[5] Echelon — FTT-10A Free Topology Transceiver User’s Guide, 078-0156-01G. Chapter 4, printed pp. 4-4–4-6 (PDF pp. 32–34): segment loading, distances, and termination.
[6] Johnson Controls — FX Supervisory Controller LON Card: Wiring. Two-wire, polarity-insensitive LON connection on the specified FTT-10 interface card.
[7] Continental Control Systems — LONWORKS FTT-10 Cables. Cable-dependent node-to-node and total-length limits for free topology.
[8] ISO/IEC 14908-2:2012 — Twisted pair communication. Official scope: the 78.125 kbit/s free-topology twisted-pair physical channel.
[9] Echelon — Introduction to the LONWORKS Platform, Revision 2. Neuron IDs, logical addressing, network variables, and network installation concepts.
[10] LonMark — LONMARK Device Interface (XIF) File Reference Guide, Rev. 4.501. December 2020; Introduction and Device Information: the network-visible interface and Program ID.
[11] LonMark — Application-Layer Interoperability Guidelines, Version 3.4. Network variables, connections, and configuration properties governing update behavior.
[12] LonMark — Temperature Sensor Functional Profile 1040, Version 1.0. A documented profile example: the nvoHVACTemp output of type SNVT_temp_p.
[13] LonMark — SNVT_temp_p, Standard Network Variable Type 105. Size, signed representation, 0.01 °C scaling, and the invalid-value code.
[14] ABB — LonWorks for drives. ACH580 and ACH480 support for the FLON-01 adapter. This does not establish what is included with a particular drive purchase.
[15] ISO/IEC 14908-4:2012 — IP communication. Official scope: transporting control-network packets over IP.
[16] Control Solutions — Babel Buster BB2-7020-NB, LonWorks to BACnet/IP. A gateway implementation: mapping SNVT data to BACnet objects, with non-bound polling.
[17] Control Solutions — Babel Buster BB2-2011-NB, LonWorks to Modbus RTU. A gateway implementation linking network variables with Modbus data.
[18] NIST SP 800-82 Rev. 3 — Guide to Operational Technology (OT) Security. The 2023 OT security guide, including building automation, availability, and safety considerations.
[19] LonMark International — LonWorks component-supply notice. Renesas component-supply notice observed on 18 September 2026; homepage content may change.
[20] LonMark — Development Resources. Alternative hardware and software implementations, rather than assuming one mandatory Neuron component.
[21] LonMark — LON Standards. The relationship between the ISO/IEC 14908, EN 14908, and ANSI/CTA references.