Rockwell Automation 20D-DL2-CKS1 Import/Export Project Components - Manual (Page 41)

Chapter 3
Additional considerations for routines
This chapter explains the import and export of routines.
A routine can be exported to an .l5x file. Routines of all language types, Function
Block Diagram, Sequential Function Chart, Ladder Diagram and Structured
Text, may be exported. However, routines may not be exported from an Add-On
Instruction container and SoftLogix external routines may not be exported.
The export file may also include any program-scoped tags, controller-scoped tags,
Add-On Instructions, user-defined data types, and user-defined string types that
are referenced by the routine. The definitions for the referenced tags, Add-On
Instructions and user-defined data types are exported to the .l5x file if they exist in
the project.
When importing a routine, you configure how the referenced components are
imported during import configuration. By default, referenced components that
collide with project components are not imported.
The following are considerations when importing a routine.
Topic Consideration
Pending Edits exist If a routine is imported into a program or equipment phase that contains other routines
with Pending Edits, all Pending Edits in the program are accepted if Accept Program
Edits is selected during import of the routine. Similarly, all Pending Edits in the program
are finalized if Finalize All Edits In Program is selected during import of the routine.
Accepted Edits exist A routine may not be imported into a program or equipment phase that contains
routines with Accepted Edits or Test Edits. Existing edits must first either be assembled
or canceled.
Routine type An existing routine may not be overwritten by a routine that is another routine type.
First scan When importing a routine into an existing program, the S:FS bit is not set during the
program’s next scan. This applies when importing a routine into an existing equipment
phase as well.
SFC routine execution
configuration
SFC execution settings are configured on a controller project, not per SFC routine. If you
export an SFC routine and import it into another project with different SFC execution
settings, the functionality of the routine could change. For example, a change in the
Last Scan of Active Steps setting could leave physical outputs in an undesired state.
Equipment Phase state routines When state routines are created while online with the controller and logic edits are
accepted but not tested, the routine will behave as if it was not implemented.
Introduction
Export considerations
Import considerations
Rockwell Automation Publication 1756-PM019E-EN-E - October 2014 41