Rockwell Automation 56AMXN/B ControlLogix AutoMax Comm Module - Manual (Page 32)

Page 32 AutoMax DCSNet /RE RIO Module
Publication number 56AMXN-UM002A-EN-P November 2002
Using the DCS Configuration Program
The DCS Configuration program was used for the 56AMXN/A to
configure the drop data mapped to scheduled data.
You do not need to use the DCS Configuration program to configure
drops scanned by the 56AMXN/B. Drop configuration is done by
writing to the module’s Configuration tag in RSLogix 5000.
The only purpose for using the configuration program is to configure
DCS bridging.
DCS Bridging
Normally the 56AMXN module gets the data it transmits for any drop
from the ControlLogix output registers mapped to that drop. This is true
whether the module is a DCS master or DCS slave.
The 56AMXN module also supports another method of obtaining the
data it transmits. This method is called bridging. A bridged node obtains
its transmit data for a drop from another 56AMXN module (and
therefore usually from another AutoMax DCS network). The module
from which it obtains the data is called the source module.
Figure 11 DCS Bridging
In the diagram, the module in slot 9 is bridged to the module in slot 4. It
obtains data from Network 1 and transmits in on Network 2.
The data can come from DCS registers from any drop on the source
module.
You can use bridging whether the module is a DCS master or a DCS
slave.
The modules must be in the same rack.
Here’s how it works… When the module is updating the drop before the
bridged drop, it sends a message to the source module for the data. The
reply comes back in time for the module to send out the data when it