BACnet

BACnet integration in Niagara is usually straightforward – until it is not. Software Pile handles both ends: standard BACnet/IP and MS/TP integration through Niagara’s native driver, and the awkward cases where devices expose non-conformant objects, proprietary properties, or firmware quirks that break discovery.

Standard BACnet Work

Device discovery and point mapping, alarm and history configuration, COV subscriptions tuned so the network is not flooded, priority-array behavior that matches how the building is actually operated, and BACnet export of Niagara points so third-party front ends can consume them.

When the Native Driver Is Not Enough

Some equipment speaks BACnet in name only. For proprietary properties, vendor-specific services, or segmentation problems, we extend integration at the Baja level: custom proxy points, tuned polling, and translation layers that make nonstandard devices behave like citizens of the station. Where a device needs a full custom driver, that is core work for us.

Scoping a BACnet Project

Useful things to have ready: device counts and models, network topology (IP vs MS/TP segments), your Niagara version, and whether the target is a Supervisor or JACE. A PICS statement for problem devices helps; a protocol capture helps more. Send what you have and we will tell you what the integration actually involves.