I and o tags, Data tags – Rockwell Automation 56AMXN/B ControlLogix AutoMax Comm Module User Manual

Page 20

Page

AutoMax DCSNet /RE RIO Module

Publication number 56AMXN-UM002A-EN-P November 2002

For example, you can inhibit the connection, then remove the inhibit to
break and remake all connections.

I and O Tags

The I and O tags are associated with the broadcast connection. The
contents vary depending on whether the 56AMXN is a DCS master or
slave.

DCS Master

The I tag contains a single DINT, Fault, which is 1 if no slaves are
connected and is 0 otherwise.

In addition, the fault is -1 (16#FFFF FFFF) if the connection is not
active. This could be because the module is not present, is inhibited, or
was configured incorrectly (wrong slot, missing or incorrect parameters,
etc.)

The O tag consists of the 8 INTs of Data, the 8 words of broadcast data
that the 56AMXN sends on DCSnet.

DCS Slave

The I tag consists of a single DINT, Fault, which is 1 if the master is not
active on the network and is 0 otherwise, and 8 INTs of Data, the 8
words of broadcast data the master is sending on DCSnet.

There is no O tag for a DCS slave.

Data Tags

Drop data appears in the I0-I7 and O0-O7 data tags. The number of tags
depends on the Comm Format. Each tag consists of 7 blocks. The
contents of each block are determined by the config tag.

The Input tags consist of a DINT Fault and 7 blocks of data. Each block
consists of 32 INTs of drop data.

The Output tags consist of a set of blocks, each of which consists of 32
INTs of data.

For example, if the module is a DCS master in slot 7 and the Comm
Format is Master – 56 drops and you write 30 to
Local:7:C.InputDropMap[4].Block[1] and
Local:7:C.OutputDropMap[4].Block[1], the drop data for drop 30 will
appear in data tags Local:7:I4.Block[1].Data and
Local:7:O4.Block[1].Data.

Input Fault Bits

The following table shows how the bits in the Fault DINT are used.

This manual is related to the following products:

1756 ControlLogix AutoMax Comm Module