De-Energize To Trip System; Use Connection Status Data To Initiate A; Fault Programmatically - Allen-Bradley GuardLogix 5580 Original Instructions Manual

De-energize to Trip System

Use Connection Status Data
to Initiate a Fault
Programmatically
Studio 5000 Logix Designer Application,
Version 31 or Later, Safety-application
Instructions
Topic
De-energize to Trip System
Use Connection Status Data to Initiate a Fault Programmatically
IMPORTANT We recommend use of general safety-application instructions
page 69) rather than the instructions detailed in this appendix.
All safety input values that are associated with a particular connection are set to
safe state when a CIP Safety connection fault condition is detected. When
using diverse input pairs, one of the inputs uses a value of one to initiate the
safety function. This requires safety logic that evaluates fault conditions, so
that the safety function is executed when an input fault occurs (even though
the input value remains at zero).
The following diagrams provide examples of the application logic that is
required to latch and reset I/O failures. The examples show the logic necessary
for input only modules, and for input and output combination modules. The
examples use the Combined Status feature of the I/O modules, which presents
the status of all input channels in one Boolean variable. Another Boolean
variable represents the status of all output channels. This approach reduces the
amount of I/O conditioning logic that is required and forces the logic to shut
down all input or output channels on the affected module.
Use the Input Fault Latch and Reset Flowchart on page 98
rungs of logic are required for different application situations.
Example 1 on page 99
while a fault condition exists. If the actual input state is required for
troubleshooting while the input failure is latched, use the logic shown in
Ladder Diagram Example 2 on page
represent the inputs to be used in the application logic. While the input failure
is latched, the internal tags are set to their safe state. While the input failure is
not latched, the actual input values are copied to the internal tags.
Use the Output Fault Latch and Reset Flowchart on page 101
which rungs of application logic in
required.
Rockwell Automation Publication 1756-RM012B-EN-P - April 2018
shows logic that overwrites the actual input-tag variables
100. This logic uses internal tags that
Ladder Diagram Example 3 on page 101
F
Appendix
Page
97
97
(Table 5 on
to determine which
Ladder Diagram
to determine
are
97