LonWorks

LonWorks is still in thousands of buildings – and integrating it into a modern Niagara installation is a specialty that gets rarer every year. Software Pile brings Lon devices into N4 stations so legacy field networks keep working alongside newer BACnet and IP systems.

LonWorks Integration Work

  • LonMark and legacy Lon device integration through Niagara’s Lon driver
  • Network variable (SNVT) mapping into typed Niagara points with proper units
  • Mixed-network installations: Lon field devices under Niagara alongside BACnet and Modbus
  • Migration planning where aging Lon infrastructure is being phased toward newer protocols without a rip-and-replace

Keeping Legacy Networks Useful

Replacing a working Lon network is expensive and disruptive. More often the right move is integration: bring Lon into Niagara now, modernize the front end and reporting, and phase field devices over time. We plan that path so nothing goes dark mid-transition.

Tell us about your Lon devices and your Niagara version. We will scope integration and, if you want it, a migration path.

What Is LonWorks?

LonWorks is a control networking technology, originally from Echelon, that was widely deployed in building automation from the 1990s onward. It uses the LonTalk protocol and defines standard data types so devices from different manufacturers can interoperate on the same network. A great deal of installed HVAC, lighting and access equipment still runs on it.

It is no longer what new installations are specified with — that is generally BACnet — but “legacy” here means “still running the building”, not “switched off”.

What Is a SNVT?

A SNVT (Standard Network Variable Type, usually pronounced “sniv-it”) is a defined data type used to exchange values between LonWorks devices — a temperature, a setpoint, a switch state — with agreed units and scaling. Standardising the types is what allows devices from different vendors to understand each other.

When integrating a LonWorks network into Niagara, mapping SNVTs correctly to Niagara points is most of the work, and getting units or scaling wrong is the most common source of values that look plausible but are not.

Is LonWorks Obsolete?

New specification has largely moved to BACnet, and the supply of new LonWorks devices has narrowed considerably. But a large installed base remains in service, and ripping out working field devices is rarely justifiable on its own.

The realistic position for most owners is a mixed estate: LonWorks equipment that still does its job, newer BACnet equipment alongside it, and a need for a single coherent view across both. That is precisely the problem Niagara was built to solve.

How Does LonWorks Integrate with Niagara?

Niagara acts as the integration layer, presenting LonWorks devices as station points alongside everything else, so graphics, schedules, alarms, histories and reports work uniformly regardless of what protocol a value arrived on. The engineering work is in the details:

  • Mapping SNVTs to Niagara points with correct units, scaling and enumerations.
  • Handling device addressing and network management on the Lon side.
  • Deciding what is polled and how often — over-polling a legacy network degrades it.
  • Dealing with vendor-specific device profiles that go beyond the standard types.
  • Making offline and fault behaviour explicit, so a dead device reads as a fault rather than a stale value.

Planning a Migration Away from LonWorks

Where replacement is genuinely warranted — unobtainable spares, a major refurbishment, or devices that no longer meet requirements — the sensible pattern is gradual. Niagara can front both the old and new networks simultaneously, so equipment is replaced in phases as budget and access allow, without a single disruptive cutover and without the graphics, reports and alarms changing underneath the operators each time.

That also lets you avoid the trap of replacing working equipment first because it is easy to reach, rather than replacing the equipment that is actually causing problems.

Related services: BAS and protocol integration services · custom driver development.