For Block Transfers; Specify A Communication Method Or Module Address - Allen-Bradley Logix5000 Reference Manual

1756 controllogix, 1768 compactlogix, 1769 compactlogix, 1789 softlogix, 1794 flexlogix, powerflex 700s with drivelogix
Hide thumbs Also See for Logix5000:
Table of Contents

Advertisement

Chapter 4
Input/Output Instructions (MSG, GSV, SSV, IOT)
For block-transfers over this
network
ControlNet
Universal remote I/O
If the destination device is
Logix5000 controller
PLC-5 controller over an EtherNet/IP
network
PLC-5 controller over a ControlNet
network
SLC 5/05 controller
PLC-5 controller over a DH+ network DH+
SLC controller over a DH+ network
PLC-3 processor
PLC-2 processor
Application on a workstation that is
receiving an unsolicited message
routed over an EtherNet/IP or
ControlNet network through
RSLinx software
190

For Block Transfers

For block transfer messages, add the following modules to the I/O configuration
of the controller.
Add these modules to the I/O configuration
·
Local communication module (for example, 1756-CNB module)
·
Remote adapter module (for example, 1771-ACN module)
·
Local communication module (for example, 1756-DHRIO module)
·
One emote adapter module (for example, 1771-ASB module) for each rack, or portion of a rack, in
the chassis
·
Block-transfer module (optional)

Specify a Communication Method or Module Address

Use the following table to select a communication method or module address for
the message.
Then select
And specify
CIP
No other specifications required.
Channel
Source Link
Destination Link
Destination Node
If there is only one DH+ link and you did not use the RSLinx software to configure
the DH/RIO module for remote links, specify 0 for both the Source Link and the
Destination Link.
CIP with Source ID
Source Link
Destination Link
(This lets the application
receive data from a
controller.)
Destination Node
The slot number of the ControlLogix controller is used as the Source Node.
Rockwell Automation Publication 1756-RM003N-EN-P - October 2011
Channel A or B of the 1756-DHRIO module that is
connected to the DH+ network.
Link ID assigned to the backplane of the controller in
the routing table of the 1756-DHRIO module. (The
source node in the routing table is automatically the
slot number of the controller.).
Link ID of the remote DH+ link where the target device
resides.
Station address of the target device, in octal.
Remote ID of the topic in RSLinx software.
Virtual Link ID set up in RSLinx
software (0...65535).
Destination ID (0...77 octal) provided by the
application to RSLinx. For a DDE topic in RSLinx
software, use 77.

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents