BACnet, Modbus, M-Bus and KNX explained - and when to use which
Most commercial buildings mix several communication protocols: BACnet for the main controls, Modbus for plant and drives, M-Bus for meters, KNX for lighting and blinds. Each was designed for a different job, and each has its own habits. This article explains them in plain terms, says when each one makes sense, and lists the questions worth asking before you start an integration.
BACnet
BACnet is the protocol designed specifically for building automation. It is published as ANSI/ASHRAE Standard 135 and as ISO 16484-5, and is maintained through ASHRAE.
- How it works: everything in a device is described as standard objects - analogue inputs, binary outputs, schedules, trend logs - each with standard properties such as present value, units and status. That makes BACnet devices largely self-describing.
- On the wire: BACnet/IP runs over ordinary Ethernet networks; BACnet MS/TP runs over RS-485 twisted pair, usually for field controllers.
- Good habits: devices announce themselves (Who-Is and I-Am), and values can be reported on change rather than polled constantly.
- Watch for: duplicate device instances and network numbers, MS/TP buses with too many devices or the wrong baud rate, and broadcast traffic across routed networks that needs BBMDs to be set up correctly.
BACnet is the natural choice for the main building controls and the head end. Products tested to the standard carry a BTL listing, which is worth asking for.
Modbus
Modbus is older and much simpler. It started in industrial control and is now found in almost every chiller, boiler, drive, UPS and meter. The specification is published by the Modbus Organization.
- How it works: a master asks a device for numbered registers or coils and the device answers. There is no built-in description of what a register means - you need the manufacturer's register map.
- On the wire: Modbus RTU is a serial protocol, so it isn't tied to one kind of cable. Most building installations run it over RS-485 two-wire, because one bus can link many devices. RS-232 also works, but it is point to point by design - one device per port, on a short cable - so several devices need a port each, a multidrop adapter or a converter to RS-485. Some kit uses four-wire RS-485/RS-422. Modbus TCP runs over Ethernet.
- Watch for: register numbering that starts at 0 in one document and 1 in another, 32-bit values split across two registers in an unexpected word order, scaling factors (a value of 215 that really means 21.5 °C), and only one master on an RTU bus.
Modbus is the right choice when that is what the plant offers - which is often. Get the register map for the exact model and firmware early, and test each point against the plant's own display.
M-Bus
M-Bus (Meter-Bus) is a European standard, EN 13757, designed for reading utility meters - heat, water, gas and electricity.
- How it works: a level converter or master powers the bus and reads each meter in turn. Meters can be addressed by a short primary address or a longer secondary address, usually based on the serial number.
- On the wire: a two-wire bus that also powers many meters; wireless M-Bus is common for water and heat meters.
- Watch for: reading too often - M-Bus is slow and many meters are battery powered - and meters whose primary addresses were never set, so every one answers at the same address.
Use M-Bus for metering, and read it at a sensible interval - every 15 minutes is plenty for most energy reporting.
KNX
KNX is an open standard (ISO/IEC 14543-3) managed by the KNX Association, widely used for lighting, blinds and room control, especially in Europe.
- How it works: devices talk to each other through group addresses - a switch sends to a group, and every light in that group responds. The system is designed and programmed with the ETS software.
- On the wire: KNX TP twisted pair is most common, with KNX IP routers and interfaces linking lines and connecting to other systems.
- Watch for: integrating without the ETS project file. Without it you are guessing which group address does what. Ask for the project file and the group address list before you start.
KNX suits lighting, shading and room control. The BMS usually reads and writes a selected set of group addresses through an IP interface or gateway rather than taking over the KNX system.
When to use which
- Main HVAC controls and the head end: BACnet.
- Packaged plant, drives, UPS and electrical equipment: whatever the equipment offers - usually Modbus, increasingly BACnet.
- Utility and sub-metering: M-Bus, or Modbus where the meters support it.
- Lighting, blinds and room controls: often KNX, integrated with the BMS at agreed points.
In practice the choice is usually made by the equipment rather than the integrator. The job is to make the protocols work together reliably.
Questions to ask before an integration
- Which protocol, which physical connection, and which settings - addresses, baud rates, IP ranges?
- Do we have the points list, register map or ETS project for the exact equipment and firmware?
- Which values are read, which are written, and how often?
- What happens when communications fail - and who gets the alarm?
- Who owns the network, and what are the IT security rules?
A word on security
BACnet/IP and Modbus TCP were designed long before today's security concerns and have little protection of their own. Keep building automation networks separate from general IT traffic, control remote access carefully, and follow the client's IT policy. BACnet Secure Connect (BACnet/SC), now part of the BACnet standard, adds encrypted, authenticated connections and is worth considering on new projects.
Further reading
The standards bodies - ASHRAE for BACnet, the Modbus Organization, and the KNX Association - publish introductions and specifications. CIBSE Guide H (building control systems) covers how protocols fit into a wider controls design.
To learn the basics with a quiz and certificate, our tecTraining courses include MS/TP and BACnet basics, and tecTools has MS/TP and IP planning calculators.