User manual

Publication 1756-RM093F-EN-P - January 2010 57
Safety Application Development Chapter 6
Generate the Safety Task Signature
The safety task signature uniquely identifies each project, including its
logic, data, and tags. The safety task signature is composed of an ID
(identification number), date, and time.
You can generate the safety task signature if all of the following
conditions are true:
• RSLogix 5000 software 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 application program testing is complete, you must generate the
safety task signature. The programming software automatically
uploads the safety task signature after it is generated.
You can delete the safety task signature only when the GuardLogix
controller is safety-unlocked and, if online, the keyswitch is in the
REM or PROG position.
When a safety task 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 (except through routine logic or another
GuardLogix controller)
Project Verification Test
To check the application program for adherence to the specification,
you must generate a suitable set of test cases covering the application.
The set of test cases must be filed and retained as the test
specification.
IMPORTANT
To verify the integrity of every download, you must manually
record the safety task signature after initial creation and check
the safety task signature after every download to make sure
that it matches the original.