BACnet/IP is the lingua franca of building automation. Modbus RTU/TCP is the workhorse on field devices, VFDs, pumps, meters. Knowing how they coexist (and where the gateways live) is half of BAS commissioning.
Four ideas to carry into the next specification conversation you have.
ASHRAE 135 / ISO 16484-5. Object-oriented data model. Multi-vendor by design. The default for any new BAS in 2026.
1979. Master/slave, register-based, ASCII-simple. Every VFD, meter, sensor speaks it. Not for system-wide architecture.
MS/TP for slow controllers on a daisy chain. BACnet/IP for IP networks. Modern installs are BACnet/IP.
A Modbus-to-BACnet gateway maps registers to BACnet objects. Cheap gateways fail under load. Spec Tridium Niagara, Cimetrics, or equivalent.
Where each protocol lives in the BAS architecture and what it talks to.
| Protocol | Physical · framing | Typical use |
|---|---|---|
| BACnet/IP | Ethernet · UDP 47808 | Supervisory · main BAS network |
| BACnet MS/TP | RS-485 · 9.6–115.2 kbps | Floor-level VAV controllers |
| BACnet/SC (secure) | TLS over WebSockets | Cloud-connected new builds |
| Modbus RTU | RS-485 · 9.6–115.2 kbps | VFDs · meters · pumps |
| Modbus TCP | Ethernet · TCP 502 | Newer field controllers |
| LonWorks | RS-485 / IP · LonTalk | Legacy European installs |
| MQTT | TCP/TLS · pub-sub | IoT / cloud BAS extensions |
| KNX/IP | Ethernet · UDP 3671 | Lighting + BAS hybrid |
Five reasons the protocol war effectively settled.
An AnalogInput object on a Honeywell controller looks identical on the wire to one on a Siemens controller. The BTL certification (BACnet Testing Laboratories) audits this. Spec BTL-listed controllers in your RFQ and you get true interchangeability.
Modbus has no built-in data model. Register 40001 might be "setpoint °C" on one device, "flow rate L/s" on another. You need vendor documentation to interpret. That looseness made it ubiquitous on field devices, every VFD maker implemented it, but it makes integration painful.
RS-485 multi-drop at 115 kbps was state-of-the-art in 1995. Today, BACnet/IP over a normal Cat6A drop runs at 1 Gbps. New BAS designs default to IP everywhere; MS/TP survives only where running cable to a remote VAV box would cost more than a serial converter.
Traditional BACnet sends unencrypted, unauthenticated UDP. A modern hospital or government building with BAS on a corporate LAN cannot accept that. BACnet/SC (Secure Connect, ASHRAE 135-2020) adds TLS and certificate authentication. Saudi government building tenders now mandate it.
BAS architecture only works if one party owns the data model, what objects exist, what they're named, how alarms route. Without that role, you get "works in isolation, fails on commissioning." Spec a dedicated integration coordinator from day one of design.
We design BACnet/IP backbones with Modbus and KNX gateways for legacy and lighting subsystems, and we own the integration model end-to-end.
Practical lighting know-how from NLC Academy. No spam, unsubscribe anytime.
By subscribing you agree to receive NLC emails.