Rockwell Automation Publication 1756-UM022D-EN-P - May 2017 159
Appendix B
Change Controller Type
Because safety controllers have special requirements and do not support certain
standard features, you must understand the behavior of the system when
changing the controller type from standard to safety or from safety to standard
in your controller project. Changing controller type affects the following:
• Supported features
• Physical configuration of the project (safety partner and safety I/O)
• Controller properties
• Project components such as tasks, programs, routines, and tags
• Safety Add-On Instructions
Change from a Standard to a
Safety Controller
To successfully change the controller type from a standard controller to a safety
controller, the chassis slot immediately to the right of the safety primary
controller must be available for the safety partner.
Upon confirmation of a change from a standard controller to a safety controller
project, safety components are created to meet the minimum requirements for
a safety controller:
• The safety task is created only if the maximum number of downloadable
tasks has not been reached. The safety task is initialized with its default
values.
• Safety components are created (safety task, safety program, and so
forth).
• A time-based safety network number (SNN) is generated for the local
chassis.
• Standard controller features that are not supported by the safety
controller, such as redundancy, are removed from the Controller
Properties dialog box (if they existed).
Topic Page
Change from a Standard to a Safety Controller 159
Change from a Safety to a Standard Controller 160
Change Safety Controller Types 161
IMPORTANT GuardLogix® 5560 controllers and 1768 Compact GuardLogix controllers are
not supported in Studio 5000® version 21 or later.