Publication 20D-UM002C-EN-P - November 2003
6-30 Communicating with Devices on an EtherNet/IP Link
The PLC-5 controller supports logical ASCII addressing so you do not have to
map a compatibility file for MSG instructions initiated by a PLC-5 controller.
Place the DriveLogix tag name in double quotes (“).
Example 3: Total connections required by DriveLogix1
The following table calculates the connections used in this example.
If you configured the local I/O modules as rack-optimized, you would only
need the DIN-rail connection to the I/O modules, reducing the above
example by 3 connections.
Typed Write SINT or INT tag any integer element (such as B3:0,
T4:0.ACC, C5:0.ACC, N7:0, etc.)
REAL tag any floating point element (such as F8:0,
PD10:0.SP, etc.)
Word Range Read any data type (such as B3:0, T4:0, C5:0,
R6:0, N7:0, F8:0, etc.)
SINT, INT, DINT, or REAL
Word Range Write SINT, INT, DINT, or REAL any data type (such as B3:0, T4:0, C5:0,
R6:0, N7:0, F8:0, etc.)
Type of Logix MSG instruction: Source: Destination:
Type of MSG Instruction: Example Source and Destination:
PLC-5 writes to DriveLogix source element N7:10
destination tag “array_1”
PLC-5 reads from DriveLogix source tag “array_1”
destination element N7:10
Connection: Amount:
DriveLogix1 controller to 3 local I/O modules
rack-optimized connection for the DIN rail
direct connection for each I/O module
1
3
DriveLogix1 controller to local 1788-ENBT 0
connected, cached MSG from DriveLogix1 to Control1 1
connected, cached MSG from DriveLogix1 to PLC-5E1 1
total connections used: 6
