Modbus is one protocol, but it travels in different ways. Modbus RTU runs over serial cable. Modbus TCP/IP runs over Ethernet. Engineers ask which one is better, and the honest answer depends on the physical layer you already have and where the data must go.

This guide compares Modbus RTU and Modbus TCP/IP, explains the third option most guides skip, and shows how to move between them without replacing existing devices.

Short Answer: Same Data Model, Different Transport

Modbus defines a protocol data unit, or PDU. It carries a function code and the data, such as “read holding registers 0 to 9.” The PDU is the same for every Modbus version.

The transport wraps that PDU in different frames. Modbus RTU adds a slave address and a CRC checksum, then sends the frame over serial wiring. Modbus TCP/IP adds an MBAP header and sends the frame over TCP on port 502.

Because the data model is identical, a Modbus RTU device and a Modbus TCP client can work together through a gateway. Nothing changes in the register map or the function codes. Only the transport changes.

Modbus RTU vs Modbus TCP/IP: Side by Side

How Modbus RTU Works

Modbus RTU uses a master-slave model. One master polls each slave in turn. The slave answers, and the master moves to the next address. Only one device talks at a time.

Each frame carries a slave address, the PDU, and a CRC checksum for error detection. Frames are separated by a short silence of about 3.5 character times, which keeps timing tight at higher baud rates.

RS-485 carries the signal over a daisy chain of up to about 1200 meters and 32 unit loads. Termination resistors at both ends keep the bus clean. RTU is deterministic: the polling cycle is predictable, which suits process control. Modbus ASCII is a slower variant that rarely appears in new projects.

How Modbus TCP/IP Works

Modbus TCP/IP sends the same PDU over Ethernet. The MBAP header carries a transaction ID, protocol ID, length, and unit ID. The unit ID lets a gateway reach a specific RTU slave behind it.

TCP handles retries, ordering, and connection state. Multiple clients can query the same server, which is a major difference from the single-master RTU model. Port 502 is the assigned port.

Because it runs on Ethernet, Modbus TCP/IP scales through switches, supports star and ring topologies, and fits standard IT tooling. It also inherits normal network design needs, such as IP planning, VLANs, and firewalls.

Modbus RTU Over TCP: The Third Option Most Guides Miss

This is where many projects go wrong. “Modbus over Ethernet” covers two different things.

Modbus TCP (native). The frame uses the MBAP header on port 502. There is no CRC, because TCP handles integrity.

Modbus RTU over TCP. The original RTU frame, CRC included, is tunneled inside a TCP connection without an MBAP header. Serial servers and device servers commonly use this mode.

The two are not interchangeable. If your SCADA expects native Modbus TCP but the serial server sends RTU over TCP, the connection opens and the polls still fail. The data never parses.

The practical rule: check the mode setting on every serial server or gateway. Native Modbus TCP and RTU over TCP are separate options, and the SCADA side must match. A conversion gateway that translates RTU to native Modbus TCP avoids the mismatch entirely.

Performance and Latency: What Actually Changes

TCP offers far more bandwidth, but bandwidth is rarely the bottleneck in Modbus.

At 9600 baud, reading ten registers takes roughly 10 to 15 milliseconds. Twenty slaves with a few registers each produce a polling cycle of a few hundred milliseconds. That is fast enough for most process data.

On TCP, each transaction includes a network round trip of a few milliseconds. The real gain is parallelism: several clients can poll at once, and switches remove the 32-node limit. A gateway adds a small amount of overhead for buffering and translation.

So TCP is not automatically faster for a small system. It is more scalable, easier to diagnose, and better suited to systems where many applications need the same data.

Which Should You Use?

A common pattern uses both: RTU on the field bus, TCP on the plant network, with a gateway in the middle. This keeps the existing wiring and adds network access.

Converting RTU to TCP When You Need Both

A Modbus gateway has two sides. The serial side polls RTU slaves and reads their registers. The Ethernet side serves those registers to Modbus TCP clients. The SCADA system sees normal Modbus TCP devices.

Several things stay the same: the register map, function codes, and unit IDs. Several things change: device addressing becomes IP-based, timeouts follow network behavior, and unit IDs must stay unique across every gateway on the network.

Multi-port gateways collect several RS-485 buses onto one Ethernet connection, which suits plants with many devices. Our Modbus RTU to TCP gateways offer multiple serial channels for exactly this layout. For cloud and IT integration, edge gateways add MQTT, OPC UA, BACnet, and IEC 104 alongside Modbus.

Security Considerations

Neither version of Modbus includes authentication or encryption. The protocol was designed for trusted networks.

Modbus TCP/IP exposes that weakness to your network. Treat port 502 like any other sensitive service: keep it off the internet, segment control networks from business networks, control access with firewalls, and use a VPN for remote maintenance.

Modbus RTU limits exposure to the physical bus, which is a smaller attack surface but still not secure. Anyone with cable access and a Modbus tool can read or write registers.

Common Mistakes

Assuming TCP is always faster. Device response time and polling strategy dominate. A slow device stays slow on Ethernet.

Confusing Modbus TCP with RTU over TCP. These are different frame formats. Mixing them causes polls that never parse.

Forgetting that timeouts change. A serial timeout of 100 ms is not a network timeout. Tune retries and timeouts after conversion.

Duplicating unit IDs behind gateways. Every gateway can serve unit ID 1. Plan addressing across the whole network.

Skipping the IP plan. Use fixed addresses or reservations for gateways and controllers, and document the subnet layout.

Exposing port 502 to the internet. Modbus has no authentication. Never publish it directly.

Expecting a gateway to fix a bad bus. Termination, polarity, and grounding come first. A gateway cannot repair a noisy RS-485 line.

FAQ

What is the difference between Modbus RTU and Modbus TCP/IP?
Modbus RTU sends the PDU over serial wiring with a slave address and CRC, using a master-slave model. Modbus TCP/IP sends the same PDU over Ethernet with an MBAP header on port 502, using a client-server model. The data model and function codes are identical.

Is Modbus TCP faster than Modbus RTU?
TCP has far more bandwidth, but device response time and polling strategy often dominate. TCP scales better with many devices and multiple clients. For a small system with slow process data, RTU is already fast enough.

Can Modbus RTU and Modbus TCP work together?
Yes, through a Modbus gateway. The gateway polls RTU slaves on the serial side and serves them to TCP clients on the Ethernet side. The register map stays the same, so the SCADA system sees normal Modbus TCP devices.

How do I convert Modbus RTU to Modbus TCP?
Use a Modbus RTU to TCP gateway. Connect the RS-485 bus to the serial port, set the slave addresses and baud rate, then configure the Ethernet side with an IP address. Map the unit IDs and confirm the polling cycle on the TCP side.

What is Modbus RTU over TCP?
Modbus RTU over TCP tunnels the original RTU frame, CRC included, inside a TCP connection with no MBAP header. Serial servers often use this mode. It is not the same as native Modbus TCP, and the SCADA side must match the mode.

What port does Modbus TCP use?
Modbus TCP uses port 502 by default. Some tools let you change the port, but 502 is the standard and the safest choice for interoperability.

How many devices can Modbus RTU support?
An RS-485 bus supports about 32 unit loads, so most installations use up to 32 devices per segment. The Modbus address range allows 247 slaves, but you reach that number with multiple buses and repeaters.

Is Modbus TCP secure?
No. Modbus TCP has no authentication or encryption. Security comes from network design: segmentation, firewalls, access control, and VPN for remote access. Never expose port 502 directly to the internet.

Which is better for long distance?
Both can cover long distance with the right media. RS-485 reaches about 1200 meters per segment and extends with repeaters or fiber converters. Modbus TCP runs over Ethernet and fiber, which covers buildings and campuses.

What is the difference between Modbus and OPC UA?
Modbus is a simple register-based protocol with no built-in security or rich data model. OPC UA adds typed data models, subscriptions, authentication, and encryption. Many plants use Modbus at the device level and convert to OPC UA for IT and analytics.

Conclusion

Modbus RTU and Modbus TCP/IP share one data model and differ in transport. RTU suits RS-485 field buses with predictable polling. TCP suits networked systems with many devices and multiple clients. The third option, RTU over TCP, is the one to identify carefully before you troubleshoot.

You rarely have to choose one and abandon the other. A gateway keeps the field bus and serves the data over Ethernet, which is how most plants bridge legacy devices into SCADA, MQTT, OPC UA, and cloud platforms.

Tell us your device list and where the data must go. Our engineers will recommend the gateway layout for your network, free and with no obligation. We build Modbus RTU to TCP gateways with multiple serial channels, plus edge gateways for MQTT, OPC UA, BACnet, and IEC 104.