Overview

The Import command lets you add an M580 control project created with Control Expert Classic to a system project. Data that is managed by the Topology Manager becomes available in its various views and panes. The other project data remains available in the control project, which you can edit by using Control Expert Editor.

During the import operation, the system project is locked.

Details about an import operation are available in the OPERATION DETAILS pane of the notification pane.

NOTE: To import a control project containing a non-M580 controller, refer to the topic describing the import of legacy controllers and non-M580 PACs.

Prerequisites

The following table describes the requirements that need to be satisfied by the Control Expert Classic M580 control project to be able to import it.

Scope Requirement

Supported file type

Full application exchange file (.zef) created by using Control Expert Classic 15.0 or later.

NOTE: You cannot import the file if the data that it contains originates from the Topology Manager. This is the case if an M580 control project is deployed from the Topology Manager or Control Expert Editor then, uploaded from the controller to Control Expert Classic, and from there, exported in .zef format.

Supported CPUs

M580 CPUs of version 2.70 or later.

DTMs

If a DTM of the following modules has been added in the DTM Browser of the control project, the corresponding module must be present in the configuration:

  • BMEAHI0812

  • BMEAHO0412

  • PMEPXM0100

  • PMESWT0100

  • PMEGPS0100

  • PMEUCM0302

If it is not the case, either add the module or remove the DTM.

Device name

For each device, the DHCP device name (Identifier) that is entered must comply with the specific requirements for this device.

For example, for a BMEAHI0812 module, the device name must be Mx80_02_AHI0812 for a module located at slot 2 of the main rack.

Refer to the user manual of the device for a description of the device name requirements.

IPsec

When IPsec is enabled, the Pre-Shared Key that is entered must contain at least 16 characters and comply with the format requirements.

Control project settings

The I/O Scanning Mode is set to Enhanced.

NOTE: The control project must have been built successfully by using Control Expert Classic 15.0 or later with the I/O Scanning Mode set to Enhanced before creating the export file (.zef). This is required because the I/O scanning mode cannot be changed after import and the Topology Manager only supports Enhanced mode.

File encryption

Encrypted project files cannot be imported.

If file encryption is active for the control project, the With Encryption check box must be cleared when the project file is exported from Control Expert Classic.

DTM Audit Tool

When you import a control project that contains DTMs, if any DTM that is required on the local computer is missing or incompatible, the DTM Audit Tool opens and provides the necessary information.

Closing the tool cancels the import operation and you need to install the required DTMs on the local computer, and start over the import operation.

Importing Deployed Control Projects

If you import a control project that has already been transferred to a PAC, the control project that is created in the system project is different from the deployed one.

You need to build and deploy it again to the PAC by using the Topology Manager.

Importing Control Projects with Local Slaves

When you import two control projects containing a local slave that is activated (adapter) and a scanner scanning the local slave respectively, some manual configuration is required after the import to recreate the connection between the scanner and the adapter.

It is also required if you are importing only either one of these control projects.

Refer to the example that illustrates an import scenario.

The table describes various scenarios where a control project with a local slave configuration is imported into a system project, the result, and the required actions to recreate the connection.

In the imported control project

In the target system project

Result after import

Action to perform

A local slave is configured and active (adapter)

Irrelevant

The local slave configuration is not imported.

You need to recreate the local slave manually for the corresponding module by using the PROPERTIES pane.

A CPU or BMENOC03•1 module is configured to scan a local slave

No PAC exists

The local slave (adapter) is recreated as a device by using the EtherNet/IP DTM Device equipment of the catalog. The device is configured with the data of the local slave of the imported control project.

It is located in the Local Slaves subfolder of the imported PAC.

You need to create a PAC that contains a module with the same part number and version as the local slave or import the control project that contains the corresponding local slave (adapter).

Then, move the local slave configuration of the EtherNet/IP device to the appropriate module listed in the Move Local Slave To submenu.

A CPU or BMENOC03•1 module is configured to scan a local slave

A PAC that contains a module with the same part number exists.

However, the DTM reference that is selected for this module does not match the DTM of the local slave in the imported control project.

The Move Local Slave To command is not available in the context menu of the EtherNet/IP device (see above).

You need to update the PAC so that it contains a module with the same part number and version as the local slave or import the control project that contains the corresponding local slave (adapter).

You can also create a new PAC.

Then, move the local slave configuration of the EtherNet/IP device to the appropriate module listed in the Move Local Slave To submenu.

A PAC that contains a module with the same part number exists.

And, no DTM reference is selected for this module or a DTM reference is selected and it matches the DTM of the local slave in the imported control project. (A local slave is not required in the existing PAC.)

The Move Local Slave To command is available in the context menu of the EtherNet/IP device (see above).

Also, the EtherNet/IP device is added to the scanner of the imported PAC in the EtherNet/IP Communication Mapping View.

You can move the local slave configuration of the EtherNet/IP device to the appropriate module listed in the Move Local Slave To submenu.
NOTE: Moving the local slave configuration to a module that appears in the Move Local Slave To submenu is optional and not required to enable the data exchange. However, it is recommended to perform this step to be consistent with other local slaves that you may have created by using the Topology Manager.

Control Project Data Migration

The table describes the result of the import operation in the system project for various types of data of the imported control project.

Type of data

In the Control Expert Classic project

Result in system project

Topology folder structure

N/a

Creates a folder in the SYSTEM PROJECT pane with the name of the imported project file.

The name may be indexed to maintain uniqueness.

If the project file name is not compatible, the folder name is Folder_x.

Project name

Project name in imported project file.

The name of the project becomes the name of the M580 PAC.

The name may be indexed to maintain uniqueness.

Racks and drops

–

Are recreated in the SYSTEM PROJECT pane.

For a redundant PAC, the rack of the controller with role B is created also.

Network data and IP addresses

–

A new logical network is created with the appropriate network address for the CPU module and each isolated module.

The same IP addresses are kept.

The logical network is created even if a logical network with the same network address already exists in the system project.

Master modules (M580 CPU and BMENOC03•1 modules) and other modules with Ethernet communication capability

Port and security configurations.

Services.

The configurations and services are kept.

Devices scanned by the CPU or a BMENOC03•1 module

Devices on the Device List.

Devices for which corresponding equipment exists in the Topology Manager catalog are added to the system project by using this equipment.

Others are added by using either of the following generic equipment depending on the protocol they use:

  • EtherNet/IP: EtherNet/IP DTM Device and the corresponding DTM.

  • Modbus TCP: Modbus TCP DTM Device and the corresponding DTM or Modbus TCP Device when no DTM is required.

NOTE: In the control project of the PAC, DTMs of scanned devices are replaced with placeholder DTMs. This is because the DTMs are managed in the Topology Manager and can be opened from the context menu of these devices.

Port, interface, and network configurations.

Services.

The configurations and services are kept.

If the scanned device belongs to a different logical network than the scanner, its interface configuration is modified to be on the same network.

Device DDT

The same values are used to configure the Instance Name and Type Name of the I/O profile.

I/O scanning data

For each device, the corresponding I/O profile is created.

In the Communication Mapping Views, the active I/O profile of each scanned device is added to the respective scanner.

NOTE: This applies even if Active Configuration is disabled for the device in the Control Expert Classic project. To disable I/O scanning, remove the I/O profile of the device from the scanner in the Communication Mapping view after import.

Local slaves

Some manual configuration may be required after import is completed to recreate the connection.

Refer to the topic describing the import of control projects with local slaves.

DTM configuration

–

The values configured in the DTMs are kept. The DTM can be opened from the context menu of the device it pertains to.

Configuration files

Files imported into or exported from the Control Expert Classic project.

You can attach to the PAC or a device configuration files that you have used (for example, for PMEPXM0100 modules).

DHCP server name and identifiers

–

DHCP client/server relationships are maintained and DHCP identifiers are kept.

Fieldbus devices

–

Slave devices appear under the master module in the SYSTEM PROJECT pane and the Fieldbus Editor is available.

Data types, variables, the program, animation tables, operator screens, and documentation.

–

The data is the same as in the migrated project and accessible when you edit the control project of the PAC.

Build state

–

The build state is Not Built.

Importing M580 Control Projects

To import a control project containing an M580 PAC into a system project, proceed as follows.

Step

Action

1

Right-click the Topology node or a topology folder in the SYSTEM PROJECT pane and select Import .

Result: The Topology: Import dialog box opens.

2

Select *.zef as file type.

3

Select a project file.

4

Click Open .

Result: If the control project contains DTMs and a missing DTM or incompatibility is detected, the DTM Audit Tool opens. Otherwise, the control project import starts. Proceed to step 7.

5

Review the information in the DTM Audit Tool and click Cancel.

Result: The DTM Audit Tool closes and the import is canceled.

6

Install the necessary DTMs on the local computer and start over the procedure.

7

Import is completed once a notification is displayed informing you that the project has been upgraded successfully.

Result: Data of the imported control project that is managed in the Topology Manager is represented by the corresponding PAC and its dependencies in the SYSTEM PROJECT pane. Their configuration data visible in the other panes and views. The other data is available in Control Expert Editor when you edit the control project from the PAC.

8

Review the information that is displayed in the ACTIVITIES and OPERATION DETAILS tabs of the notification pane related to this Import activity.

If the imported control project contains a local slave, a message is displayed and you need to recreate the connection with the local slave manually.