Allen-Bradley Compact GuardLogix 5380, Original Instructions Manual

Page: 53 / 116

Rockwell Automation Publication 1756-RM012B-EN-P - April 2018 53
Safety Application Development Chapter 6
You can generate the safety signature if the following conditions are true:
• The Studio 5000 Logix Designer application is online with
the controller.
• The controller is in Program mode.
• The controller is safety-unlocked.
• The controller has no safety forces or pending online safety edits.
• The safety task status is OK.
Once the application program tests are complete, you must generate the safety
signature. The programming software automatically uploads the safety
signature after it is generated.
You can delete the safety signature only when the GuardLogix controller is
safety-unlocked and, if online, the key switch is in the REM or PROG
position. When Protect Signature in Run mode is checked, the controller does
not allow you to delete the safety signature in Run mode.
You cannot update the firmware when a safety signature exists.
When a safety signature exists, the following actions are not permitted within
the safety task:
• Online or offline programming or editing of safety components
• Forcing safety I/O
• Data manipulation of safety components (except through routine logic
or another GuardLogix controller)
Validate the Project
To check your application program for adherence to the specification, you
must generate a suitable set of test cases that cover the application. The set of
test cases must be filed and retained as the test specification.
You must include a set of tests to prove the validity of the calculations
(formulas) used in your application logic. Equivalent range tests are acceptable.
These are tests within the defined value ranges, at the limits, or in invalid value
ranges. The necessary number of test cases depends on the formulas that are
used and must comprise critical value pairs.
IMPORTANT When the safety application has been validated, there may be occasions
that require a redownload (such as editing the Standard application)
even though the Safety application has not changed.
To verify that the correct safety application is downloaded, manually
record the safety signature after initial creation and check the safety
signature after every download to make sure that it matches the original.