Industrial IoT comparison
Modbus RTU vs Modbus TCP for IoT
Understand when to use Modbus RTU on RS485 and when to convert field data into Modbus TCP for IoT gateways.
Hardware in this guide
Product-family photos. See each product page for specifications and options.
Need a project-specific choice?
Send your existing device models, power, network and the readings you need. We can compare compatible equipment and prepare a quotation.
At your site
Modbus RTU usually lives on serial RS485 field buses. Modbus TCP runs over Ethernet/IP and is easier for SCADA, BMS and gateway handoff.
Decision table
Physical layer
- Modbus RTU
- Serial RS485 bus
- Modbus TCP
- Ethernet/IP network
- Guidance
- RTU and TCP are protocol variants, not interchangeable wiring.
Field device support
- Modbus RTU
- Common in meters and sensors
- Modbus TCP
- Common in controllers and gateways
- Guidance
- Most retrofits collect RTU then expose TCP upstream.
Integration scope
- Modbus RTU
- Low-cost multi-drop field polling
- Modbus TCP
- Higher-level LAN/SCADA integration
- Guidance
- Use a gateway when both are needed.
Equipment in the system
Example equipment arrangement. Check compatibility and agree who handles software, PLC/SCADA programming and site installation.
Data destination
Customer platform or an agreed third-party service
Implementation checks before choosing RTU or TCP
Changing the transport does not settle the device-level details. Confirm these items before selecting a converter or gateway.
Media and topology
For RTU, confirm two-wire or four-wire RS485, cable length, termination, biasing and device count. For TCP, confirm the LAN, IP plan, routing and access to the required service port.
Device identity
Record every serial device address and decide how the gateway will map it to the upstream unit identifier. Do not assume the default mapping fits every SCADA driver.
Register semantics
Confirm function codes, address notation, data types, byte and word order, scaling and write permissions. A transport conversion does not correct an incomplete register map.
Serial timing
Match baud rate, parity and stop bits, then set turnaround delay, polling interval, timeout and retry limits for the slowest field device.
TCP connection model
Confirm how many upstream clients may connect, whether connections stay open and whether the gateway serves live polls or cached values.
Failure and stale-data handling
Define how timeouts, Modbus exception responses and stale values are exposed, including timestamp or quality information needed by the receiving system.
Hardware used in the comparison
Product-family photos; the model and enclosure may vary.
Choose Modbus RTU when
- Meters and sensors already expose RS485 registers
- The field bus is short and stable
- A gateway can poll devices locally
Choose Modbus TCP when
- SCADA or BMS expects Ethernet data
- Multiple systems need shared access
- The gateway must publish readable register data upstream
Information needed for quotation
- Device model and register map
- Function codes, addresses and data types
- Serial settings, device count and bus layout
- Upstream clients, polling interval and stale-data rules
Hardware to confirm before quotation
Product-family photos; the model and enclosure may vary.
Official technical references
- Modbus Application Protocol Specification V1.1b3
Official definition of the Modbus application data unit, function codes and exception responses.
- Modbus Organization specifications and implementation guides
Official source for the current serial-line and TCP implementation guidance.
Related pages
FAQ
How do I choose between the two options?
Choose Modbus RTU when meters and sensors already expose RS485 registers. Choose Modbus TCP when SCADA or BMS expects Ethernet data. SunGene can shortlist hardware after reviewing the site and integration details.
Can SunGene quote both options?
Yes. Send the site layout, measurements, available network and quantity. We can compare equipment and accessories for both options.
Does this comparison include pricing or guaranteed certification?
No. Pricing and certification depend on the selected hardware configuration and target country, so they are confirmed during quotation.
Can we test an option before a wider rollout?
Ask for a sample or pilot configuration. Agree the interfaces, power, mounting and receiving system, then compare local readings with the received data. Confirm model-specific documents and any required approvals before ordering.
Does an RTU-to-TCP gateway change the register map?
Usually the gateway transports or maps requests; it does not make an incomplete register definition correct. Confirm unit identifiers, address offsets, data types, byte order and scaling. If remapping is required, state it before hardware selection.
What should I send before requesting an RS485 or Modbus gateway quote?
Send the device model, register map, function codes, serial settings, device count, bus layout, polling interval, upstream client count and network requirements. A sample readout is useful when available.