Rockwell Automation Allen-Bradley DriveLogix 5730 User Manual page 117

MSG instruction to keep the connection open (cache) or to close it after
sending the message.
This type of MSG:
CIP data table read or write
PLC-2, PLC-3, PLC-5, or SLC
(all types)
CIP generic
block-transfer read or write
(1)
You can connect CIP generic messages, but for most applications, we recommend you leave CIP generic messages unconnected.
The update time of local I/O modules may increase when the controller is
bridging messages.
Important: Bridging over the DriveLogix5730 controller should be
Communicating with Another Logix-based Controller
All Logix-based controllers can use MSG instructions to communicate with
each other. The following examples show how to use tags in MSG
instructions between Logix-based controllers.
Type of MSG Instruction:
Logix-based controller writes to Logix-based
controller
(CIP Data Table Write)
Logix-based controller reads from
Logix-based controller
(CIP Data Table Read)
The source and destination tags:
• must be controller-scoped tags.
• can be of any data type, except for AXIS, MESSAGE, or
MOTION_GROUP.
Communicating with other controllers over EtherNet/IP
The DriveLogix5730 controller also uses MSG instructions to communicate
with PLC and SLC controllers. The MSG instructions differ depending on
which controller initiates the instruction.
Communicating with Devices on an EtherNet/IP Link
Using this communication
method:
CIP
CIP
CIP with Source ID
DH+
CIP
na
targeted toward applications that are not real time dependent,
such as RSLogix 5000 program downloads and ControlFlash
updates.
Uses a Which you
connection: can cache:
X X
X X
X X
X
(1)
X X
X X
Example Source and Destination:
source tag array_1
destination tag array_2
source tag array_1
destination tag array_2
6-19