Specifications

Select the type of translation from Modbus to RipEX IP address (mask or table), as described in
chapter 3.
Set the UDP interface to COM1 or COM2 depending on the port that the remote RipEX uses to
connect to the Slave device.
To set up RipEX connected to Modbus RTU Slave:
As described in chapter 1 set the appropriate COM to Modbus and the Mode of Connected to Slave.
8.5. Master Modbus TCP, slaves Modbus RTU or Modbus TCP
RipEX radio modems enable full featured cooperation between the Master using Modbus TCP and
slave devices using Modbus RTU or Modbus TCP within a single network.
S
RS232
ModbusRTU
S
RS485
ModbusRTU
S
ETH
ModbusTCP
LocalTCP
connection
M
ETH
ModbusTCP
LocalTCP connection
ETH
ModbusTCP
LocalTCP connection
S
S
Fig. 8.6: Modbus TCP, Slave RTU or TCP
To set up RipEX connected to Modbus TCP Master:
Set the translation from Modbus to RipEX IP addresses to table-based, as described in chapter 3.
For devices connected over Modbus RTU, set the UDP interface to COM1 or COM2 (as in chapter
4).
For devices connected over Modbus TCP, set the UDP interface to TS1-TS5, as described in chapter
3.
You can define address ranges in the table for greater ease of use.
To set up RipEX connected to Modbus RTU Slave:
See chapters 4 and 1 respectively.
To set up RipEX connected to Modbus TCP Slave:
See chapter 3.
8.6. Multiple Modbus TCP or Modbus RTU Masters and Slaves
Any combination of network designs described in chapters 1–5 is possible. The only limitation is that
a Master with Modbus RTU cannot communicate with a Slave using Modbus TCP.
47© RACOM s.r.o. – RipEX Application notes
Modbus TCP/RTU