Discrete output point object special requirements – Rockwell Automation 284G ArmorStart - User Manual User Manual
Page 270
C-20
Bulletin 284G CIP Information
The following common services are implemented for the Discrete
Output Point Object
Table C.47 Discrete Output Common Services:
Discrete Output Point Object
Special Requirements
DOP Instances 3 and 4 Special Behavior
There are many sources that can affect an output point’s value: an I/O
message, and 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. One notable addition to DOP behavior for
the ArmorStart implementation is the Protection Fault Action and
Protection Fault Value attributes determine the behavior of the DOP
when the ArmorStart faults on a protection fault.
Service
Code
Implemented for
Service
Name
Class
Instance
0x0E
No
Yes
Get_Attribute_Single
0x10
No
Yes
Set_Attribute_Single