Mixing Normal Mappings And Block Mappings; Block Mapping To Internal I/O Registers - Weidmuller WI-GTWY-9 User Manual

WI-GTWY-9-xxx Wireless Gateway V1.18
In the above example WI-GTWY-9#1 is performing a Block Read Request to WI-GTWY-9#2.
WI-GTWY-9#1 will send a block mapping request to WI-GTWY-9#2 who will then send a
block mapping from its I/O registers 52 for a count of 10 to WI-GTWY-9#2 I/O registers 52 –
61. This Block read will be performed using the real time clock at 10-minute intervals. A
response timeout of 5 seconds is used to indicate that if the Block read values have not been
received in 5 seconds then the Comms Fail bit for this block read mapping will be set.
It is not recommended to have the Response Timeout set to 0 seconds as a Comms fail bit will be
set upon transmission.
If the Response Timeout is greater than the Block mapping time period and radio's are in a High
traffic or poor radio path then instances could occur that received messages could be from
previous block read mapping's hence giving incorrect values.
If a need for frequent communications between modules is required then Block Write mapping's
would be more suitable.

4.5.7 Mixing Normal Mappings and Block Mappings

Block mappings can include I/O Registers already used with normal I/O mappings.
For example, a remote WI-I/O 9-x I/O module could map a remote input to I/O Reg 743. At the
WI-GTWY-9-xxx, the host device could read I/O Reg 743, and you could also configure a block
mapping including this register to another WI-GTWY-9-xxx. You could write a block I/O Reg
700 – 800 to another WI-GTWY-9-xxx.

4.5.8 Block mapping to Internal I/O registers

Firmware version 1.80 and later:
63