Rockwell Automation 20-COMM-E PowerFlex EtherNet/IP Adapter User Manual
Page 140
6-14
Using Explicit Messaging
20-COMM-E EtherNet/IP Adapter User Manual
Publication 20COMM-UM010G-EN-P
ControlLogix Controller – Formatting a Message to Read Multiple Parameters Using
RSLogix 5000 Software, Any Version
Figure 6.13 Scattered Read Message Configuration Screens
The following table identifies the data that is required in each box to
configure a message to read multiple parameters.
Configuration Tab
Example Value
Description
Message Type
Service Type
(1)
Service Code
Class
Instance
Attribute
Source Element
Source Length
Destination
CIP Generic
Custom
4b (Hex.)
93 or 9F (Hex.)
(3)
0 (Dec.)
0 (Hex.)
Scattered_Read_Request
(4)
Scattered_Read_Response
Used to access Parameter Object in the adapter.
Required for scattered messages.
Code for the requested service.
Class ID for the DPI Parameter Object.
Required for scattered messages.
Required for scattered messages.
Name of the tag for any service data to be sent from
scanner or bridge to the adapter/drive.
Number of bytes of service data to be sent in the message.
The tag where the data that is read is stored.
Communication Tab Example Value
Description
Path
(2)
My_PowerFlex_Drive
The path is the route that the message will follow.
Tag Tab
Example Value
Description
Name
Scattered_Read_Message
The name for the message.
(1)
The default setting for Service Type is ‘Custom’, enabling entry of a Service Code not available from the Service Type pull-down
menu. When choosing a Service Type other than ‘Custom’ from the pull-down menu, an appropriate Hex. value is automatically
assigned to the Service Code box which is dimmed (unavailable).
(2)
Click
Browse to find the path, or type in the name of the device listed in the I/O Configuration folder.
(3)
See
for limitations of PowerFlex 7-Class and PowerFlex 750-Series drives when using DPI Parameter
Object Class code 0x93 or Host DPI Parameter Object Class code 0x9F for explicit messaging.
(4)
In this example, we are reading five parameters. Each parameter being read requires an array of three INT registers. Therefore, a
controller tag was created with its Data Type field set to ‘INT[15]’. Also, the Source Length field on the Message Configuration
screen must correspond to the selected Data Type in bytes (for this example, 30 bytes for an INT[15] array). Scattered read
messages always assume that every parameter being read is a 32-bit integer, regardless of its actual data type. Maximum length
is 132 bytes or 66 words which equates to 22 parameters. For parameter numbering, see
DPI Parameter Object on page C-16