Import Configuration Dialog - Configure Equipment Phase Properties Overview

Use this dialog box to configure how the Equipment Phase is imported into the project.

The Import Content shows the Equipment Phase, phase tags, and routine import components and any references in the References folder. The References folder only appears if the Equipment Phase being imported references controller-scoped tags, data types, Add-On Instructions, or other components.

When the imported Equipment Phase is selected, the Details pane displays the Equipment Phase’s properties.

The References folder can contain folders for referenced tags, data types, Add-On Instructions, and components, depending on what the imported Equipment Phase references.

If the operation on the phase is set to use the existing phase in the project, then the Description, Inhibit Phase, Class, and Assigned Routines fields show the values from the phase in the project and appear dimmed. Otherwise, these fields display the values from the import file.

Parameters

Import Name

Displays the name of the Equipment Phase as read from the import file.

Operation

Identifies what is done with this Equipment Phase upon import.

The field is pre-populated; however, you can choose from a pull-down list of valid choices.

If the Operation field is set to Overwrite, Create, or Discard, displays the attribute for the import component.

If the Operation field is set to Use Existing, displays the attribute for the component in the project.

For more information, see

Import Configuration Operations

.

Final Name

The final name is the name of the phase as it appears in the project after the import. Changing the Final Name changes the name in all places where this phase’s Import Name is referenced in the import content throughout the logic, By default, it is initialized to the Import Name.

When you click in the Final Name cell, a pull-down menu appears, which lets you pick from a list of all of the phases that exist in the project.

If the Final Name collides with an existing phase in the project and Overwrite is selected, the existing phase is overwritten with its tags, routines and properties of the phase in the import file. It also reschedules the existing phase if the import location is different from where the phase was originally scheduled.

Collision Details

Click 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 phase is to be scheduled, which can be a task name, Controller Fault Handler or Power-Up Handler or shows Unscheduled Phase, if it is to be unscheduled.

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 shows in the results window, upon import, that informs you if the Equipment Phase was rescheduled or unscheduled.

When online in Run Mode, Equipment Phases cannot be rescheduled and the Schedule In location appears dimmed. You cannot overwrite an Equipment Phase in a location different from its current location (by changing the Final Name).

If the Equipment Phase collides, then the scheduled location of the Equipment Phase cannot be changed, if modify task properties or modify controller properties privileges are not granted.

If the Operation field is set to Create or Overwrite, the pull-down menu contains the following:

When the Operation field is set to Use Existing, Schedule In contains the current location of the existing Equipment Phase in the project.

Preserve scheduling for child programs that already exist

Specify if child programs in the destination phase remain as they are configured or are replaced with components in the source phase that is being imported into the project.

If the check box is selected, then child programs that already exist in the destination phase remain scheduled as they are configured in the destination phase. By default, child programs are preserved in the phase.

You must clear the check box if, upon import, you wish for the child programs of the phase 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 phase will reside upon import.

If a parent is specified when you are importing from the Logical Organizer view, that parent is shown in this field. Otherwise, <none> is shown when there is not a parent selected or when you are importing from the Controller Organizer view.

If you want to modify the parent specification, click the down arrow to select an option.

Inhibit Equipment Phase

If checked, the Phase 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 Equipment Phase collides with an existing one; the imported component’s attributes are displayed); and the inhibit state of the colliding Equipment Phases is different (that is, one is inhibited and the other is not inhibited), then a message is displayed under the Inhibit Phase checkbox 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 phase.

Assigned Routines: Prestate

Shows the phase’s assigned prestate routine.

The associated main routine cannot be changed online in Run mode; the import will fail.

Assigned Routine: Fault

Shows the phase’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)