Rockwell Automation 1756-SPESMNRMXT GuardLogix Controllers User Manual - Manuel (Page 105)

Rockwell Automation Publication 1756-UM020I-EN-P - August 2012 105
Develop Safety Applications Chapter 6
Safety Application
Protection You can protect your application program from unauthorized changes by safety-
locking the controller and by generating and recording the safety task signature.
Safety-lock the Controller
The GuardLogix controller can be Safety-locked to protect safety-related control
components from modification. The Safety-lock feature applies only to safety
components, such as the safety task, safety programs, safety routines, safety Add-
On Instructions, safety tags, Safety I/O, and the safety task signature.
The following actions are not permitted in the safety portion of the application
when the controller is safety-locked:
• Online/offline programming or editing (including safety Add-On
Instructions)
• Forcing Safety I/O
• Changing the inhibit state of Safety I/O or produced connections
• Safety data manipulation (except by safety routine logic)
• Generating or deleting the safety task signature
You can safety-lock the controller project regardless of whether you are online or
offline and regardless of whether you have the original source of the program.
However, no safety forces or pending online safety edits may be present.
Safety-locked or -unlocked status cannot be changed when the keyswitch is in the
RUN position.
TIP The text of the online bar’s safety status button indicates the safety-lock status.
The application tray also displays the following icons to indicate the safety
controller’s safety-lock status.
• = controller safety-locked
• = controller safety-unlocked
TIP Safety-lock or -unlock actions are logged in the controller log.
For more information on accessing the controller log, refer to Logix5000 Controllers
Controller Information and Status Programming Manual, publication
1756-PM015 .
Safety Status Button