Import Configuration Dialog - Add-On Instructions Tab Overview

Use the
Import Configuration Dialog – Add-On Instructions
tab to specify Add-On Instruction attributes when importing an Add-On Instruction contained in a file.
When you import an Add-On Instruction:
  • You can only import to the same or newer version of the
    Logix Designer
    application; you cannot import to a prior version. Therefore, you must use caution when exporting and importing components between different versions of the application. If you import to a prior version of the application the operation may appear to succeed, but the results may not work as you intended.
  • The class of the Add-On Instruction must match the class of the destination routine or the routine will not verify.
  • The class, signature, signature history, and safety signature (if it exists) remain intact when you export and import a sealed Add-On Instruction definition.
  • You cannot import a safety Add-On Instruction into a safety project that has a safety task signature or has been safety-locked.
Attributes
Status
The first column of the dialog box provides feedback about which Add-On Instruction (if any) collides with an Add-On Instruction in the target project.
If a collision is identified, an Add-On Instruction collision icon AOI_collision_icon is shown in the row(s) corresponding to the colliding Add-On Instruction(s).
Instruction Name
The name of the Add-On Instruction being imported.
You can modify the name if the instruction collides with an existing instruction. If an imported Add-On Instruction is fully source-protected, the Instruction Name appears dimmed. All references in logic or other imported Add-On Instructions are updated to reflect the new name of the Add-On Instruction.
Description
Displays the description of the Add-On Instruction as it appears in the imported .L5X file. This field is read-only.
Revision
Displays the revision of the Add-On Instruction as it appears in the imported .L5X file. This field is read-only.
Revision Note
Displays the revision note of the Add-On Instruction as it appears in the imported .L5X file. This field is read-only.
Vendor
Displays the vendor of the Add-On Instruction as it appears in the imported .L5X file. This field is read-only.
Operation
Specify how to import an Add-On Instruction.
  • For Add-On Instructions that do not collide, the cell is read-only and displays the text Create New.
  • For Add-On Instructions that match exactly with an existing instruction in the target, the cell is read-only and contains the text Use Existing.
  • For Add-On Instructions that do collide and are different than existing instructions in the target project, the operation column is blank initially. You must specify what action to take on a given Add-On Instruction before the import may proceed. A pull-down list provides options to do one of the following:
    • Overwrite the existing Add-On Instruction
    • Use Existing Add-On Instruction in the target project
Operation appears dimmed if the selected Add-On Instruction does not contain a collision.
Compare to Existing
Click to compare the Add-On Instruction being imported and the existing Add-On Instruction in the target project. The Instruction Name Collision Dialog displays. You can choose to overwrite the Add-On Instruction or use the existing Add-On Instruction.
If you overwrite an existing Add-On instruction:
ATTENTION:
  • ATTENTION:
    Verify that all references to the Add-On Instruction execute correctly with the new Add-On Instruction.
  • Existing tags based on the Add-On Instruction data type will be updated. If the data layout is different between the two instructions, you may lose some of the current values in those tags.
  • Calls to the instruction will be edited to maintain arguments passed to existing parameters. Check all calls to this instruction to ensure they will execute correctly with the updates.
The
Compare to Existing
button is unavailable if the selected Add-On Instruction does not contain a collision.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.