Why Modbus is still everywhere
Modbus has been in continuous use since 1979 because it is simple, open, and universally supported. Nearly every PLC, RTU, gateway, sensor, and SCADA package can speak it, which makes it the common language of brownfield industrial sites.
The two dominant variants are Modbus RTU (serial) and Modbus TCP (Ethernet). They share the same data model — coils, discrete inputs, holding registers, and input registers — but differ completely in transport, addressing, and performance.
Modbus RTU: serial and deterministic
Modbus RTU runs over RS-485 (or RS-232) serial links using a master/slave model. One master polls each slave in turn; slaves never speak unless addressed. The frame is compact: a device address, a function code, data, and a CRC-16 checksum.
- Determinism: polling is fully controlled by the master, so timing is predictable on a single link.
- Cable lengths: RS-485 supports up to roughly 1200 m (4000 ft) at low baud rates, far beyond a single Ethernet segment.
- Address limit: 247 slave addresses per link (1–247), which constrains network size.
- Typical speeds: 9.6 kbit/s to 115.2 kbit/s — slow by modern standards but often sufficient for discrete I/O and telemetry.
RTU is still the right choice for long-distance field wiring, retrofit projects, and environments where Ethernet is unavailable or undesirable.
Modbus TCP: Ethernet and scale
Modbus TCP wraps the same function codes inside a TCP/IP packet, removing the slave address in favour of IP addressing. Port 502 is the well-known port. Because it rides on standard Ethernet, it inherits all the benefits of modern networking: switches, VLANs, routing, and much higher bandwidth (10/100/1000 Mbit/s).
- Many devices: hundreds of clients and servers on one network, limited by IP addressing rather than 247.
- Speed: fast enough for high-frequency data collection and HMI traffic.
- Interoperability: works over industrial Ethernet infrastructure and can cross into office networks with proper segmentation.
- Downside: TCP adds jitter and no inherent determinism; timing guarantees require additional mechanisms (e.g., TSN) for hard real-time control.
Key differences at a glance
| Aspect | Modbus RTU | Modbus TCP |
|---|---|---|
| Transport | RS-485 / RS-232 serial | TCP/IP over Ethernet |
| Topology | Master/slave, polled | Client/server, concurrent |
| Addressing | 247 slave addresses | IP address + unit ID |
| Port | — | 502 |
| Speed | 9.6–115.2 kbit/s | 10–1000 Mbit/s |
| Determinism | High (single master) | Medium (depends on network) |
| Distance | Up to ~1200 m | Segment limit (100 m copper) |
| Best for | Field wiring, retrofits | Plant networks, data collection |
How to choose
Use Modbus RTU when you need long cable runs, deterministic polling on a small number of devices, or when modernizing legacy serial instrumentation. Use Modbus TCP when you already have an Ethernet plant network, need many devices or high data rates, or want to integrate with IT systems.
In many plants the two coexist: RTU gathers data in the field, and a gateway converts it to TCP for the control room. That gateway pattern is one of the most common architectures in industrial networking, and it is exactly the kind of scenario where a protocol map helps avoid surprises.