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

AutoMax DCSNet/RE RIO Module Page 7
Publication number 56AMXN-UM002A-EN-P November 2002
• Supports up to 248 words of scheduled output data and 250 words of
scheduled input data
• Maintains diagnostic counters
As either a DCS master or slave, the module supports bridging, which
means that it can obtain its transmit data for any drop from another
56AMXN module in the same chassis.
You can use a DDE or OPC server, such as RSLinx, capable of accessing
the ControlLogix backplane, to access the DCS data directly on the
56AMXN. The module "emulates" PLC-5 integer files 100-155. Each
file corresponds to a DCS drop.
A watchdog timer is implemented in the module’s hardware. If the
firmware does not kick the watchdog within the timeout period the
watchdog times out and places the module into a safe fatal failure state.
A jabber inhibit timer is implemented in the module’s hardware. If the
network transmitter is on longer than 150% of the longest network frame
time, the jabber inhibit forces the transmitter off and places the module
into a safe fatal failure state.
The module firmware can be updated using ControlFlash.
Differences from the 56AMXN/A
For DCS Master and Slave operation, there is now an RSLogix 5000
56AMXN Module Profile. You configure the module as a 56AMXN in
RSLogix 5000, not using the 1756-MODULE generic module profile.
This results in better diagnostics for the 56AMXN in RSLogix 5000.
The 56AMXN/B can exchange much more scheduled data with the
ControlLogix processor than the 56AMXN/A could.
The DCS Master or Slave configuration data is stored with the RSLogix
5000 program. No separate DCS configuration file or configuration
program is required. It also makes the use of the configuration signature
unnecessary.
Remote I/O configuration is unchanged. You configure the 56AMXN
using the Generic Module profile in RSLogix 5000 and use the
56AmxnRioCfg program to configure the module.
The way the 56AMXN/B handles outputs in program mode and on loss
of connection is different from the way they were handled by the
56AMXN/A.
In DCS master or slave operation, if the ControlLogix was in program
mode, outputs from the 56AMXN/A continued to be updated with the
current values from the ControlLogix. If there was a loss of connection
between the ControlLogix processor and the 56AMXN, outputs held
their last state.