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

Rockwell Automation Publication 290D-UM001A-EN-P - June 2012 221
CIP Information Appendix B
All instances contain the following attributes:
The following common services will be implemented for the Discrete Output
Point Object:
Discrete Output Point Object Special Requirements
There are many sources that can affect an output point's value: an I/O message,
an explicit message, local logic, network fault and idle conditions, and protection
fault conditions. An output point must know how to select which source of data
to use to drive its value attribute.
An output that is not bound behaves much the same as in the DeviceNet
Specification. Two notable additions to unbound DOP behavior for the
Intimidator implementation are:
• Explicit control of the value attribute via Explicit messages is constrained
by the Touch Algorithm
• Protection Fault Action and Protection Fault Value
Attribute ID Access Rule Name Data Type Value
3 Get Value BOOL 0 = OFF, 1 = ON
5 Comm Fault Action BOOL 0=Comm Fault Value, 1=Hole Last State
6 Comm Fault Value BOOL 0 = OFF, 1 = ON
7 Comm Fault Action BOOL 0=Comm Fault Value, 1=Hole Last State
8 Comm Fault Value BOOL 0 = OFF, 1 = ON
113 Prot Fault Action BOOL 0=Flt Value, 1=Ignore These attributes are not
settable in instances
1,2,9 or 10
114 Prot Fault Value BOOL 0 = OFF, 1 = ON
115 Get/Set Force Enable BOOL 0=Disable, 1=Enable
116 Get/Set Force Value BOOL 0 = OFF, 1 = ON
117 Get/Set Input Binding
STRUCT:
USINT
Array of USINT
Size of appendix I encoded path
Appendix I encoded path
NULL path means attribute 3 drives the output.
Otherwise, this is a path to a bit in the Bit Table.
Service Code
Implemented for:
Service Name Class Instance
0x0E Yes Yes Get_Attribute_Single
0x10 No Yes Set_Attribute_Single