![Rockwell Automation Allen-Bradley DriveLogix 5730 User Manual Download Page 120](http://html.mh-extra.com/html/rockwell-automation/allen-bradley-drivelogix-5730/allen-bradley-drivelogix-5730_user-manual_1475407120.webp)
6-22
Communicating with Devices on an EtherNet/IP Link
The following table shows example source and destination tags and
elements for different controller combinations.
When the DriveLogix5730 controller initiates messages to PLC or SLC
controllers, you do not have to map compatibility files. You enter the data
table address of the target device just as you would a tag name.
SLC 5/05 controllers, SLC 5/04 controllers (OS402 and above), and SLC 5/
03 controllers (OS303 and above) support logical ASCII addressing and
support PLC/SLC mapping (see the examples above). For all other SLC or
MicroLogix1000 controllers, you must map a PLC-2 compatibility file (see
the PLC-2 examples above).
Type of MSG Instruction:
Example Source and Destination:
PLC-5 writes to DriveLogix5730
SLC writes to DriveLogix5730
SLC 5/05
SLC 5/04 OS402 and above
SLC 5/03 OS303 and above
source element
N7:10
destination tag
“array_1”
The PLC-5, PLC-3, and SLC controllers support logical ASCII addressing so you do not have to
map a compatibility file for MSG instructions initiated by a PLC-5, PLC-3, or SLC controller. Place
the DriveLogix5730 tag name in double quotes (“).
You could optionally map a compatibility file. For example, if you enter
10
for the compatibility file,
you enter
N10:0
for the destination tag.
PLC-2 writes to DriveLogix5730
source element
010
destination tag
200
The destination tag is the three-digit PLC-2 address you specified for PLC-2 mapping.
PLC-5 reads from DriveLogix5730
SLC reads from DriveLogix5730
SLC 5/05
SLC 5/04 OS402 and above
SLC 5/03 OS303 and above
source tag
“array_1”
destination element
N7:10
The PLC-5, PLC-3, and SLC controllers support logical ASCII addressing so you do not have to
map a compatibility file for MSG instructions initiated by a PLC-5, PLC-3, or SLC controller. Place
the DriveLogix5730 tag name in double quotes (“).
You could optionally map a compatibility file. For example, if you enter
10
for the compatibility file,
you enter
N10:0
for the source tag.
PLC-2 reads from DriveLogix5730
source tag
200
destination element
010
The source tag is the three-digit PLC-2 address you specified for PLC-2 mapping.
Summary of Contents for Allen-Bradley DriveLogix 5730
Page 6: ...4 ...
Page 10: ...p 4 Notes ...
Page 22: ...1 12 What is DriveLogix5730 Notes ...
Page 68: ...3 20 Placing and Configuring Local I O Notes ...
Page 134: ...6 36 Communicating with Devices on an EtherNet IP Link Notes ...
Page 182: ...9 10 Communicating with Devices on a DH485 Link Notes ...
Page 200: ...B 10 Access Procedures Notes ...
Page 205: ......
Page 206: ......
Page 207: ......