Modbus RTU daisy chain with gateway, energy meter and heat pump over RS485
On this page

Modbus RTU is the serial variant of Modbus. A master polls the devices on an RS485 line one by one, and every message ends with a CRC-16 checksum. Modicon introduced the protocol in 1979, and it is still the first choice at the device level in HVAC, heat pumps, energy meters and refrigeration. Problems on site usually come from three places: the frame structure, the RS485 wiring and the difference between function codes and register types.

What is Modbus RTU exactly?

Modbus RTU is a serial variant of the Modbus protocol that sends binary frames over RS485 (or RS232) and uses CRC-16 for error detection. RTU stands for Remote Terminal Unit, a term that goes back to the PLC world where Modbus was introduced by Modicon in 1979. The application layer (function codes and register addresses) is identical to Modbus TCP and Modbus ASCII, only the transport differs.

According to the Modbus Application Protocol V1.1b3 specification, maintained by the Modbus Organization, RTU is the most common form of Modbus over a serial line. You recognise a Modbus RTU installation by three terminals on a connector block (A, B, GND). The devices sit in a daisy chain, with up to 32 of them on a single bus.

Modbus RTU sits inside virtually every new heat pump, energy meter and refrigeration controller. Higher layers like BACnet, KNX or OPC UA take over supervision. At the layer where you, as an installer, pull cable and make first contact, RTU remains the standard. For a broader explanation of Modbus itself, see What is Modbus?.

How a Modbus RTU frame is structured

A Modbus RTU frame always has five fields in this fixed order: slave address, function code, data, CRC, and then a silent interval of 3.5 character times. The order never changes; only the length of the data field varies per function code.

1 byteSlave address1 byteFunction codeN bytesData2 bytesCRC-163.5 charactersSilent intervalt = 0frame endnext frame
Fixed field order of a Modbus RTU frame. The silent interval marks the frame end, after which the bus is free for the next request.

The slave address is one byte with a value between 1 and 247. Address 0 is reserved for broadcast messages to which slaves do not reply. The function code tells the slave what the master wants to do, for example 0x03 to read holding registers. The data field carries the parameters of the request or response and is variable in length. The CRC-16 is a 2-byte checksum that the slave (and master) computes over all preceding bytes. It uses polynomial 0xA001 as defined in the Modbus over Serial Line Specification V1.02, section 2.5.1.2.

The silent interval of 3.5 character times is often overlooked on site. At baud rates up to 19200 baud the interval scales with the baud rate (at 9600 baud it is 3.65 ms), above 19200 baud it is fixed at 1.75 ms. Slaves use the interval to detect where one frame ends and the next begins. If your polling tool keeps the interval too short, you will see random timeout errors.

RS485 physical layer in practice

Every RS485 device exposes three terminals: A (non-inverting signal), B (inverting signal) and GND (common ground). A and B form the differential pair that carries the signal. GND gives all devices the same voltage reference.

ABGND
A
signal, non-inverting
B
signal, inverting
GND
common ground
RS485 terminal blockThe three connections every Modbus RTU bus starts with. A and B together form the differential pair.

In practice you see three classic mistakes. The first is A and B swapped, which most devices tolerate because some manufacturers label A and B opposite to the TIA-485-A convention. The second is GND forgotten, which works until devices sit on different mains phases and the voltage difference grows. The third is power cables run too close to the RS485 cable, which over a 50 m run can already inject enough noise to trigger CRC errors.

For a clean installation, separate ELV signal cables (RS485 included) from LV power cables by at least 200 mm parallel run distance, or route them through a dedicated trunking. Use shielded twisted-pair cable, ideally Belden 9841 or an equivalent Cat 5e, with ferrite cores on critical points. The relevant guidance comes from the LV installation standards aligned with IEC 60364-5-52 (separation of circuits).

Termination: 120 ohms at both ends

Place a 120 ohm termination resistor at each physical end of the daisy chain and none in the middle. That is the entire rule. If installers forget one terminator, reflections distort the signal and trigger CRC errors. If they fit three or four, the resistors pull in parallel below the line driver IC's minimum load and the signal collapses.

120 Ωbus startGatewaySlave01Slave02Slave03120 Ωbus end
120 ohm termination resistors belong at both physical ends of the daisy chain. The gateway happens to sit at the start here; that is not required, as long as it is not a midpoint.

Many gateways and some slaves have built-in 120 ohm termination via a DIP switch or jumper. Always check that termination is enabled at the right places and that it is not accidentally active in the middle of the bus.

Slave addresses, baud rate and parity

Every slave on the bus needs a unique slave address between 1 and 247. For energy meters you typically start at 1 and number sequentially; for heat pumps the address is usually set in the service menu or via DIP switches. The address travels in every RTU frame. Duplicate addresses cause immediate collisions, because two slaves answer at the same time.

The baud rate applies to the whole bus. Every device on the same physical RS485 line must use the same baud rate. Common choices are 9600, 19200 and 38400 baud. Standard projects often run at 9600 baud 8N1 because that combination is the most stable across a 200 to 1200 m daisy chain. Higher baud rates shorten the polling cycle but make the installation more sensitive to cable quality and reflections.

Parity is the second half of the 8N1 jargon. 8N1 means 8 data bits, no parity, 1 stop bit. The Modbus over Serial Line Specification also defines 8E1 (even parity, 1 stop bit) and 8O1 (odd parity, 1 stop bit). Some older devices require 8E1, so always check the datasheet before commissioning a bus.

Function codes and register types that matter

A function code tells the slave what the master wants to do. Of the 24 codes defined in the specification, in HVAC and refrigeration you mostly use seven.

FCNameUseWho uses it
01Read CoilsRead on/off relay stateRefrigeration, lighting
02Read Discrete InputsRead alarm and status contactsAlarm monitoring
03Read Holding RegistersRead setpoints and configDominant FC in HVAC
04Read Input RegistersRead measured valuesEnergy meters, PV
05Write Single CoilSwitch a relayManual control
06Write Single RegisterWrite a setpointSetpoint change
16Write Multiple RegistersWrite several registersBulk configuration

The four register types differ in access and in the Modicon prefix you often see in datasheets. Coils (0x prefix) are 1 bit read-write, discrete inputs (1x) are 1 bit read-only. Input registers (3x) are 16 bit read-only, holding registers (4x) are 16 bit read-write. In practice 80 percent of what you read sits in holding (4x) and input (3x) registers.

A 32-bit float spread across two 16-bit registers is common in energy meters. Always check in the datasheet whether the manufacturer sends high word first (big endian) or low word first (little endian). Eastron, Carlo Gavazzi and most European meters use big endian; some Asian brands do the opposite.

Worked example: read an input register with FC04

Suppose you read voltage L1 from an Eastron SDM630. The datasheet lists it as input register 30001, so that is function code 04 at register address 0x0000, two registers because the value is a 32-bit float. The request is exactly 8 bytes long.

ByteContentMeaning
00x01slave address 1
10x04function code 04 (read input registers)
2-30x00 0x00start register address
4-50x00 0x02number of registers (2)
6-70x71 0xCBCRC-16

The slave responds with 9 bytes: slave address (1B), function code (1B), byte count (1B = 4), 4 data bytes (the float), and 2 bytes CRC. At 9600 baud the full cycle takes around 20 ms. With a 1-second polling interval you can poll over 30 slaves in sequence without overlap. The SDM630 is also available as a ready-made template in the template library.

Troubleshooting: five common RTU problems

When a bus does not behave, walk through these five in order before looking deeper.

SymptomProbable causeFix
No response from one specific deviceWrong or duplicated slave addressCheck DIP switches or menu setting; a logger reveals bus traffic
Random CRC errors across the whole busTermination forgotten or doubledWith power off, measure between A and B; should read 60 ohms (two 120 ohm in parallel)
Works on one device, fails with severalA and B swapped on a tapInspect every connection, A to A and B to B
Random timeouts at high pollingSilent interval too shortIncrease polling interval to at least 2x frame time plus 3.5 character times
Works during the day, fails at nightPower cable couples into RS485Separate cables by at least 200 mm or run them in dedicated trunking

For stubborn problems a serial protocol logger like a USB-RS485 adapter with Wireshark or a Modbus scanner is invaluable. It shows byte-by-byte what request the master sends and what response (or lack of one) comes back.

Modbus RTU and the EPBD building automation duty

The EPBD recast (EU 2024/1275), Article 13, requires building automation and control systems (BACS) in non-residential buildings above 290 kW effective rated output. By 31 December 2029 that threshold drops to 70 kW. A large group of mid-size buildings then falls under the obligation: offices around 1000 m², secondary schools, smaller hospitals. Member states had to transpose the recast by 29 May 2026, so the national rules differ per country (building automation requirement).

For an installer, a heat pump in such a building then has to deliver its data to a higher-level system, and Modbus RTU is often the underlying transport. According to the EHPA Market Report 2025, around 60 percent of new heat pump installations across Europe ship with a Modbus or BACnet interface. For energy meters, where Eastron, Janitza and Carlo Gavazzi dominate the European market, the share is higher still.

In practice you build the chain with a gateway that polls the Modbus RTU bus and forwards the data over MQTT or an API to a monitoring platform. That chain supplies the measurement data and the open data access the EPBD asks for.

What is the difference between Modbus RTU and Modbus TCP?

Modbus RTU sends binary frames over a serial RS485 or RS232 connection with CRC-16 error checking. Modbus TCP sends the same function codes inside a TCP/IP packet with an MBAP header on port 502 over Ethernet. The application layer is identical; only the transport differs.

How many slaves can a Modbus RTU bus support?

Logically Modbus RTU supports 247 slave addresses plus broadcast address 0. Electrically RS485 limits a segment to 32 standard loads. If you need more devices, split the bus with repeaters or use a second gateway port.

What baud rate is common for Modbus RTU?

9600 baud 8N1 is the most stable default in European HVAC and refrigeration. 19200 and 38400 baud appear where polling cycles must be shorter, but they are more sensitive to cable quality and reflections. Always start at 9600 baud and step up once everything runs.

Do you need termination resistors on Modbus RTU?

Yes, place a 120 ohm termination resistor at both physical ends of the daisy chain. Never in the middle, as the resistors then pull in parallel below the minimum load of the line driver IC and the signal collapses.

How long can a Modbus RTU cable run?

The TIA/EIA-485-A standard allows up to 1200 m at 9600 baud with twisted-pair cable. At 38400 baud the limit drops to roughly 600 m. For stable installations, keep a 30 percent margin on these figures.

What does 8N1, 8E1 and 8O1 mean?

These shorthand codes describe the serial frame setting: 8 data bits, parity (None, Even or Odd), and 1 stop bit. 8N1 is the Modbus default. 8E1 is required by some older devices. Every device on a bus must share the same setting.

The ModbusCloud Gateway reads Modbus RTU and Modbus TCP devices with the ready-made templates from the library.