Modbus TCP Overview
TheMODBUS_TCP route enables communication with PLCs, RTUs, and industrial devices using the Modbus TCP/IP protocol. It supports reading and writing registers and coils with configurable polling intervals and automatic batch optimization.
Basic Syntax
Connection Configuration
MODBUS_CONFIG Parameters
string
required
Modbus TCP server hostname or IP address.
integer
Modbus TCP port. Default: 502.
integer
Modbus slave/unit ID (1-247). Default: 1.
integer
Connection timeout in milliseconds. Default: 5000.
integer
Read operation timeout in milliseconds. Default: 1000.
integer
Write operation timeout in milliseconds. Default: 1000.
integer
Number of retry attempts on failure. Default: 3.
integer
Delay between retries in milliseconds. Default: 100.
Connection Example
Address Types
Modbus defines four address spaces:Most Modbus devices use Holding Registers for configuration and Input Registers for measured values. Check your device documentation for the correct address type.
Data Types
string
required
The data type determines how raw register values are interpreted:
TAG Configuration
Complete TAG Parameters
TAG Parameters Reference
Address Configuration
Address Configuration
Value Transformation
Value Transformation
Filtering
Filtering
Publishing
Publishing
Write Configuration
Write Configuration
Event-Based Operations
For on-demand Modbus operations (not polling), use the EVENT syntax. Publish a message to SOURCE_TOPIC to trigger the operation; the route executes it and publishes the result to DESTINATION_TOPIC.Query Syntax
TheWITH QUERY value uses LoT object syntax: unquoted keys, unquoted identifiers, and numeric values. The entire query is wrapped in double quotes.
Supported Operations
Query Parameters by Operation
To write a value on demand, publish a message to SOURCE_TOPIC. The route executes the write and publishes the result to DESTINATION_TOPIC:
Complete Examples
- Basic Sensor Reading
- Multiple Polling Rates
- Bidirectional Control
- Coils and Digital I/O
- Combined (Cyclic + On-Demand)
Read temperature and pressure from a Modbus device:
Troubleshooting
Connection Timeout
Connection Timeout
- Verify IP address and port are correct
- Check firewall settings (port 502 must be open)
- Ensure device is powered on and connected to network
- Try increasing
CONNECTION_TIMEOUT
Incorrect Values
Incorrect Values
- Verify
ADDRESSmatches device documentation - Check
BYTE_ORDERandWORD_ORDERsettings - Confirm
DATA_TYPEmatches register size - Verify
SCALINGandOFFSETcalculations
Write Operations Fail
Write Operations Fail
- Ensure
WRITABLEis set to “true” - Verify
ADDRESS_TYPEisHOLDING_REGISTERorCOIL - Check device permissions for write operations
- Verify value is within
MIN_VALUEandMAX_VALUE
Slave ID Errors
Slave ID Errors
- Confirm correct
SLAVE_ID(usually 1 for TCP devices) - Some gateways use different slave IDs for different devices
- Check device documentation for correct unit ID
Next Steps
Modbus Serial
Connect to RS-232/RS-485 Modbus RTU devices.
Industrial Overview
Learn common patterns for all industrial routes.

