Generate the Safety Signature
The safety signature is composed of a safety signature ID (identification number), and a time
stamp (date and time). The safety signature ID applies to the entire safety portion of the
controller application and uniquely identifies each application, including its logic, and configuration.
ATTENTION:
The safety signature is required for the controller
to operate at a SIL 2 or SIL 3 rating. Controller operation without a safety signature is only
suitable during development.
You can generate the safety signature if the following conditions are true.
- The programming software is online with the controller.
- The controller must be in Program/Remote Program mode.IMPORTANT: You must ensure that the Program mode state of any output does not cause an unsafe condition.
- The controller is safety-unlocked.
- The safety task status is OK.
- The controller does not already have a safety signature. You must delete an existing safety signature before another can be generated.
The programming software automatically uploads the safety signature after it is
generated.
IMPORTANT:
When the safety application is validated, there can be occasions that require redeployment
(such as editing the standard application) even though the safety application has not
changed.
To verify that the correct safety application is deployed, manually record the safety
signature after initial creation and check the safety signature after every deployment to
make sure that it matches the original.
See Safety Signature ID for more information about the functionality of
the Safety Signature ID.
Provide Feedback