Table of Contents
Advertisement
Chapter 6
Safety Application Development
Download the Safety
Application Program
56
No aspect of safety can be modified while the controller is in the safety-locked
state. When the controller is safety-locked, the following actions are not
permitted in the safety task:
• Update the firmware
• Online or offline programming or editing
• Forcing safety I/O
• Data manipulation of safety components (except through routine logic
or another GuardLogix controller)
• Creating or editing safety Add-On Instructions
• Generating or deleting the safety signature
IMPORTANT
The default state of the controller is safety-unlocked. You can place the safety
application in a safety-locked state regardless of whether you are online, offline,
or you have the original program source. However, no safety forces or pending
safety edits can be present. Safety-locked or -unlocked status cannot be
modified when the keyswitch is in the RUN position.
To provide an additional layer of protection, separate passwords can be used to
safety-lock or -unlock the controller. Passwords are optional.
For more information about the safety-lock feature, see the user manual for the
controller:
• ControlLogix 5580 and GuardLogix 5580 Controllers User Manual,
publication
1756-UM543
• CompactLogix 5380 and Compact GuardLogix 5380 User Manual,
publication
5069-UM001
Upon download, application testing is required unless a safety signature exists.
IMPORTANT To verify that the correct safety application is downloaded or restored from a
memory card, you must manually check that the safety signature matches
the original signature in your safety documentation.
Downloads to a safety-locked GuardLogix controller are allowed only if the
safety signature and the firmware revision of the offline project all match what
is contained in the target GuardLogix controller and the safety task status of
the controller is OK.
IMPORTANT If the safety signature does not match and the controller is safety-locked,
you must unlock the controller to download. In this case, downloading to
the controller deletes the safety signature. As a result, you must revalidate
the application.
Rockwell Automation Publication 1756-RM012B-EN-P - April 2018
If a safety signature exists and the controller is safety-locked, only
projects with a matching safety signature can be downloaded to
controller.
Hide quick links:
Advertisement
Table of Contents
