|Parent(s)||System → Servers|
|Instance||Must be 0|
Modbus Serial Slave Channel (SlaveAsync)
An Async Slave Channel defines a logical connection from a Modbus master to the RediGate via a serial port. Under the Slave Channel, one or more Modbus slave device addresses may be defined in separate objects, each pointing to an RTDB from which the data is obtained.
Enter the Modbus slave address that will respond on this slave channel
|Reserved||Reserved field, currently unused.|
|Source Channel||Master Channel or Internal Channel of the Field Unit and RTDB to be attached to this Slave unit.|
|Source Field Unit|
Field Unit address containing the RTDB to be used as data represented in this Slave unit.
32-bit data is only supported in 40,xxx RTDB registers, not 30,xxx registers. In order for the Modbus Slave Attach to work properly, the registers in the attached RTDB must be defined in a specific order. That order is:
NOTE: The RTDB attached to the Modbus slave should include at least one register in each of the four address ranges (1, 10001, 30001, 40001), observing the rules stated in the bullets above. For instance, if the RTDB definition includes 16-bit registers after UINT32 or REAL32 registers, those 16-bit registers will not work properly when attached to the Modbus Slave.
Modbus Network Slave Channel (SlaveNetwork, SlaveModbusTCP)
An SlaveNetwork or SlaveNetworkTCP channel defines a logical connection from a Modbus master to the RediGate via a network TCP/IP port. Under the Slave Channel, one or more Modbus slave device addresses may be defined in separate objects, each pointing to an RTDB from which the data is obtained. Up to six Modbus clients can be connected simultaneously to the same slave channel instance (IP port).