Rockwell Automation 20-COMM-E PowerFlex EtherNet/IP Adapter - Manual (Page 94)

5-2 Using the I/O
20-COMM-E EtherNet/IP Adapter User Manual
Publication 20COMM-UM010G-EN-P
Understanding the I/O Image
The terms ‘input’ and ‘output’ are defined from the controller’s point of
view. Therefore, output I/O is data that is produced by the controller and
consumed by the adapter. Input I/O is status data that is produced by the
adapter and consumed as input by the controller. The I/O image will vary
based on the following:
• Size (either 16-bit or 32-bit) of the Reference/Feedback words and
Datalink words used by the drive. To determine the size of the
Reference/Feedback and Datalinks, view adapter Parameters 18 - [Ref/
Fdbk Size] and 19 - [Datalink Size]. For information to access
parameters, see
Using the PowerFlex 7-Class HIM to Access
Parameters on page 3-2 .
• Configuration of I/O (Parameter 23 - [DPI I/O Cfg]). If all I/O is not
enabled, the image is truncated. The image always uses consecutive
words starting at word 0.
• ControlLogix/CompactLogix Controllers only—The drive profile
used in RSLogix 5000 software (drive Add-on Profile in version 16.00 or
later, Classic Profile in versions 13.00…15.00, or Generic Profile in all
versions).
ControlLogix Controller Image
Because the drive Add-on Profile in RSLogix 5000 software, version 16.00
or later, and the Classic Profile, versions 13.00…15.00, provide descriptive
controller tags, the I/O image (tag size and location) is automatically
configured based on the drive being used. When using the Generic Profile
(
page 4-16 ) in RSLogix 5000 software, however, controller tags are not
descriptive or defined.
The ControlLogix controller I/O image changes depending on the size of
the drive’s Reference/Feedback and Datalinks, and the number of Datalinks
used.
Table 5.A , Table 5.B , and Table 5.C show the I/O image when using
various PowerFlex drives, and all Datalinks enabled.