Import/Paste Configuration Dialog - Configure Program Properties Overview

Use this dialog box to configure how the program is imported into the project, or how it is pasted into the project using the
Paste Special > With Configuration
 command.
The References folder can contain folders for referenced tags, data types, Add-On Instructions, or Components, depending on the imported program references.
The Import Content shows the import component and any references in the References folder. The References folder appears if there is logic that references tags, data types, Add-On Instructions, or other components.
When the imported program is selected in the import content, the Details pane displays the program’s properties.
If the operation on the program is set to use the existing program in the project, then the Description, Inhibit Program, Class, and Assigned Routines fields show the values from the program in the project and appear dimmed. Otherwise, these fields display the values from the import file.
Parameters
Import Name
Displays the name of the program as read from the import file.
Operation
Identifies what is done with this program upon import.
The field is pre-populated; however, you can choose from a pull-down list of valid choices.
For more information, see below for
Import Configuration Operations
.
Final Name
The final name is the name of the program as it appears in the project after the import. Changing the Final Name changes the name in all places where this program’s Import Name is referenced in the import content throughout the logic, By default, it is initialized to the Import Name.
When you select in the Final Name cell, a menu appears, which lets you pick from a list of all of the programs that exist in the project.
If the Final Name collides with an existing program in the project and Overwrite is selected, the existing program is overwritten with its tags, routines and properties of the program in the import file. It also reschedules the existing program if the import location is different from where the program was originally scheduled.
IMPORTANT:
You may either create or avoid a collision by modifying the final name, (based on if you modify the final name to match that of an existing final name in the project).
Collision Details
Select this button to find differences between the imported component and the existing component. See below for
Component Name Collision Dialog - Property Compare Tab Overview
 and
Component Name Collision Dialog - Project References Tab Overview
.
Description
Shows the description of the program.
The description can be changed, unless the Operation is Discard or Use Existing.
Schedule In
Contains the location where the program is to be scheduled, which can be a task name, Controller Fault Handler or Power-Up Handler or displays Unscheduled Programs, if it is to be unscheduled.
TIP:
If you are importing a single program folder, Scheduled In is unavailable and set to Unschedule Programs/Phases.
Initially, this control defaults to the context from which the import was initiated, unless the Operation field is initially set to Use Existing. In which case, it shows the location where the existing program is scheduled.
When offline or when online in Program mode, a message displays in the results window, upon import, that informs you if the program was rescheduled or unscheduled.
When online in Run Mode, programs cannot be rescheduled and the Schedule In location appears dimmed. You cannot overwrite a program in a location different from its current location (by changing the Final Name).
If the program collides, then the scheduled location of the program cannot be changed, if modify task properties or modify controller properties security privileges are denied.
If the Operation field is set to Create or Overwrite, the pull-down menu contains the following:
  • A list of all tasks in the project
  • Unscheduled programs
  • Controller Fault Handler
  • Power-Up Handler
When the Operation field is set to Use Existing, Schedule In contains the current location of the existing program in the project.
If offline or online in Remote Program mode and if the program is scheduled as either the Controller Fault Handler or the Power-Up Handler, then any previously scheduled program is given an unscheduled status (moved to the Unscheduled folder) when the import proceeds.
Preserve scheduling for child programs that already exist
Specify if child programs in the destination program remain as they are configured or are replaced with components in the source program that is being imported into the project.
If the check box is selected, then child programs that already exist in the destination program remain scheduled as they are configured in the destination program. By default, child programs are preserved in the program.
You much clear the check box if, upon import, you wish for the child program that is being imported into the project to be scheduled in the task that is identified in the Schedule In field.
Parent
Specify where the program will reside upon import. If you want to modify the parent specification, select the down arrow to select an option.
If a parent is specified when you are importing from the Logical Organizer view, that parent is shown in this field. Otherwise, the default setting for Parent depends on whether you exported the component from the Controller Organizer or the Logical Organizer, whether you are importing it to the Controller Organizer or the Logical Organizer, and on the Operation setting.
  • If you exported the program from the Controller Organizer and you are importing it to either the Controller Organizer or the Logical Organizer:
    • Parent is set to <none> if Operation is set to Create or Discard.
    • Parent is set to the parent configured in the destination project if Operation is set to Use Existing or Overwrite.
  • If you exported the program from the Logical Organizer and you are importing it to the Logical Organizer:
    • Parent is set to the selected program in the Logical Organizer if Operation is set to Create or Discard.
    • Parent is set to the parent configured in the destination project if Operation is set to Use Existing.
    • Parent is set to the selected item in the Logical Organizer if Operation is set to Overwrite.
  • If you exported the program from the Logical Organizer and you are importing it to the Controller Organizer:
    • Parent is set to <none> if Operation is set to Create, Discard, or Overwrite.
    • Parent is set to the parent configured in the destination project if Operation is set to Use Existing.
Inhibit Program
If selected, the Program is inhibited on import and does not execute until it is uninhibited.
The selected or cleared state defaults to that contained in the import file (unless Operation is set to Use Existing).
If the Operation field is set to Overwrite (that is, the imported program collides with an existing one and the imported component’s attributes are displayed) and the inhibit state of the colliding programs is different (that is, one is inhibited and the other is not inhibited), then a message is displayed under the Inhibit Program check box indicating this condition.
Class
This field only appears when importing into a safety controller and displays Standard or Safety to reflect the class of the program.
Assigned Routines: Main
Shows the program’s assigned main routine.
The associated main routine cannot be changed online in Run mode; the import will fail.
Assigned Routine: Fault
Shows the program’s assigned fault routine.
The associated fault routine cannot be changed online in Run mode; the import will fail.
Preserve existing tag values in offline project
When an existing tag has
Operation
 set to
Overwrite
, this check box provides the option to indicate whether data table-backed tag data values are preserved (check box selected) or overwritten (check box cleared) in an offline project as a result of an import. The check box is selected by default.Keep the following considerations in mind when using the check box:
  • Tag data values are never overwritten in the online controller, regardless of the check box state. The check box only affects values written to the offline project.
  • Data table-backed tag data values include the value of the tag as well as any force-tag values. The state of the check box (selected or cleared) applies to all data table-backed tags in the import.
  • Types for tags that are not data table-backed follow special rules for import and are unaffected by the check box state. Tag configuration data for these types is always overwritten, in both the online controller and the offline project. Tag data values for these tag types are not present in the export file and so are never overwritten anywhere. These types include:
    • ALARM_ANALOG
    • ALARM_DIGITAL
    • AXIS
    • COORDINATE_SYSTEM
    • ENERGY_BASE
    • ENERGY_ELECTRICAL
    • Message
    • MOTION_GROUP (All tags of any Motion-related type cannot be written while online)
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.