Programmatic Changes to the Safety Application Signature
If there are no changes to your safety application, then the safety application signature and all of its underlying elements remain constant across software and firmware releases with the following possible exceptions:
- You update the controller with a firmware revision that contains a change to the offline compiler or internal signature algorithm. These changes can trigger a change to the safety signature. These types of changes are infrequent.
- You use the copy/paste or import function in a way that causes an internal difference in a component. For example, if you copy a safety routine from Project1 to Project2 and TagA is program-scoped in Project1, but controller-scoped in Project2, then the safety signature for the routine changes.
Unlike the safety application signature, the controller safety signature always changes with any firmware release change, so that you complete some validation testing at the functional controller level, even if no changes were made to the safety project.
Controller and Safety Application Signatures
Provide Feedback