Modbus TCP vs Modbus RTU: Choosing the Right Protocol for Your Line

Modbus remains the most widely supported industrial protocol, but engineers often ask whether to standardize on RTU (serial) or TCP (Ethernet). The answer depends on distance, latency requirements, and the age of the installed base.

What Actually Differs

Modbus RTU transmits over RS-485 or RS-232 using a master-slave model with binary framing and a CRC16 error check. Modbus TCP wraps the same application data in a TCP/IP packet, which means it can route across switches, VLANs, and even site WANs.

• RTU - 2-wire RS-485, up to roughly 1200 m per segment, 32 nodes per segment without repeaters, deterministic polling.
• TCP - standard Ethernet, unlimited logical nodes, easily 100 m per copper segment, no built-in timing guarantee.

Latency and Jitter

RTU polling over a dedicated serial line has low and predictable jitter, which is why some motion and high-speed machine controls still prefer it. TCP introduces network overhead and potential jitter from switch buffering, but for most process data - temperatures, pressures, counters - the difference is irrelevant.

Practical Guidance

• Retrofitting an existing RTU network: keep RTU. Replacing cabling is rarely justified by the protocol change alone.
• New installations with modern PLCs and HMIs: choose TCP. Cabling is cheaper, diagnostics are easier, and the same network can carry OPC UA or MQTT later.
• Mixed fleets: use protocol gateways that translate RTU to TCP at the cell level instead of rewiring field devices.

Rule of thumb: if the plant already speaks serial and nobody complains about speed, do not fix what is not broken. If you are designing for the next ten years, Ethernet wins.