Modbus RTU vs Modbus TCP: Differences and When to Use Each

Modbus is one of the oldest industrial protocols still in wide use. Power meters, inverters, PLCs, generator controllers, and many industrial sensors speak Modbus. When connecting these devices to an IoT platform, the first question is usually: Modbus RTU or Modbus TCP?

This article explains the difference between them, their strengths and limits, and the mistakes most often made when reading Modbus data.

Modbus basics: master and slave

Modbus works as question and answer. One side (the master, or client) requests data, and the device (the slave, or server) replies. Data lives in registers at specific addresses, such as the voltage, current, or power registers of a power meter. Each manufacturer documents its register map, and that document is the key to integration.

Modbus RTU: serial over RS-485

• Medium: serial cable, usually RS-485, with one line shared by many devices (multi-drop).
• Addressing: each device on a line has a unique address, up to 247.
• Distance: RS-485 reaches around 1,200 metres at low speeds, suiting panels spread across a plant.
• Settings: baud rate, parity, and stop bits must match between the master and every device.
• Strengths: cheap, robust against interference when installed correctly, and supported by almost every older device.

Modbus TCP: over Ethernet

• Medium: ordinary Ethernet or IP networks, on standard port 502.
• Addressing: devices are found by IP address, plus a unit identifier when a gateway to serial devices sits behind it.
• Strengths: faster, uses existing network infrastructure, and several clients can read the same device.
• Note: Modbus TCP devices on an office network need protecting, because Modbus itself has no authentication.

A quick comparison

Aspect	Modbus RTU	Modbus TCP
Medium	RS-485 serial	Ethernet / IP
Device identity	Address 1 to 247	IP address (+ unit ID)
Distance	Up to about 1,200 m per segment	Follows the network
Common in	Older devices, scattered panels	Newer devices, plant networks

Common mistakes when reading Modbus data

• Address offset errors. Some documents number registers like 40001, others start at 0. One register off makes the value meaningless.
• Byte and word order. 32-bit values, such as decimal numbers, span two registers. The order differs between manufacturers. Reversed, the numbers look random.
• Missed scaling. Many devices store values as integers that must be divided by 10 or 100.
• RS-485 cabling without termination or with reversed polarity, causing intermittent communication.
• Two devices with the same address on one RTU line.

Connecting Modbus to an IoT platform

Modbus devices cannot send data to the cloud by themselves. A gateway acts as master: it reads registers periodically, converts them into meaningful values, then sends them to the platform over MQTT or HTTP. A good gateway also buffers data if the internet connection drops.

Practical steps before integrating: gather the register maps for all devices, record their addresses and serial settings, and test reading one device before adding the rest. Field experience connecting older PLCs is covered in connecting legacy Modbus RTU PLCs to the cloud.

An example of reading one register

An illustration from a power meter: the manufacturer's document says phase R voltage is stored in a holding register with a scale of 0.1 V. The gateway reads it with function code 03 and gets 2305. After applying the scale, the value is 230.5 V. If the result looks like 23,050 or a random number, the scale was probably missed, the address is off by one, or the register read is half of a 32-bit value.

That is why testing always starts with one value that is easy to check with another tool, such as a voltage you can compare with a multimeter.

Checklist before integrating

• A register map for every device model, including scale and data type.
• The Modbus address of every device, confirmed unique on each line.
• Serial settings: baud rate, parity, and stop bits.
• An RS-485 wiring layout, including termination resistors at both ends.
• The polling interval you need, since reading too fast can overload a line with many devices.

Frequently asked questions

How many devices fit on one RS-485 line?

The RS-485 standard generally supports 32 unit loads per segment without a repeater. Modern devices often present a smaller load, allowing more. Check your device specifications.

Can Modbus RTU be converted to Modbus TCP?

Yes, with a gateway or a serial-to-Ethernet converter.

Is Modbus secure?

Modbus has no built-in authentication or encryption. Secure it through network separation and a gateway that sends data out encrypted.

Reading Modbus with IncludeGateways

IncludeGateways reads Modbus RTU devices over RS-485 and sends the data to the INCLUDE platform over 4G or whatever network is available. Existing power meters, inverters, and PLCs can reach the dashboard without replacement, for example for energy monitoring in InEnergy.