BACnet vs Modbus: differences, gateways and when to use each
Part of the BACnet guide
BACnet and Modbus both move values between controllers, but they describe those values differently. Modbus exposes numbered 16-bit registers and single-bit coils, and the meaning of each one lives in the manufacturer’s manual. BACnet exposes objects that carry their own name, units and status and can be discovered on the live network. In the BACnet vs Modbus decision the equipment usually decides: building controllers speak BACnet, meters, drives and generator controllers speak Modbus, and most sites end up reading both.
This page is part of the BACnet guide. The Modbus side has its own guide at /learn/modbus, and the BACnet data model is in BACnet objects and properties.
BACnet vs Modbus at a glance
| BACnet | Modbus | |
|---|---|---|
| Published by | ASHRAE, Standard 135; ISO 16484-5 | Modbus Organization |
| First published | 1995 | 1979 |
| Home ground | Building automation: HVAC, plant, room control | Industrial devices: PLCs, drives, meters, generators |
| Data model | Objects with properties | Four tables of coils and registers |
| A value is addressed by | Device instance, object type, object instance, property | Unit ID, table, register address |
| Data types | Typed: REAL, enumerated, unsigned, character string and more | 16-bit words and single bits; anything larger is by convention |
| Name and units | Carried by the object (Object_Name, Units) | In the manual only |
| Value health | Status_Flags and Reliability on each object | None in the protocol |
| Discovery | Who-Is and I-Am, then read the Object_List | None; the register map has to be known |
| Roles | Any device may be client and server | One client polls servers |
| Unsolicited data | Change of value subscriptions, alarm and event notifications | None; polling only |
| Write arbitration | 16-level priority array on commandable objects | Last write wins |
| Ethernet transport | BACnet/IP on UDP port 47808 | Modbus TCP on TCP port 502 |
| Serial transport | MS/TP on RS-485, token passing | RTU on RS-485, one client polls |
| Serial addresses | Masters 0 to 127, slaves 128 to 254 | 1 to 247 |
| Built-in security | None on BACnet/IP and MS/TP; BACnet/SC adds TLS | None |
The same point in both protocols
Take a supply air temperature of 72.0 degrees.
In Modbus, the manual says the value is in holding register 40108 as a signed integer in tenths of a degree. The client reads the register and gets a number:
Request: read holding registers, address 0x006B, quantity 1
Response: 0x02D0 (720)Nothing in the response says it is a temperature, that it is scaled by ten, or that the sensor is healthy. If the manual is wrong about the address by one, the client reads a different, equally plausible number. The Modbus protocol page covers the off-by-one trap and the byte order problem for 32-bit values.
In BACnet, the same point is analog input 3. The client can ask for several properties at once:
Request: ReadPropertyMultiple analog-input,3
Present_Value, Object_Name, Units, Status_Flags
Response: Present_Value 72.0 (REAL)
Object_Name "AHU-1 Supply Air Temp"
Units degrees-fahrenheit
Status_Flags {false, false, false, false}The value arrives as a float in engineering units, the name and units come from the device, and the four status flags say that the point is not in alarm, not in fault, not overridden and not out of service. No manual was needed to find it, because the Device object’s Object_List names every object the controller holds.
What the richer model costs
BACnet does more per point, and it asks more of the device and of the person setting it up.
- More to configure. A BACnet device needs a unique device instance across the whole site, and depending on the data link a network number, a BBMD or foreign device registration, or an MS/TP address and Max_Master. A Modbus device needs an address and, on serial, matching baud rate and parity.
- More bytes. A BACnet/IP ReadProperty for one value is a 17-byte request and a 23-byte response in the UDP payload. A Modbus TCP read of one register is 12 bytes out and 11 back. On a slow serial trunk the difference adds up, and MS/TP also spends time passing the token.
- More variation between devices. BACnet devices implement different subsets of the standard, declared in the manufacturer’s conformance statement (PICS). Whether a device supports ReadPropertyMultiple or change of value notifications has to be checked. Nearly every Modbus device supports the same handful of read and write function codes, although the register layout is different every time.
- Harder to implement. A Modbus RTU client fits in a page of code. A BACnet stack has tagged encoding, segmentation, routing and a state machine per data link.
Modbus puts the work into the integration instead: someone has to obtain the register map, enter each address, data type, scale and byte order by hand, and test each value against the equipment’s display.
Commands and overrides
A Modbus write replaces the value in the register. If a PLC program and a supervisory system both write to the same register, each overwrites the other, and nothing in the protocol records who wrote last.
A BACnet write to a commandable object goes into one of 16 priority slots, and the object follows the occupied slot with the lowest number. An operator override at priority 8 holds against a schedule writing at 16, and when the operator releases the override by writing NULL, the schedule’s value takes effect again without being re-sent. Any external system that writes to a building controller needs an agreed priority level and has to relinquish what it commands.
Gateways between BACnet and Modbus
Protocol gateways translate in both directions, and they are common wherever a chiller, generator or power meter with a Modbus port has to appear on a BACnet building management system.
A gateway that presents Modbus registers as BACnet objects holds a mapping table: this holding register, with this data type and scale, becomes this analog input with these units and this name. The discovery that BACnet promises works only as far as that table has been filled in, and a wrong entry produces a well-formed BACnet object with a wrong value. Three things to check on such a gateway:
- Staleness. The gateway polls Modbus on its own schedule, so the BACnet Present_Value is as old as the last successful poll. Find out how the gateway reports a Modbus device that has stopped answering; the right behaviour is to set the object’s Reliability and the
faultstatus flag, and not every gateway does. - Scale and units. The scale factor lives in the gateway’s table, not in either protocol.
- Writes. A BACnet write at any priority becomes a plain Modbus write on the other side, so the priority array ends at the gateway.
In the other direction, a gateway that presents BACnet objects as Modbus registers discards names, units and status unless they are mapped to registers of their own.
BACnet vs Modbus: when to use each
Choose by the equipment and by who else needs the data.
Use BACnet when the device is part of the building’s HVAC or plant control, when a building management system has to discover and command it, when several systems write to the same outputs, or when the specification for the building calls for it, as many do.
Use Modbus when the device is a power meter, a variable frequency drive, a generator or transfer switch controller, a PLC, or a sensor with an RS-485 port, and when the reader is one supervisory system. The Modbus RTU and Modbus TCP pages cover the two transports.
When a device offers both, as many chillers, boilers and drives do through an option card, BACnet saves engineering time if the reader can discover objects, and Modbus is the simpler choice if the reader is a PLC with a fixed register map. A monitoring system that reads directly in each device’s own protocol avoids the gateway and its mapping table altogether.
On the serial side, do not mix the two on one cable. BACnet MS/TP and Modbus RTU both use RS-485, but a token-passing ring and a polled bus cannot share a pair of wires.
Reading both with ControlCom
The ControlCom Edge Server, the on-site component of ControlCom Connect, lists both protocols in the same Add New Client dialog: BACnet IP and BACnet MSTP next to Modbus TCP and Modbus RTU. A BACnet client is configured with objects (an Object Type, an Instance Number and a Property Identifier), and a Modbus client with tags (an address scope, data type, address, scale and offset). Both map each value to a platform variable, so a chilled water temperature read over BACnet and a generator’s kW read over Modbus end up as the same kind of data in the platform.
The BACnet client documentation and the Modbus client documentation list the fields for each. The page for facility managers describes how a building team uses the combined data.
Building controllers on BACnet and meters and generators on Modbus are read by one Edge Server and land as variables in the same ControlCom Connect account.