Discrete output point object special requirements, Dop instances 3 and 4 special behavior – Rockwell Automation 284 ArmorStart User Manual User Manual
Page 390
C-18
Bulletin 283 CIP Information
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, 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 used in a DeviceLogix program behaves much
the same as in the DeviceNet Specification. One notable addition to
DOP behavior for the ArmorStart implementation is that Protection
Fault Action and Protection Fault Value attributes determine the
behavior of the DOP when the ArmorStart faults on a protection fault.
The following State Transition Diagram is used for DOP Instances 3
and 4 when they are not in use in a DeviceLogix Program.
Figure C.1 State Transition Diagram — Unbound DOP Instances 3 and 4
Non-Exi
s
t
a
nt
Av
a
il
ab
le
Idle
Re
a
dy
R
u
n
DNet F
au
lt
Protection F
au
lt
Receiv
e Idle
Protection F
au
lt
DNet F
au
lt
DNet F
au
lt
DNet
F
au
lt
Protection F
au
lt
DNet
Idle
Receiv
e
D
a
t
a
Connection Tr
a
n
s
ition
s
to E
s
t
ab
li
s
hed
Power On
Connection T
r
a
n
s
ition
s
to E
s
t
ab
li
s
hed
Protection F
au
lt
Protection F
au
lt Re
s
et