Bi-directional data exchange between IAB & Studio 5000
Logix Designer Help
Background Information:
The purpose of this feature is to streamline the transfer of products between an IAB design and Studio
5000, minimizing redundant efforts. However, due to technical constraints, certain items cannot
currently undergo the export/import process.
For exports, the primary objective is to generate the I/O Tree in Studio 5000 with as many devices as
feasible. It may be necessary to fine-tune the configuration of a module in Studio 5000 post-import.
Import functionality primarily aims to assist users in constructing their control system architecture,
facilitating the expansion of existing systems, and transitioning legacy products and networks to meet
evolving technological demands.
Export Assumptions:
- This export will be an evolving process where support for Devices will be added over time. Not
all Devices are supported at initial launch.
- The export is based upon testing from Studio 5000 Version 35 due to varying levels of
Device support in different versions of Studio 5000.
- The export leverages Controller and Device assignments in IAB’s Advanced Communication
Details interface to determine which Devices are assigned to which Controller.
- Each Controller will have a separate L5X file created for it. These can be individually
imported into Studio 5000
- If a Device is not supported in IAB’s Advanced Communication Details interface, it will
not be exportable to Studio 5000
- If a Controller does not have an I/O or Device assignments, it will not be exported.
- If a Device is assigned to multiple Controllers (Listen only Connections), it will be
exported to both Controllers.
- If an I/O chassis has individual I/O modules assigned to more than 1 Controller, the
entire chassis will be exported to each Controller.
- When exporting a Chassis definition, IAB does not consider the actual Chassis Size. The export
will assume the largest Chassis Size possible for the given chassis.
- At present, the RPI and Connection Type selections within the Advanced Communication
Details Interface are exclusively accessible for the majority of products belonging to the 1756
and 1734 family. Studio 5000 will create a default module definition for all other families during
import. You may need to adjust parameters in Studio 5000 to accurately reflect the necessary
settings.
- IAB and Studio 5000 do not follow the same naming conventions for Chassis / Devices. Due to
this difference, the export will manually adjust names within IAB to fit the required conventions
within Studio 5000. Any name changes are included as part of the output logs.
Warnings / Potential Problems:
- IAB is not capable of knowing which version of Studio 5000 or which Device Profiles are
installed. Due to this limitation, the import into Studio 5000 can experience issues:
- If Devices are imported into a version of Studio 5000 that does not support them
- If Device Profiles are not installed in Studio 5000 for all Devices in the import
- The limitations above could result in:
- Specific Devices erroring during the import and not being added to the I/O Tree.
- Unexpected crash of Studio 5000 due to Devices not having Profiles installed.
- Unfortunately, there is no way to accurately predict how the L5X file will import into
lower versions of Studio 5000, or what will happen if Device Profiles are not installed.
-
Additional Information about the export:
- When an export is performed within IAB, there are several informational dialogs or logs that are
displayed/created to help you identify Devices that have experienced problems:
List of Devices that will not be exported because they are not assigned to a Controller in IAB’s
Advanced Communication Details Interface:
List of Controllers that had ALL items Successfully exported, or Controllers that had 1 or more
Devices that were not exported. It is important to review the Controller log files to understand
the reason why a Device may not have been exported:
* In the event some devices were not exported, it is important to review the Controller
log files to understand the reason why a Device may not have been exported.
The Log Files will be broken down into 3 main sections:
System Errors:
System Errors (Contact Tech Support for assistance):
!!! CStudio5000XMLAssembler: Failed to export XML for Device011.
* You will need to contact IAB Tech Support and provide your IAB project for assistance in
fixing this issue.
Successful Exports:
The following items were successfully exported:
Device Local_0_Comm (1756-EN2TR)
"CLogix010 (Copy 1)" was changed to "CLogix010Copy1" to comply with L5X naming
conventions.
Device CLogix006 slot 2 (1756-L7SP): Informational: Safety Partner is included in
Controller definition (No action necessary).
Device Local_3_Mod (1756-M02AE)
Device Local_4_Mod (1756-M02AEK)
Device Device022 (2711R-T10T): Informational: HMI's with only Class 3 Connections are
not part of the Export to Studio 5000 (No action necessary).
* These items successfully exported. Any informational notes will be included to help
understand any potential confusing points or to point out naming changes.
Devices Not Exported:
The following items were NOT exported. See comment below:
Device LinkingDevice003 (1788-EN2FFR): Warning: Due to technical limitations of the
export, this module cannot be exported to Studio 5000. Please add to I/O Configuration
Tree manually.
Device XMCondMon001 slot 1 (1444-TSCX02-02RB): Warning: Due to technical
limitations of the export, this Condition Monitoring Expansion modules cannot be
exported to Studio 5000. Please add to I/O Configuration Tree manually.
Device XMCondMon001 slot 2 (1444-RELX00-04RB): Warning: Due to technical
limitations of the export, this Condition Monitoring Expansion modules cannot be
exported to Studio 5000. Please add to I/O Configuration Tree manually.
Device XMCondMon001 slot 3 (1444-AOFX00-04RB): Warning: Due to technical
limitations of the export, this Condition Monitoring Expansion modules cannot be
exported to Studio 5000. Please add to I/O Configuration Tree manually.
Device XMCondMon001 slot 4 (1444-RELX00-04RB): Warning: Due to technical
limitations of the export, this Condition Monitoring Expansion modules cannot be
exported to Studio 5000. Please add to I/O Configuration Tree manually.
Device XMCondMon001 slot 5 (1444-RELX00-04RB): Warning: Due to technical
limitations of the export, this Condition Monitoring Expansion modules cannot be
exported to Studio 5000. Please add to I/O Configuration Tree manually.
Device PwrMntr500_001 (1420-V1-ENT): Warning: Due to technical limitations of the
export, this module cannot be exported to Studio 5000. Please add to I/O Configuration
Tree manually.
* These items were not successfully exported for the reason listed in the comment. It is
possible that these may be addressed in future releases.
Import Assumptions:
- Import will be an evolving process where support for more devices will be added over time.
Not all Devices are supported at initial launch.
- Each. L5X file can be individually imported into IAB Application & treated as single
independent project in IAB Application.
- The Device will get created in IAB based on the AOP data availability in IAB’s Advanced
Communication Detail directory. If a Device is not supported/doesn’t have AOP information, it
will not be importable in IAB application.
- When importing, all Chassis definitions and IP address information will be set in IAB with
reference to information available in. L5X file. (read more on IP assignment under limitations)
- RPI and Connection related information will be set in IAB’s Advances communication interface.
- IAB will follow the same naming conventions for Chassis / Devices as in Studio 5000.
Import Limitations:
- As Studio. L5X file will not have network topology related information, IAB asks user to select
desired network topology during import process.
- The limitations above could result in:
- Single network topology throughout the project.
- Actual network architecture in the field may be different from the newly created one.
- Multiple network topologies are not supported in the import process. But later user can
edit them manually.
- If Logix designer has a non-Ethernet/IP communication adapter such as CNBR, DNB, RIO the
associated IO modules will still be created in IAB, but it will not connect to any network. Users
can still connect to a desired network manually.
- As Studio .L5X will not have information regarding redundancy module, IAB will place
redundancy module in the first available slot after the controller.
- Import of obsolete products is very limited and it is based on the information available in IAB.
Refer log files for more information.
- Due to technical limitations, In some cases IP address information present in. L5X file will be
overwritten with IAB rule set during import.
Example: In scenarios where multiple devices share the same IP address in Star topology, the
import process will prioritize the inclusion of a switch in the network topology. Subsequently,
devices are assigned the next available IP address to maintain network integrity and avoid address
conflicts.
Additional Information about the import:
- When an import is performed within IAB, there are several informational dialogs or logs that are
displayed/created to help you identify Devices that have experienced problems:
The window is utilized to validate catalogs, distinguishing between valid and invalid ones.
Invalid catalogs are those that are either currently unsupported in the import feature, absent
from the IAB, or contain obsolete products.
Log files will also contain the same set of information regarding the validation process of
catalogs.
The following items were successfully Imported:
Local 1756-L72 Slot=0
N27 1756-CN2R Slot=1
N29 1756-CN2R Slot=2
ENBT1 1756-EN2T Slot=3
ENBT2 1756-EN2T Slot=4
EN2TR 1756-EN2TR Slot=5
N1 1794-ACNR15 Slot=0
The following items are currently not incorporated into the Import. Contact Tech Support to
request.
GT2_PLC 1756-L63 Slot=0 -Not Valid
N40_CGCM 1407-CGCM -Not Valid
N41_CGCM 1407-CGCM -Not Valid
Device Support (as of [Link] Release):
Due to the volume of Devices in IAB, we have prioritized the following items to be supported as
part of the Export/Import feature:
Devices Export Support Import Support
Controllers
1756 ControlLogix L7/L8 Controllers 1756 ControlLogix L7/L8 Controllers
1769 CompactLogix L1/L2/L3 1769 CompactLogix L1/L2/L3
Controllers Controllers
5069 CompactLogix 5000 Controllers 5069 CompactLogix 5000 Controllers
DIO 1715 Redundant I/O 1718 Ex I/O
1718 Ex I/O 1734 Point I/O
1719 Ex I/O 1756 ControlLogix I/O
1732 ArmorBlock I/O 1769 Compact I/O
1734 Point I/O 1794 Flex I/O
1738 ArmorPoint I/O 5069 Compact 5000 I/O
1756 ControlLogix I/O 5094 Flex 5000 I/O
1769 Compact I/O
1794 Flex I/O
5015 FlexHA 5000 I/O
5032 ArmorBlock 5000 I/O
5069 Compact 5000 I/O
5094 Flex 5000 I/O
Motion Kinetix 300
Kinetix 350
Kinetix 5100
Kinetix 5300
Kinetix 5500
Kinetix 5700
Kinetix 6500
Drives and motor ArmorStart Devices
control PowerFlex Drives
Encoders
Energy Monitoring PowerMonitor 5000
Network Infra Stratix Switches (Not all Startix switch
products are supported. Please refer log files)
Multiple other Networked Devices
Process PlantPAx Systems (may need to
regenerate old projects to have export
be possible)
The following items have limited or No support (see export/import logs for more information):
- Technology Partner products
- Non-EtherNet/IP devices
- Generic Device
