Import and export

Use the import/export feature to import into or export out of a project. The

Logix Designer

application provides five different Import/Export file formats:

Full project exported to ASCII text file (.L5K, or to an Extensible Markup Language (XML) formatted file .L5X),

Tag definitions and program documentation exported to ASCII text files in a Comma Separated Value (CSV) or Tab Separated Value (.TXT) format, and

Import and Export these components in an Extensible Markup Language (XML) formatted file (L5X):

Programs & Equipment Phases

Routines & Phase State Routines (any language)

Logic (Ladder Diagram Rungs only)

User-defined Data Types (data types and custom Strings)

Add-On Instructions

Trends

Tag-based alarms

Modules

Import or export hardware diagrams to or from a standard file type to share data between different software applications and the

Logix Designer

Professional Edition using these formats:

Web Ontology Language (OWL)

AutomationML (AML)

Export these components from a project to an .L5X file and then later use these same components in other projects by importing the .L5X file into the project. The export includes referenced components needed for an import (for example, tags) in the .L5X file.

The import/export feature uses these file types:

.L5K and Files

An ASCII representation of the data for an entire project and, when imported, creates a new project file or overwrites an existing project file.

.CSV Files

A comma-separated text file containing the tags and logic comments. Export various object descriptions to a .CSV file to create, edit, translate, and spell check descriptions with offline tools, such as Microsoft Excel. When importing the .CSV file, the system merges that description into the

Logix Designer

application database.

Export a .CSV file that contains as ASCII representation of tag information. Furthermore, import from a .CSV file and modify or add tag information to an open project.

For more information about importing and exporting a .CSV file, see About the Import/Export Comment Data Feature
.

.TSV Files

A tab-separated text file containing the tags and logic comments. Similar to the .CSV file format, except values are separated by tabs instead of commas.

.L5X Files

An Extensible Markup Language (XML) formatted file. These files can contain an export of the entire project or an export of selected components (and component references).

.RDF files

AutoCAD Electrical

For AutoCAD Electrical, use the Rockwell Automation Data Adapter to exchange data between the

Logix Designer

application version 32.00.00 and AutoCAD Electrical versions 2014 through 2018. Data Adapter is a tool used to translate Rockwell Automation hardware data in OWL (.rdf) format for auto generation of two-dimensional footprint and PLC I/O schematic drawings in AutoCAD Electrical. Download the Data Adapter tool from Rockwell Automation's Product Download and Compatibility Center (PCDC).

This workflow shows the supported process for bidirectional data exchange from

Studio 5000

applications to AutoCAD Electrical applications.

.AML files

EPLAN Electric P8

For EPLAN Electric P8, use AML data files (.aml) and associated PLC data import/export workflows to exchange data between the

Logix Designer

application version 32.00.00 and EPLAN Electric P8 version 2.7 and later.

This workflow shows the process for data exchange from supported

Studio 5000®

applications to the EPLAN Electric P8 application when starting the data exchange within

Studio 5000

This workflow shows the process for data exchange from the EPLAN Electric P8 application to supported

Studio 5000

applications when starting the data exchange within EPLAN.

Initiating Import of Components and Logic Comments

Initiate the import of components and logic comments as follows:

From the Controller Organizer, import a program, equipment phase, routine or phase state routine, Add-On Instruction, user-defined data type, string type, or trend by right-clicking on the component’s folder and accessing the import option from the context menu.

From the Ladder Editor, import ladder rungs by right clicking on a rung header and selecting Import Rungs
.

From the main File
menu, select Import Component
and then select the type of component to import.

From the main Tools
menu, select Import
and then select to import tags and logic comments or components.

TIP:

When exporting a component, make sure to select the component to be exported.

From the
Select Project Controller
dialog box, select a project controller for the CAD tool.

When importing a component, make sure to select the container where that component should go (for example, to import a program, select the task where the program belongs).

Note that some of the options appear dimmed for:

Safety tasks or when the project is safety secured

Online in Run mode

When activation for a component or permission to create or modify a component is not present

The controller is online with an Add-On Instructions, or the routine or Add-On Instructions is source protected

In Hard Run

When the component type does not exist in the project

Safety Mapped Tags

When importing safety components while the controller is online, safety tag mapping is not exported or imported. When importing components, if tag mapping is required, map the tags after the import is completed.

Project Documentation

Projects may now contain comments and descriptions in multiple languages. Exports from a multi-language project include all languages existing in the project (for the components exported).

Imports also support multiple languages. When importing into a multi-language project:

All languages in a multi-language export are imported.

Prompt appears to specify the language of a single-language export.

When importing into a single-language project:

Prompt appears to select one of the languages in a multi-language export file to import.

The documentation in a single-language export file are imported.

Languages are identified uniquely by appending a colon and the language code to the existing .L5X token. For example, the United States English token is appended as :en-US. For more information about the Project Documentation Languages feature, refer to About Project Documentation Languages
.

External Access

When importing from an .L5K file or tag/logic component import from .CSV or .TXT files, the

Logix Designer

application verifies that the imported External Access value is valid and compatible with its tag.

This table summarizes all incompatible External Access values that may result when modifying an .L5K, .L5X or .CSV file outside of the application and then trying to import the file:

Tag Type/Usage	Incompatible External Access Values
InOut Parameter	Read/Write Read Only None
EnableIn and EnableOut Parameter	Read/Write None
PLC-5® / SLC™ , or PLC-2® mapped tags	None

If importing tags with no External Access value specified, these default values are used:

Object Name	Default External Access during Import
Controller and Program standard tags	Read/Write
All Safety tags	Read/Write
Add-On Instruction local tags	Read/Write
Add-On Instruction input parameters	Read/Write
Add-On Instruction Output, EnableIn, and EnableOut parameters	Read Only
Add-On Instruction InOut parameters	N/A
Equipment Phase Output parameter	Read Only
Members of all data types	Read/Write
Alias tag	External Access value of its target

OPC UA Access

Tag Type/Usage	Incompatible OPC UA Access Values
Program Output Parameter	Read/Write
Program InOut Parameter	Read/Write Read Only
Safety controller and program scope tags	Read/Write
Const controller and program scope tags	Read/Write