Modbus RTU - Knowledge Base

Modbus RTU overview covering serial RS-485 transport, framing, CRC error detection, and pre-commissioning requirements.

Categories:

What Modbus RTU Is

Modbus RTU (Remote Terminal Unit) is Modbus transported over RS-485 serial with binary framing and CRC-16 error checking. It is the most common Modbus variant in field device integration.

Modbus RTU frame structure with CRC-16 error detection

RTU vs TCP

AspectModbus RTUModbus TCP
TransportRS-485 serialEthernet TCP/IP
FramingBinary with CRC-16MBAP header (no CRC)
AddressingSlave ID (1–247)IP address + Unit ID
TopologyMultidrop busIP network
Speed9600–115200 baud10/100/1000 Mbps

Key Serial Parameters

All devices on an RS-485 trunk must agree on these settings:

ParameterCommon Values
Baud rate9600, 19200, 38400, 115200
Data bits8
ParityNone, Even
Stop bits1, 2

[!WARNING] A single device with mismatched serial settings can disrupt the entire trunk. Verify every device before connecting.

Pre-Commissioning

Before connecting devices:

  1. Confirm serial parameters for every device on the trunk
  2. Verify unique Slave IDs (1–247)
  3. Confirm register map revision and addressing convention
  4. Check RS-485 wiring topology (daisy-chain, not star)
  5. Apply termination resistors at both bus ends

See Modbus RTU Pre-Commissioning Checklist for a complete walkthrough.

Common Problems

  • Entire trunk stops communicating — One device with mismatched baud rate, parity, or stop bits disrupts all other devices on the bus. Verify every device’s serial parameters before connecting. See Modbus RTU Pre-Commissioning Checklist.
  • Intermittent timeouts — Duplicate Slave IDs or RS-485 wiring faults (star topology, missing termination). See Modbus Troubleshooting Guide.
  • No response on correct address — Device may require a specific inter-frame gap or have non-standard timeout requirements. See Modbus Troubleshooting Guide.
  • Wrong register values — Addressing convention mismatch (0-based vs 1-based). See Modbus Addressing & Register Reference.

Need more help?

If this page does not resolve the issue, contact Chipkin support with the product model, protocol details, and any diagnostics you have already captured.

Open Chipkin Support