User manual

105G Wireless Gateway User Manual

Elpro_man_105g_1.18.doc Page 62

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 105U I/O module could map a remote input to I/O Reg 743. At the 105G,

the host device could read I/O Reg 743, and you could also configure a block mapping including

this register to another 105G. You could write a block I/O Reg 700 – 800 to another 105G.

4.5.8 Block Mappings to internal I/O Registers.

Firmware version 1.80 and later:

Using the Block mapping feature this will allow sending block write mapping to self. This could

be useful if wanting to have a global output to indicate a comms problem from any remote

module by block mapping the internal status registers to a local output.

4.5.9 Comms Fail for Block Mappings

Each block mapping has an associated mapping number. Up to 500 block mappings may be

entered. A status register is maintained for each block mapping. The most significant bit of this

If a block mapping does not receive an acknowledgement from the remote module, then the

comms fail status is set - this can be monitored by the host device.

4.5.10 “Repeater-only” Configuration

Any 105G module can act as a repeater unit. However a 105G may need to be installed as a

repeater only (that is, there is no host device connected). In this case, the base 105G, the 105G-

MD1 unit would normally be used as this is the lowest cost of the 105G modules.

A 105G can be configured as a “Repeater-only” unit. The advantages are:

 the serial port will then provide on-line diagnostics (instead of off-line diagnostics), or

 Serial expansion I/O modules can be connected to the serial port - normally an MD1 could

not be used as the serial ports would already be in use by the protocol device, e.g. PLC, etc.