User manual
Chapter Three Operation
Page 53 March 2010
Since the WI-MOD-9-E supports ModBus TCP Client and Server simultaneously, the ModBus
TCP Server for unit B above could also be enabled. This would allow one (or more) external
ModBus TCP Clients anywhere on the extended wired or wireless network to connect to unit B
and monitor the status of the I/O registers – including the I/O at units A, C, and D. This is a very
powerful and flexible feature which could, for example, be exploited by a central monitoring
facility or SCADA.
The configurable ModBus I/O transfer options are summarized in the tables below.
ModBus TCP Configuration:
Enable ModBus TCP
Server (Slave)
Check this box to enable the onboard ModBus TCP Server. All ModBus
TCP connections to the module IP Address and specified ModBus
Server Device ID will be routed to the onboard I/O registers.
ModBus Server Device ID Specify the ModBus Device ID for the onboard ModBus TCP Server.
Allowed values are 0 to 255.
Enable ModBus TCP Client
(Master)
Check this box to enable the onboard ModBus TCP Client. I/O to be
transferred via the ModBus TCP client is specified with ModBus TCP
Client Mappings.
ModBus Client Scan Rate Enter the delay (in milliseconds) between execution of consecutive
ModBus TCP Client Mappings to the same Server.
Reset Registers on
Comm.’s Fail
When Enabled the value in any onboard I/O register will be reset to zero
if a valid ModBus transaction directed to/from the given register has not
been completed for longer than the Comm.’s Fail Timeout.
Comm.’s Fail Timeout The period of time after which onboard I/O registers will be reset if a
valid ModBus transaction directed at that register has not completed.
ModBus TCP Client Mappings:
Local Register Enter the starting onboard I/O register number that the specified
ModBus Master transaction will transfer I/O to/from.
I/O Count Specify the number of consecutive I/O register to be transferred for the
specified transaction.
Function Code Specify the ModBus Function Code for the transaction.
Destination Register Enter the starting I/O register number in the destination device that the
specified ModBus Master transaction will transfer I/O to/from.
Device ID Enter the ModBus Device ID of the destination ModBus device
Server IP Address Specify the IP Address of the destination ModBus TCP Server for the
specified transaction.
Response Timeout Enter the timeout (in milliseconds) to wait for a response to the
specified transaction.
Comm.’s Fail Register Enter the onboard I/O Register number to store the communication
status of the specified transaction. The Specified register will be set to 0
if communications is successful, 0xFFFF if there is no connection to the
specified server, or 0xFFxx where xx is the ModBus Exception Code