Table of Contents
Advertisement
I/O Device Connection Status
The CIP Safety protocol allows the recipients of I/O data to determine the
status of that data:
• The controller detects input connection failures, which sets all input
data to the safe state and the associated input status to faulted.
• The output device detects output connection failures, which is
responsible for de-energizing its outputs.
• Generally, the safety controller also has input connections from output
devices; the safety controller determines the status of these input
connections, however the input connection status is not the primary
mechanism to de-energize the outputs.
IMPORTANT You are responsible for application logic to latch these I/O failures, and to
verify that the system restarts properly.
De-energize to Trip System
GuardLogix controllers are part of a de-energize to trip system, which means
that zero is the safe state. Some, but not all, safety I/O device faults cause all
device inputs or outputs to be set to safe state. Faults that are associated to a
specific input channel result in that specific channel being set to safe state; for
example, a pulse test fault that is specific to channel 0 results in channel 0 input
data being set to the safe state. If a fault is general to the device and not to a
specific channel, the combined status bit displays the fault status and all device
data is set to the safe state.
For information on how to use GuardLogix safety application instructions, see
Appendix F
on
page 97
Safety Set Reference Manual, publication 1756-RM095.
Rockwell Automation Publication 1756-RM012B-EN-P - April 2018
Monitor Status and Handle Faults
and the GuardLogix Safety Application Instructions
Chapter 7
65
Hide quick links:
Advertisement
Table of Contents
