DriverMUX Addressing

The address used by an I/O tag may or may not need to change when the DriverMUX tag switches between drivers.  The following three scenarios are provided to help you with I/O addressing.

 

Scenario 1:  Two lines of communication are set up between a PLC in the field and VTS:  one uses radio and the other uses a modem.

In this case, tag addressing is simple: The address is defined by the PLC device and does not change with the communication driver.

 

Scenario 2:  Connecting to different RTUs.

For this scenario, the tag addressing used by the primary driver will be different from that used by the secondary. By way of example, perhaps one used Allen Bradley equipment and the other uses Modicon.

In this case, an I/O Tag will have to reference its intended data location by two completely different addresses.  The address parameter of the I/O tag must therefore contain both addresses where each address is given inside curly braces and are given in the order of the Primary and Secondary subordinate drivers.

Ex.   {Primary Address}{Secondary Address}

 

Scenario 3:  A subordinate driver is also a DriverMUX tag, and each driver requires a different address for the I/O devices.

In this scenario, the addresses in each I/O tag will be nested in curly braces where the left to right order matches the primary to secondary configuration of the DriverMUX configuration:

 

Ex. {Primary Address}{{Secondary Address}{Tertiary Address}}