What is BACnet?
Building Automation and Control NetworksReviewed

BACnet (Building Automation and Control Networks) is the open data communication protocol for building automation, published by ASHRAE as Standard 135 since 1995 and as ISO 16484-5. It defines how controllers for heating, cooling, lighting, access and metering describe their data as objects and exchange it, so equipment from different manufacturers can work in one building system.
- StandardANSI/ASHRAE 135, ISO 16484-5
- First published1995
- NetworksBACnet/IP, MS/TP, BACnet/SC
- BACnet/IP portUDP 47808 (0xBAC0)
01
What BACnet does
BACnet gives every controller in a building a common vocabulary. A zone temperature is an Analog Input object, a fan command a Binary Output, an occupancy schedule a Schedule object, and every object has standard properties such as Present_Value, Units and Status_Flags.
Because the vocabulary is standard, a supervisor can discover devices it has never seen, list their objects and read or command them without a custom driver per manufacturer.
Key functions
- Device and object discovery (Who-Is, I-Am)
- Read and write object properties
- Change-of-value subscriptions
- Schedules, calendars and trend logs
- Alarms and event notification
- Prioritized commands through a priority array
02
Why BACnet matters
BACnet is the reason a building can mix controllers from different vendors and still be run from one screen. Most commercial buildings in North America have BACnet somewhere, which makes it the main way outside software reaches HVAC and lighting.
For energy work it opens the largest flexible loads in a building. Reading BACnet points shows what the HVAC system is doing; writing them, carefully and at the right priority, lets software shift that load for tariffs or grid events.
03
How BACnet works
A BACnet device holds objects; each object has properties; clients use services to act on them. ReadProperty and WriteProperty read and change values, SubscribeCOV asks a device to report when a value changes, and Who-Is and I-Am find devices on the network.
Writable outputs have a priority array of 16 slots. Life-safety functions write at the highest priorities and normal operation lower down; the device acts on the highest-priority value present, and a writer releases its slot when it is done. BACnet runs over several networks: BACnet/IP on UDP, MS/TP on RS-485 serial wiring, and BACnet Secure Connect (BACnet/SC), which uses TLS over WebSockets.
01
Supervisor
Who-Is, ReadProperty
02
BACnet/IP or MS/TP
Routed through the building
03
Controller
Objects and properties
04
Equipment
AHU, VAV, chiller, lights
04
How BACnet feeds Voltra
Voltra discovers BACnet devices and points on a building network and maps HVAC, lighting and metering points into the same device model as chargers, solar and storage. It reads alongside the existing BMS, so building alarms and energy alarms sit in one list.
Learn more
BMS
BACnet discovery and building points next to energy assets.
Learn more
Voltra Edge
The on-site runtime that reaches local BACnet networks.
05
Frequently asked questions
BACnet/IP carries BACnet messages over Ethernet and IP networks using UDP, normally port 47808. MS/TP (master-slave/token-passing) carries them over RS-485 serial wiring, common for field controllers. Routers join the two.
BACnet Secure Connect, added to the standard in 2019 (ANSI/ASHRAE Addendum 135-2016bj), sends BACnet messages over TLS-secured WebSockets through hubs, with certificates for each device. It addresses the lack of security in BACnet/IP.
They solve different problems. BACnet has a rich object model, discovery and scheduling for building systems; Modbus is a minimal register protocol common in meters and electrical equipment. Many buildings use both.
The BACnet Testing Laboratories (BTL) test products against the standard. A BTL-listed device has passed tests for the BACnet functions it claims to support.



