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.

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.

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.

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.

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

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

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.

More articles from 3EC

3EC logo