What is Modbus? How It Works, Benefits, and Applications in Building Automation

Author: T. Graf | Date: August 14, 2026

Modbus is an open communication protocol for exchanging process data between automation devices. A client—such as a building management system—queries values or states. The addressed servers, such as sensors, transducers, or controllers, return the requested data or execute a write command.

The protocol was developed in 1979 by Modicon for industrial control systems. Today, Modbus is used in industrial and building automation because it allows devices from different manufacturers to connect via serial lines or Ethernet-based networks. Suitable wireless solutions can also integrate Modbus devices wirelessly into an automation system.

Modbus defines how requests are structured, how devices and data fields are addressed, and how measured values, states, or setpoints are read and written. The physical transmission path is separate from this. Therefore, Modbus can be used, for example, as Modbus RTU over RS-485 or as Modbus TCP over Ethernet.

Our Modbus Sensors
Back to blog

How does Modbus work?

Modbus operates on a request-response principle. The client initiates communication and sends its request to a specific server. The request includes, among other things, the desired function and the address of the required data range. The server processes the request and returns the requested data or a response confirming that the command has been executed.

In building automation, for example, the building management system can request a room temperature sensor to provide its current reading. The request is addressed to the correct device and the register documented in the device manual. The sensor responds with the stored value, which the building management system interprets based on the manufacturer’s documentation and uses for display or control.

  • Modbus is the protocol – not the line

    Modbus belongs to the application layer and describes communication between devices. The physical connection is separate from this. Modbus RTU is frequently transmitted over RS-485, whereas Modbus TCP uses Ethernet and TCP/IP. Therefore, the transmission path and the protocol must not be equated.

  • Client and Server Instead of Master and Slave

    The client initiates a request, and the addressed server responds. In older device documentation, the terms “master” and “slave” are still frequently used to describe this process. During the planning phase, each device or participant must also be uniquely addressed.

Advantages of Modbus

  • Openly documented

    Specifications and implementation guides are available from the Modbus Organization.

  • Serial or Ethernet

    Modbus RTU uses serial communication; Modbus TCP operates over TCP/IP networks.

  • Standardized functions

    Function codes define the reading and writing of bits and registers.

  • Cross-manufacturer

    Devices from different vendors can be integrated if the interface and data model are compatible.

  • Expandable in a planned manner

    Compatible devices can be added within a suitable network structure.

  • Devices interchangeable

    With compatible interfaces and register assignments, individual devices can be replaced.

  • Integrable into existing systems

    Modbus RTU and Modbus TCP can be integrated into existing automation systems.

  • Scalable according to system architecture

    Additional segments, repeaters or gateways enable the construction of larger systems.

Modbus registers and function codes

Registers are addressable data areas in a Modbus device. They can contain measured values, setpoints, operating states, or configuration parameters. The standard distinguishes individual bit values, known as coils and discrete inputs, as well as 16-bit input and holding registers.

The function code tells the server which operation is to be performed. Function code 03 reads holding registers, for example, and function code 04 reads input registers. Which registers and functions a device supports is specified in its Modbus documentation.

Register address, data type, scaling, unit, and byte order must be considered together. A stored raw value is only unambiguous once the device manual describes how it is to be interpreted. For 32-bit values, two consecutive 16-bit registers and a defined word order may also be required.

Contents

What is Modbus RTU? What is Modbus TCP? Modbus ASCII and wireless Modbus solutions Modbus in building automation Avoid common Modbus errors Wired Modbus sensors and measuring devices Modbus, Modbus-SD or W-Modbus? Conclusion: Select Modbus to match the infrastructure FAQ

What is Modbus RTU?

Modbus RTU is a binary-coded serial implementation of the Modbus protocol. In building automation, RS-485 is often used for this. Multiple devices can communicate along a properly planned bus line; each node requires a unique address.

For a working connection, the baud rate, parity, and stop bits must match on the devices involved. Cable routing, topology, and termination resistors also need to match the installation. Modbus RTU typically works asynchronously during serial transmission and separates messages using defined time intervals.

What is Modbus TCP?

Modbus TCP transmits Modbus messages over TCP/IP and is typically used in Ethernet-based automation networks. Devices are addressed via IP addresses. A unit ID can additionally identify a downstream participant, for example behind a gateway.

Modbus TCP makes it easier to integrate into existing IP infrastructures. However, classic Modbus TCP does not provide built-in encryption or strong authentication. Therefore, devices should not be reachable from the public Internet without protection. Network segmentation, firewalls, and secured remote access are part of a suitable security concept.

Modbus ASCII and wireless Modbus solutions

Modbus ASCII encodes data as ASCII characters. This makes telegrams easier to inspect during diagnostics, but compared with the binary RTU representation they require more characters for the same information. In new building automation projects, RTU and TCP are usually more relevant; ASCII is found mainly in existing or special system environments.

Modbus data can also be integrated via suitable wireless solutions and a gateway. However, such a solution is not automatically a separate transmission standard of the Modbus Organization. For compatibility, range and wireless planning, the specific system, the gateway and the supported devices are decisive.

Learn more about W-Modbus

Modbus in building automation

In building automation, Modbus connects field devices with controllers, automation stations, or the building management system. Sensors provide measured values digitally, enabling higher-level systems to monitor states, visualize values, and implement control strategies.

Typical measured variables include temperature, relative humidity, differential pressure, CO₂, VOC, fine dust, and air velocity. Setpoints, operating modes, and status messages can also be transmitted via dedicated registers.

Digital communication can reduce wiring and integration effort compared with the purely star-shaped transmission of individual analog signals. The specific benefit depends on topology, number of devices, cable runs, and system concept. Modbus does not automatically save energy; the protocol provides the data on the basis of which a suitable control strategy can operate more efficiently.

Discover wired Modbus sensors

Avoid common Modbus errors

Support for Modbus alone does not yet guarantee communication between two devices. Transmission mode, parameters, functions, and data mapping must match on both sides.

During commissioning, check in particular:

  • unique device addresses
  • baud rate, parity and stop bits
  • A/B connections according to the respective manufacturer documentation
  • bus topology, stub lines, and termination
  • register address and possible address offset
  • function code, data type, and scaling
  • byte and word order for multi-part values
  • network segmentation and access rights for Modbus TCP

An exception response or a communication status helps with diagnostics, but does not automatically identify the physical fault location. Power supply, cabling, termination, and parameter settings must continue to be checked systematically.

Wired Modbus sensors and measuring devices

View all

Modbus, Modbus-SD, or W-Modbus?

The classic S+S Modbus sensors are wired solutions with galvanic isolation. They are suitable for projects in which electrical isolation is part of the intended system design.

Modbus-SD is the cost-optimized wired product line for applications that do not require electrical isolation. The communication protocol remains Modbus RTU; the difference lies in the device design and the intended area of application.

W-Modbus is suitable for wireless retrofits and installations where bus lines should be avoided. The final selection depends on the electrical environment, existing infrastructure, cable routes, and project-specific requirements.

Request Technical Consultation

Conclusion: selecting the right Modbus option for the infrastructure

Modbus is an established protocol for exchanging process data in industrial and building automation. Modbus RTU is suitable for serial fieldbus structures, while Modbus TCP enables communication in Ethernet-based networks. Clear addresses, suitable communication parameters and correctly documented register mapping are crucial for reliable operation.

For product selection, S+S offers wired Modbus sensors, the cost-optimized Modbus SD series and wireless W-Modbus solutions. Which version is the right fit depends not only on the protocol, but also on the electrical environment and the installation concept.

Technical sources:

FAQ

What is the difference between Modbus RTU and Modbus TCP?

Modbus RTU transmits compact binary messages over a serial connection, often RS-485. Modbus TCP transports Modbus messages over Ethernet and TCP/IP. The basic functions and data areas are similar; network architecture, addressing, message framing, and commissioning differ.

Is Modbus a bus system or a protocol?

Modbus is primarily an application-layer communication protocol. It can be used over different transmission media. With Modbus RTU, RS-485 often forms the physical bus connection; with Modbus TCP, transmission takes place over an Ethernet and TCP/IP network.

What cable is required for Modbus RTU?

For Modbus RTU over RS-485, a suitable twisted-pair cable is typically used. Cable type, shielding, conductor cross-section, maximum length, and termination depend on baud rate, the noise environment, and manufacturer requirements. The installation instructions for the devices used and the current Serial-Line Implementation Guide are therefore authoritative.

Is Modbus TCP secure?

Classic Modbus TCP does not provide encryption or strong participant authentication by itself. It should therefore not be accessible unprotected from the public internet. Suitable measures include segmented networks, firewalls, secured remote access, and – if supported by the components – Modbus Security with TLS

What distinguishes Modbus, Modbus-SD and W-Modbus at S+S?

Classic S+S Modbus devices are hardwired and galvanically isolated. Modbus-SD also communicates by cable via Modbus RTU, but for cost-optimized applications it dispenses with galvanic isolation. W-Modbus integrates suitable sensors wirelessly into the automation infrastructure via a gateway.