The safety status shows only when the safety controller is online. See Online Workspace. The safety status can show:
Safety partner is missing or unavailable (SIL 3) - Partnership fault displays in
the Safety tab. Also pre-deployment check fails if you attempt to deploy in this
scenario.
Safety partner hardware is incompatible with the primary controller -
Partnership fault displays in the Safety tab. Also pre-deployment check fails if
you attempt to deploy in this scenario.
Safety partner firmware is incompatible with the primary controller -
Partnership fault displays in the Safety tab. Also pre-deployment check fails if
you attempt to deploy in this scenario.
Safety task inoperable. - This status is a major safety fault and you are
notified in the Safety tab. Existing fault indications in the Execution Explorer
are also applied.
Safety task OK. - No fault or error is reported.
Except for safety task OK, the descriptions indicate that safety faults exist,
which you must resolve to proceed.
IMPORTANT:
The status of the safety partner shows on
the Safety Partner Information tab of the Device profile of the safety controller
only when the safety controller is online.
Safety Partner Status
Monitor Safety Connections
Input tags have status members that are called ConnectionFaulted and RunMode to
monitor input connections.
The ConnectionFaulted value indicates whether the safety connection between the
safety producer and the safety consumer is Valid (0) or Faulted (1). If
ConnectionFaulted is set to Faulted (1) for any reason, the safety data goes to a
predefined safe state, and the RunMode value is set to Idle State (0).
The RunMode value indicates if a device in Run Mode (1) or Idle State (0) is actively
updating consumed data. Idle state is indicated if the connection is closed, the
safety task is faulted, or the remote controller or device is in Program mode or
Test mode. For safety I/O connections, the RunMode is always inverse the
ConnectionFaulted status. It does not provide unique data.
The following table describes the combinations of the ConnectionFaulted and RunMode
states.
Safety Connection Status
ConnectionFaulted Status
RunMode Status
Safety Connection Operation
0 = Valid
1 = Run
The producing device is actively controlling data. The producing
device is in Run mode.
0 = Valid
0 = Idle
Invalid for safety I/O connections.
1 = Faulted
0 = Idle
The safety connection is faulted. The state of the producing
device is unknown. The safety data goes to a predefined safe
state and the RunMode value is set to Idle State (0).
1 = Faulted
1 = Run
Invalid state.
If a device is inhibited, the ConnectionFaulted bit is set to Faulted (1) and the
RunMode bit is set to Idle (0) for each connection associated with the device. As a
result, the safety data goes to a predefined safe state.
Utilizing Status
Connection Status (.ConnectionFaulted) is the status of the safety input connection
between the safety controller and safety I/O module. When the connection is
operating properly, this bit is LO (0). When the connection is NOT operating
properly, this bit is HI (1). When the connection status is HI (connection not
operating properly), the input tag values are set to a predefined safe state and
considered invalid data.
Point Status is available for safety inputs (.Ptxx.Status). When a point status tag
is HI (1), it indicates that individual channel is functioning and wired correctly,
and that the safety connection between the safety controller and the safety I/O
module on which this channel resides is operating properly.
Whether combined status or point status is used is application-dependent. Point
status simply provides more granular status.
The dual-channel safety instructions have built-in safety I/O status monitoring.
Input status and Output status are parameters for the safety input and output
instructions. The DCS instruction (and other dual-channel safety instructions) has
input status for input channels A and B. The CROUT instruction has input status for
Feedbacks 1 and 2, and has output status for the output channels that the CROUT
outputs O1 and O2 drive. The status tags used in these instructions must be HI (1)
for the safety instruction output tags (O1 for input instructions and O1/O2 for
CROUT) to be energized.
For proper safety instruction operation, it is important to drive the input status
and output status tags BEFORE/ABOVE the safety instruction as shown in the following
figure.
Instruction Examples
When you use instructions, such as XIC and OTE, you are responsible for interrogating
the safety I/O status:
Before you use a safety input channel as an interlock, verify that the safety
input channel status is HI (1).
Before you energize a safety output channel, verify that the safety output
channel status is HI (1).
