Rockwell Automation 1756-RIO ControlLogix Remote I/O Communication Interface Module User Manual - Manual (Page 51)

Publication 1756-UM534B-EN-P - November 2010 51
Configure Scanner Mode Chapter 2
Map I/O Data You must map the I/O data to locations in the ControlLogix controller input
and output data before you can scan the Remote I/O network.
Mapping connects locations in the ControlLogix input and output tags to
locations on the Remote I/O network (discrete data on racks and block
transfer reads and writes.)
Connections (produced/consumed) occur between the 1756-RIO module and
the ControlLogix controller. They are point-to-point links between two end
points.
Produced/consumed tag data is the information that gets passed back and
forth over the line between the two end points.
There are up to 10 blocks of produced/consumed tag data. Discrete and block
transfer tag data gets ‘packed’ into the ControlLogix produced/consumed
data. When discrete and block transfer tag data are mapped, or when the
configuration tool ‘auto maps’ the data for you, you are selecting which of
those blocks the tag data is mapped to, and the offset in the block where the
tag data is found.
See Scanner Mode I/O Map on page 129.
When mapping is complete, you must export the aliases to the 1756-RIO
module and import the configuration to the RSLogix 5000 project.
See Aliases on page 84 , for a complete discussion of exporting and importing
aliases.
IMPORTANT
It is essential that the control program on the host controller
matches the addresses in the mapping configuration on the
1756-RIO module, otherwise the control program may
inadvertently write to the incorrect I/O locations. If you change
the data mappings on the 1756-RIO module, make sure that the
control program uses the correct addresses.