Import considerations for differences between imported and existing sequences

The following table lists considerations you should keep in mind when there are differences between an imported Equipment Sequence and an Equipment Sequence that exists in your project.
Changed setting
Dialog box and results
Keep in mind
Step name
Import Configuration Dialog - Import Content
 shows changes to the:
  • Sequence Properties
  • Parameters and Local tags
  • Routines
Sequence Properties - Collision Details
 reports that:
  • The change in step name caused the step backing tag, a local tag, to be reported as deleted and a new tag created.
Parameters and Local Tags - Collision Details
 reports that:
  • The old step backing tag exists only in the project.
  • The new step backing tag does not exist in the project.
Routines - Collision Details
 reports that:
  • The logic is different.
Look at the Parameters and Local Tags to see the name of the step backing tags being deleted and created to know which steps are affected by the import.
Sequence step's associated phase
Import Configuration Dialog - Import Content
 shows changes to the:
  • Sequence Properties
  • Routines
Sequence Properties - Collision Details
 reports that:
  • The change in associated phase results in changes to number of step tags to be imported, number of new step tags, and the number of old step tags deleted.
Routines - Collision Details
 reports that:
  • The Reports logic is different.
The name of the changed step is not reported. This change is reported only as a Logic change and an update to the number of step tags.
Sequence transition expression
Import Configuration Dialog - Import Content
 shows changes to the:
  • Sequence Properties
  • Routines
Sequence Properties - Collision Details
 reports that:
  • The change in transition expression is marked as a difference but the
    Equipment Sequence Name Collision
     dialog box does not show what has changed.
Routines - Collision Details
 reports that:
  • The logic is different.
When the
Logix Designer
 application reports that the logic is different without a step change, there is a change to a transition expression.
Sequencing parameter attributes (
Value
,
Initial Value
,
Initialize as Valid
, and
Expression
)
Import Configuration Dialog - Import Content
 shows changes to the:
  • Sequence Properties
  • Parameters and Local tags
Sequence Properties - Collision Details
 reports:
  • The number of modified sequencing parameters.
  • Changes to the
    Initial Value
     and
    Initialize as Valid
     boxes as separate property changes in the comparison.
Parameters and Local Tags - Collision Details
 reports:
  • The
    Property Compare
     tab shows the name of the affected tag; reports that the
    Initialize As Valid
     and
    Expression
     fields have changed; and that the data is different.
  • The
    Data Compare
     tab reports each changed sequencing parameter and its
    Value
    ,
    Initial Value
    , and
    Valid
     boxes.
  • The
    Project References
     tab lists referenced projects.
If
Preserve existing tag values in offline project
 is selected on the
Import Configuration
 dialog box, the
Value
,
Initial Value
, and
Initialize as Valid
 boxes are not overwritten. However, the
Expression
 box is overwritten.
Step tag attributes (
Value
,
Initial Value
,
Initialize as Valid
, and
Expression
)
Import Configuration Dialog - Import Content
 shows changes to the:
  • Sequence Properties
Sequence Properties - Collision Details
 reports:
  • The number of modified Step Tags.
  • Changes to the
    Initial Value
    ,
    Initialize as Valid
    , and
    Expression
     boxes as separate property changes in the comparison.
  • Differences in Step tags and sequencing parameters are not reported the same way.
  • A change in step tag configuration on import does not identify which step tag is changing.
  • A change to the
    Value
     box is not specifically called out.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.