Rockwell Automation 294D ArmorStart LT Distributed Motor Controller DeviceNet Version - User Manual - Manual (Page 204)

204 Rockwell Automation Publication 290D-UM001A-EN-P - June 2012
Appendix B CIP Information
CIP Explicit Connection
Behavior The ArmorStart LT allows run, jog and user outputs to be driven by connected
explicit messages when no I/O connection exists, or when a I/O connection
exists in the idle state. a single EtherNet/IP Class 3 explicit connection will be
allowed to send “explicit control” messages via an “Active Explicit” connection.
An EtherNet/IP Class 3 explicit connection becomes the “explicit control”
connection when it becomes the first EtherNet/IP Class 3 explicit connection to
send a “set” service to one of the following:
• The “value” attribute of any Discrete Output Point (DOP) instance (Class
Code 0x09).
• The “data” attribute of any output (consumed) Assembly instance (Class
Code 0x04).
• Attribute 3 or 4 of the Control Supervisor Object (Class Code 0x29).
EDS Files
The information contained in the EDS (Electronic Data Sheet) files for
ArmorStart LT DeviceNet can be extracted via the network.
CIP Object Requirements The following CIP objects will be covered in the following subsections:
Class Object
0x0001 Identity Object
0x0002 Message Router
0x0003 DeviceNet
0x0004 Assembly Object
0x0005 Connection Manager Object
0x0008 Discrete Input Point Object
0x0009 Discrete Output Point Object
0x000A Analog Input Point
0x000B Analog Output Point
0x000F Parameter Object
0x0010 Parameter Group Object
0x001D Discrete Input Group Object
0x001E Discrete Output Group Object
0x0029 Control Supervisor
0x002C Overload Object
0x0097 DPI Fault Object
0x098 Alarm Object
0x0376 Trip and Warning Email Object
0x032F Email Object