Weidmuller WI-I/O-9-U2: Wireless Mesh I/O & Gateway User Manual V1.2.2 - Manual (Page 72)

71
Request Pause
– Is the delay between serial requests in milliseconds
Response Wait
– Is the serial response timeout in milliseconds – a serial retry will be
sent if a response is not received within this timeout.
Maximum Tries
– Is the maximum number of request retries performed on the serial
port.
Serial - Modbus RTU Slave
When configured as a Modbus RTU slave the only parameter that will need to be
configured are the Date Rate, Data Format and Flow Control.
4.3.14 Modbus Configuration
The WI-I/O 9-U2 provides Modbus TCP Client/ Server & Modbus RTU Master/Slave
functionality for I/O transfer. Modbus TCP Client, Modbus RTU Master and Modbus
TCP Server/RTU Slave can all be supported simultaneously, and when combined with
the built in Modbus TCP to RTU convertor the WI-I/O 9-U2 can transfer I/O to/from
almost any combination of Modbus TCP or RTU devices.
The Modbus configuration is done using the Econfig or WI Mesh Utility depending on
what communication mode has been configured in the module.
The WI-I/O 9-U2 has pre-defined data areas for Inputs and Outputs as well as the
different I/O types, e.g. Bits, Words, Long, Floats, etc., which include the onboard
Input/Outputs and are shared for both Client and Server. For a full list of the available
I/O and address, locations please see section Appendix B: I/O Store Registers.
Modbus configuration screen is setup in
Tabs; each tab has the different
configuration parameters available for that
operation.
The two main Modbus configuration tabs are;
 ‘Modbus TCP Server & RTU Slave’ which is used for configuring any Modbus
TCP Server or RTU Slave parameters.
 ‘Modbus TCP Client & RTU Master’ which is use for any Modbus TCP Client and
Modbus RTU Master Configuration parameters.
Modbus TCP Server & RTU Slave
‘Modbus TCP Server enabled’ allows the WI-I/O 9-U2 to accept connections from one
or more Modbus TCP Clients via Ethernet or RTU Masters via the RS485 or R232 serial
interfaces. All Modbus transactions routed to the onboard Modbus TCP Server/RTU
Slave are directed to/from the onboard general purpose I/O registers. The Modbus TCP
Server is shared with the Modbus TCP to RTU converter
, so that the Modbus “Device
Figure 55 - Modbus Configuration