What is BACnet?
Part of the BACnet guide
BACnet is a communication standard for building automation, published by ASHRAE as Standard 135 and by ISO as ISO 16484-5. A BACnet device describes itself as a collection of objects (an analog input, a binary output, a schedule), each with a set of properties, and other devices use a fixed list of services to discover those objects, read them, write them and subscribe to their changes. Because the objects and services are defined by the standard and not by a vendor, a controller from one manufacturer can be read by a workstation from another.
This page belongs to the BACnet guide. The data model has its own page, BACnet objects and properties, and the two common transports are covered in BACnet/IP and BACnet MS/TP.
Where BACnet came from
An ASHRAE committee began work on a vendor-neutral building protocol in 1987, and the result was published as ANSI/ASHRAE Standard 135 in 1995. ISO adopted it in 2003. The standard is maintained continuously: addenda add object types, services and data links, and a consolidated edition appears every few years. A device declares which revision of the protocol it implements in the Protocol_Revision property of its Device object.
The layers of BACnet
BACnet separates what is said from how it travels. The standard defines three layers of its own and sits on top of several physical networks.
| Layer | What it defines | Where in the standard |
|---|---|---|
| Application | Objects, properties and the services that act on them | Clauses 12 to 16, 20 and 21 |
| Network | Network numbers and routing between BACnet networks | Clause 6 |
| Data link | BACnet/IP, MS/TP, Ethernet, ARCNET, point-to-point, LonTalk and others | Clauses 7 to 11, Annexes J and later |
The application layer is identical on every data link. A ReadProperty request for the present value of analog input 1 has the same bytes whether it crosses an Ethernet network or an RS-485 trunk; only the envelope around it changes. That is what lets a BACnet router pass messages between an IP network and a serial trunk without interpreting them.
Each BACnet network has a network number from 1 to 65534. The network layer header of a routed message carries the destination network number and the address of the device on that network, and the router that owns the network delivers it. Network number 65535 means a global broadcast to every network.
Clients, servers and services
BACnet has no fixed master. Any device may send a request (acting as a client) and any device may answer one (acting as a server), and many do both: a supervisory controller answers reads from a workstation while it reads the room controllers beneath it.
Requests come in two kinds. A confirmed service expects an answer: an acknowledgement carrying data, a simple acknowledgement, or an error. An unconfirmed service is sent without one and may be broadcast.
| Service | Kind | What it does |
|---|---|---|
| Who-Is | Unconfirmed | Asks devices to announce themselves, optionally within a range of device instances |
| I-Am | Unconfirmed | Announces a device: its instance, maximum APDU length, segmentation support and vendor identifier |
| Who-Has / I-Have | Unconfirmed | Finds the device that holds an object with a given name or identifier |
| ReadProperty | Confirmed | Reads one property of one object |
| ReadPropertyMultiple | Confirmed | Reads several properties of several objects in one request |
| WriteProperty | Confirmed | Writes one property, with an optional priority |
| SubscribeCOV | Confirmed | Asks a device to send a notification when a value changes |
| ConfirmedEventNotification | Confirmed | Delivers an alarm or event to its recipients |
When a server cannot do what was asked it returns an error with an error class and an error code, such as unknown-object, unknown-property or write-access-denied. A request the device cannot parse or does not implement gets a Reject or Abort instead.
How devices find each other
Every BACnet device contains exactly one Device object, and its instance number is the device’s identity on the whole internetwork. The instance is a 22-bit number, 0 to 4194302, and it has to be unique across every connected network, not only on the local segment.
Discovery works by broadcast. A client sends Who-Is, and each device that hears it answers with I-Am. The client records the address the I-Am came from and now knows how to reach that device instance. This step is called dynamic device binding.
Client Who-Is (broadcast) "Who is out there?"
Device A I-Am device,1001 max APDU 1476 vendor 5
Device B I-Am device,1002 max APDU 480 vendor 24
Client ReadProperty device,1001 Object_List "What do you contain?"
Device A ComplexACK analog-input,1 analog-input,2 binary-output,1 ...After the binding, the client reads the Object_List property of the Device object to learn what the device contains, then reads the properties of each object it is interested in.
Two devices with the same instance number break this. Both answer the same Who-Is, the client keeps whichever I-Am arrived last, and the device appears to change address, vendor and contents from one minute to the next. Assign instance numbers from a site-wide plan before the devices go on the network.
Reading a conformance statement
No device implements all of BACnet. The standard groups capabilities into BACnet Interoperability Building Blocks (BIBBs), each naming one service and one side of it. DS-RP-B means the device answers ReadProperty (data sharing, ReadProperty, B side, the server); DS-RP-A means it can send one. Device profiles bundle BIBBs into the roles found in a building:
| Profile | Name | Typical equipment |
|---|---|---|
| B-OWS | Operator Workstation | Front-end software |
| B-BC | Building Controller | Supervisory or plant controller |
| B-AAC | Advanced Application Controller | Air handler or central plant controller |
| B-ASC | Application Specific Controller | VAV box or fan coil controller |
| B-SA | Smart Actuator | Networked valve or damper actuator |
| B-SS | Smart Sensor | Networked sensor |
The manufacturer’s Protocol Implementation Conformance Statement (PICS) lists the profile, the BIBBs, the object types and the data links a product supports. Read it before assuming a feature exists. If you plan to subscribe to changes of value, the PICS needs to list DS-COV-B; if you plan to read many properties per request, look for DS-RPM-B.
What to check before connecting to a BACnet device
- The data link and its settings: the IP address and UDP port for BACnet/IP, or the baud rate and MAC address for MS/TP.
- The device instance, and that nothing else on the site uses it.
- The network number, if the device sits behind a router.
- The object list, with types and instance numbers, from the points schedule or from a discovery tool.
- For writes, which priority level the site assigns to your system. The objects and properties page explains the priority array.
Sites that mix building controllers with meters, drives and generator controllers usually have Modbus on the same job. BACnet vs Modbus explains how the two differ.
Reading BACnet with ControlCom
The ControlCom Edge Server, the on-site component of ControlCom Connect, has a BACnet client for each of the two common data links, added from the Add New Client dialog as BACnet IP or BACnet MSTP. The client takes the controller’s Device Instance, a Poll Interval (ms) (1000 by default) and a Timeout (seconds) (15 by default), then a list of objects, each mapped to a platform variable. The Edge Server’s local web interface includes a BACnet tool with a Send Who-Is button and a table of the devices that answer, showing device number, address, vendor, maximum APDU and segmentation, so the discovery step above can be done from the same machine that will do the polling.
The BACnet client documentation and the BACnet tool documentation list the fields. The platform overview shows where the values go next.
The Edge Server discovers BACnet devices on the building network and reads their objects into ControlCom Connect, next to the meters and generators the building management system does not cover.