BACnet protocol: a working guide to objects, BACnet/IP and MS/TP

Catalin NegruPublished 4 min read

The BACnet protocol is the standard way building equipment exchanges data: a chiller, an air handler or a room controller presents its points as objects with named properties, and any other BACnet device can discover those objects, read them and command them. ASHRAE publishes it as Standard 135 and ISO adopted it as ISO 16484-5. The name stands for Building Automation and Control networks.

This guide covers what a BACnet device exposes, what the bytes on the wire mean on Ethernet and on RS-485, and which settings have to agree before a read succeeds. The protocol facts follow ANSI/ASHRAE Standard 135: Clause 9 for MS/TP, Clause 12 for the object types, Annex J for BACnet/IP.

Where the BACnet protocol is found

BACnet is the language of the building management system. Chillers, boilers, air handling units, variable air volume boxes, rooftop units and the supervisory controllers above them publish temperatures, setpoints, valve positions, fan status and alarms as BACnet objects. Hospitals, campuses, office towers and data centers run it across thousands of points, and equipment from different manufacturers shares one network because the object model is the same for all of them.

Two data links carry most of the traffic. BACnet/IP runs on the building’s Ethernet network over UDP, usually between supervisory controllers, workstations and larger plant. BACnet MS/TP runs on a daisy-chained RS-485 pair and connects the small controllers on each floor. A BACnet router joins the two, so a workstation on the IP side can read a room controller on a serial trunk without knowing how it is wired.

Electrical and mechanical equipment in the same plant room often speaks Modbus instead. The Modbus guide covers that side, and BACnet vs Modbus compares the two.

How the pages in this guide fit together

What is BACnet? explains the layers of the protocol, the client and server roles, how Who-Is and I-Am discover devices, and how to read a manufacturer’s conformance statement.

BACnet objects and properties is the data model reference: object types and their numbers, the property identifiers you read most, status flags, and the 16-level priority array that decides which write wins.

BACnet/IP covers the Ethernet variant: the four-byte BVLC header, a Who-Is and a ReadProperty exchange decoded byte by byte, UDP port 47808, and why discovery stops at an IP router until a BBMD is configured.

BACnet MS/TP covers the serial variant: the frame layout and its two CRCs, how the token moves between master nodes, what Max Master and Max Info Frames do, and the RS-485 wiring rules.

BACnet vs Modbus puts the two protocols side by side, from the data model to commissioning effort, and describes what a gateway between them does.

The problems that take the most time

Most BACnet faults fall into a short list, and each has a recognizable signature.

SymptomUsual causeCovered in
Who-Is finds devices on one subnet onlyBroadcasts do not cross IP routers without a BBMDBACnet/IP
Two devices alternate under one device numberDuplicate device instance on the internetworkWhat is BACnet?
A write is accepted but the output does not changeA higher priority slot in the priority array holds the valueBACnet objects and properties
One controller on a serial trunk never answersMAC address above Max Master, duplicate MAC or wrong baud rateBACnet MS/TP
A value reads correctly but is flagged as badThe fault or out-of-service bit in Status_FlagsBACnet objects and properties

Reading BACnet with ControlCom

ControlCom Connect is a hosted platform, so it does not talk to building controllers itself. The on-site component, the ControlCom Edge Server, does. Its BACnet client connects to a controller over BACnet/IP or BACnet MS/TP and reads object properties into platform variables. Each client is configured from the platform: the controller’s address and Device Instance, a Poll Interval, and one entry per object with its Object Type, Instance Number and Property Identifier, mapped to a variable. The Edge Server applies a saved configuration on its next restart.

The BACnet client documentation  lists every field. The Edge Server’s local web interface also has a BACnet tool  that sends Who-Is and shows each discovered device with its objects and properties, which is how you find the instance numbers to configure. The page for facility managers describes what the data is used for once it arrives, and the healthcare page covers the hospital plant room case.

The Edge Server reads BACnet/IP and MS/TP controllers on site and maps each object to a variable in ControlCom Connect, where it can be trended, alarmed on and reported.

In this guide

  1. 1What is BACnet?What BACnet is and how it works: the layers of ASHRAE 135, client and server roles, Who-Is and I-Am discovery, device instances and conformance statements.
  2. 2BACnet objects and properties: types, identifiers and the priority arrayBACnet objects and properties explained: object types and identifiers, Present_Value and Status_Flags, property numbers, and the 16-level priority array.
  3. 3BACnet/IP: frame format, UDP port 47808, BBMDs and routingBACnet/IP explained byte by byte: the BVLC header, a decoded Who-Is and ReadProperty, UDP port 47808, BBMDs, foreign devices and routed addresses.
  4. 4BACnet MS/TP: frame format, token passing and RS-485 wiringBACnet MS/TP (MSTP) explained: frame format and CRCs, how the token passes between masters, Max Master, Max Info Frames, baud rates and RS-485 wiring.
  5. 5BACnet vs Modbus: differences, gateways and when to use eachBACnet vs Modbus compared: objects against registers, discovery, data types, command priority, transports and wiring, and gateways between the two.