From a safety controller to another safety controller

Use the same platform to change from one safety controller to another safety controller (for example, from a 1756-L72S controller to a 1756-L73S controller) or to change from one safety controller to another safety controller across platforms (for example, from a 1756-L71S controller to a 1769-L30ERMS controller).
Changing safety controllers within the same platform
Change a safety controller within the same platform to configure more or less safety controller memory than is currently available. Creating, deleting, or changing the class of any tasks, programs, routines, tags, or other parameters does not create compatibility issues. The change is within platform; therefore, the I/O remains compatible with the target controller.
Changing safety controller across platforms
When changing from one safety controller type to another safety controller type, the class of any tasks, programs routines, and tags remain unaltered. The Logix Designer application deletes I/O modules that are not compatible with the target controller.
The Logix Designer application updates the safety level in the project appropriately, depending on the safety level the target controller supports.
  • If the target controller supports the same safety level as the source controller, the safety level in the project remains the same upon completion of the change.
  • If the target controller does not support the same safety level as the source controller, the safety level in the project changes to the target controller's supported safety level. For example, when changing from a project with a SIL3/PLe safety level:
    • If the target controller supports only SIL2/PLd, changes the safety level in the project from SIL3/PLe to SIL2/PLd.
    • If the target controller supports SIL3/PLe, the safety level in the project remains SIL3/PLe.
The representation of the safety partner updates to appear appropriately for the target controller.
  • When changing from a GuardLogix Safety controller to a Compact GuardLogix Safety controller, the Logix Designer application removes the safety partner because it is internal to the Compact GuardLogix controller.
  • When changing from a Compact GuardLogix Safety controller to a GuardLogix Safety controller:
    • If the target controller is a GuardLogix 5570 controller, the Logix Designer application creates the safety partner.
    • If the target controller is a GuardLogix 5580 controller, the Logix Designer application only creates the safety partner if the source project is at a SIL3/PLe safety level.
Safety Network Numbers
The Logix Designer application assigns a Safety Network Number (SNN) to each port on the target controller that supports a CIP Safety connection and preserves SNNs when the ports are the same. Otherwise the application assigns the port a new time-based SNN.
  • If the target controller's backplane port is the same as the source controller's backplane port, then the target backplane port gets the SNN of the source backplane port. For example:
    • When changing from a GuardLogix 5570 Safety controller to a GuardLogix 5580 Safety controller, the backplane port is the same for both controllers. The backplane port of the GuardLogix 5580 Safety controller gets the SNN of the GuardLogix 5570 Safety controller's backplane port.
      The GuardLogix 5580 Safety controller also has an Ethernet port. The Ethernet port gets a new time-based SNN.
  • For the Ethernet port, the source Ethernet port reserves the SNN of the target Ethernet port. For example:
    • When changing from a CompactLogix 5370 Safety controller to a CompactLogix 5380 Safety controller, the
      EtherNet/IP mode
      for CompactLogix 5380 Safety controller sets to
      A1/A2:Linear/DLR
      and the A1/A2 port gets the SNN of the CompactLogix 5370 Safety controller's Ethernet port.
      The CompactLogix 5380 Safety controller also has a backplane port that supports CIP Safety. Its gets a new time-based SNN since the CompactLogix 5370 Safety controller's backplane port does not support CIP Safety and has no SNN.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal