BACnet
An open communication protocol that lets HVAC equipment and building controls from different manufacturers exchange data and commands over a shared network.
What is BACnet?
BACnet is a communication protocol designed specifically for building control systems: heating, ventilation and air conditioning, but also lighting, access control and fire detection. Developed by ASHRAE, it is published as ANSI/ASHRAE Standard 135 and adopted internationally as ISO 16484-5. Its original purpose still holds: letting equipment from different manufacturers talk to each other without a proprietary gateway.
In practice, every connected device exposes its data as objects — a temperature, a run status, a setpoint, an alarm — that other devices on the network can read and, with the right permissions, write. That shared vocabulary is what separates BACnet from plain analog signal wiring.
BACnet/IP and MS/TP
Two transport variants dominate in commercial buildings. BACnet/IP runs on the building’s Ethernet network and suits supervisory controllers, operator workstations and major equipment. BACnet MS/TP runs on RS-485 twisted pair and serves the more numerous, simpler field devices. Most installations use both, linked by a BACnet router.
The choice matters in retrofits: pulling a new RS-485 segment through an existing building costs less than extending the IP infrastructure, but speed and the number of devices per segment are limited. Topology is decided before controllers are purchased, not after.
What the protocol changes in operation
A well-designed BACnet network makes visible what used to be invisible. You see the real boiler staging sequence, the actual position of a control valve rather than its theoretical setpoint, how a rooftop unit behaves in shoulder season. Drifting settings — a stuck economizer, a short-cycling boiler, a zone heating and cooling at once — show up in trend data before they turn into an occupant complaint or a high bill.
What to watch for
An open protocol is not enough on its own. A device can be “BACnet compatible” while exposing only a handful of points, which sharply limits what can be read or driven from the front end. The list of objects actually available therefore belongs in the specification, alongside the transport variant and the addressing scheme. The same caution applies to any integration or controls upgrade on an existing HVAC plant.