Tag, Component, or Definition Already Exists Messages

Tag <tag name> already exists in project as [program | equipment phase]-scoped tag. Imported logic will reference existing tag.

A referenced tag is controller-scoped and a program-scoped tag of the same name exists.

The imported logic references the existing [program | equipment phase]-scoped tag unless the final name is changed.

The Operation field is set according to configuration operations rules.

Tag <tag name> already exists in project and has a different data type. Values for existing tag may be lost.

The referenced tag collides with a tag that has a different data type name. Existing logic references may not verify and some existing tag data values may be lost. Imported logic references may not verify.

To create a new tag or to overwrite a different tag, change the final name.

The Operation field is set according to configuration operations rules.

Standard controller-scoped tag <tag name> already exists in project as a Safety controller-scoped tag

A referenced tag is a controller-scoped standard tag and it collides with a controller-scoped safety tag.

The Operation field is set according to configuration operations rules.

Safety controller-scoped tag <tag name> already exists in project as a Standard controller-scoped tag

A referenced tag is a controller-scoped safety tag and it collides with a controller-scoped standard tag when importing into a safety controller project.

The Operation field is set according to configuration operations rules.

Equipment phase <phase name> already exists in project with a different parameter configuration

The imported equipment phase collides with an existing equipment phase and there are differences in input or output parameters or parameter properties and the Operation field is set to Overwrite.

The Operation field is set according to configuration operations rules.

Routine <routine name> already exists in project and is different. Existing logic references may be affected.

The colliding imported routine and the existing routine is not the Main Routine and logic is different and the Operation is Overwrite.

To create a new routine, change the final name.

The Operation field is set according to configuration operations rules.

Routine <routine name> already exists in project. Imported logic references may be affected.

The colliding referenced routine and the imported routine is a routine or rung and the Operation for that routine or rung is Overwrite.

The Operation field is set according to configuration operations rules.

Add-On Instruction definition <Add-On Instruction name> already exists in project. Existing references may be affected.

The colliding imported Add-On Instruction edit date is different from the existing Add-On Instruction with the same name. The following existing references to the instruction type may be affected:

To create a new Add-On Instruction, change the final name.

The Operation field is set according to configuration operations rules.

Add-On Instruction definition <Add-On Instruction name> already exists in project. Imported and existing references to instruction may be affected.

The colliding imported referenced Add-On Instructions edit dates are different. This includes Add-On Instructions referenced by logic or tags, as well as Add-On Instructions referenced by other Add-On Instructions.

The following existing or imported references may be affected:

To create a new Add-On Instruction, change the final name.

The Operation field is set according to configuration operations rules.

Data type <data type name> already exists in project and is different. Existing references may be affected.

The colliding imported User-defined Data Type data type definitions is different from a User-defined Data Type of the same name, but the User-defined Data Type is not referenced in the project and the Operation field is set to Overwrite.

The following existing references of the data type may be affected:

To create a new data type, change the final name.

The Operation field is set according to configuration operations rules.

Data type <data type name> already exists in project. Imported and existing references may be affected.

The colliding referenced User-defined Data Types data type definitions are different, but the User-defined Data Type is not referenced in the project.

The following imported references of the data type may be affected:

To create a new data type, change the final name.

The Operation field is set according to configuration operations rules.