Import Program and Equipment Phase Considerations
The import process for Program (includes Equipment Phase) follows this behavior:
Configuration | Behavior |
Final Name | When online in Remote Run mode, if you change the Final Name so that the resulting operation is use existing or discard, an attention flag appears.
Unable to import <component type> <import component name>. The <component type> will be discarded on import.
Unable to overwrite <component type> <existing component name>. The existing <component type> will be used. Changing the Final Name does not change the Schedule In field. If online in Remote Run mode, and the Final Name change causes a new collision with a program scheduled in a different task or folder, then the current Schedule In specifies the above attention flag apply. |
Schedule In | Schedule In specifies the name of the task under which the program is to be scheduled. This field defaults to the context from which the import was initiated unless the Operation was forced to Use Existing. As a result, an overwritten component might be in a different location than shown. When not online, in Remote Run mode, and the operation is create or overwrite, you can select one of these for Schedule In:
When the operation is use existing, Schedule In is read only and specifies the current location of the existing program. When the operation is discard, Schedule In is read only and specifies the location from its last setting. If offline or if online in Remote Program mode and the program is scheduled as either the Controller Fault Handler or the Power Up Handler, any previously scheduled program in that position moves to the Unscheduled folder during the import. |
Inhibit Program | If the operation is create, overwrite, or discard, this field reflects the inhibit state of the program being imported. If the operation is use existing, this field is read only and reflects the inhibit state of the existing program. |
Class | The Class is read only and displays the class for the current component. This field is always visible for import to a safety controller, in which case, the Class is either Standard or Safety. |
Assigned Routines: Main Assigned Routine: Prestate Assigned Routine: Fault | This field is read only and displays the associated routine, If online and in Run mode, the import content must match the existing project for the import to be successful. |
In Run mode, if no routine was previously configured, then one can be configured; but if one was already configured, it cannot be changed. This means that if a new version of a program is imported online in Run mode, the import fails if the Main Routine or Fault Routine configuration was changed.
You can create, modify, and delete phase programs. You can overwrite a phase program in Run mode and test the changes, even if it involves implementing or undoing the implementation of a state routine.
When you import a program or equipment phase online in Remote Run mode:
- A new Main, Fault, or Prestate Routine can be created, but an existing routine can only be overwritten by another routine with the same name and type. The routine name cannot be changed.
- If the import overwrites an existing program, the program cannot be rescheduled into a different task. The import uses the existing task.
- Other considerations include:
- When a program contains routines with accepted edits or test edits, logic cannot be imported into that program. Existing edits must either be assembled or canceled.
- When a program contains routines with pending edits, logic can be imported into that program. If logic is imported with the option to accept edits or finalize all edits in program, then in addition to the imported logic being accepted or finalized, any other pending edits in other routines in the program are also accepted or finalized.
- If a program has tags or routines marked as delete, those components are not deleted unless you select Finalize All Edits In Program. If the program is imported as pending edits or accepted edits, those tags or routines are not deleted by the import. However, after the import completes and edits have been assembled, you can delete those tags or routines that are no longer referenced.
- Programs must have unique names. The import does not let a program overwrite an equipment phase or vise versa.
- When importing a program, the associated tags and routines are components, rather than external references. Unlike reference components, you cannot modify the operation, final name, or description settings of the components. The operations of the components are based on the operation for the imported component. If the operation of any component is forced to discard or use existing, the operation of the import components are also forced to the same operation.
- When you import an Equipment Phase that overwrites the name of a phase referenced by a step in an Equipment Sequence, any difference in the number or configuration of the phase’s parameters that are selected for sequencing causes all sequences in the project to update those steps. The parameter changes are propagated to all Equipment Sequences in the project.
Program Tag Definitions
The program tag definitions follow these import processes:
Configuration | Behavior |
Operation | The Operation is read only and depends on the program.
When an import program has a Use Existing Operation, any tags in the project that are not in the import program also have a Use Existing Operation and their names appear in the Final Name field This lets you view any tags you would delete if you changed the operation to overwrite. |
Final Name | The Final Name is read only. If the operation is discard, Final Name is blank. Otherwise, Final Name displays the same content as the Import Name field. For cases where the tag exists in the project but not in the import content (blank Import Name), Final Name displays the name of the tag that will be deleted. |
Usage | The Usage is read only and depends on the operation.
|
Alias For | Read-only. Shows the Alias For tag specifier. |
Data Type | Data Type is read only. If the Operation is Create, Overwrite, or Discard, Data Type displays the type of the tag as read from the import file. If the Operation is Use Existing or Delete, Data Type displays the type of the tag in the current project. Data Type is blank if the tag is an alias. |
Description | Standard Description behavior. |
Importing Programs Online
When a program is overwritten, there might be
- tags and routines that did not previously exist.
- some tags and routines that are identical.
- some tags and routines that still exist, but are different.
- some tags and routines that were in the old version of the program that are not in the new version.
These tags and routines need to be created, modified, or deleted in the project.
In delete situations, when edits are not finalized, tags being deleted might still be referenced by the original logic and routines being deleted might still be executing. These components cannot be deleted until you finalize the changes.
In create situations, new tags and routines are created. Routines are created empty and their contents are left pending or inserted as test edits, depending on online editing options selected. If edits are being tested, the new routine contents are there. If the original logic is executing, the new routine is empty.
Provide Feedback