Logix 5000 Controllers Import/Export Project Components ... · Logix 5000 Controllers Import/Export...

Programming Manual

Logix 5000 Controllers Import/Export Project Components 1756 ControlLogix, 1756 GuardLogix, 1769 CompactLogix, 1769 Compact GuardLogix, 1789 SoftLogix, 5069 CompactLogix, 5069 Compact GuardLogix, Studio 5000 Logix Emulate

Important user information

Read this document and the documents listed in the additional resources section about installation, configuration, and operation of this equipment before you install, configure, operate, or maintain this product. Users are required to familiarize themselves with installation and wiring instructions in addition to requirements of all applicable codes, laws, and standards.

Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required to be carried out by suitably trained personnel in accordance with applicable code of practice. If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be impaired.

In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.

The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams.

No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual.

Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited.

Throughout this manual, when necessary, we use notes to make you aware of safety considerations.

WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injury or death, property damage, or economic loss.

ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence

Important: Identifies information that is critical for successful application and understanding of the product.

Labels may also be on or inside the equipment to provide specific precautions.

SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be present.

BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous temperatures.

ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to potential Arc Flash. Arc Flash will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL Regulatory requirements for safe work practices and for Personal Protective Equipment (PPE).

Allen-Bradley, Rockwell Software, Rockwell Automation, and TechConnect are trademarks of Rockwell Automation, Inc.

Trademarks not belonging to Rockwell Automation are property of their respective companies.

Rockwell Automation Publication 1756-PM019I-EN-E - December 2018 3

Summary of Changes

This manual includes new and updated information. Use these reference tables to locate changed information.

Grammatical and editorial style changes are not included in this summary.

Global changes

This table identifies changes that apply to all information about a subject in the manual and the reason for the change. For example, the addition of new supported hardware, a software design change, or additional reference material would result in changes to all of the topics that deal with that subject.

Subject Reason

None

New or enhanced features

This table contains a list of topics changed in this version, the reason for the change, and a link to the topic that contains the changed information.

Topic Name Reason

Introduction on page 13 Added information about data exchange files that represent Rockwell Automation devices in the automation system.

Additional Considerations for Data Exchange on page 69

Added information about data exchange with other software applications, data exchange file type capabilities and limitations, and data exchange device support tables.


Table of contents

Studio 5000 environment ................................................................................ 9 Additional resources ....................................................................................... 9 Legal notices ................................................................................................. 10

Chapter 1

Introduction ................................................................................................... 13 Export considerations ................................................................................... 17

Security considerations for exporting components ................................ 19 Export logic components .............................................................................. 19 Import considerations ................................................................................... 20

Online import ......................................................................................... 20 Motion .................................................................................................... 22 Safety ...................................................................................................... 23 Security .................................................................................................. 23 Multiple components .............................................................................. 23

Import logic components .............................................................................. 24 Configuration properties for import .............................................................. 25

Properties for imported components ...................................................... 25 Configure multiple component properties .............................................. 29 Program connections .............................................................................. 32

Create a new connection .................................................................. 36 Configure component references ........................................................... 38 References configuration example ......................................................... 40 Undefined references .............................................................................. 41 Attention flags ........................................................................................ 41 Errors and warnings on import ............................................................... 42

Project documentation .................................................................................. 42 Find and replace ............................................................................................ 44

Compatibility .......................................................................................... 45

Chapter 2

Introduction ................................................................................................... 47 Export considerations ................................................................................... 47 Import considerations ................................................................................... 47

Chapter 3


Summary of Changes

Preface

Import and export logic components

Additional considerations for rungs

Additional considerations for routines

Table of contents

6 Rockwell Automation Publication 1756-PM019I-EN-E - December 2018

Chapter 4


Chapter 5


Chapter 6

Introduction ................................................................................................... 55 Create export files ......................................................................................... 55

Export to separate files ........................................................................... 56 Export to one file .................................................................................... 57

Import an Add-On Instruction ...................................................................... 58 Import considerations ............................................................................. 58 Import configuration .............................................................................. 59

Update an Add-On Instruction to a later revision using import .................... 60

Chapter 7

Introduction ................................................................................................... 63 Create export files ......................................................................................... 63 Import alarms and alarm definitions ............................................................. 63 Import considerations ................................................................................... 64

Chapter 8


Chapter 9

Data exchange with other software applications .......................................... 69 Data exchange file type capabilities and limitations ..................................... 70 Data exchange device support tables ............................................................ 72

1715 ........................................................................................................ 72 1719 ........................................................................................................ 72 1732 ........................................................................................................ 72 1734 POINT I/O ..................................................................................... 72 1738 ........................................................................................................ 74 1746 ........................................................................................................ 74

Additional considerations for programs and equipment phases

Additional considerations for user-defined types

Import and export Add-On Instructions

Import and export tag-based alarms and alarm definitions

Additional considerations for tags

Additional considerations for data exchange

Table of contents


1747 ........................................................................................................ 74 1753 ........................................................................................................ 74 1756 ControlLogix ................................................................................. 74 1757 ........................................................................................................ 79 1768 CompactLogix ............................................................................... 79 1769 ........................................................................................................ 80 1771 ........................................................................................................ 81 1783 Stratix ............................................................................................ 81 1784 ........................................................................................................ 82 1785 ........................................................................................................ 82 1788 ........................................................................................................ 82 1789 ........................................................................................................ 82 1791DS ................................................................................................... 82 1791ES ................................................................................................... 83 1794 FLEX I/O ...................................................................................... 83 1797 ........................................................................................................ 83 1799 ........................................................................................................ 84 193/592 ................................................................................................... 84 20-750 .................................................................................................... 84 5069 CompactLogix ............................................................................... 84 5094 ........................................................................................................ 85 ArmorPoint ............................................................................................. 85 ArmorStart .............................................................................................. 85 Communication ...................................................................................... 85 DPI to EtherNet/IP ................................................................................. 87 Drive ....................................................................................................... 87 Embedded ............................................................................................... 88 Energy Management Products ............................................................... 89 HMI ........................................................................................................ 89 Kinetix .................................................................................................... 89 Motion .................................................................................................... 89 MPI to EtherNet/IP................................................................................. 90 PowerFlex .............................................................................................. 90 Specialty ................................................................................................. 92 Other ....................................................................................................... 93

Index


Preface

The Studio 5000 Automation Engineering & Design Environment® combines engineering and design elements into a common environment. The first element is the Studio 5000 Logix Designer® application. The Logix Designer application is the rebranding of RSLogix 5000® software and will continue to be the product to program Logix 5000™ controllers for discrete, process, batch, motion, safety, and drive-based solutions.

The Studio 5000® environment is the foundation for the future of Rockwell Automation® engineering design tools and capabilities. The Studio 5000 environment is the one place for design engineers to develop all elements of their control system.

These documents contain additional information concerning importing and exporting projects and project components.

Resource Description

Logix 5000 Controllers Import/Export Reference Manual, publication 1756-RM084

Provides detailed reference information and examples for importing and exporting projects and components.

Logix 5000 Controllers Security Programming Manual, publication 1756-PM016

Describes how to configure security for controller projects using the Logix Designer application.

Product Certifications webpage, available at http://ab.rockwellautomation.com

Provides declarations of conformity, certificates, and other certification details.

View or download publications at http://www.rockwellautomation.com/literature. To order paper copies of technical documentation, contact the local Rockwell Automation distributor or sales representative.

Studio 5000 environment

Additional resources

http://literature.rockwellautomation.com/idc/groups/literature/documents/rm/1756-rm084_-en-p.pdf

http://literature.rockwellautomation.com/idc/groups/literature/documents/pm/1756-pm016_-en-p.pdf

http://ab.rockwellautomation.com/

http://www.rockwellautomation.com/literature

Preface


Copyright Notice

Copyright © 2018 Rockwell Automation Technologies, Inc. All Rights Reserved. Printed in USA.

This document and any accompanying Rockwell Software products are copyrighted by Rockwell Automation Technologies, Inc. Any reproduction and/or distribution without prior written consent from Rockwell Automation Technologies, Inc. is strictly prohibited. Please refer to the license agreement for details.

End User License Agreement (EULA)

You can view the Rockwell Automation End-User License Agreement ("EULA") by opening the License.rtf file located in your product's install folder on your hard drive.

Other Licenses

The software included in this product contains copyrighted software that is licensed under one or more open source licenses. Copies of those licenses are included with the software. Corresponding Source code for open source packages included in this product are located at their respective web site(s).

Alternately, obtain complete Corresponding Source code by contacting Rockwell Automation via the Contact form on the Rockwell Automation website: http://www.rockwellautomation.com/global/about-us/contact/contact.page Please include "Open Source" as part of the request text.

A full list of all open source software used in this product and their corresponding licenses can be found in the OPENSOURCE folder included with the Release Notes. The default installed location of these licenses is C:\Program Files (x86)\Common Files\Rockwell\Help\<Product>\ReleaseNotes\OPENSOURCE\index.htm.

Trademark Notices

Allen-Bradley, ControlBus, ControlFLASH, Compact GuardLogix, Compact I/O, ControlLogix, CompactLogix, DCM, DH+, Data Highway Plus, DriveLogix, DPI, DriveTools, Explorer, FactoryTalk, FactoryTalk Administration Console, FactoryTalk Alarms and Events, FactoryTalk Batch, FactoryTalk Directory, FactoryTalk Security, FactoryTalk Services Platform, FactoryTalk View, FactoryTalk View SE, FLEX Ex, FlexLogix, FLEX I/O, Guard I/O, High Performance Drive, Integrated Architecture, Kinetix, Logix5000, Logix 5000, Logix5550, MicroLogix, DeviceNet, EtherNet/IP, PLC-2, PLC-3, PLC-5, PanelBuilder, PowerFlex, PhaseManager, POINT I/O, PowerFlex, Rockwell Automation, RSBizWare, Rockwell Software, RSEmulate, Historian, RSFieldbus, RSLinx, RSLogix, RSNetWorx for

Legal notices

http://www.rockwellautomation.com/global/about-us/contact/contact.page

http://www.rockwellautomation.com/global/about-us/contact/contact.page

Preface


DeviceNet, RSNetWorx for EtherNet/IP, RSMACC, RSView, RSView32, Rockwell Software Studio 5000 Automation Engineering & Design Environment, Studio 5000 View Designer, SCANport, SLC, SoftLogix, SMC Flex, Studio 5000, Ultra 100, Ultra 200, VersaView, WINtelligent, XM, SequenceManager are trademarks of Rockwell Automation, Inc.

Any Rockwell Automation logo, software or hardware product not mentioned herein is also a trademark, registered or otherwise, of Rockwell Automation, Inc.

Other Trademarks

CmFAS Assistant, CmDongle, CodeMeter, CodeMeter Control Center, and WIBU are trademarks of WIBU-SYSTEMS AG in the United States and/or other countries. Microsoft is a registered trademark of Microsoft Corporation in the United States and/or other countries. ControlNet is a trademark of ControlNet International. DeviceNet is a trademark of the Open DeviceNet Vendors Association (ODVA). Ethernet/IP is a trademark of ControlNet International under license by ODVA.

All other trademarks are the property of their respective holders and are hereby acknowledged.

Warranty

This product is warranted in accordance with the product license. The product’s performance may be affected by system configuration, the application being performed, operator control, maintenance, and other related factors. Rockwell Automation is not responsible for these intervening factors. The instructions in this document do not cover all the details or variations in the equipment, procedure, or process described, nor do they provide directions for meeting every possible contingency during installation, operation, or maintenance. This product’s implementation may vary among users.

This document is current as of the time of release of the product; however, the accompanying software may have changed since the release. Rockwell Automation, Inc. reserves the right to change any information contained in this document or the software at any time without prior notice. It is your responsibility to obtain the most current information available from Rockwell when installing or using this product.

Environmental Compliance

Rockwell Automation maintains current product environmental information on its website at http://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page

http://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page

http://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page

Preface


Contact Rockwell

Customer Support Telephone — 1.440.646.3434

Online Support — http://www.rockwellautomation.com/support/

http://www.rockwellautomation.com/support/


Chapter 1

Import and export logic components

This chapter explains import and export of logic components and the exchange of data files that represent Rockwell Automation devices in the automation system.

Use the Logix Designer application to perform online edits for the Logix family of controllers.

The import/export functionality provides a greater degree of flexibility during development and deployment of projects. Import/Export supports the ability to export a component of a Logix Designer project and then import that component into either the same, or a different project, offline or online (even in Remote Run mode). Import/Export provides the ability to import components to create something new in a project, or to update something that exists.

Export and import these logic components offline and online:

• Rungs

• Routines

• Programs and equipment phases

• User-defined data types (UDT) and user-defined string types

• Add-On Instructions

• Trends

• Modules

Changes or additions to a project that may be impractical to do with online editing can be completed offline and then imported in one operation into a running controller by using the extended import/export feature. Engineering collaboration is also facilitated because many engineers can work on one or more of the project components independently offline and then use import to merge the changes into one project.

Introduction

Chapter 1 Import and export logic components


With online editing, modify or create a component and then modify other components referenced by that component in the project sequentially. Importing online differs from online edits in that it provides the ability to create and delete components, as well as update referenced components, in one step.

ATTENTION: All Rockwell Automation XML files are encoded in UTF-8 file format. Users editing XML files must use a text editor like Notepad that supports UTF-8 encoding. When saving the edited file by using a non-UTF-8 compatible editor after making changes, the encoding breaks, resulting in a non-valid XML file.

Data Exchange

Exchange data files that represent Rockwell Automation devices in the automation system produced in a tool such as EPLAN Electric P8 or AutoCAD Electrical. Create a Logix Designer project file that represents a controller-centric subset of the system without having to manually add, name, or recreate high-level configuration of the associated devices.

• 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)

The .rdf and .aml file types are used only for PLC data exchange as described below. When saving the Logix Designer project file to the data exchange file types, none of the tasks, programs, routines Add-On Instructions, user-defined type data from the project is stored. Only export the project file types when exchanging data with eCAD tools.

Tip: Import of eCAD data via data exchange file types is only possible when creating a new Logix Designer project. This data cannot be merged into an existing project.

Tip: Data exchange features differ between Studio 5000 Logix Designer and Studio 5000 Architect. Use the data exchange interface in Studio 5000 Architect to exchange I/O point tag/alias data and to conduct merge workflows into Studio 5000.

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.

Import and export logic components Chapter 1


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.

Number Description

Architect v 3.0 and later • Multiple controller environment

• Hardware device configuration exchange

• IO point tag (alias) exchange

• Round trip/merge exchange

Logix Designer v 32 • Single controller environment

• Hardware devices configuration exchange

• Round trip/merge data exchange not supported, must always bring data into new .ACD file

Version 2.7 and later • Import AML file to transfer PLC data to EPLAN Electric P8 interface

• Automation data attachment to part data/macros properly configured for AML

• Data can be connected manually if part data/macros aren't AML compatible

• Recreate Ethernet/ControlNet connections on single line drawing

• IO point symbolic address/function text placement from Architect ONLY

• Make IO point symbolic address/function text edits bring back into Architect ONLY



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.

Number Description

Version 2.7 and later • Utilize specific workflows are defined by EPLAN TechTip:PLC data Exchange to configure RA devices as

PLC Boxes with rack/slot, IO point symbolic address, function definition and network topology properties in EPLAN Electric P8

• IO point symbolic address and function text placement to Architect ONLY

• Make IO point symbolic address/description edits in Architect ONLY, bring back into EPLAN

Architect 3.0 and later • Multiple controller environment






• Round trip/merge data exchange not supported, must always bring data into new .ACD file

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.

Number Description

Architect v 3.0 and later • Multiple controller environment






• Round trip/merge data exchange not supported, must bring changes into new .ACD file

Data Adapter v 10 • Stand alone tool

• MUST be installed in same environment as AutoCAD Electrical

• Can also be co-located with Studio 5000

Version 2014 - 2018 • Rockwell Automation PLC and IO footprint symbol placement

• PLC and IO schematic symbol placement

• IO point name placement from Architect ONLY

• Make IO point name edits, use tool to bring back into Architect ONLY

Keep these considerations in mind when exporting components.

• More than is expected may appear in an .l5x file. Some components referenced by the exported component are also exported.

• Starting with version 24.00.00 of Logix Designer application, use program parameters to share data directly between programs in addition to Controller-scoped tags. For more information on program

Export considerations



parameters, refer to 1756-PM021, Logix 5000 Controllers Program Parameters Programming Manual.

When exporting a The exported component includes the

The exported file also includes referenced

Set of rungs Rungs Controller-scoped tags, program-scoped tags, user-defined data types, user-defined string types, Add-On Instructions

Routine Routine Controller-scoped tags, program-scoped tags, user-defined data types, user-defined string types, Add-On Instructions

Program (For considerations when exporting multiple programs using multi-select, see Multiple Components.)

Program, routines, and program-scoped tags

Controller-scoped tags, user-defined data types, user-defined string types, Add-On Instructions When exporting a program from the Logical Organizer, the program logical hierarchy is exported in addition to the program specified. Refer to the online help for information about the Logical Organizer.

Equipment Phase Equipment phase, routines, phase-scoped tags, and controller-scoped PHASE tag

Controller-scoped tags, user-defined data types, user-defined string types, Add-On Instructions

User-defined data type User-defined data type User-defined data types, user-defined string types, Add-On Instructions

User-defined string type User-defined string type

Add-On Instruction Add-On Instruction, Logic routine and any scan mode routines, and parameter and local tags

User-defined data types, user-defined string types, Add-On Instructions

Trend Trend

For example, if exporting a rung with an instruction that uses (references) a bit in a tag that is a user-defined type tag, the export content includes the referenced tag and the referenced user-defined type, along with the rungs. When importing the rung, choose whether to also import the referenced tag and user-defined type.

• Only the offline data values of tags are exported to the .l5x file, even when the project is online with the controller. When exporting components that include tags while online, the software prompts to upload tag values before exporting the component.

Important: Whether exporting while offline or online with the controller, only offline data values of tags are exported to the .l5x file.

• Export a component that has Test Edits, but the resulting file cannot be imported. If an .l5x file with Test Edits is selected for import, then the import aborts.

See also

1756-PM021, Logix 5000 Controllers Program Parameters Programming Manual





Multiple Components on page 23

The table describes considerations to keep in mind when exporting secured components.

For this security setting Keep this in mind

Permission set A permission set that restricts viewing an Add-On Instruction or routine in the Logix Designer application does not prevent a user from exporting and viewing the Add-On Instruction or routine in clear text. To prevent exporting the component, configure the permission set to deny the Routine: Export or AOI: Export permissions. To prevent exporting a component in clear text, configure the permission set to deny the Add-On Instruction: Export Unencoded permission for Add-On Instructions and the Routine: Export Unencoded permission for routines.

Source Key Protection When a component is protected with a Source Key, users without the source key cannot alter the logic of the component, and the protected component is written to the export file in an encoded format.

License-Based Source Protection The protected component is written to the export file in an encoded format unless the user's license contains Export permission. To export in non-encrypted text, the license must contain the Export permission, and when saving the export file, the user must clear the Encode Protected Content check box.

For more information on security considerations, see the Logix 5000 Controllers Security Programming Manual, publication 1756-PM016.

See also

Logix 5000 Controllers Security Programming Manual, publication 1756-PM016

Export logic components to import the component into another project, or to create a backup copy of a component while modifying the original.

To export logic components:

1. In the Logix Designer application Controller Organizer, select the logic component to export.

Tips: • Select multiple programs, Add-On Instructions, and user-defined data types for export. See the Import and Export Add-On Instructions chapter for detailed information.

• Also export logical components from the Logical Organizer. Select multiple programs and include child folders and programs in their hierarchical levels. Refer to the Logix Designer application online help for instructions.

2. Right-click and select Export <logic component>.

Security considerations for exporting components

Export logic components





3. In File Name, enter a file name for the export file.

Tip: Export multiple Add-On Instructions to a single file or to multiple files. See Configure multiple component properties for detailed information.

4. (Optional) Edit the default description or add a description, if desired.

A default description is supplied for some component exports.

Tip: The file description can be viewed in a tooltip during import when selecting which file to import.

5. Select Export.

See also

Configure multiple component properties on page 29

This section covers general considerations for all component-type imports. See the chapters for specific components (program, routine, rungs, Add-On Instructions, User-Defined data types, tags, and data exchange) for additional export and import considerations for that component, whether it is imported directly or as a reference during another component import.

Important: When editing online, if the program scan time is large, or the number of modified rungs is large, HMI and Logix Designer application communication timeouts may occur when edits are finalized. The timeout is caused by the (scan time) x (number of changed rungs). A large program with a very fast scan, or a lot of rungs (but only a few modified), may not timeout.

Tip: Starting with version 24.00.00 of the Logix Designer application, use program parameters to share data between programs in much the same way as using controller-scoped tags. Program parameters are imported and exported in the same way as tags in most instances. For more information on program parameters, refer to the Logix 5000 Controllers Program Parameters Manual, publication 1756-PM021.

See also

1756-PM021, Logix 5000 Controllers Program Parameters Programming Manual

The table describes considerations for importing components while online.

Topic Consideration

Tag data values When overwriting tags while online, data values are not written to the online project. Data values for overwritten tags while online are written only to the offline project. Data values for tags created while online are written to the offline and online project. Select the Preserve existing tag values in offline project check box to prevent tag values from being overwritten in the offline project.

Import considerations

Online import





Topic Consideration

Locking controller edits When performing an online import, the controller is locked, preventing other workstations connected to the controller from making edits until the import completes. If another workstation has the controller locked, an online import cannot be initiated.

Tag attributes Tag attributes (for example, External Access, Constant, and Style) are written to the online project and the offline project. If existing tags are to be overwritten with new attributes that are incompatible with existing user logic, the import is not allowed.

Online options When importing programs, equipment phases, routines, or rungs online, the logic can be imported as:

• Pending Edits that exist only in the offline project and are not downloaded to the controller.

• Accepted Edits that are downloaded to the controller where they can be tested, accepted, or canceled.

• Finalized Edits that are downloaded to the controller, assembled, and cannot be canceled.

As with normal online editing, with any online option chosen, any tags, data types, or Add-On Instructions that are created or modified are downloaded immediately. In addition, any task, program, or routine properties that are modified are downloaded immediately. These changes remain in the controller, even if logic edits are later canceled. Pending Edits and Accepted Edits options do not apply to Add-On Instructions and user-defined types, so Online Options are not presented during an Add-On Instruction or user-defined type import. Under these conditions, only the Finalize All Edits in Program option is available. • When online with the controller and importing a program that contains connections to

InOut parameters and:

• Changing the final connection of an InOut parameter online.

• When the connections are different than what is currently downloaded to the controller. Finalize All Edits In Program is the only option because the program is overwritten on Import. Configure the InOut connections such that the InOut parameter connection is taken not from the destination controller but from the Import file, or from a new final name for the connection entered by the user.

• When importing a program or programs with connections online and in Remote Run mode, and:

• A connection is changed from connect to disconnect.

• A connection is changed from disconnect to connect.

• The final name of a connection is changed.

• A connection is added and its operation is set to connect.

• When importing program hierarchies or multiple programs online and in Remote Run mode.

External access If the External Access is changed, it may change the behavior of the running HMI. Changed External Access attributes for overwritten tags can cause changes to HMI behavior, regardless of whether logic changes are tested, accepted, or finalized.



Topic Consideration

Asynchronous import Import operations are not synchronized with the Program Scan (just as online editing operations are not synchronized). For most objects, this does not matter because: • Existing online tag data values are never overwritten.

• New tags and their initial data values are written to the controller before the new logic runs.

• The switch-over to the new logic is synchronized with the program scan (just like online editing).

In general, although online tag data values are not overwritten, some object attributes can change asynchronously to the Program Scan. Some examples: • Changed attributes of existing programs or equipment phases (such as changing the Initial

Step Index of an equipment phase) are written to the controller before switch-over, so old logic can run with the new configuration.

• An existing program without a main routine could become configured with a main routine as part of import, and that main routine runs immediately even though the new logic for that routine has not yet been accepted.

• Changing Logix-based alarm tag configuration (such as alarm messages or associated tag definitions) can go into effect while the old alarm trigger logic is still active, resulting in alarm messages that do not match the condition.

Communication timeouts Communication timeouts may occur when rungs are deleted online in Run mode if the program scan time is long or the number of rungs being deleted is large. If using Partial Import Online and choosing Pending or Accept edits, when finalizing those edits, a timeout can occur. This timeout can occur as HMI or Logix Designer application communication timeouts. Keep these timing considerations in mind. • Finalizing online edits while in Run mode causes brief interruptions to communication,

which are usually unnoticeable.

• The length of the communication interruption is related to the product of the (task scan time) x (the number of changed rungs).

• When very long program scans or large quantities of changed rungs occur, the communication interruption can be long enough to cause timeouts.

• The timeout of a Rockwell Automation HMI is typically 8 seconds, while a Logix Designer online session typically has a 30-second timeout.

• It does not matter whether the edits came from individual online edits or from a Partial Import Online (choosing Pending or Accepted edits).

• Partial Import Online (choosing Finalize Edits) does not cause the communication timeout, due to the use of asynchronous transaction commit processing.

The table describes considerations for importing motion components while online.

Topic Consideration

Motion components limitations while online

Motion tags (Axis, Coordinate System, and Motion Group) cannot be created, modified or deleted during an online import, however, existing motion tags can be referenced. When doing an offline import, motion tags can be created and modified.

Motion



The table describes considerations for importing safety components.

Topic Consideration

Safety components limitations while online

Safety components cannot be created, modified or deleted during an online import.

Safety components limitations while offline

Safety components cannot be created, modified or deleted during an offline import. If a Safety Signature exists, the project is Safety locked. A non-recoverable safety fault is present if the Safety Partnership status between the primary controller and the safety partner is any value other than OK, or if Safety modify permissions are denied.

Scheduled location In a Safety project, Safety programs cannot be imported into a Standard task and vice versa.

Safety programs imported into a standard project

Safety programs imported into a Standard project are converted to Standard programs during the import processing and a warning appears in the Errors Pane during initial parsing of the .l5x file. In this case, imported logic does not verify after import if it contains instructions that are only valid in a Safety routine.

Controller Fault Handler and Power-Up Handler

A Safety program cannot be scheduled in the Controller Fault Handler or Power-Up Handler folders.

The table describes considerations for importing a secured project or component.

Topic Consideration

Project or components are secured by a permission set

If the project or components in it are secured by a permission set, the import process may not be able to create, delete, or modify some components, depending on the security actions that have been granted or denied for those components.

Project or components are secured by License-Based Source Protection

A CmStick containing a license with Use permission must be present locally on any USB port on the computer. Use permission cannot be obtained from a network license server. All other license privileges can be contained on the local CmStick, or provided by a license server on the network.

For more information on security considerations, see the Logix 5000 Controllers Security Programming Manual, publication 1756-PM016.

See also

Logix 5000 Controllers Security Programming Manual , publication 1756-PM016 .

The table describes considerations for importing multiple User-defined types and Add-On Instructions and multiple target programs.

Topic Consideration

Importing multiple User-defined types (UDTs) and Add-On Instructions (AOIs)

When User-defined types (UDTs) and Add-On Instructions (AOIs) are imported using the Multiple Components option, all UDTs and AOIs are treated as references. Unlike child components, referenced components can be configured independently from the import target.

Safety

Security

Multiple components





Topic Consideration

Controller Fault Handler and Power-Up Handler disabled

When importing multiple target programs, the Controller Fault Handler and Power-Up Handler are unavailable in the Schedule In list.

Use these steps to import logic components. Import components from the Controller Organizer and from the Logical Organizer.

Importing components into a controller while online can affect controller operation. Use caution when modifying logic while online in Remote Run or Run mode.

To import logic components:

1. Select the item and choose the import component menu item as described in the table.

To import a Right-click And choose

Set of rungs A rung or set of rungs within a Ladder routine editor

Import Rungs

Routine A program Import Routine

Program A task, the Controller Fault Handler folder, the Power-Up Handler folder, or the Unscheduled Programs folder

Import Program

Equipment Phase A task or the Unscheduled Programs folder Import Equipment Phase

Important: This feature is disabled in this version of the Logix Designer application.

User-defined data type User-Defined folder Import Data Type

User-defined string type Strings folder Import String Type

Add-On Instruction Add-On Instructions folder Import Add-On Instruction

Trend Trends folder Import Trend

2. Select the file to import.

Select multiple components for import. See Configure multiple component properties for information.

3. Select Import.

4. Continue by selecting the configuration options described in the section below, Configuration properties for import.

See also

Configure multiple component properties on page 29

Import logic components



This section describes configuration options for importing components.

Tip: Trends do not require any import configuration, so the Import Configuration dialog box does not appear and the trend is imported immediately.

When importing components, the previously exported information is brought into the project based on the selected import configuration. Determine how the imported component (a program, for example) connects to the existing project either by overwriting an existing component of the same type, or by creating a new one.

The screen capture shows a typical Import Configuration dialog box. (The dialog box might contain options different than those shown here, depending on the imported component.)

An import component collides with an existing component if a component of the same type, scope, and with the same name exists in the project. By configuring the Final Name of the imported component, you determine whether the imported component collides with an existing component, or it does not (if a component of the same type, scope and with the same name does not exist in the project). For a collision, you can use the existing project component or you can overwrite it. For a non-collision, you can create a project component or you can discard, and not import, the component from the import file. In any case, any imported logic references are updated to be the same as the Final Name.

Configuration properties for import

Properties for imported components



By configuring the Operation for the component, you determine whether it is imported from the file or an existing component is used. Incompatibility of a collision or other situations, for example, project security privileges, may affect what Operations are permitted for a component.

The table describes the configuration options.

Configuration Description

Import Name The Import Name is read-only and shows the name of the component as read from the import file.

Operation The Operation determines whether the component from the import file is imported. Not all operations are applicable to a given component in all situations. Sometimes there is only one possible operation permitted in a particular situation. Choose from these options:

• Use Existing (collisions) to use the existing component in the project. The component definition in the import file is not imported. If the component collides and there is no definition for the component in the import file, then this is the only Operation available.

• Overwrite (collisions) to import the component definition from the import file and overwrite the existing component definition in the project.

Important: If selecting Overwrite for a reference tag, the tag data that is different is written to the offline project only, even if online with the controller.

• Create (non-collisions) to import the component from the import file creating a new component in the project.

• Discard (non-collisions) to discard the component and abort import. If the main component from the import file (the program during a program import, for example) is discarded, the references can still be imported. If a referenced component is discarded, any imported logic references are not defined in the project and might not verify after import.

• Undefined (non-collision) is the only Operation available if the component does not collide and there is no definition for the component in the import file. The imported logic is not verified after import.

• Delete (non-collision) indicates that this component will be deleted from the project on import.

Final Name The Final Name determines the name of the component that shows in the project after the import (except in the case of a Delete Operation). Create or avoid collisions by changing the Final Name. If change the Final Name to differ from the Import Name, all logic references in the import content are updated. If change the Final Name of a component during configuration so that it collides with a different existing component after it was colliding with another, any changes made to the Operation are preserved.

Description The Description that is shown depends on the Operation. If the Operation is: • Overwrite or Create, the description is initially the description from the import file. Edit

it during import configuration.

• Discard, the description is initially the description from the import file. It is read-only and may not be edited.

• Use Existing or Delete, the description is the existing component description. It is read-only and may not be edited.

• Undefined, no description is shown.

The description for members of an expanded tag follow the same rule the tag follows. Only members of the tag that have descriptions are shown when the tag is expanded.




Schedule In The Schedule In setting determines the task in which the imported component is scheduled. The default setting for Schedule In depends on the Operation setting and whether you import the component into the Controller Organizer or the Logical Organizer. If you import the component into the Controller Organizer: • When selecting a task or handler and Operation is set to Overwrite, Schedule In is

set to the selected task or handler.

• When selecting a task or handler and Operation is set to Use Existing, Schedule In is set to the task or handler where the program is scheduled in the destination project.

• When the selection in Controller Organizer is not a task or handler, Schedule In is set to Unscheduled Programs/Phases.

If importing the component into the Logical Organizer: • When set Operation to Create or Discard, Schedule In is set to Unscheduled

Programs/Phases.

• When set Operation to Use Existing or Overwrite, Schedule In is set to the Task or Handler for which the program is scheduled in the destination project.

Adjust the Schedule In setting when: • Operation is set to Create (the target component is being created).

• Operation is set to Overwrite and not online in Remote Run mode.

Change the Schedule In setting when:

• Import a program folder.

• Operation is set to any setting other than Create or Overwrite.

Preserve scheduling for child programs that already exist

When selecting this setting, any child programs that exist in the destination project remain scheduled as configured in the project. When clearing this setting, all imported programs are scheduled in the task specified by the Schedule In setting. This setting is available when Operation is set to Create or Overwrite; otherwise it is read-only. When enabled, this setting is selected by default. The setting is not preserved between import sessions.




Parent Determines where the imported component is organized. The default setting for Parent depends on whether exported the component from the Controller Organizer or the Logical Organizer, whether importing it to the Controller Organizer or the Logical Organizer, and on the Operation setting. • If exported the program from the Controller Organizer and importing it to either

the Controller Organizer or the Logical Organizer:

• Parent is set to the selected program in the Logical Organizer if the operation is Create or Discard.

• Parent is set to the parent configured in the destination project if Operation is set to Use Existing or Overwrite.

• If exported the program from the Logical Organizer and 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 exported the program from the Logical Organizer and 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.

When there is a collision, the components colliding may be identical, or they may be different. If they are the same, the Operation defaults to Use Existing. If they are different, imported components default to Overwrite while referenced components default to Use Existing. Choose Overwrite to use the component definition from the import file, or Use Existing to use the component in the project. Icons on the Import Configuration dialog box (next to the Operation control) show whether colliding components are identical or different.

Situation Icon

Component shows only in the import file (non-collision)

Component shows only in the project (non-collision) Component collides with a component in the project and differences exist Component collides with a component in the project and they are identical No icon

To see the differences between the import component and the colliding project component, select Collision Details and a dialog box opens. Use the information in the dialog box to determine whether to overwrite or to use the existing component.



For components that do not collide, select Properties for more information on the component.

Important: A component selected for import that collides with an existing component defaults to overwriting the project component unless the components are identical, in which case, the project component is used. If the project component is used, references may still be imported.

This section describes the settings to use to import and configure multiple components.

To configure multiple component properties:

1. Select components for export from a project.

2. Export those components.

3. Select those components and import them into another project.

Use one of these methods to import multiple components.

• Select File>Import Component and choose the component type to import.

• Copy the programs, Add-On Instructions, or user-defined data type, right-click a task in the organizer, and select Paste With Configuration.

Tip: The Paste With Configuration menu option works when copying from the Controller Organizer to the Logical Organizer, and vice versa.

Configure multiple component properties



The screen capture shows a typical Import Configuration dialog box for multiple components. (The dialog box might contain options different than those shown here, depending on the imported components.)

Imported items are listed in the Import Content pane. These items are listed in the Import Content pane based on the items that are part of the import content.



• Programs -- If importing multiple programs, the grid shows the programs that are being imported into the project. If importing multiple hierarchies, the grid shows the programs and the children of the programs that are being imported into the project.

• Tags, Add-On Instructions, data types and other components -- References include any tags directly referenced by any imported logic or tags (using Alias For).

• Connections -- Lists the connections, from programs that are external to the programs in the import content, that are also connected to programs in the existing project.

The table describes the multiple-import configuration parameters.


Multiple Programs The Import Content pane shows the number of programs that are being imported into the project. The value shown in the parenthesis excludes children of the programs. If differences occur among the programs, the difference icon appears in the Differences column of the Programs grid.

Imported Programs Shows the number of parent and child programs (if applicable) that are being imported into the project.

Operation Identifies what is done with the programs upon import.

• If Import is selected, all programs are imported into the project.

• If Discard is selected, the programs are not imported into the project.

The field is set to Import by default. Select Discard, if necessary. Tip: To see the Operation value for a specific program, check the Programs grid of the program's child program.

Schedule In Shows the task in which the imported programs are scheduled. The default value for Schedule In is either the selected task or Unscheduled Programs/Phases based on which method was use to import the content, and from which organizer the import was initiated.

• If using Paste Special>With Configuration in the Controller Organizer, the default value is the selected task.

• If using the Paste Special>With Configuration option or the File>Import Component option in the Logical Organizer, the default value is Unscheduled Programs/Phases.

Set Operation to Import to modify Scheduled In.

Do not change scheduling of existing programs

When selected, programs that exist in the project remain scheduled as they are configured in the project. The check box is selected by default. When cleared, upon import, programs are scheduled in the task specified in Schedule In. To modify this option:

• Operation must be set to Import.

• The controller cannot be in Remote Run mode.




Parent Specifies how the programs are organized upon import.

• When importing a program into the Logical Organizer, the default is the Parent in the selected program in the Logical Organizer.

• The default is <none> when a Parent is not specified in the selected program in the Logical Organizer, or when importing programs into the Controller Organizer. If a Parent is not specified, the programs remain organized as they are configured in the project.

Set Operation to Import to modify the Parent option.

Do not change parent of existing programs

Select this check box and programs that exist in the project remain organized as they are configured in the project. The check box is selected by default. Clear this check box and upon import, programs are organized in the program that is specified in Parent. All child programs are imported as organized in the import content regardless if the check box is selected or cleared. Set Operation to Import to modify this option.

See also

Program connections on page 32

When importing a program, it might require configuration of connections to program parameters or controller scope tags that exist in the project. Configure connections when selecting the target program on the Import Configuration dialog box and Operation is set to Overwrite or Create. If Operation is set to Use Existing or Discard, the Connections grid does not appear.

When importing multiple programs, any connections between the programs being importing cannot be configured, and do not appear in the Connections grid. However, any connections with endpoints outside these programs do appear and may be configured.

The Logix Designer application imports the connection endpoints, and they remain what they were in the original project. If the endpoints exist in the destination project, they bind automatically. If the endpoints do not exist, they are flagged as errors and the Final Connection name must change to bind them to the correct connections, or remove the connections.

These diagrams describe how imported connections are established.

Program connections



In My Original Project, the parameters in Program1 are connected to parameters in Program2.

When importing the original Program1 into My New Project, the parameters in Program1 connect automatically to matching parameters in Program2. Parameters that do not match are flagged as errors. Change the Final Connector for those parameters.

If the endpoint names are different in My New Project (for example, Program3), either open the Connections grid and change the Final Connection name on the endpoints from Program2 to Program3, or go to the References grid and change the final name on Program2 to Program3 in one place, and all the connections change automatically.



To open the Connections grid, select Connections on the Import Configuration dialog box.

This screen capture shows the Connections grid as it would appear when importing Program1 into My New Project, as described earlier in this section. To fix the connection errors, select Disconnect in the Operation field, or select a different connection in the Final Connection field.

The indicator column at the far left of the Connections grid shows the condition of the connection. The table describes the connection conditions.

Indicator Connection Condition

* Indicates a row in which content has changed and the change has not been saved.

Indicates a row in which the connection endpoints are invalid due to a syntax error. If selecting OK to begin the import, an error message opens. Fix or remove the connection before proceeding.



Indicator Connection Condition

* Indicates a row in which content has changed and the change has not been saved.

Indicates that the connection being imported will contain an error at the completion of the import. Proceed with the import, and the connection is created, but fix the error before downloading the project to the controller.

Indicates a row in which to create a connection.

The table describes the Connections grid columns and settings.

Column Description

Parameter The parameter identified in this field is the parameter in the import content that is to be connected to another parameter on a program that exists in the project. A New Connection option is available on the last row of the grid if the import content contains only one program. Create connections that are not part of the import content by connecting a program parameter in the import content to an endpoint connection on a program that is in the project to have a new connection that did not exist in the import content nor in the program that exist in the project. See Create a new connection for more information.

Data Type Shows the data type of the parameter. A parameter can only be connected to a member or bit of a tag or parameter with the same data type or an error occurs when verifying the program.

Usage Shows the usage type of the parameter as Input, Output, InOut, or Public.

Import Connection Shows the name of the connection endpoint for the parameter as read from the import file. Import Connection is blank if the connection is only defined in the program that exists in the project.

Differences

Indicates if there are differences between the connections in the import content and the connections in the target project. Also identifies if a connection exists in the import content, or if it exists in the program that is in the project. Select the Browse button in the Details column to see more extensive component properties. Two icons show how the imported content matches the content of the program that exists in the project:

Indicates a connection that is present in the import content and not in the project.

Indicates a connection that is present in the project and not in the import content.

Operation Identifies whether the connection is made upon import of the program into the project. Select Connect or Disconnect to change the connection status for the connection. Connect - Upon import of the program, this connection that is defined in the import content will be created in the project. This is the default value when a connection between the parameter and the final connection is valid. Disconnect - Upon import of the project, the connection that is defined in the import content will not be created in the project. This is the default value when the connection between the parameter and the final connection is not valid. See the example later in this section for more information on the Operation field.

Details

Select the Browse button to open the Connection Properties dialog box. On the Connection Properties dialog box, select Connect or Disconnect to change the connection status for the connection.



Column Description

Final Connection The parameter or tag in the existing project that the import parameter will be connected to. Change the value in Final Connection based on the value in Operation. Type the final connection name or select the down arrow to make a selection from the tag browser. If the parameter is a MODULE InOut parameter, the module browser appears instead of the tag browser. For more information about the tag browser and module browser, see the online help topics Using the Tag Browser and Using the Module Browser. If entering an invalid final connection, the error indicator displays in the leftmost column. Hover the cursor over the error indicator to see a description for the cause of the error. See the example later in this section for more information on the Final Connection field.

Using the Operation and Final Connection fields to establish connections

This is an example on using the Operation and Final Connection fields to establish connections.

Parameter in Imported File

Connection in Imported File

Operation Value Final Connection field What happened in this case

\Prog1.InA \Prog2.OutA Connect \Prog2.OutA This connection exists in both the import content and in the program in the project, so the connection is the same.

\Prog1.InB \Prog2.OutB Connect \Prog2.OutB The endpoint parameter does not exist in the target project file.

If importing the program offline, the error flag appears. Continue the import, but resolve the error before downloading the project to the controller.

If importing the program online, the red-x error appears, resolve the error before continuing the import. To resolve the error, either: • Set the Operation Value to Disconnect (see Example Row 3 in this table).

• Select an existing parameter in the Final Connection field to reassign the connection (see Example Row 4 in this table).

\Prog1.InB \Prog2.OutB Disconnect \Prog2.OutB Example Row 3: Parameter \Prog2.OutB does not exist in the target project, so set Operation Value to Disconnect.

\Prog1.InA \Prog2.OutA Connect \Prog3.OutB Example Row 4: Parameter \Prog2.OutA does not exist in the target project, so in Final Connection, select an existing parameter to reassign the connection.

\Prog1.InC none Connect \Prog3.OutD This connection did not exist, so in Final Connection, select an existing parameter to create the connection. See Create a new connection for more information on creating connections.

See also

Create a new connection on page 36

When importing one program, create a new connection on the last row of the Connections grid. The new connection connects a program parameter in the import content to an endpoint connection in a program that is in the project. The new connection did not previously exist in the import content nor in the project. The New Connection row is not available when importing multiple programs with existing connections between the programs that are importing.

Create a new connection



Type the parameter name for the new connection or select the down arrow to make a selection from the tag browser. Because only parameters that are in the import content are valid for the Parameters field, only the parameters that reside in the import content are listed in the tag browser. For more information about the tag browser, see Using the Tag Browser in the online help.

When both the parameter and final connection have been specified, the connection is made (added) to the connection grid after moving off the New Connection row or after pressing Enter. If entering an invalid parameter or final connection, the connection is not created and the error indicator displays in the leftmost column. Hover the cursor over the error indicator to see a description for the cause of the error.



In addition to determining how the component is imported, configure how references are imported. The references are all other components used by the exported component at the time it was exported. For example, a program .l5x file contains the definition of all controller-scoped tags, user-defined data types, user-defined string types, and Add-On Instructions referenced by the program at the time the program was exported. During import configuration, determine what the references from the imported component connect to after import. Connect a reference to an existing component in the project and not import the referenced component from the import file. Or, use the referenced component in the import file either by creating a new component in the project from the definition in the import file or by overwriting an existing component of the same type in the project.

As with imported components, if the Final Name of a referenced component (such as a tag) matches a component of the same type and scope in the project, these components collide. If there is no collision, the component is identified as needing to be created (Operation is Create).

Icons in the Differences column ( ) on the Import Configuration dialog box show whether components collide with differences, or the component only exists in the import file or the project.

Configure component references



Select the icon in the Details column ( ) and a Collision dialog box opens showing the differences between the import component and the colliding project component. Use the information in the Collision dialog box to determine whether to overwrite or use the existing component.

For components that do not collide, click the same icon for more information on the component.

Tip: A referenced component that collides with an existing component defaults to using the project component (Operation is Use Existing), even if the definitions of the components are different. To import the referenced component definition from the import file, Overwrite must be selected.

Connecting a referenced component to a component of the same type, but with another name in the project, causes any reference to the component in the imported logic to be updated to the new name. For example, if connecting a Boolean reference tag A to B[3].ACCUM.4 (where B is an existing tag in the project that is an array of structures), then all references in the imported logic that used to say A now say B[3].ACCUM.4. Another way to connect reference tags to existing tags in the project is to modify their Alias For field. This is permitted when the reference tag is being created or the reference tag is overwriting an existing tag (offline only), regardless of whether it was originally an alias tag. Use the Import Configuration dialog box to configure the references that must connect during the import process.

Important: It is important to note that even if a component has an Operation of Discard, Use Existing, or Undefined, if the Final Name differs from the Import Name, then the imported logic references to that component are updated to reflect the Final Name. For example, if entering an invalid name as the Final Name for a tag reference, the Operation is set to Discard but the imported logic references to that tag are still updated to the invalid Final Name.



The example shows how an imported routine plugs into the components in a project after configuring it.

For example, if importing a routine, the routine itself is the main import component. References that should be connected during the import could include program-scope tags, controller-scope tags, user-defined data types, any routines called by JSR instructions, and any Add-On Instructions in the routine logic.

In this example, a routine export file contains the definitions of Tag_A, Tag_B, AOI_1, and UDT_1. The routine also contains a reference to Routine_A, but excludes the logic in Routine_A.

During import configuration, connect each:

• Reference tag in the import routine to a program or controller-scoped tag in the project.

• Reference routine in the import routine to a routine in the project.

• User-defined data type defining a reference tag in the import routine to a user-defined data type in the project.

• Add-On Instruction in the import routine to an Add-On Instruction in the project.

References configuration example



These tags, user-defined data types, and Add-On Instructions might exist in the project, or they can be created when importing the routine.

• Tag_A is set to Create, so the imported logic referencing Tag_A references the newly created Tag_A in the project.

Tag_B has its Final Name changed to Tag_D and is set to Use Existing, so it is not created, and imported logic referencing Tag_B instead references existing Tag_D.

• Routine_A has its Final Name changed to Routine_B, so imported JSRs to Routine_A uses the existing Routine_B.

• AOI_1 is set to Overwrite an existing Add-On Instruction called AOI_1, so not only do imported logic and tags use AOI_1, but also any existing references to AOI_1 in the project now uses the new definition of AOI_1 from the imported routine.

• UDT_1 is set to Overwrite an existing user-defined data type called UDT_2, so imported logic and tags use UDT_2 and the existing UDT_2 is overwritten (except for the name) with the definition from UDT_1. Logic and tags from the project now use the new definition of UDT_2.

In the Logix Designer editor, it is possible to create logic that references tag, user-defined data type, or Add-On Instruction components that do not yet exist. These are considered undefined references. If exporting that logic, there is no component definition to export for that undefined reference. On import, these tags, user-defined data types, or Add-On Instructions appear with an Operation of Undefined during import configuration unless the component exists in the project (in which case the Operation is Use Existing). Similarly, when logic references any type of component other than a tag, user-defined data type, user-defined string type, or Add-On Instruction (for example, a routine that is referenced by a JSR instruction), the definition for these referenced components are excluded from the import file and they also appear with an Operation of Undefined if the component does not exist in the project.

During import configuration, these undefined references can be configured as well. Since there is no definition for these components in the .l5x file, a project component cannot be overwritten or a component created during the import process. Use an existing component for that reference. Configure which component in the project to connect the reference to, or leave the reference undefined. An undefined reference that collides with an existing component defaults to using the project component.

Attention (red) flags provide alert to import situations that may be unintended or may lead to a project that does not verify successfully after import. What they describe may or may not prevent the import from proceeding. If online, and the project does not verify successfully when accepting or finalizing edits, the import fails. Not all attention flags cause a project to fail verification. The red flag indicates the potential problem to

Undefined references

Attention flags



make a decision about what to do. Ignore the attention message or try to change the Final Name or Operation of the component to resolve the issue.

Tip: Hover the cursor over the attention flag to open a tooltip that explains the issue.

When an import fails or is canceled, all changes caused by the import are discarded, leaving the project in the same state it was in before the import, even if the project is online with the controller. If the import fails, the Import Configuration dialog box opens with Errors selected. To attempt to import again, inspect the errors and warnings, reconfigure the import, and click OK.

The Logix Designer application provides the option to set the display language for project documentation, such as tag descriptions and rung comments, using any of the supported localized languages. Store project documentation for multiple languages in one project file rather than in language-specific project files. Define the localized languages that the project supports and set the current, default, and optional custom localized language. The software uses the default language if the current language's content is blank for a particular component of the project. Use a custom language to tailor documentation to a specific type of project file user. When configuring project documentation in the Logix Designer application for a project, dynamically switch between languages in that project within the software.

These project documentation items support multiple languages:

• Component descriptions in tags, routines, programs, equipment phases, User-Defined data types, and Add-On Instructions

• Engineering units and state identifiers added to tags, User-Defined data types, or Add-On Instructions

• Trends

• Controllers

• Alarm Messages (in configuration of ALARM_ANALOG and ALARM_DIGITAL tags)

• Tasks

• Property descriptions for modules in the Controller Organizer

• Rung comments, Sequential Function Chart fields, and Function Block Diagram fields

The export and import features of the Logix Designer application support project documentation. Transfer project components between projects that have different project documentation settings.

Errors and warnings on import

Project documentation



If a component was exported to an .l5x file from a project with project documentation turned off and is then imported into a project with project documentation turned on, all project documentation brought in by the import is associated with the project’s current language.

If a component was exported to an .l5x file from a project with project documentation turned on, all language switched comments are exported with the component. When importing an .l5x file that includes language switched comments, the Import Configuration dialog box includes a Current Import Documentation Language selection.

If the project has project documentation turned on, all language-switched comments from the .l5x file are imported into the project. This may result in additional languages being available in the project after import. Selecting a language in Current Import Documentation Language allows editing of that language’s comments from the import file during the import configuration process.

If the project does not have project documentation turned on, import only one set of localized comments from the import file. In this case, selecting a language in Documentation to Import determines which language’s comments are imported with components from the import file. Edit the language’s comments during the import configuration process, but only the final language selected when import proceeds is imported with components.

Important: Only comments associated with imported components are brought in from the import file. If an existing component is used, import file comments for that component are not imported.

Important: Multiple localized alarm messages can be stored (in configuration of ALARM_ANALOG or ALARM_DIGITAL tags) even if the project does not have project documentation turned on. Therefore, all alarm messages are imported, regardless of the Documentation Language to Import selection on the Import Configuration dialog box.

Important: The Documentation Language to Import selection does not affect the setting of the language defined in the project after import.



Use the Find controls in the Import Configuration dialog box control bar to search for text within the dialog box. Use the Find/Replace dialog box to configure whether Find searches through the Import Name, Final Name, Description, Alias For, and the Data Type fields. As the search progresses, the Import Configuration dialog box automatically switches to different panes within the dialog as needed.

Replace text fields during the search. Replacing text fields facilitates development of a component template to import repeatedly, replacing template text during each import. When designing a program template, keep in mind that during a program import, the program tag names and descriptions cannot be edited or replaced. However, during import, edit the names and descriptions of controller-scoped tags referenced from the program. Similarly, when importing an equipment phase, edit the names and descriptions of tags in the equipment phase, and when importing an Add-On Instruction, editing the names and descriptions of the parameters and local tags is not allowed.

To find and replace:

1. On the Import Configuration dialog box, select Find/Replace.

2. In the Find What box, enter text that to search. Enter a search string or select text from a previous search.

3. To replace text that is found, in the Replace With box, enter the replacement text.

To use wildcards in the search string and in the replacement text, select Use Wildcards. Use asterisks (*) as wildcard characters. The table provides examples of Find-Replace operations using wildcards.

Find What Replace With Text Found Replacement Result

tk1_*_001 PRE_*_010 tk1_me_001 PRE_me_010

tk3_* tk4_* tk3_unit tk4_unit

*001 *002 mi_2001 mi_2002

*tank* *TNK* M1_tank_003 M1_TNK_003

* PRE_* some_name PRE_some_name

4. To limit search and replace to the currently selected pane, select Search current view only. Change the selected pane without closing the Find/Replace dialog box.

Find and replace



5. Use the Find Within check boxes to configure which fields to search.

6. Select Find to search for the next matching item.

7. Select Replace to replace the text in a text field. Select Replace All to replace all instances of the search text specified in Find What with the text in Replace With field.

See also

Properties for imported components on page 25

The import/export feature supports backward compatibility for import operations and forward compatibility for export operations.

Backward compatibility means that the Logix Designer application can import .l5k or .l5x files that were generated by a previous version of the application. In some cases, an older .l5k file might not correctly import into a later version of the application.

The import/export feature supports forward compatibility for export operations. It does not support backward compatibility for export operations. This means that earlier versions of the Logix Designer application cannot read .l5k or .l5x files that were created with later versions of the application. In some cases, an .l5k or .l5x file created with a later version of the Logix Designer application may import with warnings into an earlier version of the application. In these cases, attributes on components may be set to default values during import.

Compatibility



Each version of the Logix Designer application exports .l5k files with a specific import/export Logix Designer application version number. The Logix Designer application imports any .l5k file with the same major revision number and the same or lower minor revision number. The major Logix Designer application version number increments when file properties prevent the application from supporting backward compatibility for import operations. The minor version number increments whenever there is a change in the file (a new module, an attribute is added, the set of options for an attribute is changed) that does not affect backward compatibility for Logix Designer application import operations.

Important: Use caution when copying and pasting components between different versions of Logix Designer application. Logix Designer application supports pasting to only the same or later version. Pasting to an earlier version of Logix Designer application is not supported. When pasting to an earlier version, the paste action might succeed but the results might not be as intended.


Chapter 2

Additional considerations for rungs

This chapter explains import and export of rungs.

One rung or a contiguous set of selected rungs may be exported to an .l5x file.

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 rungs. If they exist in the project, the definitions for the referenced tags, Add-On Instructions, and user-defined data types are exported to the .l5x file. In the case of rungs exported from an Add-On Instruction routine, if they exist at the time of export, any parameters and local tags referenced are exported.

When importing rungs, configure how the referenced components are imported during import configuration. By default, referenced components that collide with project components are not imported.

Considerations when importing rungs.

Topic Consideration

Pending Edits exist If rungs are imported into a program or equipment phase that contains pending edits, all pending edits in the program are accepted if Accept Program Edits is selected during import of the rungs. Similarly, all pending edits in the program are finalized if Finalize All Edits In Program is selected during import of the rungs.

Accepted Edits exist Rungs cannot 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.

First scan When importing rungs into an existing program, the S:FS bit is not set during the program’s next scan. This applies when importing rungs into an existing equipment phase as well.

Collision handling If selecting Overwrite Selected Rungs in the Import Rungs dialog box, the imported rungs overwrite the rungs selected in the project. If Overwrite Selected Rungs is cleared, the imported rungs are inserted before the selected rungs in the project if the ladder editor is in Insert mode, they are inserted after the selected rungs if the ladder editor is in Append mode.

Introduction



Chapter 2 Additional considerations for rungs


Topic Consideration

Tag scope When exporting rungs from a program or equipment phase and import them into an Add-On Instruction routine, any referenced controller-scoped or program-scoped tags are converted on import. The tag is converted to a local tag unless local scoped is not allowed (for example, a Motion Group tag cannot be a local tag), in which case the tag is converted to an InOut parameter. When exporting rungs from an Add-On Instruction routine and import them into a routine in a program or equipment phase, the referenced parameters and local tags are converted on import. The parameter or local tag are converted to a program-scoped or phase-scoped tag unless it is not allowed (for example, a Motion Group tag cannot be a program-scoped tag), in which case it is converted to a controller-scoped tag.

For considerations for referenced user-defined types, Add-On Instructions, and tags that may be imported with the rungs, see import and export of user-defined types, Add-On Instructions and tags.

See also

Import and export user-defined types on page 53

Import and export Add-On Instructions on page 55

Import and export tags on page 67


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. If they exist in the project, the definitions for the referenced tags, Add-On Instructions, and user-defined data types are exported to the .l5x file.

When importing a routine, configure how the referenced components are imported during import configuration. By default, referenced components that collide with project components are not imported.

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 exporting an SFC routine and importing 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



Chapter 3 Additional considerations for routines


For considerations for referenced user-defined types, Add-On Instructions, and tags that may be imported with the rungs see import and export of user-defined types, Add-On Instructions, and tags.

See also

Import and Export user-defined types on page 53


Import and export Tags on page 67


Chapter 4

Additional considerations for programs and equipment phases

This chapter explains import and export of programs. All topics apply to equipment phases as well; any exceptions are noted.

A program can be exported to an .l5x file. The exported program includes all of its program tags and routines, which are imported with the program automatically.

The export file may also include any controller-scoped tags, Add-On Instructions, user-defined data types, and user-defined string types referenced by the program. 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.

As with other export types, I/O module data type definitions are not exported. I/O module data types are created within a project when the associated I/O module is created in the project. On import, program-scoped tags may not be modified. As a result, if a program-scoped tag aliases an I/O module type tag, the I/O module must first exist in the project in order to import the program. To export the program so that it can be imported into a project with another module type, first alias the program-scoped tag to a controller-scoped tag of a non-I/O module type, and then alias the controller-scoped tag to the I/O module. These program-scoped tags can then be created during the import of the program if necessary.

When importing a program, the program-scoped tags and routines are imported as part of the program. The Operation, Final Name, Description, and any other settings of the program-scoped tags and routines cannot be modified; instead, the Operations are based on the Operation selected for the program.

Programs cannot overwrite equipment phases, and vice-versa. Programs and equipment phases must have unique names.

Configure how the referenced components are imported during import configuration. By default, referenced components that collide with project components are not imported.

Considerations when importing a program.

Introduction



Chapter 4 Additional considerations for programs and equipment phases


Topic Consideration

Accepted or Test Edits exist A program with Accepted Edits or Test Edits may not be overwritten.

Deletes of program-scoped tags and routines during program overwrite

When importing a program to replace an existing program, any tags or routines in the existing program that are not in the new program are deleted during import. However, if online and Import Logic Edits as Pending or Accept Program Edits is selected in the Online Options dialog box, then these tags and routines cannot be deleted because they are referenced by existing logic until edits are finalized. In this situation, although they were identified during import configuration with an Operation of Delete, these tags and routines are not deleted as part of the import. Delete them in the Logix Designer editor after finalizing edits.

Safety program scheduled location A Safety program cannot be scheduled in the Controller Fault Handler or Power-Up Handler folders.

Configuration of Equipment Phase state routines In the configuration for an equipment phase state routine, when the Complete State Immediately if not Implemented option is selected in version 17.00.00 and later of the application, an implemented, but empty (no logic), phase state routine behaves the same as an unimplemented phase state routine. The state immediately completes and execution of the phase continues. The phase then enters the next state in the state machine. 00In version 16.00.00 or later of the application, if an equipment phase enters a state for which a state routine exists, but contains no logic, execution of the phase stops regardless of whether the Complete State Immediately if not Implemented option is selected. The routine does complete, but there is no logic to run. If importing a new state routine and, in the Online Options dialog box, select: • Import Logic Edits as Pending, an empty routine is created in the controller and the pending edits only exist in the offline

project.

• Accepts Program Edits, an empty routine is created in the controller and the logic is placed in a test edits container in the routine. If not actively testing edits, the routine is empty when running.

• Finalize All Edits in Program, the routine is created with the new logic and is not empty.

In the first two cases, if the Complete State Immediately if not Implemented option is selected, the empty routine completes immediately and allows phase execution to continue.

First scan If a new program or equipment phase is created in a controller in Remote Run mode, logic in that program or equipment phase receives a value of 1 for the S:FS system flag (First Scan flag) until the main routine has run once. Any other logic imports (that is overwriting an existing program or equipment phase, or any routine or rung imports) does not result in a value of 1 for S:FS system flag.

Pre-scan Logic imported while online with the controller in Remote Run mode is not pre-scanned before it begins to run.

Program scheduled location while online An imported program that is configured to overwrite an existing program cannot be scheduled into a location that differs from the existing program while online with the controller in Remote Run mode; the existing scheduled location is used.

Renamed tags When overwriting an existing program and the imported program is modified such that a program-scoped tag has been renamed, during import, the existing tag is deleted and a tag with the new name is created. All logic references are updated to reference the new tag. Therefore, the online tag values are not preserved and the tag values from the imported tag are downloaded to the controller. To preserve the data values of the renamed tag and minimize the logic changes, rename the program tag in the online project to the new name before importing the modified program.

Importing multiple programs Controller Fault Handler and Power-Up Handler Disabled: When importing multiple target programs, the Controller Fault Handler and Power-Up Handler are unavailable in the Schedule In list.

For considerations for referenced user-defined types, Add-On Instructions, program tags, and referenced tags that may be imported with a program see, Importing and exporting user-defined types, Add-On Instructions, and tags.

See also

Import and export user-defined types on page 53


Import and export tags on page 67


Chapter 5

Additional considerations for user-defined types

This chapter explains import and export of user-defined data types and user-defined string types.

A user-defined type (either user-defined data type or user-defined string type) can be exported to an .l5x file.

The export file may also include any Add-On Instructions, user-defined data types, and user-defined string types referenced by the exported user-defined type. The definitions for the referenced Add-On Instructions and data types are exported to the .l5x file if they exist in the project and if Include all referenced Add-On Instructions and User-Defined Types is selected during export.

Also export user-defined data type references when a program, routine, set of rungs, or Add-On Instruction is exported.

When importing a user-defined type, configure how the referenced components are imported during import configuration. By default, referenced components that collide with project components are not imported.

User-defined types cannot overwrite Add-On Instructions. User-defined types and Add-On Instructions must have unique names.

Considerations when importing a user-defined type.

Topic Consideration

Tag data Imported tags that reference a user-defined data type in the import file may be affected if the user-defined data type is not imported as well. In this case, the imported tag’s data may be converted if the existing data structure is different and tag data may be lost. If an existing user-defined data type is overwritten, project tag data may be converted if the data structure is different and tag data may be lost.

Data type modification while online

A user-defined data type that is referenced in the project may not be overwritten. If the existing user-defined data type is not referenced, it may be overwritten while online.

Final Name change If the Final Name of a user-defined type reference is modified during import configuration, all logic, tags, Add-On Instructions, and other user-defined types in the import that reference the user-defined type are updated to reference the new name. As a result, the edit date of any Add-On Instructions that references the user-defined type is updated.

Introduction



Chapter 5 Additional considerations for user-defined types


See Import and export Add-On Instructions for considerations for referenced Add-On Instructions that may be imported with the user-defined type.

See also

Import and Export Add-On Instructions on page 55


Chapter 6

Import and export Add-On Instructions

This chapter explains import and export of Add-On Instructions.

When exporting an Add-On Instruction, the exported Add-On Instruction includes all of its parameters, local tags, and routines. These are imported with the Add-On Instruction automatically.

Optionally, include any nested Add-On Instructions or user-defined data types that are referenced by the exported Add-On Instruction. Referenced Add-On Instructions and data types are exported to the .l5x file, if the Include all referenced Add-On Instructions and User-Defined Types check box is selected during the export.

Add-On Instruction definition references may also be exported when a program, routine, set of rungs, or user-defined data type is exported.

Tip: If an Add-On Instruction uses Message (MSG) instruction and InOut parameters of type MESSAGE, consider exporting a rung containing the Add-On Instruction to include the MESSAGE tags. This captures the message configuration data, such as type and path.

In deciding how to manage Add-On Instruction definitions in export files, consider the goals in storing the definitions.

If Then

Want to store many Add-On Instructions that share a set of common Add-On Instructions or user-defined data types in a common location

See Export to separate files.

Want to distribute an Add-On Instruction as one file See Export to one file.

Want to manage each Add-On Instruction as a standalone instruction

Want to preserve the instruction signature on Add-On Instruction

Tip: Add-On Instructions with instruction signatures are encrypted upon export to prevent modifications to the export file.

See also

Export to separate files on page 56

Export to one file on page 57

Introduction

Create export files

Chapter 6 Import and export Add-On Instructions


To store many Add-On Instructions that share a set of common Add-On Instructions or user-defined data types in a common location, export each Add-On Instruction and user-defined data types to separate files without including references.

To export to separate files:

1. Select the Add-On Instruction in the Controller Organizer, and choose Export Add-On Instruction.

2. Select the common location to store the .l5x file.

3. Type a name for the file.

4. Clear the Include all referenced Add-On Instructions and User-Defined Types check box.

5. Select Export.

6. Repeat the previous steps to individually export the other shared Add-On Instructions and user-defined data types.

By using export in this way, manage the shared Add-On Instruction and user-defined data types independently of the Add-On Instructions that reference them. Using this approach, can update the shared component without regenerating all the export files for the instructions that reference it. That is, it is stored in only one file instead of in every file whose instruction references it. This approach makes it easier to maintain the instructions to update only one export file.

Export to separate files

Import and export Add-On Instructions Chapter 6


To use Add-On Instructions that were exported in a separate file without references, first import any user-defined data types of Add-On Instructions that the exported instruction references before the import of the referencing instruction can be successful. (This assumes that the referenced user-defined data types of Add-On Instructions do not exist in the project.) To do this, work from the bottom up. Import the lowest-level user-defined data types and any user-defined data types that reference them. Then, import the lowest-level Add-On Instructions, followed by any Add-On Instructions that reference those low-level Add-On Instructions. Once all items referenced by the Add-On Instruction are in place, the import of the Add-On Instruction succeeds.

See also

Export to one file on page 57

To manage each Add-On Instruction as a standalone, export the instruction and any referenced Add-On Instructions or user-defined data types into one export file. By including any referenced Add-On Instructions or user-defined data types, also makes it easier to preserve the instruction signature of an Add-On Instruction.

To export to one file:

1. Select the Add-On Instruction in the Controller Organizer and choose Export Add-On Instruction.

2. Choose the location to store the .l5x file.

Export to one file



3. Type a name for the file.

4. Select the Include all referenced Add-On Instructions and User-Defined Types check box.

5. Click Export.

This procedure exports the selected Add-On Instruction and all referenced instructions into the same export file. This file can be used to distribute an Add-On Instruction. When the exported Add-On Instruction is imported into the project, the referenced instructions are also imported in one step.

See also

Export to separate files on page 56

Import an Add-On Instruction that was exported from another Logix Designer project. When importing an Add-On Instruction, the parameters, local tags, and routines are imported as part of the Add-On Instruction. Once the project has the Add-On Instruction, use it in programs.

This section covers import guidelines for Add-On Instructions or Add-On Instruction references.

Editing an .l5k or .l5x File The EditedDate attribute of an Add-On Instruction must be updated if the Add-On Instruction is modified by editing an .l5k or .l5x file. If the Logix Designer application detects edits to the Add-On Instruction, but the Edited Date attribute is the same, the Add-On Instruction is not imported.

When importing Add-On Instructions directly or as references, consider these guidelines.

Topic Consideration

Tag Data Imported tags that reference an Add-On Instruction in the import file may be affected if the Add-On Instruction is not imported as well. In this case, the imported tag’s data may be converted if the existing Add-On Instruction’s data structure is different. Tag data may be lost. If an existing Add-On Instruction is overwritten, project tag data may be converted if the Add-On Instruction’s data structure is different. Tag data may be lost. See Import Configuration for more information.

Logic Imported logic that references the Add-On Instruction in the import file may be affected if the Add-On Instruction is not imported. If an existing Add-On Instruction is used for the imported logic reference and the parameter list of the Add-On Instruction in the project is different, the project may not verify or it may verify but not work as expected. If an existing Add-On Instruction is overwritten, logic in the project that references the Add-On Instruction may be affected. The project may not verify or may verify but not work as expected. See Import Configuration for more information.

Add-On Instructions While Online

An Add-On Instruction cannot be overwritten during import while online with the controller, though a new Add-On Instruction may be created while online.

Import an Add-On Instruction




Topic Consideration

Final Name Change If the Final Name of an Add-On Instruction is modified during import configuration, the edit date of the imported Add-On Instruction is updated. In addition, all logic, tags, user-defined data types, and other Add-On Instructions in the import file that reference the Add-On Instruction are updated to reference the new name. As a result, the edit date of any Add-On Instruction that references the Add-On Instruction is updated. Add-On Instructions that are sealed with an instruction signature cannot be renamed during import.

User-Defined data types Add-On Instructions cannot overwrite user-defined data types. Add-On Instructions and user-defined data types require unique names.

Instruction Signature When importing an Add-On Instruction with an instruction signature into a project where referenced Add-On Instructions or user-defined data types are not available, consider removing the signature. Overwrite an Add-On Instruction that has an instruction signature by importing another Add-On Instruction with the same name into an existing routine. Add-On Instructions that are sealed with an instruction signature cannot be renamed during import.

Safety Add-On Instructions Importing a safety Add-On Instruction into a standard project is not allowed. Importing a safety Add-On Instruction into a safety project that has been safety-locked or one that has a safety task signature is not allowed. Import a safety Add-On Instruction while online. Class, instruction signature, signature history, and safety instruction signature, if it exists, remain intact when an Add-On Instruction with an instruction signature is imported.

Important: Importing an Add-On Instruction created in version 18.00.00 or later of the application, into an earlier project that does not support Add-On Instruction signatures causes the Add-On Instruction to lose attribute data and the instruction may no longer verify.

See also

Import Configuration on page 59

When selecting a file to import, use the Import Configuration dialog box to choose how the Add-On Instruction and referenced components are imported.

If no issues exist, select OK to complete the import.

If the Add-On Instruction collides with an Add-On Instruction in the project:

• Rename it by typing a new, unique name in the Final Name field.

• Choose Overwrite from the Operation menu.

Import configuration



• Choose Use Existing from the Operation menu.

Tip: Rename an Add-On Instruction only if it has not been sealed with an instruction signature. To rename an Add-On Instruction that has been source-protected, use the source key.

Use the Collision Details button to view the Property Compare tab, which shows the differences between the two instructions, and the Project References tab, which shows where the existing Add-On Instruction is used and how the arguments are updated to locations where the existing Add-On Instruction is called.

To update an instruction to a later revision, import it from an .l5x file or copy it from an existing project. Update an Add-On Instruction only when offline.

To update an Add-On Instruction to a later revision using import:

1. Select the Add-On Instruction folder and choose Import Add-On Instruction.

2. Select the file with the Add-On Instruction and select Open.

3. From the Operation list on the Import Configuration dialog box, choose Overwrite.

Update an Add-On Instruction to a later revision using import



4. Select Collision Details to see any differences in the Add-On Instruction definition, and to see any changes that will be made to the logic where the Add-On Instruction is called.

Differences listed in the Property Compare tab are shown in bold in the Name column.

Tip: The Compare dialog box compares metadata for each instruction definition, such as description, revision, or edited date. For effective revision control, enter a detailed revision note in the Add-On Instructions Definition dialog box. To open the dialog box, right-click an Add-On Instruction and select Open Definition.

The Project References tab shows a list of locations where the Add-On Instruction is called, and for each location, shows how the arguments in the Add-On Instruction will be updated to adapt to the new parameters.



Important: Beginning with version 18.00.00, when changing the parameters of an Add-On Instruction (add, delete, or move), each location where the Add-On Instruction is called is modified so that the existing arguments continue to match their previous parameters. Importing and Overwriting an existing Add-On Instruction may cause changes to the existing logic that uses the Add-On Instruction.

Important: If the logic calling the Add-On Instruction is within a source-protected routine, and the key is not available, the arguments are not shown or updated. Instead, the Location will be identified as Source Not Editable.

For more information on updates to arguments, see Logix 5000 Controllers Add-On Instructions.

See also

Logix 5000 Controllers Add-On Instructions

http://literature.rockwellautomation.com/idc/groups/literature/documents/pm/1756-pm010_-en-p.pdf/n


Chapter 7

Import and export tag-based alarms and alarm definitions

This chapter explains export and import of tag-based alarms and alarm definitions.

Tag-based alarms and alarm definitions can be exported to an XML file for offline editing, and they are exported to the .l5x file as part of a program, routine, user-defined data type, or Add-On Instruction export.

To create export files (tag-based alarms):

1. On the main menu, select Tools > Export > Alarms or Tools > Export > Alarm Definitions to open the Export Alarms and Alarm Definitions dialog box.

2. Select a destination for the file and adjust the file name if necessary.

3. Click Save.

Tip: To open an XML file in an Excel spreadsheet, open it as an XML table. After editing, select XML data as the file type in the Save as dialog box.

Keep these considerations in mind when editing alarms and alarm definitions in an XML file or in a spreadsheet:

• One message is exported for each alarm or alarm definition.

Delete alarms and alarm definitions from the XML file, but those items are not removed from the Logix Designer project when importing the modified XML file.

After exporting alarms or alarm definitions to an XML file, import the file into a project.

Keep these consideration in mind when importing alarms and alarm definitions from an XML file:

• If alarms and alarm definitions are deleted from the XML file, those items are not removed from the Logix Designer project when importing the modified XML file.

Introduction

Create export files

Import alarms and alarm definitions

Chapter 7 Import and export tag-based alarms and alarm definitions


To import tag-based alarms and alarm definitions:

1. On the main menu, select Tools > Import > Alarms or Tools > Import > Alarm Definitions to open the Import Alarms and Alarm Definitions dialog box.

2. In the Import dialog box, select the file and select Open to open the Collision Handling dialog box.

3. On the Collision Handling dialog box, select the method the Logix Designer application should use in case of differences or duplication between the imported alarms and alarms that exist in the project.

The table describes the handling options.

Option Description

Create New Alarms & Overwrite Existing Alarms

New alarms in the XML file are created in the project, and existing alarms in the project are overwritten with the same alarms in the XML file. This is the default option.

Create New Alarms & Preserve Existing Alarms

New alarms in the XML file are created in the project, but existing alarms in the project are not overwritten with the same alarms in the XML file.

Skip New Alarms & Overwrite Existing Alarms

New alarms in the XML file are not created in the project, and existing alarms in the project are overwritten with the same alarms in the XML file.

Keep these considerations in mind when importing an XML file containing alarms or alarm definitions:

• The import file must be an XML file. If the import file is not an XML file, try opening the file in Excel and, in the Open XML dialog box, select As an XML table. Then save the file as an XML file by selecting XML data as the file type in the Save as dialog box.

• The XML file must be in the same alarm format as the exported file. If it was corrupted somehow or incorrectly edited after it was exported, try exporting the alarm list again and import the resulting XML file.

• The XML file must contain only the attributes that are recognized as attributes of an alarm or an alarm definition, such as AckRequired, Latched, and Severity. If an XML file is edited incorrectly after export, an attribute might be altered to make it unrecognizable, or an unknown attribute might be added. Remove or correct any unrecognized attributes in the XML file.

• The XML file must contain only the elements that are recognized as elements of an alarm or an alarm definition. If an XML file is edited incorrectly after export, an attribute might be altered to make it unrecognizable, or an unknown element might be added. In the alarm import XML file, elements appear in angle brackets, such as <Message>, <AlarmClass>, and <HMIGroup>. Remove or correct any unrecognized elements in the XML file.


Import and export tag-based alarms and alarm definitions Chapter 7


Keep the following consideration in mind when copying and pasting an Add-On Instruction in a project:

• When an Add-On Instruction (AOI) tag is copied and pasted in a project, alarm definitions associated with the tag are not included.

After you copy and paste an AOI tag, open the Alarm Definition list and copy and paste the alarm definition for the tag. Follow these steps:

1. In the Controller Organizer, right-click Alarms and select Edit Alarm Definitions.

2. Right-click the alarm definition for the AOI tag and select Copy.

3. Right-click again and select Paste. The alarm definition is pasted into the list with _000 added to the alarm name.

4. Double-click the copy of the alarm definition to open the Alarm Definition Properties dialog box.

5. In the Input box, change the input tag to the AOI tag that you copied and pasted.


Chapter 8

Additional considerations for tags

This chapter explains import and export of referenced tags.

Tip: Starting with version 24.00.00 of Logix Designer application, use program parameters to share data between programs in much the same way controller-scoped tags are used. Program parameters are imported and exported in the same way as tags in most instances. For more information on program parameters, refer to 1756-PM021, Logix 5000 Controllers Program Parameters Programming Manual.

Tags are not exported to an .l5x file themselves, but they are exported to the .l5x file as part of a program, equipment phase, or Add-On Instruction export (program-scoped tags with a program export, equipment phase-scoped tags with an equipment phase export, and parameters and local tags with an Add-On Instruction export).

Tags may also be exported to an .l5x file as references from another component being exported (controller-scoped tag references with a program or equipment phase export or program-scoped and controller-scoped tag references with a rung or routine export). The definitions for the referenced tags are exported to the .l5x file by default if they exist in the project.

When exporting logic, especially if it is intended for general use, be aware that logic that references a bit member of a tag or member of a user-defined data type tag cannot be replaced during import to reference another bit or user-defined data type member. To connect the logic reference to another bit or member of a tag, consider editing the logic before export so the reference is to a full tag name (and alias if need be) so that the reference can be connected to the desired tag on import.

When importing a program, the program-scoped tags are imported with the program automatically (the same as they are for equipment phase). When importing an Add-On Instruction, the parameters and local tags are imported with the Add-On Instruction automatically.

During program or equipment phase imports, referenced controller-scoped tags may also be imported. For routine and rung imports, referenced tags may be imported as well. Configure how referenced tags are imported during import configuration. By default, referenced tags that collide with project components are not imported.

Introduction



Chapter 8 Additional considerations for tags


Keep the following considerations in mind when importing tags.

Topic Consideration

Tag data Imported tags that reference an Add-On Instruction or user-defined data type in the import file may be affected if the Add-On Instruction or user-defined data type is not imported as well. In this case, the imported tag’s data may be converted if the existing data structure is different and tag data may be lost. If an existing Add-On Instruction or user-defined data type is overwritten, project tag data may be converted if the data structure is different and tag data may be lost. If the data is not convertible, it is overwritten with the default values for the type. When array dimensions are changed, existing array members retain their values and descriptions and new members have the default values and description (usually 0 and no description).

Consumed tags Consumed tags cannot be imported from an .l5x file. They are converted to base tags and a warning appears in the Errors or Warning pane during initial parsing of the .l5x file.

Tag values while online When importing into a controller while online, if existing tags are being overwritten by imported tags, the tag values are not written to the controller. Tag values are written only to the offline project. The tag values in the controller maintain their current values but other tag attributes are written to the controller. Values for tags that are created during import are written to the controller. However, existing tag values are never overwritten in the online controller. Prevent tag values from being overwritten in the offline project by selecting Preserve existing tag values in offline project on the Import Configuration dialog box.

Tag values while offline Prevent tag values from being overwritten in the offline project by selecting Preserve existing tag values in offline project on the Import Configuration dialog box.

Tag attributes while online Tag attributes (for example, External Access, Constant, and Style) are written to the online project and the offline project. If existing tags are to be overwritten with new attributes that are incompatible with existing user logic, the import is not allowed.

Tag scope An import tag maintains the scope of the tag as it was when exported if the tag initially collides with another scoped tag in the project. In that case, an attention (red) flag appears on the tag indicating the scope collision. However, If changing the Final Name of a tag so that it subsequently collides with a tag of another scope in the project, the imported tag is changed to the scope of the existing tag. Resolve the attention flag that appears on initial collision due to a scope issue by changing the Final Name to avoid the collision with that tag or, if the import component is routine or rungs, change the scope of the import tag by selecting the tag row and selecting Toggle Tag Scope.


Chapter 9

Additional considerations for data exchange

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

Import and export in the Logix Designer application support these file formats:

• Web Ontology Language (OWL) uses an .rdf file to exchange data.

Recommended for the most rich data exchange with all Rockwell Automation specific features identified for data exchange. The RDF (Resource Description Framework) serves for data representation, OWL (Web Ontology Language) builds on RDF and defines the dictionary. Both are open standards for data exchange. They are used as a basis for a Rockwell Automation specific data format.

Tip: When exchanging data between Rockwell Automation software applications, always use the RDF file type.

• AutomationML (AML) uses an .aml file to exchange data.

AML is an open industry standard format dedicated to automation usage. The AML specification includes a set of data structures implemented in the application. This implementation enables interoperability with other software applications that use the AutomationML Automation Project Configuration format, such as EPLAN Electric.

Some Rockwell Automation devices are only partially supported by the AML format because they include capabilities that are not within the scope of the current AML standard. When a product is partially supported, it can be imported or exported, but may require some additional configuration to reconfigure the unsupported features. Check the Errors window in the Logix Designer application for details.

See also

Data exchange device support tables on page 72

Data exchange file type capabilities and limitations on page 70

Data exchange with other software applications

Chapter 9 Additional considerations for data exchange


AutomationML (AML) is an XML-based data format for storing automation-related data. Import and export AML and RDF within the Logix Designer application.

Current Logix Designer application supported devices are:

• Chassis

• Controllers

• Controllers with Ethernet

• I/O modules

• ControlNet communication modules

• Ethernet communication module

• Motion modules

• Redundancy modules

• Specialty modules

• Ethernet switches

• Servo drives

• Ethernet network (one only)

• Ethernet connection

• ControlNet network (trunk) (multiple)

• PowerFlex devices

Some devices are not supported by AML or RDF data exchange with the Logix Designer application and, if they are present, are omitted from the export file. These devices are:

• CompactLogix L2x, L3x, L4x, -L37ERMO, and -L37ERMOS controllers

• HMI devices

• Classic profiles (profiles that do not have a Module Definition dialog box) (excluding controllers)

• Devices not included:

Data exchange file type capabilities and limitations

Additional considerations for data exchange Chapter 9


• 1734 Address Reserve module (1734-ARM)

• 1756 Redundancy modules (1756-RM2)

• 1794 Extended-Local I/O adapter (1794-FLA)

• Unmanaged switches (1783-US)

• Generic switch

• Generic computer

• Flex Terminal Base Unit device (1794-TB, 1797-TB)

• Power Supply devices

• End Cap and cable devices

• Stratix expansion module switches (1783-MX, 1783-MS, 1783-RMS)

• PowerFlex Peripheral modules

• Other trunks

Some devices cannot be exported to AML. These devices are:

• CompactExtensionConnection (indicating a multi-part chassis)

• FlexLogixTrunk

Important: Attempting to export a hardware diagram that includes either of these devices results in an error and the export does not succeed.

Device properties

AML and RDF support storing a subset of device and tag properties. This table identifies the properties that are stored for data exchange with the Logix Designer application:

Device Property

All

GUID

Name

Chassis, Modules in Chassis, Independent physical devices

Catalog number

Position

Firmware version

IP address

Description

Unsupported properties are omitted in an AML export. Some properties can be calculated and restored upon import and others must be explicitly configured after import. Unsupported properties are:

• LeftRackSize and RightRackSize properties of CompactLogix chassis. If possible this data is calculated during post-processing and restored during import.



• Redundancy

• Safety Level

• Servo drive grouping

• Stratix expansion module owner assignment. If possible this data is calculated during post-processing and restored during import.

See also

Data exchange with other software applications on page 69

Data exchange device support tables on page 72

AutomationML web site (https://www.automationml.org)

Use the tables in this section to determine which form of data exchange is supported by a Logix Designer application device. Devices included in a project that are not supported cannot be imported from or exported to an RDF or AML file.

See also

Data exchange with other software applications on page 69

Data exchange file type capabilities and limitations on page 70

Data exchange is not supported for 1715 communication, and digital and analog input and output devices.

Data exchange is not supported for 1719 communication, and digital and analog, input and output devices.

Data exchange is not supported for 1732 safety, communication, and digital and analog input and output devices.

Data exchange support for 1734 POINT I/O safety, communication, specialty, and digital and analog input and output devices:

1734 POINT I/O safety, communication, specialty, digital, and analog

Catalog Number or Product Family RDF support AML support

1734-232ASC Yes Yes

1734-485ASC Yes Yes

1734-4IOL No No

1734-8CFG Yes Yes

1734-8CFGDLX Yes Yes

1734-ACNR Yes Yes

1734-AENT Yes Yes

Data exchange device support tables

1715

1719

1732

1734 POINT I/O

https://www.automationml.org/




1734-AENTR Yes Yes

1734-ARM Yes Yes

1734-DIN Yes Yes

1734-EP24DC Yes Yes

1734-EPAC Yes Yes

1734-FPD Yes Yes

1734-IA11-2 No No

1734-IA11-8 No No

1734-IA16-2 No No

1734-IA2 Yes Yes

1734-IA4 Yes Yes

1734-IB2 Yes Yes

1734-IB4 Yes Yes

1734-IB4D Yes Yes

1734-IB8 Yes Yes

1734-IB8S Yes Yes

1734-IE2C Yes Yes

1734-IE2V Yes Yes

1734-IE4C Yes Yes

1734-IE4S Yes Yes

1734-IE8C Yes Yes

1734-IJ Yes Yes

1734-IK Yes Yes

1734-IM2 Yes Yes

1734-IM4 Yes Yes

1734-IR2 Yes Yes

1734-IR2E Yes Yes

1734-IT2I Yes Yes

1734-IV2 Yes Yes

1734-IV4 Yes Yes

1734-IV8 Yes Yes

1734-MODULE No No

1734-OA2 Yes Yes

1734-OA4 Yes Yes

1734-OB2 Yes Yes

1734-OB2E Yes Yes

1734-OB2EP Yes Yes

1734-OB4 Yes Yes

1734-OB4E Yes Yes

1734-OB8 Yes Yes




1734-OB8E Yes Yes

1734-OB8S Yes Yes

1734-OE2C Yes Yes

1734-OE2V Yes Yes

1734-OE4C Yes Yes

1734-OV2E Yes Yes

1734-OV4E Yes Yes

1734-OV8E Yes Yes

1734-OW2 Yes Yes

1734-OW4 Yes Yes

1734-OX2 Yes Yes

1734sc-IE2CH No No

1734sc-IE4CH No No

1734sc-IF4U No No

1734sc-OE2CIH No No

1734-SSI Yes Yes

1734-VA11-2 No No

1734-VA11-3 No No

1734-VA11-8 No No

1734-VA16-2 No No

1734-VA16-4 Yes Yes

1734-VHSC24 Yes Yes

1734 POINT I/O power supplies Yes Yes

Data exchange is not supported for 1738 communication, specialty, and digital and analog input and output devices.

Data exchange is not supported for 1746 specialty, and digital and analog input and output devices.

Data exchange is not supported for 1747 communication devices.

Data exchange is not supported for 1753 GuardPLC devices.

Data exchange support for 1756 ControlLogix devices:

1756 ControlLogix


1756 ControlLogix all chassis Yes3 Yes3

1738

1746

1747

1753

1756 ControlLogix




1756 ControlLogix all motion modules Partial Partial

1756 ControlLogix all specialty modules Partial Partial

1756 ControlLogix all redundancy modules Partial2 Partial2

1756 generic module Partial Partial

1756-A10 Yes3 Yes3

1756-A13 Yes3 Yes3

1756-A17 Yes3 Yes3

1756-A4 Yes3 Yes3

1756-A4LXT Yes3 Yes3

1756-A5XT Yes3 Yes3

1756-A7 Yes3 Yes3

1756-A7LXT Yes3 Yes3

1756-CFM No No

1756-CN2 Yes Yes

1756-CN2R Yes Yes

1756-CNB ControlLogix communication module Partial Partial

1756-CNBR Yes Yes

1756-DHRIO ControlLogix communication module No No

1756-DMA30 No No

1756-DMA31 No No

1756-DMA50 No No

1756-DMB30 No No

1756-DMD30 No No

1756-DMF30 No No

1756-DNB No No

1756-EN2F Yes Yes

1756-EN2T Yes Yes

1756-EN2TP Yes Yes

1756-EN2TR Yes Yes

1756-EN2TSC ControlLogix communication module Partial Partial

1756-EN3TR Yes Yes

1756-ENBT Yes Yes

1756-ENET No No

1756-EWEB ControlLogix communication module No No

1756-HIST1G Yes Yes

1756-HIST2G Yes Yes

1756-HSC No No

1756-HYD02 No No

1756-IA16 ControlLogix digital I/O module Partial Partial

1756-IA16I Yes Yes




1756-IA32 Yes Yes

1756-IA8D Yes Yes

1756-IB16 Yes Yes

1756-IB16D Yes Yes

1756-IB16I Yes Yes

1756-IB16IF ControlLogix module Partial Partial

1756-IB16ISOE Yes Yes

1756-IB32 Yes Yes

1756-IC16 Yes Yes

1756-IF16 Yes Yes

1756-IF16H Yes Yes

1756-IF16IH No No

1756-IF4FXOF2F Yes Yes

1756-IF6CIS No No

1756-IF6I No No

1756-IF8 Yes Yes

1756-IF8H Yes Yes

1756-IF8I ControlLogix module Partial Partial

1756-IF8IH ControlLogix module Partial Partial

1756-IG16 Yes Yes

1756-IH16I Yes Yes

1756-IH16ISOE Yes Yes

1756-IM16I Yes Yes

1756-IN16 Yes Yes

1756-IR12 No No

1756-IR6I No No

1756-IRT8I ControlLogix module Partial Partial

1756-IT16 No No

1756-IT16I No No

1756-IT6I2 No No

1756-IV16 Yes Yes

1756-IV32 Yes Yes

1756-L1 Yes Yes

1756-L53 Yes Yes

1756-L55 Yes Yes

1756-L60M03SE Yes Yes

1756-L60M03SE SERCOS No No

1756-L61 Yes Yes

1756-L61S Yes Yes

1756-L62 Yes Yes




1756-L62S Yes Yes

1756-L63 Yes Yes

1756-L63S Yes Yes

1756-L64 Yes Yes

1756-L65 Yes Yes

1756-L71 Yes Yes

1756-L71S Yes Yes

1756-L72 Yes Yes

1756-L2S Yes Yes

1756-L3 Yes Yes

1756-L73S Yes Yes

1756-L4 Yes Yes

1756-L5 Yes Yes

1756-L7SP Yes Yes

1756-L81E ControlLogix controller Partial Partial

1756-L81ES ControlLogix controller Partial1 Partial1








1756-L8SP ControlLogix controller Partial Partial

1756-LCE ControlLogix controller Partial Partial

1756-LSC8XIB8I ControlLogix specialty module Partial Partial

1756-LSP ControlLogix safety controller Yes Yes

1756-M02AE No No

1756-M02AS No No

1756-M03SE No No

1756-M08SE No No

1756-M08SEG No No

1756-M016SE No No

1756-MODULE No No

1756-OA16 Yes Yes

1756-OA16I Yes Yes

1756-OA8 Yes Yes

1756-OA8D Yes Yes

1756-OA8E Yes Yes

1756-OB16D Yes Yes




1756-OB16E Yes Yes

1756-OB16I Yes Yes

1756-OB16IEF ControlLogix digital I/O module Partial Partial

1756-OB16IEFS ControlLogix digital I/O module Partial Partial

1756-OB16IS Yes Yes

1756-OB32 Yes Yes

1756-OB8 Yes Yes

1756-OB8EI Yes Yes

1756-OB8I No No

1756-OC8 Yes Yes

1756-OF4 Yes Yes

1756-OF6CI No No

1756-OF6VI No No

1756-OF8 Yes Yes

1756-OF8H Yes Yes

1756-OF8I ControlLogix analog I/O module Partial Partial

1756-OF8IH ControlLogix analog I/O module Partial Partial

1756-OG16 Yes Yes

1756-OH8I Yes Yes

1756-ON8 Yes Yes

1756-OV16E Yes Yes

1756-OV32E Yes Yes

1756-OW16I Yes Yes

1756-OX8I Yes Yes

1756-PA72 Yes Yes

1756-PA75 Yes Yes

1756-PA75R Yes Yes

1756-PAR Yes Yes

1756-PAR2 Yes Yes

1756-PAXT Yes Yes

1756-PB72 Yes Yes

1756-PB75 Yes Yes

1756-PB75R Yes Yes

1756-PBR Yes Yes

1756-PBR2 Yes Yes

1756-PBXT Yes Yes

1756-PLS No No

1756-PPMPC No No

1756-RIO ControlLogix communication module Partial Partial

1756-RM* No No




1756sc-CTR8 No No

1756sc-CT32 No No

1756sc-IF8H No No

1756sc-IF8U No No

1756sc-OF8H No No

1756-SYNCH ControlLogix communication module No No 1 Safety level properties not supported. 2 Other networks trunk not supported 3 Chassis power supply configuration not included. * All devices of type

Data exchange is not supported for 1757 devices.

Data exchange support for 1768 CompactLogix devices:

1768 CompactLogix


1768 CompactLogix controllers, banks, power supplies and modules Yes Partial1

1768-L43 CompactLogix modules No No

1768-L43 DIN rail No No

1768-L43S No No

1768-L43S DIN rail No No

1768-L45 CompactLogix modules No No

1768-L45 DIN rail No No

1768-L45S No No

1768-L45S DIN rail No No

1768-CNB CompactLogix modules No No

1768-CNBR CompactLogix modules No No

1768-DIN CompactLogix modules Yes Yes

1768-ENBT CompactLogix modules No No

1768-EWEB CompactLogix modules No No

1768-M04SE CompactLogix modules No No

1768-MODULE CompactLogix generic module No No

1768-PA3 Yes Yes

1768-PB3 Yes Yes 1 Configuration relationships calculated during post-processing. Confirm that the configuration is correct before committing the project. 2 RightRackSize property not supported.

1757

1768 CompactLogix




1769 CompactLogix


1769 CompactLogix controllers, banks, and modules Partial1 Partial1

1769 CompactLogix all digital I/O modules Partial1 Partial1

1769 CompactLogix all analog I/O modules Partial1 Partial1

1769 CompactLogix all specialty modules Partial1 Partial1

1769 CompactLogix generic module Partial1 Partial1

1769-L16ER-BB1B CompactLogix controller Partial1 Partial1


1769-L18ERM-BB1B CompactLogix controller Partial1 Partial1


1769-L20 No No

1769-L23* CompactLogix controllers Partial1 Partial1


1769-L27ERM-QBFC1B CompactLogix controllers Partial1 Partial1


1769-L31 CompactLogix controllers No No

1769-L32C CompactLogix controllers No No

1769-L32E CompactLogix controllers No No


1769-L35CR CompactLogix controller No No

1769-L35E CompactLogix controller No No



1769-L38* Yes Yes

1769-L40 No No

1769-MODULE No No

1769sc-IF4IH No No

1769sc-IF8U No No

1769sc-IR6I No No

1769sc-IT6I No No

1769sc-OF4IH No No

1769-SDN CompactLogix communication module No No

1769-AENTR CompactLogix communication module Partial1 Partial1 * All devices of type 1 Configuration relationship between controller and its owned I/O or other types of modules not supported.

1769




Data exchange support for 1783 Stratix devices:

1783 Stratix


1783 Stratix 2000 switches Yes Yes

1783 Stratix 5400 switches Partial1 Partial1


1783-BMS06* Yes Yes

1783-BMS010* Yes Yes

1783-BMS12T4E2CGL Stratix 5700 switch Partial1 Partial1

1783-BMS12T4E2CGNK Stratix 5700 switch Partial1 Partial1

1783-BMS12T4E2CGP Stratix 5700 switch Partial1 Partial1

1783-BMS20* Yes Yes

1783-BMS4S2SGA Stratix 5700 switch Partial1 Partial1

1783-BMS4S2SGL Stratix 5700 switch Partial1 Partial1




1783-EMS04T Partial2 Partial2

1783-EMS08T Partial2 Partial2

1783 Ethernet Taps Partial1 Partial1

1783-HMS16T4CGN Yes Yes

1783-HMS16TG4CGN Yes Yes

1783-HMS16TG4CGR Yes Yes

1783-HMS4* Yes Yes

1783-HMS8* Yes Yes

1783-IMS28* No No

1783-LMS5 No No

1783-LMS8 No No

1783-MS06T Yes Yes

1783-MS06T plus 4-Port Expansion Module No No

1783-MS06T plus 4-Port in Expansion Modules 1 and 8-Port in Expansion Modules 2 No No

1783-MS06T plus 8-Port in Expansion Module 1 and 4-Port Expansion Modules 2 No No

1783-MS06T plus two 4-Port Expansion Modules No No

1783-MS10T Yes Yes

1783-MS10T plus 4-Port Expansion Module No No

1783-MS10T plus 4-Port Expansion Module 1 and 8-Port in Expansion Module 2 No No

1783-MS10T plus 8-Port in expansion module 1 and 4-Port in Expansion Module 2 No No

1783-MS10T plus two 4-Port Expansion Modules No No

1771

1783 Stratix




1783-MX04* Partial3 Partial3

1783-MX08* Partial3 Partial3

1783-NATR No No

1783-RMS06T Yes Yes

1783-RMS06T plus 4-Port Expansion Module No No

1783-RMS06T plus 4-Port in Expansion Modules 1 and 8-Port in Expansion Modules 2 No No

1783-RMS06T plus 8-Port in Expansion Module 1 and 4-Port Expansion Modules 2 No No

1783-RMS06T plus two 4-Port Expansion Modules No No

1783-RMS10T Yes Yes

1783-RMS10T plus 4-Port Expansion Module No No

1783-RMS10T plus 4-Port Expansion Module 1 and 8-Port in Expansion Module 2 No No

1783-RMS10T plus 8-Port in expansion module 1 and 4-Port in Expansion Module 2 No No

1783-RMS10T plus two 4-Port Expansion Modules No No

1783-US03T01F Partial2 Partial2

1783-US06T01F Partial2 Partial2

1783-US5T Partial2 Partial2

1783-US8T Partial2 Partial2

1783-WAPxK9 No No

1783-ZMS16TA No No

1783-ZMS24TA No No

1783-ZMS4T4E2TGN No No

1783-ZMS4T4E2TGP No No

1783-ZMS8T8E2TGN No No

1783-ZMS8T8E2TGP No No

1783-ZMS8TA No No 1 Configuration relationships are not supported. Relationship will be calculated by post-processing during import. 2 Connections only 3 Stratix expansion module * All devices of type





Data exchange is not supported for 1791DS devices.

1784

1785

1788

1789

1791DS



Data exchange is not supported for 1791ES devices.

Data exchange support for 1794 FLEX I/O devices:

1794 FLEX I/O


1794 FLEX I/O DIN, power supplies and modules Partial1 Partial1

1794-ASB No No

1794-IF4ICF FLEX I/O module Partial1 Partial1

1794-IF8IHNF FLEX I/O module Partial1 Partial1

1794-FLA No No

1794-IB8S No No

1794-IE8H Yesl2 Yesl2

1794-IJ2I No No

1794-L33 No No

1794-L34 No No

1794-OE8H/A Yesl3 Yesl3

1794-PS1 Yes4 Yes4

1794-PS13 Yes4 Yes4

1794-PS3 Yes4 Yes4

1794TB* Yes5 Yes5 1 Configuration relationship between controller and owned IO modules not supported. 2 As 1794-IE8H/B 3 As 1794-OE8H/B 4 Power Supply ignored 5 Yes Flex Terminal Base unit ignored * All devices of type

Data exchange support for 1797 devices:

1797


1797-ACNR15 Yes Yes

1797-IBN16 No No

1797-IE8* No No

1797-IJ2 No No

1797-IRT8 No No

1797-OB4D No No

1797-OE8 No No

1794 FLEX I/O

1797

1791ES




1797-PS* Yes1 Yes1

1797-TB* Yes2 Yes2 * All devices of type 1 Power Supply ignored 2 Terminal Base Unit ignored


Data exchange is not supported for 193/592 devices.

Data exchange support for 20-750 devices:

20-750


20-750-ENETR* Yes Yes

20-750-S* Ye Yes

20-750-S1* Yes Yes * PowerFlex peripheral


5069 CompactLogix


5069 CompactLogix controllers, banks and modules Partial1 Partial1

5069-AENTR Partial2 Partial2

5069-AEN2TR communication module Partial2 Partial2

5069-ARM Yes Yes

5069-ECR Yes3 Yes3

5069-FPD Yes4 Yes4

5069 CompactLogix digital I/O modules Partial2 Partial2

5069 CompactLogix analog I/O modules Partial2 Partial2

5069 CompactLogix specialty modules Partial2 Partial2

5069-L306* controllers Yes Yes

5069-L3100* controllers Yes Yes

5069-310* controllers Yes Yes

5069-L320ER* controllers Partial2 Partial2

1799

193/592

20-750

5069 CompactLogix




5069-L330ER* controllers Yes Yes




5069-L460ERMW controllers Yes Yes

5069-SERIAL No No 1 DIN description not supported. 2 Configuration relationships not supported. Relationship calculated by post-processing during import. 3 End cap ignored. 4 Power Supply ignored. * All devices of type


Data exchange is not supported for ArmorPoint devices.

Data exchange is not supported for ArmorStart devices.

Data exchange is not supported for these communication devices.

Communication


100-1167-001 No No

1440-ACNR No No

2PCA-7844-B101 No No

56AMXN No No

ACT350 EtherNet/IP No No

ACT350-2P EtherNet/IP No No

Bus Module No No

Checker 4G1 No No

Checker 4G7 No No

CompactBus No No

CONTROLNET-MODULE No No

DACS EtherNet/IP Adapter No No

DataMan 200 Series No No



DriveLogix5730 Ethernet Port No No

E1 Plus No No

5094

ArmorPoint

ArmorStart

Communication




EA3600 EtherNet/IP No No

EtherNet/IP No No

ETHERNET-BRIDGE No No

ETHERNET-MODULE No No

EX250-S* No No

EX260-SEN* No No

EX500-GEN1 No No

FlexBus No No

HMS-EN2MB-R No No

HMS-EN2PB-R No No

HMS-EN2SE-R No No

IB-E01 No No

IB-E03B No No

IB-E04F No No

ILX34-AENWG No No

ILX69-PBM No No

ILX69-PBS No No

IND131 EtherNet/IP No No



IND780 ControlNet No No


In-Sight 1700 Series No No



In-Sight Micro Series No No

Link_OS_Printer No No

LMDrive No No

MVI56* No No

MVI69* No No

OCP-ETG No No

OCX-* No No

PCIe-ETAP No No

PCI-ETAP No No

RA56-ESA No No

RIO-ADAPTER No No

SLP85xD No No

SST-ESR2-C* No No

SST-PB3*-CPX No No

SST-PFB/PB3-CLX-RLL No No




SST-SR4-CLX-RLL No No

STB3574 EtherNet/IP No No

Stratix 8000* No No

Stratix 8300* No No

SWG70 No No

Thyro* No No

WHA-GW No No

WMF No No * All devices of type

Data exchange is not supported for DPI to EtherNet/IP devices.

Data exchange is not supported for these drives.

Drives


1305-ACDrive-CN1 No No

1305-ACDrive-EN1 No No

1336E-IMPACTDrive-CN1 No No

1336E-IMPACTDrive-EN1 No No

1336F-PLUSIIDrive-CN1 No No

1336F-PLUSIIDrive-EN1 No No

1336R-REGENBrake-CN1 No No

1336R-REGENBrake-EN1 No No

1336S-PLUSDriveLG-CN1 No No

1336S-PLUSDriveLG-EN1 No No

1336S-PLUSDriveSM-CN1 No No

1336S-PLUSDriveSM-EN1 No No

1336T No No

1336T-FORCEDriveCNA-CN1 No No

1336T-FORCEDriveCNA-EN1 No No

1336T-FORCEDrivePLC-CN1 No No

1336T-FORCEDrivePLC-EN1 No No

1336T-FORCEDriveStd-CN1 No No

1336T-FORCEDriveStd-EN1 No No

1394C-SJT05-D No No

1394C-SJT10-D No No

1394C-SJT22-D No No

DPI to EtherNet/IP

Drive




1395 No No

1397DigitalDCDrive-CN1 No No

1397DigitalDCDrive-EN1 No No

150-SMC Flex-C No No

150-SMC Flex-E No No

150-SMC Flex-ER No No

150-SMC Flex-Q No No

150-SMCDialogPlus--CN1 No No

150-SMCDialogPlus--EN1 No No

2098-DSD* No No

2099-BM* No No

2364F-RGU* No No

8720MC* No No

Drives AOP Infrastructure No No

FLEX-MODULE No No

Generic SERCOS Drive No No

GV3000 No No

Multi-Drive-25-COMM-E2P No No

Rockwell Automation UDC AOP Infrastructure No No

SMC-50* No No

WebPak 3000 No No * All devices of type

Data exchange support for embedded devices:

Embedded


Embedded Compact, analog, output No No

Embedded Point I/O Yes Yes

Embedded Compact, specialty No No

Embedded Compact, digital, input, output No No

Embedded HSC Yes Yes

Embedded IF4XOF2 Yes Yes

Embedded IQ16F Yes Yes

Embedded 0B16 Yes Yes

Embedded



Data exchange is not supported for energy management products.

Data exchange is not supported for HMI devices.

Data exchange support for Kinetix devices:

Kinetix


2093-AC05* No No

2093-AM* No No

2094-AC* No No

2094-AM* No No

2094-BC* No No

2094-BM* No No

2094-EN02D-M01* No No

2094-SE02F-M00-S0/2094-AC* No No

2094-SE02F-M00-S0/2094-AM* No No

2094-SE02F-M00-S0/2094-BC* No No

2094-SE02F-M00-S0/2094-BM* No No

2094-SE02F-M00-S1/2094-AC* No No

2094-SE02F-M00-S1/2094-AM* No No

2094-SE02F-M00-S1/2094-BC* No No

2094-SE02F-M00-S1/2094-BM* No No

2094--SEPM-B24-S No No

Kinetix 300 servo drives Partial1 Partial1

Kinetix 350 servo drives Partial1 Partial1

Kinetix 5500 servo drives Partial1 2 Partial1 2

Kinetix 5700 servo drives Partial1 2 Partial1 2

MDx-SB1003P-Qxx* No No * All devices of type 1 Configuration relationships not supported. Relationship calculated by post-processing during import. 2 Motion group property not supported by AML.

Data exchange is not supported for these motion devices.

Motion


2094-SEPM-B24-S No No

842-CM-M No No

Energy Management Products

HMI

Kinetix

Motion



Data exchange is not supported for MPI to EtherNet/IP devices.

Data exchange support for PowerFlex devices:

PowerFlex


22C... No No

22N... No No

25* Yes Yes

PowerFlex 523 drives Partial1 2 Partial1 2


PowerFlex 527-STO CIP Safety drive Partial1 Partial1

PowerFlex 700 No No



DriveLogix 57* No No

PowerFlex 4 Class Multi* No No

PowerFlex 400* No No

PowerFlex 40* No No

PowerFlex 4* No No

PowerFlex 523-C No No

PowerFlex 523-E* Yes Yes

PowerFlex 525-C No No

PowerFlex 525-E* Yes Yes

PowerFlex 527-STO CIP Safety Yes Yes

PowerFlex 70 ED* No No

PowerFlex 700 AC* No No

PowerFlex 700 Vector* No No



PowerFlex 70* No No

PowerFlex 753-CNETC No No

PowerFlex 753-ENETR Yes Yes

PowerFlex 753-NET-C No No

PowerFlex 753-NET-E Yes Yes

PowerFlex 753-NET-Q No No

PowerFlex 755 HiPwr-PMM-EENET No No

PowerFlex 755 HiPwr-CNETC No No

PowerFlex 755 HiPwr-EENET Yes Yes

MPI to EtherNet/IP

PowerFlex




PowerFlex 755 HiPwr-ENETR Yes Yes

PowerFlex 755 HiPwr-NET-C No No

PowerFlex 755 HiPwr-NET-E Yes Yes

PowerFlex 755 HiPwr-NET-Q No No

PowerFlex 755 PMM-EENET No No

PowerFlex 755-CNETC No No

PowerFlex 755-EENET* Yes Yes

PowerFlex 755-ENETR Yes Yes

PowerFlex 755 HiPwr-EENET-CM* Yes Yes

PowerFlex 755-NET-C No No

PowerFlex 755-NET-E Yes Yes

PowerFlex 755-NET-Q No No

PowerFlex 755T* No No

PowerFlex 755 DC FC* No No

PowerFlex 755 DC* No No




* All devices of type 1 Configuration properties not fully supported. 2 PowerFlex 523-E2P drive imports as a type PowerFlex 523-E drive but includes the PowerFlex 523-E2P description in the configuration properties. 3 PowerFlex 525-E drive imports as a type PowerFlex 523-E drive and includes the PowerFlex 523-E description in the configuration properties. PowerFlex 525-E2P drive imports as a type PowerFlex 525-EENET drive but includes the PowerFlex 525-E2P description in the configuration properties. PowerFlex 525-EENET-Multi drive imports as a type PowerFlex 525-EENET drive but includes the PowerFlex 525-EENET-Multi description in the configuration properties. 4 PowerFlex 753-NET-E drive imports as a type PowerFlex 753-ENETR drive but includes the PowerFlex 753-NET-E description in the configuration properties. 5 PowerFlex 755 HiPwr-ENETR2 drive imports as a type PowerFlex 755 HiPwr-EENET drive but includes the PowerFlex 755 HiPwr-ENETR description in the configuration properties. PowerFlex 755 HiPwr-NET-E drive imports as a type PowerFlex 755 HiPwr-EENET drive but includes the PowerFlex 755 HiPwr-NET-E description in the configuration properties. PowerFlex 755-EENET drive imports as a type PowerFlex 755 HiPwr-EENET drive but includes the PowerFlex 755-EENET description in the configuration properties. PowerFlex 755-ENETR drive imports as a type PowerFlex 755 HiPwr-EENET drive but includes the PowerFlex 755-ENETR description in the configuration properties. PowerFlex 755-EENET-CM drive imports as a type PowerFlex 755 HiPwr-EENET drive but includes the PowerFlex 755-EENET-CM description in the configuration properties. PowerFlex 755-EENET-CM -S drive imports as a type PowerFlex 755 HiPwr-EENET drive but includes the PowerFlex 755-EENET-CM-S description in the configuration properties. PowerFlex 755-EENET-CM-S1 drive imports as a type PowerFlex 755 HiPwr-EENET drive but includes the PowerFlex 755-EENET-CM-S1 description in the configuration properties. PowerFlex 755-HiPwr-EENET-CM drive imports as a type PowerFlex 755 HiPwr-EENET drive but includes the PowerFlex 755-HiPwr-EENET-CM description in the configuration properties. PowerFlex 755-HiPwr-EENET-CM-S drive imports as a type PowerFlex 755 HiPwr-EENET drive but includes the PowerFlex 755-HiPwr-EENET-CM-S description in the configuration properties. PowerFlex 755-HiPwr-EENET-CM-S1 drive imports as a type PowerFlex 755 HiPwr-EENET drive but includes the PowerFlex 755-HiPwr-EENET-CM-S1 description in the configuration properties. PowerFlex 755-NET-E drive imports as a type PowerFlex 755 HiPwr-EENET drive but includes the PowerFlex 755-NET-E description in the configuration properties.

Data exchange is not supported for these specialty devices.

Specialty


124x No No

1440-DYN02-01RJ No No

1444-DYN04-01RA No No

1642 No No

2198-ABQE No No

3202 No No

3204 No No

Specialty




3401 - 3401L No No

3601 No No

3602 - 3602D No No

48MS-SN1PF1-M2 No No

48MS-SN1PF2-M2 No No

56RF-IN-IP* No No

5XRF_IN_IP No No

7662 No No

842E-M No No

842E-S No No

A3XX No No

ACU No No

AX8 No No

FANUC CNC* No No

FANUC Robot No No

FANUC Robt R30iB Plus No No

HI1734-WS No No

HI1756-xDF No No

HI1756-xFC No No

HI1756-xWS No No

HI1769-xFC No No

HI1769-xWS No No

Liquiline_CA80xx No No

Liquiline_CM44x No No

Liquistation_CSFxx No No

Memograph_M_RSG45 No No

Onyx-S/SC2 No No

Promag* No No

Promass* No No

* All devices of type

Data exchange support for other devices:

Other


Logix Designer projects Partial1 Partial1

Generic switches Yes Yes

Ethernet switches - Generic Yes Yes

Other




Generic computers Partial2 Partial2

PanelView Plus graphic terminals Yes Yes

MobileView mobile terminals Yes Yes

FactoryTalk View applications or servers No No

Graphics No No

Files No No

Text Boxes No No

Shapes No No

Links No No

Combination Generator Control Module No No

Combination Generator Control Module, 2-Port No No

Powermonitor1000 No No

1557... No No

20-COMM-E Yes3 Yes3

22-COMM-E Yes3 Yes3

2706-PENETX No No

440C-CR30-22BBB No No

CEP7-ETN No No

CIP-MODULE No No

DEVICENET-SAFETYMODULE No No

DPI-DRIVE-PERIPHERAL-MODULE No No

DSI-DRIVE-PERIPHERAL_MODULE No No

Emulate 5570 No No

ETHERNET-SAFETYMODULE No No

ETHERNET-SAFETY-STANDARD-MODULE No No

FLEX_MODULE No No

Generic Computer Yes4 Yes4

Generic Switch Yes5 Yes5

L2yEmbedded Analog_IO Yes6 Yes6

L2yEmbedded Counters Yes7 Yes7

L2yEmbedded Discrete_IO Yes8 Yes8

Logix Block No No

MDCOMM-ENET No No

RHINOBP-DRIVE-PERIPHERAL-MODULE Yes3 Yes3

RIO-MODULE No No

RSLinx No No

SCANport-DRIVE-PERIPHERAL-MODULE No No

VersaView CE* No No

Other Networks Yes No




1 Project must not include any unsupported devices. Data imported subject to the limitations on included devices. 2 The computer name property of the generic computer object not supported for AML export or import. Assigns a default name to the generic computer object during import that can be updated after the import is complete. 3 PowerFlex peripheral. 4 Computer ignored. 5 Connections only. 6 As 1.10.164 7 As 1.109.71 8 AS 1.7.64


A Add-On Instruction 55

export 19 import 24

alarms 63 attention flags 41

B backward compatibility 45

C canceled import 42 collision

import 59, 60 communication timeouts 20, 58 compare instructions 60 component

configuration 59 export 13, 19 import 13, 24

configuration attention flags 41 components 59 example 40 import 38, 59 options 25, 58 references 38 undefined references 41

Connections grid 36 considerations

export 17 import 58 motion 22 online import 20 safety 23 security 19, 23

D data exchange 13

data exchange file type capabilities and limitations 70 support tables 72, 74, 79, 80, 81, 82, 83, 84, 85, 87, 88, 89, 90, 92, 93 with other software applications 69

description export 19

E equipment phase 51

export 19 export considerations 67 import 24 import considerations 58

export Add-On Instruction 55 component description 19 components 13, 19 considerations 17 equipment phase 51 L5X 13, 19 local tag 67 parameter 67 program 51 routine 49 rungs 47 tag 67 user-defined data type 53 user-defined string type 53

export considerations equipment phase 67 local tag 67 parameter 67 program 67 routine 67 rungs 67 security 19 tag 67 user-defined data type 67 user-defined string type 67

exportIXexport 55

F failed import 42 find

text 44 use wildcards 44

Index

Index


I import

Add-On Instruction 55 canceled 42 components 13, 24 configuration 38, 59 considerations 58 equipment phase 51 failed 42 L5X 13, 24 local tag 67 multiple components 29 parameter 67 program 51 routine 49 rungs 47 tag 67 user-defined data type 53 user-defined string type 53

Import Configuration dialog box 60 import considerations

equipment phase 58 local tag 58 multiple components 23 parameter 58 program 58 routine 58 rungs 58 security 23 tag 58 user-defined data type 58 user-defined string type 58

importIXimport 58

L L5X

export 13, 19 import 13, 24

local tag export considerations 67 import considerations 58

M motion 22

multiple components 23, 29

O online import 20

P parameter

export considerations 67 import considerations 58

program 51 export 19 export considerations 67 import 24 import considerations 58

Project References tab 60 Property Compare tab 60

R references

configuration 38 undefined 41

replace text 44

routine 49 export 19 export considerations 67 import 24 import considerations 58

rungs 47 export 19 export considerations 67 import 24 import considerations 58

S safety 23 safety Add-On Instruction

import 58 safety task signature 58 search and replace 44 security 19, 23

Index


T tag 67

export considerations 67 import considerations 58

tooltip attention flags 41

trend export 19 import 24

U undefined references 41 update Add-On Instruction revision 60 user-defined data type 53

export 19 export considerations 67 import 24 import considerations 58

user-defined string type 53 export 19 export considerations 67 import 24 import considerations 58

UTF-8 file format 13

W wildcards 44

X XML files 13

Rockwell Automation Publication 1756-PM019I-EN-E - December 2018

Supersedes Publication 1756-PM019H-EN-E - February 2018 Copyright © 2018 Rockwell Automation Technologies, Inc. All Rights Reserved. Printed in the U.S.A.

Rockwell Automation support

Rockwell Automation provides technical information on the web to assist you in using its products. At http://www.rockwellautomation.com/support you can find technical and application notes, sample code, and links to software service packs. You can also visit our Support Center at https://rockwellautomation.custhelp.com for software updates, support chats and forums, technical information, FAQs, and to sign up for product notification updates.

In addition, we offer multiple support programs for installation, configuration, and troubleshooting. For more information, contact your local distributor or Rockwell Automation representative, or visit http://www.rockwellautomation.com/services/online-phone.

Installation assistance

If you experience a problem within the first 24 hours of installation, review the information that is contained in this manual. You can contact Customer Support for initial help in getting your product up and running.

United States or Canada 1.440.646.3434

Outside United States or Canada Use the Worldwide Locator available at http://www.rockwellautomation.com/locations, or contact your local Rockwell Automation representative.

New product satisfaction return

Rockwell Automation tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility. However, if your product is not functioning and needs to be returned, follow these procedures.

United States Contact your distributor. You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor to complete the return process.

Outside United States Please contact your local Rockwell Automation representative for the return procedure.

Documentation feedback

Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this document, complete the feedback form, publication RA-DU002.

http://www.rockwellautomation.com/support

https://rockwellautomation.custhelp.com/

http://www.rockwellautomation.com/services/online-phone

http://www.rockwellautomation.com/locations

http://literature.rockwellautomation.com/idc/groups/literature/documents/du/ra-du002_-en-e.pdf

Logix 5000 Controllers Import/Export Project Components ... · Logix 5000 Controllers Import/Export...

Documents

Transcript of Logix 5000 Controllers Import/Export Project Components ... · Logix 5000 Controllers Import/Export...