From a controller with embedded Ethernet ports

When changing a controller to a target controller of another type, elements that do not apply to the target controller’s environment are either deleted or result in a verification error.
These controllers have embedded Ethernet ports:
  • CompactLogix 5370 controllers
  • CompactLogix 5380, CompactLogix 5480, and ControlLogix 5580 controllers
Ethernet Ports
Changing from a controller with embedded Ethernet ports to a controller without embedded Ethernet ports creates different results based on certain criteria.
  • Depending on the controller, results in deleted embedded Ethernet settings.
  • If the target controller supports one or more configurable Ethernet port pairs, the EtherNet/IP mode of those ports is the same as the source controller. However, if the port pair has no modules underneath it, results in a possible changed EtherNet/IP mode to allow Ethernet modules in the source project to move to the target controller. This occurs when changing from a CompactLogix 5480 controller to a CompactLogix 5380 controller and only the B1 port has modules underneath it (see below).
  • If the project has more Ethernet ports with modules underneath them than the target controller, and the target controller has one or more Ethernet ports, results in no change of controller and receive an error.
  • If the target controller has no Ethernet ports, result is removed Ethernet modules underneath the source controller's Ethernet ports.
When changing from a CompactLogix 5480 controller or CompactLogix 5380 controller to a ControlLogix 5580 controller:
  • The ControlLogix 5580 controller has only one Ethernet port. If only one of the Ethernet ports in the source controller has modules underneath it, results in preserved modules from the source controller. Otherwise, results in no change of controller and receive an error. To change the controller, make sure only one Ethernet port in the source controller contains modules. Refer to the Output window,
    Errors
     tab for more information.
When changing from a CompactLogix 5480 controller to a CompactLogix 5380 controller:
  • The CompactLogix 5380 controller does not have a B1 Ethernet port. If the source project has modules underneath the B1 port, results in possibly no change of controller and receive an error. To change the controller, refer to the Output window,
    Errors
     tab for information.
  • If only the B1 port contains modules, results in modules move to the A2 port of the CompactLogix 5380 controller, and the EtherNet/IP mode sets to Dual IP, regardless of the EtherNet/IP mode of the source project.
Changing from a controller without embedded Ethernet ports to a controller with embedded Ethernet ports results in created embedded Ethernet settings.
Embedded Digital I/O Modules
The CompactLogix 5370 L1 digital I/O module supports change-of-State (COS).
Changing from a CompactLogix 5370 L1 controller to anything other than another CompactLogix 5370 L1 controller results in the loss of the source project’s change-of-state configuration.
Expansion I/O
These CompactLogix 5370 L1 controllers contain Expansion I/O:
  • 1769-L16ER-BB1B
  • 1769-L18ER-BB1B
  • 1769-L18ERM-BB1B
  • 1769-L19ER-BB1B
When changing from a CompactLogix 5370 L1 CompactLogix controller to another CompactLogix 5370 L1 CompactLogix controller:
  • Creates Expansion I/O modules from the source controller in the target controller.
  • The number of Expansion I/O modules created in the source controller cannot exceed the maximum number of Expansion I/O allowed for the controller.
When changing from a CompactLogix 5370 L1 CompactLogix controller to another CompactLogix 5370 L1 CompactLogix controller or from a CompactLogix 5370 L2 or L3 controller to another CompactLogix 5370 L2 or L3 controller, results in preserved Expansion I/O modules from the original project.
If the number of Expansion I/O modules in the source controller exceeds the maximum number of Expansion I/O modules in the target controller, the invalid configuration generates a verification error.
Slot Numbers
Embedded I/O modules take between 1 and 3 slots in the CompactLogix 5370 L2 controllers. Changing from one controller to another may invalidate the slot numbers for modules in Expansion I/O slots in the target chassis.
CIP Motion
Changing from a controller that supports CIP motion to a controller that does not support CIP motion preserves CIP axes and drives from the source project. However, the change generates a verification error. Delete these objects or change to a controller type that supports CIP motion.
Embedded Input/Output Module Tags
The CompactLogix 5370 L1 and the CompactLogix 5370 L2 controllers have embedded I/O modules. When changing from a CompactLogix 5370 L1 controller to a CompactLogix 5370 L2 controller or from a CompactLogix 5370 L2 controller to a CompactLogix 5370 L1 controller, the process preserves the tag references when the source controller contains references to embedded I/O tags and the target controller contains those devices. The process preserves tag references to the embedded Discrete_IO device.
Because the Discrete_IO device in L1 and L2 have different fields, a reference to a field that does not exist in the target Discrete_IO device generates a verification error.
Creates two types of tag references when changing between CompactLogix 5370 L1 and CompactLogix 5370 L2 controller types or from a CompactLogix 5370 L2 controller with three embedded I/O modules to a CompactLogix 5370 L2 controller with one embedded I/O module:
  • Preserved tag reference — refers to the equivalent device in the new controller project.
  • Unpreserved tag reference — results in the verification error seen when referencing a tag that no longer exists in the new controller project.
Tip: Changing to a controller type that does not have any embedded I/O modules, results in unpreserved embedded I/O tag references.
IMPORTANT
An unpreserved reference must not refer to a tag in the target project. Before downloading the new project, change the unpreserved tag references to some other tag or remove the reference.
Tag Configuration Data
In summary, when changing from a CompactLogix  5370 L1 or CompactLogix  5370 L2 controller type to another CompactLogix  5370 L1 or CompactLogix  5370 L2 controller type results in:
  • Preserved tags only for fields that match in the two configuration tags.
  • Unsaved input and output tag values since the old values do not apply to the new devices.
  • If a field does not exist in the source controller but does in the destination controller, the field uses the default value.
  • If a field exists in the source controller but not in the destination controller, the source project loses the value for that field.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal