GuardLogix Safety Task Fault — Recovery & Safety Signature

Allen-Bradley · advanced · 40 min

A GuardLogix safety task fault holds the machine safe until you clear it correctly. Read the safety fault, fix the cause, clear the major fault in Studio 5000, and understand the Safety Signature rules.

⚠️ The safety task exists to keep people safe. Clear its faults by resolving the real cause and re-verifying the safety functions — never by removing monitoring or bypassing feedback.

What a safety task fault is

On an Allen-Bradley GuardLogix controller, the safety task runs your SIL 2 / PLd safety logic (per IEC 61508 / ISO 13849) separately from the standard task. A safety fault (including a Safety Partner fault on dual-controller systems) stops the safety task and drives the machine to the safe state. Recovery means reading the specific fault, fixing the cause, and clearing it the right way — not just clicking through it.

Read the fault

1. Go online in Studio 5000 Logix Designer.
2. View the faults. Open the controller's fault view — GuardLogix reports safety fault codes, and on redundant-safety systems a Safety Partner Fault if the safety partner is missing or mismatched. Note the exact fault.
3. Interpret it. Common classes: a safety I/O connection loss (a safety input/output module or device dropped its connection), a safety partner problem, or a program/logic fault in the safety task.

Fix the cause, then clear

1. Restore safety I/O. If a safety input/output connection was lost, check the module, its network, and the connected safety device. For output feedback faults, this is where feedback monitoring (SFX) matters — SFX verifies the actual state matches the commanded state, so a fault can indicate a welded contact or a stuck output that feedback monitoring correctly caught. Fix the device, don't defeat the monitoring.
2. Resolve a Safety Partner fault by ensuring the safety partner is present, healthy, and the firmware matches.
3. Clear the major fault. In Studio 5000 you can right-click the fault and choose "Clear Major Fault." The fault clears only if its cause is gone.

The Safety Signature

The Safety Signature is a hash that certifies the validated safety program. Two rules matter during troubleshooting:

• To generate a safety task signature, the controller must be in Program mode with no safety forces, no pending online safety edits, and no safety faults — the safety status must read Safety Task OK. So you cannot re-sign until the fault is truly cleared.
• Unlocking the controller removes the signature lock, but the existing signature remains attached to the safety routines until explicitly cleared; safety routines can't be edited while signature data exists.

Step-by-step

1. Go online; view the safety fault code (and Safety Partner status).
2. Fix the named cause — safety I/O connection, a stuck/welded output caught by SFX feedback, or a partner/firmware issue.
3. Clear Major Fault in Studio 5000.
4. Confirm Safety Task OK.
5. If you edited safety logic, re-validate the safety functions and re-generate the safety signature (requires Program mode, no forces/edits/faults).

Never do this

Never remove feedback monitoring, force a safety output, or edit signed safety logic without a validation process to make a fault go away. A GuardLogix safety fault that keeps returning is telling you a real device or connection is bad.