Guide · 2026-11-01 · By DNT
BACnet, Modbus, KNX or MQTT: how we choose
The four solve different tasks. The right choice depends on what has to talk to what, and on who will run it afterwards.
The background is a map of DNT's six areas and the connections between them. Digital Products is connected to Software & AI. Software & AI is connected to Digital Products, Connected Systems, Automation & CTS and R&D. Connected Systems is connected to Software & AI, Automation & CTS and Hardware & Machines. Automation & CTS is connected to Software & AI, Connected Systems and Hardware & Machines. Hardware & Machines is connected to Connected Systems, Automation & CTS and R&D. R&D is connected to Software & AI and Hardware & Machines. This page belongs to Connected Systems and Automation & CTS.
- Automation
- CTS
- Connected Systems
The question often arrives as a choice between products, but these four are not rivals in one class. Each solves its own part of the task, and in many plants several of them work side by side. This is how we think when the choice has to be made.
Start with the task, not the protocol
Three questions settle most of it:
- What is already in the plant, and what does it speak?
- Do the devices only need reading, or must they work together?
- Who will run and fault-find this in ten years?
The last one is the most often forgotten. A solution nobody on site can read is an expensive one, however elegant it was on the day it was handed over.
BACnet: when the systems of a building must talk
BACnet was made for building automation. It describes not only how data is sent, but also what things are: a temperature, a setpoint, an alarm, a schedule. That is why it fits when equipment from several makers has to come together in one CTS. It is rarely worth it when a single device only has to be read.
Modbus: simple, and everywhere
Modbus dates from 1979 and is still everywhere. One side asks, the other answers with numbers from its registers. It is simple and dependable, and that is its strength. Its weakness is the same thing: a number means nothing in itself. What a register holds stands in the device's manual, and classic Modbus has neither encryption nor access control, so it belongs on a protected network.
KNX: the installation in the building
KNX controls lighting, blinds, heating and ventilation in homes and buildings, with components from many makers on one bus. Control is spread out in the devices, so the whole does not hang on one central unit. It is at home in rooms and installations. Fast, time-critical regulation of a process plant belongs in a PLC or a dedicated controller instead.
MQTT: when data has to leave the plant
MQTT is a different kind of thing. It is a light way of moving messages: devices publish to a broker, and whoever needs the data subscribes. It suits many devices sending measurements to software, often over unstable connections, and the receivers need not know each other. The standard says nothing about what the numbers mean, so that has to be agreed in the project.
Often the answer is several at once
A plant can easily have Modbus down to the devices, BACnet up to the CTS and MQTT out to a data platform, with the control itself in a PLC. Then the skill lies less in choosing a protocol and more in making the transitions between them dependable.
We use all four often, but it always depends on the project. We are married to none of them, and we will say so when one of them does not make sense.
Related
Automation & CTSConnected Systems
Technology Index
- FREQUENTLY USED · ProtocolBACnetAn open protocol for building automation and control networks.
- FREQUENTLY USED · ProtocolModbusA simple, widely used protocol for reading and writing values in controllers, meters and drives.
- FREQUENTLY USED · ProtocolKNXAn open standard for home and building control.
- FREQUENTLY USED · ProtocolMQTTA light publish/subscribe protocol for sending measurements and events between devices and systems.