Modbus is one of the most established communication protocols used in industrial automation. It can be found in PLC systems, variable speed drives, energy meters, remote I/O, instrumentation, HMIs, gateways and many other industrial devices.
Two terms appear particularly often: Modbus RTU and Modbus TCP. They are related, but they do not use the same physical network and should not be treated as interchangeable connection types.
Understanding the difference helps engineers, technicians and purchasing teams select the correct PLC modules, gateways, switches, converters, VSDs and field devices for a project.
What Is Modbus?
Modbus is an application-layer communication protocol originally developed for industrial control systems. It provides a structured way for devices to exchange data such as measurements, status information, commands and configuration values.
Typical Modbus data can include:
- Motor speed references
- VSD output frequency
- Motor current
- Pressure or level values
- Energy meter readings
- Alarm states
- Digital input and output status
- Setpoints
- Equipment operating status
Modbus defines how this information is organised and requested. The physical method used to transport the messages depends on the Modbus implementation.
What Is Modbus RTU?
Modbus RTU is commonly used over serial communication networks, particularly RS-485.
A typical Modbus RTU installation may consist of a PLC or gateway communicating with multiple field devices on an RS-485 bus.
Examples include:
- PLCs communicating with VSDs
- Energy meters connected to a data concentrator
- Remote I/O stations
- Temperature controllers
- Process instruments
- Building or utility monitoring equipment
Each device on the serial network normally has a unique Modbus address.
What Is RS-485?
RS-485 is an electrical signalling standard widely used for serial industrial communications. It is not the same thing as Modbus.
Modbus RTU is the protocol being communicated, while RS-485 commonly provides the electrical communication layer carrying those messages.
This distinction matters because RS-485 can carry protocols other than Modbus, and Modbus can operate over communication technologies other than RS-485.
What Is Modbus TCP?
Modbus TCP carries Modbus communication over TCP/IP networks, normally using Ethernet.
Instead of connecting devices on a serial RS-485 bus, devices communicate through an Ethernet network using IP addressing.
A typical Modbus TCP network can include:
- PLCs
- Industrial Ethernet switches
- HMIs
- SCADA systems
- VSDs with Ethernet interfaces
- Remote I/O
- Industrial gateways
- Energy monitoring equipment
Modbus TCP commonly uses TCP port 502, although network architecture and security controls must always be considered for the specific system.
Modbus RTU vs Modbus TCP at a Glance
| Feature | Modbus RTU | Modbus TCP |
|---|---|---|
| Typical physical network | RS-485 serial | Ethernet |
| Device identification | Serial device address | IP networking plus Modbus addressing as applicable |
| Typical cabling | Twisted-pair serial cable | Industrial Ethernet copper or fibre infrastructure |
| Network equipment | Serial interfaces, repeaters or converters where required | Ethernet switches, routers and gateways where required |
| Common applications | Field devices, meters, drives, instruments | PLCs, SCADA, HMIs, drives, remote I/O and networked automation |
The exact implementation depends on the equipment. A device supporting Modbus RTU does not automatically support Modbus TCP, and vice versa.
What Is a Modbus Address?
On a Modbus RTU network, field devices are normally assigned individual addresses so that the communicating device can identify the intended unit.
If two devices are configured with the same address on the same serial segment, communication problems can occur.
Modbus TCP devices are also part of an IP network and therefore require appropriate IP configuration. Some gateways and devices additionally use a unit identifier to route Modbus requests internally or to downstream serial devices.
What Are Modbus Registers?
Modbus devices expose data through defined data areas. Common terminology includes:
- Coils
- Discrete inputs
- Input registers
- Holding registers
The meaning of an individual register is determined by the device manufacturer.
For example, a VSD manufacturer may assign one register to output frequency, another to motor current and another to a speed reference command.
You therefore need the manufacturer's Modbus register map or communication manual to integrate the device correctly.
Why Register Numbers Can Be Confusing
Register references are not always presented consistently across software packages and manuals.
Some documentation uses traditional references such as 40001 for holding registers, while software may use zero-based or one-based addressing internally.
As a result, a register shown in a manual may appear offset by one or represented differently in the PLC, SCADA or gateway configuration.
Do not assume the addressing convention. Confirm the manufacturer's register map and the convention used by the software or controller.
What Is a Modbus Function Code?
Modbus function codes define the type of operation requested.
Depending on the device, these operations can include reading coils, reading input registers, reading holding registers or writing values.
The device manual normally specifies which functions are supported for particular data points.
A register being visible in a register map does not necessarily mean that it can be written to. Some values are read only.
Serial Settings Matter on Modbus RTU
Devices on a Modbus RTU network must be configured with compatible serial communication parameters.
Important settings can include:
- Baud rate
- Parity
- Number of data bits
- Stop bits
- Device address
If the serial parameters do not match, communication will normally fail even if the wiring is correct.
RS-485 Wiring and Termination
Reliable RS-485 communication depends on correct network design and installation.
Important considerations can include:
- Correct signal polarity
- Appropriate cable
- Bus topology
- Termination at appropriate points
- Biasing where required
- Screening and earthing practices
- Cable length
- Communication speed
- Electrical noise
Requirements depend on the equipment and installation. Manufacturer instructions should be followed rather than applying one universal wiring arrangement to every network.
Ethernet Infrastructure Matters on Modbus TCP
Modbus TCP depends on the underlying Ethernet network.
Problems can therefore arise from issues that are not specific to Modbus itself, including:
- Incorrect IP addresses
- Duplicate IP addresses
- Incorrect subnet configuration
- Damaged Ethernet cabling
- Switch port problems
- VLAN configuration
- Routing or firewall rules
- Network congestion
- Loss of power to network equipment
Industrial networks should be designed with appropriate availability, segmentation, environmental and cybersecurity requirements for the application.
Can Modbus RTU Devices Communicate with Modbus TCP Devices?
Not directly simply because both devices support Modbus.
A Modbus RTU device communicates through a serial interface, while a Modbus TCP device communicates through an IP network.
A suitable Modbus gateway can bridge between the two where the architecture and equipment support it.
What Is a Modbus RTU to TCP Gateway?
A Modbus gateway provides communication between serial Modbus equipment and Ethernet-based Modbus systems.
For example, several existing RS-485 energy meters could connect to the serial side of a gateway, while a SCADA system communicates with the gateway through Ethernet.
The gateway handles the translation and routing required between the two communication environments.
Gateway selection can depend on:
- Number of serial ports
- RS-232, RS-422 or RS-485 support
- Number of connected devices
- Ethernet interfaces
- Operating temperature
- Mounting requirements
- Isolation requirements
- Power supply
- Configuration features
- Cybersecurity requirements
Modbus and Variable Speed Drives
Many VSDs support Modbus RTU as a built-in or optional communication interface. Some drives also support Modbus TCP through an integrated Ethernet interface or optional communication card.
Using communications rather than individual hardwired signals can allow a controller to access multiple drive parameters over one network.
Depending on the VSD, these may include:
- Start and stop commands
- Speed reference
- Output frequency
- Motor current
- Drive status
- Fault codes
- Operating parameters
Whether control commands should be implemented over the network depends on the application, safety requirements and control philosophy.
Modbus and PLC Systems
PLCs can act in different communication roles depending on the platform and application.
A PLC may communicate directly through an integrated serial or Ethernet port, through a dedicated communication module, or through an external gateway.
When selecting PLC hardware, confirm the exact protocol and physical interface required. An Ethernet port does not automatically mean that every industrial Ethernet protocol is supported.
Modbus and SCADA
SCADA systems frequently communicate with Modbus devices either directly or through PLCs, gateways and data concentrators.
A SCADA system can use Modbus data for:
- Process monitoring
- Alarm indication
- Historical trending
- Energy monitoring
- Equipment status
- Remote commands where permitted
The architecture should consider network reliability, access control, cybersecurity and the consequences of communication failure.
Common Modbus RTU Problems
Typical troubleshooting areas include:
- Incorrect A/B polarity
- Wrong device address
- Mismatched baud rate
- Mismatched parity or stop bits
- Duplicate addresses
- Incorrect termination
- Poor bus topology
- Electrical noise
- Incorrect register address
- Unsupported function code
- Incorrect data format
Common Modbus TCP Problems
Typical troubleshooting areas include:
- Incorrect IP address
- Duplicate IP address
- Incorrect subnet or gateway settings
- Network path or switch problems
- TCP port blocked by network controls
- Incorrect unit identifier where relevant
- Incorrect register mapping
- Unsupported function
- Device connection limits
- Application timeouts
Understanding Data Types
A Modbus register is commonly 16 bits, but industrial values are not always represented by a single register.
Devices may use:
- 16-bit integers
- Unsigned integers
- Signed integers
- 32-bit integers
- Floating-point values
- Bit fields
- Scaled integer values
Multi-register values can also involve word-order or byte-order considerations.
If a register is communicating but the displayed value makes no sense, confirm the required data type, scaling and byte or word order in the manufacturer's documentation.
Modbus Is Not a Safety System
Standard Modbus communication should not automatically be treated as a safety-rated control mechanism.
Emergency stops, protective functions and safety-related control must be designed using equipment and architectures appropriate to the required safety function and applicable standards.
Modbus and Cybersecurity
Traditional industrial protocols were developed primarily for operational communication, not as complete cybersecurity systems.
Modbus TCP networks should therefore be incorporated into an appropriate industrial cybersecurity architecture.
Depending on the installation, measures can include network segmentation, controlled remote access, firewalls, managed switches, access restrictions, monitoring and secure configuration practices.
Industrial control networks should not be exposed directly to untrusted networks merely because remote access is convenient.
Choosing Between Modbus RTU and Modbus TCP
The correct choice depends on the equipment and system architecture rather than on one protocol being universally better.
Modbus RTU can be practical for relatively simple field-device networks and existing serial installations. Modbus TCP can integrate naturally into Ethernet-based automation networks and can make use of modern industrial networking infrastructure.
Many facilities use both, with gateways connecting legacy or field-level serial networks to Ethernet-based control and monitoring systems.
What Information Should You Provide When Requesting Modbus Equipment?
For purchasing or replacement enquiries, provide as much information as possible.
- Existing manufacturer: ___
- Exact model or part number: ___
- Required protocol: Modbus RTU or Modbus TCP
- Physical interface: RS-485, Ethernet or other
- Number of devices: ___
- Serial ports required: ___
- Ethernet ports required: ___
- Power supply: ___
- Mounting: DIN rail, panel or other
- Operating environment: ___
- Isolation requirement: ___
- Managed network features required: ___
- PLC, SCADA or VSD platform: ___
- Quantity: ___
If replacing an existing communication device, clear photographs of the product label and connections can also help identify the correct equipment.
Technical Note
This article provides general industrial communication information. Network architecture, serial wiring, control logic, cybersecurity, functional safety and equipment configuration must be assessed for the specific application. Manufacturer documentation, applicable standards and site procedures take precedence, and installation or configuration should be performed by appropriately competent personnel where required.
Related catalogue examples: PLCs & Programmable Controllers. For an equipment enquiry, contact Softcore Group Industrial Solutions at info@softcoregroup.co.za.