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™

Rockwell Automation Publication 1756-PM019K-EN-P - March 2022

Supersedes Publication 1756-PM019J-EN-P - September 2020

Programming Manual Original Instructions

Logix 5000 Controllers Import/Export Project Components

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

Rockwell Automation recognizes that some of the terms that are currently used in our industry and in this publication are not in
alignment with the movement toward inclusive language in technology. We are proactively collaborating with industry peers to
find alternatives to such terms and making changes to our products and content. Please excuse the use of such terms in our
content while we implement these changes.

2 Rockwell Automation Publication 1756-PM019K-EN-P - September 2020

 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.
Change Topic
New Studio 5000 Logix Designer® application branding Studio 5000® environment on page 9

New or enhanced features

None in this release.

Rockwell Automation Publication 1756-PM019K-EN-P - September 2020 3

 Table of Contents

Summary of Changes Studio 5000 environment ........................................................................... 9

Preface Additional resources .................................................................................... 9
Legal Notices .............................................................................................. 10

Chapter 1
Additional considerations for Introduction ................................................................................................ 11
rungs Export considerations ................................................................................ 11
Import considerations ................................................................................ 11

Chapter 2
Additional considerations for Introduction ................................................................................................13
routines Export considerations ................................................................................13
Import considerations ................................................................................13

Chapter 3
Additional considerations for Introduction ............................................................................................... 15
programs and equipment Export considerations ............................................................................... 15
Import considerations ............................................................................... 15
phases

Chapter 4
Additional considerations for Introduction ............................................................................................... 17
user-defined types Export considerations ............................................................................... 17
Import considerations ............................................................................... 17

Chapter 5
Import and export Add-On Introduction ............................................................................................... 19
Instructions Create export files ...................................................................................... 19
Export to separate files ........................................................................ 19
Export to one file .................................................................................. 21
Import an Add-On Instruction................................................................. 22
Import considerations ........................................................................ 22
Import configuration...........................................................................23
Update an Add-On Instruction to a later revision using import ........... 24

Chapter 6
Import and export tag-based Introduction ............................................................................................... 27
alarms and alarm definitions Create export files ...................................................................................... 27
Import alarms and alarm definitions....................................................... 27
Import considerations .............................................................................. 28

Rockwell Automation Publication 1756-PM019K-EN-P - September 2020 5

Table of Contents

Chapter 7
Additional considerations for Introduction ................................................................................................31
tags Export considerations ................................................................................31
Import considerations ................................................................................31

Chapter 8
Additional considerations for Data exchange with other software applications .................................... 33
data exchange Data exchange file type capabilities and limitations .............................. 34
Data exchange device support tables ....................................................... 36
1715 .........................................................................................................36
1719.........................................................................................................36
1732 ........................................................................................................36
1734 POINT I/O .....................................................................................36
1738 ....................................................................................................... 38
1746 ....................................................................................................... 38
1747 ....................................................................................................... 38
1753........................................................................................................ 38
1756 ControlLogix ................................................................................ 38
1757......................................................................................................... 41
1768 CompactLogix ............................................................................. 42
1769 CompactLogix.............................................................................. 42
1771 .........................................................................................................43
1783 Stratix ............................................................................................43
1784 ........................................................................................................45
1785 ........................................................................................................45
1788 ........................................................................................................45
1789 ........................................................................................................45
1791DS....................................................................................................45
1791ES ....................................................................................................45
1794 FLEX I/O .......................................................................................45
1797 ....................................................................................................... 46
1799 ....................................................................................................... 46
193/592 .................................................................................................. 46
20-750 ................................................................................................... 46
5069 CompactLogix ............................................................................. 46
5094........................................................................................................47
ArmorPoint ...........................................................................................47
ArmorStart............................................................................................47
Communication ...................................................................................47
DPI to EtherNet/IP.............................................................................. 49
Drive ..................................................................................................... 49
Embedded ............................................................................................ 50

6 Rockwell Automation Publication 1756-PM019K-EN-P - September 2020

 Table of Contents

Energy Management Products .......................................................... 50

HMI ...................................................................................................... 50
Kinetix .................................................................................................. 50
Motion ................................................................................................... 51
MPI to EtherNet/IP .............................................................................. 51
PowerFlex.............................................................................................. 51
Specialty ................................................................................................ 53
Other .....................................................................................................54
Index

Rockwell Automation Publication 1756-PM019K-EN-P - September 2020 7

 Preface
This manual contains import and export specifications for the Logix Designer
application components.
Rockwell Automation recognizes that some of the terms that are currently
used in our industry and in this publication are not in alignment with the
movement toward inclusive language in technology. We are proactively
collaborating with industry peers to find alternatives to such terms and
making changes to our products and content. Please excuse the use of such
terms in our content while we implement these changes.

Studio 5000 environment 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.

Additional resources These documents contain additional information concerning importing and
exporting projects and project components.
Resource Description
Logix 5000™ Controllers Import/Export Reference Provides detailed reference information and
Manual, publication 1756-RM084 examples for importing and exporting projects and
components.
Logix 5000 Controllers Security Programming Manual, Describes how to configure security for controller
publication 1756-PM016 projects using the Logix Designer application.

Rockwell Automation Publication 1756-PM019K-EN-P - September 2020 9

Preface
Resource Description
Product Certifications webpage, available at Provides declarations of conformity, certificates, and
http://ab.rockwellautomation.com 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.

Legal Notices Rockwell Automation publishes legal notices, such as privacy policies, license
agreements, trademark disclosures, and other terms and conditions on the
Legal Notices page of the Rockwell Automation website.

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.

Open Source 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. The default
installed location of these licenses is C:\Program Files (x86)\Common
Files\Rockwell\Help\<Product Name>\Release
Notes\OPENSOURCE\index.htm.

10 Rockwell Automation Publication 1756-PM019K-EN-P - September 2020

 Chapter 1

Additional considerations for rungs

Introduction This chapter explains import and export of rungs.

Export considerations 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.

Import considerations 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.
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.

Rockwell Automation Publication 1756-PM019K-EN-P - September 2020 11

Chapter 1 Additional considerations for rungs
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 17
Import and export Add-On Instructions on page 19
Import and export tags on page 31

12 Rockwell Automation Publication 1756-PM019K-EN-P - September 2020

 Chapter 2

Additional considerations for routines

Introduction This chapter explains the import and export of routines.

Export considerations 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.

Import considerations 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 SFC execution settings are configured on a controller project, not per SFC
configuration 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 When state routines are created while online with the controller and logic edits
routines are accepted but not tested, the routine will behave as if it was not
implemented.

Rockwell Automation Publication 1756-PM019K-EN-P - September 2020 13

Chapter 2 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 17
Import and export Add-On Instructions on page 19
Import and export Tags on page 31

14 Rockwell Automation Publication 1756-PM019K-EN-P - September 2020

 Chapter 3

Additional considerations for programs and

equipment phases

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

Export considerations 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.

Import considerations 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.
Topic Consideration
Accepted or Test Edits exist A program with Accepted Edits or Test Edits may not be overwritten.

Rockwell Automation Publication 1756-PM019K-EN-P - September 2020 15

Chapter 3 Additional considerations for programs and equipment phases
Topic Consideration
Deletes of program-scoped tags and routines When importing a program to replace an existing program, any tags or routines in the existing program that are not in
during program overwrite 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 In the configuration for an equipment phase state routine, when the Complete State Immediately if not
routines 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 17
Import and export Add-On Instructions on page 19
Import and export tags on page 31

16 Rockwell Automation Publication 1756-PM019K-EN-P - September 2020

 Chapter 4

Additional considerations for user-defined

types

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

Export considerations 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.

Import considerations 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 A user-defined data type that is referenced in the project may not be
online 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.

Rockwell Automation Publication 1756-PM019K-EN-P - September 2020 17

Chapter 4 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 19

18 Rockwell Automation Publication 1756-PM019K-EN-P - September 2020

 Chapter 5

Import and export Add-On Instructions

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

Create export files 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 See Export to separate
Instructions or user-defined data types in a common location 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 19
Export to one file on page 21

Export to separate files 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.

Rockwell Automation Publication 1756-PM019K-EN-P - September 2020 19

Chapter 5 Import and export Add-On Instructions

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.
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

20 Rockwell Automation Publication 1756-PM019K-EN-P - September 2020

 Chapter 5 Import and export Add-On Instructions
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 21

Export to one file 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.

3. Type a name for the file.

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

Rockwell Automation Publication 1756-PM019K-EN-P - September 2020 21

Chapter 5 Import and export Add-On Instructions
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 19

Import an Import an Add-On Instruction that was exported from another Logix
Designer project. When importing an Add-On Instruction, the parameters,
Add-On Instruction 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.

Import considerations This section covers import guidelines for Add-On Instructions or Add-On
Instruction references.
ATTENTION: 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 An Add-On Instruction cannot be overwritten during import while online with the
Online controller, though a new Add-On Instruction may be created while online.
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.

22 Rockwell Automation Publication 1756-PM019K-EN-P - September 2020

 Chapter 5 Import and export Add-On Instructions
Topic Consideration
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 Importing a safety Add-On Instruction into a standard project is not allowed.
Instructions 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 23

Import configuration 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.

Rockwell Automation Publication 1756-PM019K-EN-P - September 2020 23

Chapter 5 Import and export Add-On Instructions
• 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.

Update an Add-On 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.
Instruction to a later
revision using import
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.

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.

24 Rockwell Automation Publication 1756-PM019K-EN-P - September 2020

 Chapter 5 Import and export Add-On Instructions
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.

Rockwell Automation Publication 1756-PM019K-EN-P - September 2020 25

Chapter 5 Import and export Add-On Instructions
IMPORTANT Beginning with version 18.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

26 Rockwell Automation Publication 1756-PM019K-EN-P - September 2020

 Chapter 6

Import and export tag-based alarms and

alarm definitions

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

Create export files 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.
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.

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. Select 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.

Import alarms and After exporting alarms or alarm definitions to an XML file, import the file
into a project.
alarm definitions
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.

Rockwell Automation Publication 1756-PM019K-EN-P - September 2020 27

Chapter 6 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.
This table describes the handling options.
Option Description
Create New Alarms & New alarms in the XML file are created in the project, and existing
Overwrite Existing Alarms alarms in the project are overwritten with the same alarms in the XML
file.
This is the default option.
Create New Alarms & New alarms in the XML file are created in the project, but existing
Preserve Existing Alarms alarms in the project are not overwritten with the same alarms in the
XML file.
Skip New Alarms & New alarms in the XML file are not created in the project, and existing
Overwrite Existing Alarms alarms in the project are overwritten with the same alarms in the XML
file.

Import considerations 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

28 Rockwell Automation Publication 1756-PM019K-EN-P - September 2020

 Chapter 6 Import and export tag-based alarms and
alarm definitions
<Message>, <AlarmClass>, and <HMIGroup>. Remove or correct any
unrecognized elements in the XML file.
Keep this 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. Use 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.

Rockwell Automation Publication 1756-PM019K-EN-P - September 2020 29

 Chapter 7

Additional considerations for tags

Introduction 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.

Export considerations 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.

Import considerations 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.

Rockwell Automation Publication 1756-PM019K-EN-P - September 2020 31

Chapter 7 Additional considerations for tags
Keep these 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 Tag attributes (for example, External Access, Constant, and Style) are written to the
online 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.

32 Rockwell Automation Publication 1756-PM019K-EN-P - September 2020

 Chapter 8

Additional considerations for data exchange

Data exchange with other Import or export hardware diagrams to or from a standard file type to share
data between different software applications.
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 35
Data exchange file type capabilities and limitations on page 33

Rockwell Automation Publication 1756-PM019K-EN-P - September 2020 33

Chapter 8 Additional considerations for data exchange

Data exchange file type AutomationML (AML) is an XML-based data format for storing
automation-related data. Import and export AML and RDF within the Logix
capabilities and limitations 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:
• 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

34 Rockwell Automation Publication 1756-PM019K-EN-P - September 2020

 Chapter 8 Additional considerations for data exchange
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 33
Data exchange device support tables on page 35
AutomationML web site (https://www.automationml.org)

Rockwell Automation Publication 1756-PM019K-EN-P - September 2020 35

Chapter 8 Additional considerations for data exchange

Data exchange device 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
support tables 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 33

Data exchange file type capabilities and limitations on page 33

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

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

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

1734 POINT I/O 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 AML
support 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
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

36 Rockwell Automation Publication 1756-PM019K-EN-P - September 2020

 Chapter 8 Additional considerations for data exchange
Catalog Number or Product Family RDF AML
support support
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

Rockwell Automation Publication 1756-PM019K-EN-P - September 2020 37

Chapter 8 Additional considerations for data exchange

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

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

1747 Data exchange is not supported for 1747 communication devices.

1753 Data exchange is not supported for 1753 GuardPLC™ devices.

1756 ControlLogix Data exchange support for 1756 ControlLogix devices:

1756 ControlLogix
Catalog Number or Product Family RDF AML
support support
1756 ControlLogix all chassis Yes3 Yes3
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 Yes 3
Yes3
1756-A4 Yes3 Yes3
1756-A4LXT Yes3 Yes3
1756-A5XT Yes3 Yes3
1756-A7 Yes 3
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

38 Rockwell Automation Publication 1756-PM019K-EN-P - September 2020

 Chapter 8 Additional considerations for data exchange
Catalog Number or Product Family RDF AML
support support
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

Rockwell Automation Publication 1756-PM019K-EN-P - September 2020 39

Chapter 8 Additional considerations for data exchange
Catalog Number or Product Family RDF AML
support support
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-L72S 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 Partial 1
Partial1
1756-L82E ControlLogix controller Partial Partial
1756-L82ES ControlLogix controller Partial 1
Partial1
1756-L83E ControlLogix controller Partial Partial
1756-L83ES ControlLogix controller Partial1 Partial1
1756-L84E ControlLogix controller Partial Partial
1756-L84ES ControlLogix controller Partial 1
Partial1
1756-L85E ControlLogix controller Partial Partial
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

40 Rockwell Automation Publication 1756-PM019K-EN-P - March 2022

 Chapter 8 Additional considerations for data exchange
Catalog Number or Product Family RDF AML
support support
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

1757 Data exchange is not supported for 1757 devices.

Rockwell Automation Publication 1756-PM019K-EN-P - March 2022 41

Chapter 8 Additional considerations for data exchange

1768 CompactLogix Data exchange support for 1768 CompactLogix devices:

1768 CompactLogix
Catalog Number or Product Family RDF AML
support support
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.

1769 CompactLogix Data exchange support for 1769 CompactLogix devices:

1769 CompactLogix
Catalog Number or Product Family RDF AML
support support
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 Partial 1
Partial1
1769 CompactLogix generic module Partial1 Partial1
1769-L16ER-BB1B CompactLogix controller Partial 1
Partial1
1769-L18ER-BB1B CompactLogix controller Partial1 Partial1
1769-L18ERM-BB1B CompactLogix controller Partial 1
Partial1
1769-L19ER-BB1B CompactLogix controller Partial1 Partial1
1769-L20 No No
1769-L23* CompactLogix controllers Partial1 Partial1
1769-L24* CompactLogix controllers Partial 1
Partial1
1769-L27ERM-QBFC1B CompactLogix controllers Partial1 Partial1

42 Rockwell Automation Publication 1756-PM019K-EN-P - March 2022

 Chapter 8 Additional considerations for data exchange
Catalog Number or Product Family RDF AML
support support
1769-L30* CompactLogix controllers Partial1 Partial1
1769-L31 CompactLogix controllers No No
1769-L32C CompactLogix controllers No No
1769-L32E CompactLogix controllers No No
1769-L33* CompactLogix controllers Partial 1
Partial1
1769-L35CR CompactLogix controller No No
1769-L35E CompactLogix controller No No
1769-L36* CompactLogix controllers Partial1 Partial1
1769-L37* CompactLogix controllers Partial 1
Partial1
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.

1771 Data exchange is not supported for 1771 devices.

1783 Stratix Data exchange support for 1783 Stratix devices:

1783 Stratix
Catalog Number or Product Family RDF AML
support support
1783 Stratix® 2000 switches Yes Yes
1783 Stratix® 5400 switches Partial1 Partial1
1783 Stratix® 5700 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 Partial 1
Partial1
1783-BMS20* Yes Yes
1783-BMS4S2SGA Stratix 5700 switch Partial1 Partial1
1783-BMS4S2SGL Stratix 5700 switch Partial1 Partial1
1783 Stratix 6000 switches Partial1 Partial1
1783 Stratix 8000 switches Partial1 Partial1
1783 Stratix 8300 switches Partial 1
Partial1
1783-EMS04T Partial2 Partial2
1783-EMS08T Partial2 Partial2

Rockwell Automation Publication 1756-PM019K-EN-P - March 2022 43

Chapter 8 Additional considerations for data exchange
Catalog Number or Product Family RDF AML
support support
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 No No
Modules 2
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 No No
2
1783-MS10T plus two 4-Port Expansion Modules No No
1783-MX04* Partial 3
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 No No
Modules 2
1783-RMS06T plus 8-Port in Expansion Module 1 and 4-Port Expansion Modules No No
2
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 No No
2
1783-RMS10T plus two 4-Port Expansion Modules No No
1783-US03T01F Partial2 Partial2
1783-US06T01F Partial2 Partial2
1783-US5T Partial 2
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

44 Rockwell Automation Publication 1756-PM019K-EN-P - March 2022

 Chapter 8 Additional considerations for data exchange
Catalog Number or Product Family RDF AML
support support
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

1784 Data exchange is not supported for 1784 devices.

1785 Data exchange is not supported for 1785 devices.

1788 Data exchange is not supported for 1788 devices.

1789 Data exchange is not supported for 1789 devices.

1791DS Data exchange is not supported for 1791DS devices.

1791ES Data exchange is not supported for 1791ES devices.

1794 FLEX I/O Data exchange support for 1794 FLEX™ I/O devices:

1794 FLEX I/O

Catalog Number or Product Family RDF AML
support support
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 Yes 4
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

Rockwell Automation Publication 1756-PM019K-EN-P - March 2022 45

Chapter 8 Additional considerations for data exchange

1797 Data exchange support for 1797 devices:

1797
Catalog Number or Product Family RDF AML
support support
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
1797-PS* Yes 1
Yes1
1797-TB* Yes2 Yes2
*
All devices of type
1
Power Supply ignored
2
Terminal Base Unit ignored

1799 Data exchange is not supported for 1799 devices.

193/592 Data exchange is not supported for 193/592 devices.

20-750 Data exchange support for 20-750 devices:

20-750
Catalog Number or Product Family RDF AML
support support
20-750-ENETR* Yes Yes
20-750-S* Ye Yes
20-750-S1* Yes Yes
*
PowerFlex peripheral

5069 CompactLogix Data exchange support for 5069 CompactLogix devices:

5069 CompactLogix
Catalog Number or Product Family RDF AML
support support
5069 CompactLogix controllers, banks and modules Partial1 Partial1
5069-AENTR Partial2 Partial2
5069-AEN2TR communication module Partial 2
Partial2
5069-ARM Yes Yes
5069-ECR Yes3 Yes3

46 Rockwell Automation Publication 1756-PM019K-EN-P - March 2022

 Chapter 8 Additional considerations for data exchange
Catalog Number or Product Family RDF AML
support support
5069-FPD Yes4 Yes4
5069 CompactLogix digital I/O modules Partial2 Partial2
5069 CompactLogix analog I/O modules Partial 2
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 Partial 2
Partial2
5069-L330ER* controllers Yes Yes
5069-L340ER* controllers Yes Yes
5069-L350ER* controllers Yes Yes
5069-L380ER* 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

5094 Data exchange is not supported for 5094 devices.

ArmorPoint Data exchange is not supported for ArmorPoint devices.

ArmorStart Data exchange is not supported for ArmorStart® devices.

Communication Data exchange is not supported for these communication devices.

Communication
Catalog Number or Product Family RDF AML
support support
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
DataMan 500 Series No No
DataMan 8000 Series No No

Rockwell Automation Publication 1756-PM019K-EN-P - March 2022 47

Chapter 8 Additional considerations for data exchange
Catalog Number or Product Family RDF AML
support support
DriveLogix5730 Ethernet Port No No
E1 Plus No No
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
IND560 EtherNet/IP No No
IND570 EtherNet/IP No No
IND780 ControlNet No No
IND780 EtherNet/IP No No
In-Sight 1700 Series No No
In-Sight 3400 Series No No
In-Sight 5000 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

48 Rockwell Automation Publication 1756-PM019K-EN-P - March 2022

 Chapter 8 Additional considerations for data exchange
Catalog Number or Product Family RDF AML
support support
WHA-GW No No
WMF No No
*
All devices of type

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

Drive Data exchange is not supported for these drives.

Drives
Catalog Number or Product Family RDF AML
support support
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
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

Rockwell Automation Publication 1756-PM019K-EN-P - March 2022 49

Chapter 8 Additional considerations for data exchange
Catalog Number or Product Family RDF AML
support support
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

Embedded Data exchange support for embedded devices:

Embedded
Catalog Number or Product Family RDF AML
support support
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

Data exchange is not supported for energy management products.

Energy Management
Products
Data exchange is not supported for HMI devices.
HMI
Data exchange support for Kinetix® devices:
Kinetix
Kinetix
Catalog Number or Product Family RDF AML
support support
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

50 Rockwell Automation Publication 1756-PM019K-EN-P - March 2022

 Chapter 8 Additional considerations for data exchange
Catalog Number or Product Family RDF AML
support support
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 Partial 1
Partial1
Kinetix 350 servo drives Partial 1
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.

Motion Data exchange is not supported for these motion devices.

Motion
Catalog Number or Product Family RDF AML
support support
2094-SEPM-B24-S No No
842-CM-M No No

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

PowerFlex Data exchange support for PowerFlex devices:

PowerFlex
Catalog Number or Product Family RDF AML
support support
22C... No No
22N... No No
25* Yes Yes
PowerFlex 523 drives Partial 12
Partial1 2
PowerFlex 525 drives Partial 13
Partial1 3
PowerFlex 527-STO CIP Safety™ drive Partial1 Partial1
PowerFlex 700 No No
PowerFlex 753 drives Partial 14
Partial1 4
PowerFlex 755 drives Partial 15
Partial1 5
DriveLogix™ 57* No No
PowerFlex 4 Class Multi* No No
PowerFlex 400* No No

Rockwell Automation Publication 1756-PM019K-EN-P - March 2022 51

Chapter 8 Additional considerations for data exchange
Catalog Number or Product Family RDF AML
support support
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 7000* No No
PowerFlex 700* 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
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

52 Rockwell Automation Publication 1756-PM019K-EN-P - March 2022

 Chapter 8 Additional considerations for data exchange
Catalog Number or Product Family RDF AML
support support
*
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.

Specialty Data exchange is not supported for these specialty devices.

Specialty
Catalog Number or Product Family RDF AML
support support
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
3401 - 3401L No No

Rockwell Automation Publication 1756-PM019K-EN-P - March 2022 53

Chapter 8 Additional considerations for data exchange
Catalog Number or Product Family RDF AML
support support
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

Other Data exchange support for other devices:

Other
Catalog Number or Product Family RDF AML
support support
Logix Designer projects Partial1 Partial1
Generic switches Yes Yes
Ethernet switches - Generic Yes Yes
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

54 Rockwell Automation Publication 1756-PM019K-EN-P - March 2022

 Chapter 8 Additional considerations for data exchange
Catalog Number or Product Family RDF AML
support support
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 Yes 4
Yes4
Generic Switch Yes5 Yes5
L2yEmbedded Analog_IO Yes6 Yes6
L2yEmbedded Counters Yes 7
Yes7
L2yEmbedded Discrete_IO Yes8 Yes8
Logix Block No No
MDCOMM-ENET No No
RHINOBP-DRIVE-PERIPHERAL-MODULE Yes 3
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

Rockwell Automation Publication 1756-PM019K-EN-P - March 2022 55

 Index
local tag 31
parameter 31

Index program 31
routine 31
rungs 31
tag 31
user-defined data type 31
A user-defined string type 31
exportIXexport 19
Add-On Instruction 19
alarms 27 I
C import
Add-On Instruction 19
collision configuration 23
import 23, 24 considerations 22
communication timeouts 22 equipment phase 15
compare instructions 24 local tag 31
component parameter 31
configuration 23 program 15
configuration routine 13
components 23 rungs 11
import 23 tag 31
options 22 user-defined data type 17
considerations user-defined string type 17
import 22 Import Configuration dialog box 24
import considerations
D equipment phase 22
local tag 22
data exchange parameter 22
support tables 36, 38, 41, 42, 43, 45, 46, program 22
47, 49, 50, 51, 53, 54 routine 22
rungs 22
E tag 22
equipment phase 15 user-defined data type 22
user-defined string type 22
export considerations 31
import considerations 22 importIXimport 22
export
L
Add-On Instruction 19
equipment phase 15 local tag
local tag 31 export considerations 31
parameter 31 import considerations 22
program 15
routine 13 P
rungs 11
parameter
tag 31
user-defined data type 17 export considerations 31
user-defined string type 17 import considerations 22
export considerations program 15
equipment phase 31 export considerations 31

Rockwell Automation Publication 1756-PM019K-EN-P - March 2022 57

Index
import considerations 22
Project References tab 24
Property Compare tab 24

R
routine 13
export considerations 31
import considerations 22
rungs 11
export considerations 31
import considerations 22

S
safety Add-On Instruction
import 22
safety task signature 22

T
tag 31
export considerations 31
import considerations 22

U
update Add-On Instruction revision 24
user-defined data type 17
export considerations 31
import considerations 22
user-defined string type 17
export considerations 31
import considerations 22

58 Rockwell Automation Publication 1756-PM019K-EN-P - March 2022

Rockwell Automation support
Use these resources to access support information.
Technical Support Center Find help with how-to videos, FAQs, chat, user forums, and product notification rok.auto/support
updates.
Knowledgebase Access Knowledgebase articles. rok.auto/knowledgebase
Local Technical Support Phone Numbers Locate the telephone number for your country. rok.auto/phonesupport

Literature Library Find installation instructions, manuals, brochures, and technical data publications. rok.auto/literature
Product Compatibility and Download Center Get help determining how products interact, check features and capabilities, and rok.auto/pcdc
(PCDC) find associated firmware.

Documentation feedback
Your comments help us serve your documentation needs better. If you have any suggestions on how to improve our content, complete the form at
rok.auto/docfeedback.

Waste Electrical and Electronic Equipment (WEEE)

At the end of life, this equipment should be collected separately from any unsorted municipal waste.

Rockwell Automation maintains current product environmental information on its website at rok.auto/pec.

Allen-Bradley, expanding human possibility, Logix, Rockwell Automation, and Rockwell Software are trademarks of Rockwell Automation, Inc.

EtherNet/IP is a trademark of ODVA, Inc.

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

Rockwell Otomayson Ticaret A.Ş. Kar Plaza İş Merkezi E Blok Kat:6 34752, İçerenkÖy, İstanbul, Tel: +90 (216) 5698400 EEE YÖnetmeliğine Uygundur

Rockwell Automation Publication 1756-PM019K-EN-P - March 2022

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