Rockwell Automation 20-COMM-ER 20-COMM-ER Dual-Port EtherNet/IP Communication Adapter User Manual - Manual (Page 124)

124 Rockwell Automation Publication 20COMM-UM015B-EN-P - July 2013
Chapter 6 Using Explicit Messaging
The following table identifies the data that is required in each box to configure a
message to write a single parameter.
ControlLogix Controller Example Ladder Logic Program to Read or Write
Multiple Parameters, RSLogix 5000 Software, All Versions
Because the example ladder logic rungs, configuration screens, and request/
response data to read or write multiple parameters using RSLogix 5000 software,
all versions, are identical to those for RSLogix 5000 software, version 15.00 or
later, see the information contained on
page 112 through page 119 for complete
details.
MicroLogix 1100/1400
Controller Examples
When using RSLogix 500 software, version 7.10 and earlier, explicit messaging
must be performed using the PCCC N-File method. For RSLogix 500 software,
version 7.20 and later, the CIP messaging method has been added along with the
PCCC N-File method. However, it is recommended to use the CIP method
because it is easier to use and understand. For this reason, only instructions for
the CIP method are provided.
The CIP messaging method provides two ways to perform explicit messaging:
Configuration Tab Example Value Description
Message Type
Service Type (1)
Service Code (1)
Class
Instance (2)
Attribute (3)
Source Element
Source Length
CIP Generic
Set Attribute Single
10 (Hex.)
93 or 9F (Hex.) (5)
140 (Dec.)
9 or A (Hex.)
Accel_Time_1 (6)
2 (6)
Used to access the Parameter Object in the adapter.
This service is used to write a parameter value.
Code for the requested service.
Class ID for the DPI Parameter Object.
Instance number is the same as parameter number.
Attribute number for the Parameter Value attribute.
Name of the tag for any service data to be sent from the scanner or bridge to the adapter/drive.
Number of bytes of service data to be sent in the message.
Communication Tab Example Value Description
Path (4) My_PowerFlex_Drive The path is the route that the message will follow.
Tag Tab Example Value Description
Name Single_Write_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) The instance is the parameter number in the drive (Port 0). For example, to write to parameter 4 of a peripheral in Port 7 of an SMC-50 controller, the instance would
be 21504 + 4 = 21508. See DPI Parameter Object on page 198 (Class code 0x93) to determine the instance number.
(3) Setting the Attribute value to ‘9’ will write the parameter value to the drive’s Nonvolatile Storage (EEPROM) memory, which retains the parameter value even after
the drive is power cycled. Important: When set to ‘9’, the EEPROM may quickly exceed its life cycle and cause the drive to malfunction. Setting the Attribute value
to ‘A’ (10 decimal) will write the parameter value to temporary memory, which deletes the parameter value after the drive is power cycled. When frequent write
messages are required, we recommend using the ‘A’ (10 decimal) setting.
(4) Click Browse to find the path, or type in the name of the device listed in the I/O Configuration folder.
(5) See Table 17 on page 106 for limitations of PowerFlex 7-Class drives when using DPI Parameter Object Class code 0x93 for explicit messaging.
(6) In this example, Accel Time 1 is a 16-bit parameter requiring the tag Data Type field to be set to ‘INT’ when creating the controller tag. If the parameter being written
to is a 32-bit parameter, the tag Data Type field must be set to ‘DINT’. Also, the Source Length field on the Message Configuration screen must correspond to the
selected Data Type in bytes (for example, 4 bytes for a DINT or a REAL). When using a PowerFlex 700S drive, Accel Time 1 is a floating point number requiring the
Data Type field to be set to ‘REAL’ when creating the controller tag. See the drive documentation to determine the size of the parameter and its data type (16-bit or
32-bit integer or REAL).