Siemens Desigo PX Driver for Tridium Niagara

The Desigo PX driver lets Tridium Niagara take over the front-end of a Siemens Desigo PX installation without replacing the field hardware. Existing PX automation stations continue running their HVAC, lighting, and safety logic; Niagara handles visualisation, alarming, scheduling, history, analytics, and multi-vendor integration above them.

Most Desigo PX deployments use BACnet over LonTalk – BACnet objects and services transported across a LonWorks FTT-10 twisted-pair backbone. The combination falls between Niagara’s stock drivers: the BACnet driver expects IP or MS/TP, while the LON driver expects native LonWorks SNVTs rather than the BACnet stack on top. A standard Niagara LON option card provides the physical connection; the Desigo PX driver handles BACnet over LonTalk on top, so each PX object discovers as a fully self-describing BACnet object with name, status, present value, engineering units, and alarm state.

Discovery walks the LonWorks network and imports the controller hierarchy, points, schedules, and alarm objects with their original metadata intact. Standard BACnet object types map directly into Niagara: AnalogInput, AnalogOutput, AnalogValue, BinaryInput, BinaryOutput, BinaryValue, MultistateValue, Schedule, Calendar, and Notification Class. Engineering unit codes, COV increments, and out-of-service flags carry across, so a temperature point in a PXC discovers in Niagara as a typed AnalogValue in degC rather than a raw float. BACnet priority arrays survive end-to-end – a manual override written from a Niagara graphic at priority 8 coexists with control logic running on the PXC at priority 16 without either side accidentally winning.

Both polling and change-of-value subscription modes are supported, schedules and calendars from the PX controllers integrate directly into Niagara’s schedule service, alarms can be received and acknowledged from Niagara, and time synchronisation keeps the Desigo network aligned with the JACE clock. Unit facets and status flags carry through, so Niagara graphics show the same engineering values operators see on the original Desigo front-end.

The retrofit case is typical: a site has dozens to hundreds of PX controllers running reliably, no business case for replacing them, but the original Siemens Insight or earlier Desigo Web supervisor is end-of-life. The driver lets Niagara take over only the supervisory layer.

Most Insight migrations happen gradually rather than as a single weekend cutover. A new JACE can come online, discover a subset of the PXC controllers, and run alongside the existing Insight server while operators verify the Niagara graphics match the old ones zone by zone. Both supervisors share the LonWorks network during the changeover, with time synchronisation keeping trend timestamps consistent across the transition. Once a zone is validated, more controllers move under Niagara, and the Insight server is decommissioned on the operator’s schedule rather than the project’s deadline.

Desigo PX is Siemens’ European field-controller line. For US deployments built on the Apogee family, the Apogee P1 (FLN) and Apogee P2 (ALN) drivers cover the equivalent layer. On modern Siemens sites where the customer has standardised on Desigo CC as the unified supervisor across Desigo and Apogee, the Desigo CC driver talks to that platform directly through its REST API. For Siemens industrial PLCs running alongside the BMS, the Simatic S7 driver connects S7-1200, S7-1500, and earlier families.