Integrator's guide · 20 July 2026
Getting a Cylon Unitron Site onto Niagara
If you have been handed "get the Cylon site onto Niagara", here is what actually crosses over, and what you can leave alone.
“Get the Cylon site onto Niagara” – if you have been handed that, here is what actually crosses over, and what you can leave alone.
Cylon Unitron is a large installed base: years of sites still running daily that now need a modern, vendor-neutral head-end – usually Niagara – without disturbing controls that already work.
The good news: you front-end it, you don’t rebuild it.
One door per network
Each Unitron network reaches Niagara through one point: its UC32net communication controller, over TCP/IP (default port 4950). Behind it, the field controllers sit on an RS-485 trunk – you never connect to them directly. One UC32net per network, and a single Niagara Supervisor front-ends as many of them as the site has.
To open the door you need the site number and the UC32net address. Both live in the Unitron project or on the UC32net’s own display.
What maps across
- Field controllers and their points are discovered, not re-entered. Points are typed (analog or digital, hardware or software) and addressed 1-1024.
- Global schedules on the communication controller become Niagara Boolean Schedules.
- The field programming stays exactly where it is. No CXpro session, no downtime on the control logic.
What you are really buying
Time. The field investment stays, the front end becomes something your team already supports, and you stop depending on aging Cylon-specific tooling just to see the site. Twenty-year-old controllers that still hold setpoint aren’t technical debt. The software you need to run just to see them is.
Our Cylon Unitron driver for Tridium Niagara does exactly this: TCP/IP to the UC32net, device and point discovery, schedules included. If you are modernizing a Cylon estate, get in touch and we can talk through the specifics, or send your Niagara Host ID for a free trial.