Migrate a Project from ABCLX to OPCLX

This chapter provides details on how to migrate from a Plant SCADA project configured with the ABCLX driver to the OPCLX driver.

Note:
• The migration feature is available in all versions of Plant SCADA from v7.20. The migration tool may require a Service Pack and/or Hotfix on versions prior to v7.50.
• Virtual Port (VP) is obsolete in OPCLX compare to ABCLX.

To migrate a project from ABCLX to OPCLX:

1. Open the Projects activity in Plant SCADA Studio.

2. Select the project that you want to migrate.

3. On the command bar, select Migration Tool.

   The Project Migration dialog box appears.

4. In the Select a project to migrate drop-down box, select the project that you want to migrate.

5. Initially the Migrate ABCLX to OPCLX check box is disabled. Click Configure. The <Project>:<Project Name> dialog box appears.

   For more information on the fields on this dialog box, see the Field Description and Layout of <Project>:<Project Name> Dialog Box section below.

6. In the OPCServer Type group box, select the OPC server name (FactoryTalk or RSLinx Classic).

7. If you want to migrate all the listed devices to OPCLX, then choose Select All check box. Else, select the required I/O devices.

8. You can change the corresponding OPC Topic and OPC Server.

   Note:
   • By default the OPC Server drop-down list is empty with an edit option to enter the OPC server name manually.
   • To select an OPC server under OPC Server drop-down list, in the OPCServerBrowse field, click Browse. The available OPC servers on the local machine are listed under OPC Server drop-down list. Select the required OPC server from the drop-down list. If no servers are found, then click edit and enter OPC server details manually.

9. If you want to browse the OPC servers on a remote machine, in the Machine Name field, enter the IP address or machine name of the remote server..

   Note:
   • The Browse button is disabled until you enter the remote machine name or IP address.
   • If the machine name or IP address is invalid, a pop-up with the message invalid machine name is displayed.
   • If the local machine is unable to establish connection with the specified remote machine, a pop-up with the message Failed to retrieve OPC servers is displayed.
   • If the connection is not successful, click edit and provide OPC server details manually.

   On successful connection with the remote server, the OPC servers of the remote machine are displayed in the OPC Server drop-down list. The first OPC server is selected by default.

10. After updating the required fields, click OK.

    If you do not want to proceed with the migration process, then click the close button at the top-right corner of the <Project>:<Project Name> dialog box.

Note: If migration does not happen or some of the items are not migrated properly, then the log file will be updated with the items that are not migrated.

Field Description and Layout of <Project>:<Project Name> Dialog Box

Different fields and their descriptions are given below:

• OPCServer Type: FactoryTalk and RSLinx Classic are the supported OPCSERVER/GATEWAY. Based on the selected gateway/OPC server, tags are migrated.

• OPC Topic: This is the alias name configured for the device in the Allen Bradley OPC server.

• OPC SERVER: This is the Prog IDs of the OPC servers installed on the given machine.

The layout of <Project>:<Project Name> dialog box is as below:

• It lists the devices in the project that you can migrate from ABCLX to OPCLX.

• Different clusters are displayed in separate tabs. Related primary and standby I/O devices are listed under each cluster.

• Each of the primary and standby device names is displayed as <Devicename>_<Mode>_<Priority>.

• You can enter OPC topic only for the primary devices. You cannot modify the OPC topic for the standby devices. By default, the I/O device name is displayed as Topic Name which can be changed by editing OPC Topic field.

• For the standby devices, OPC topic is set to the OPC topic of its corresponding primary device. If you modify the OPC topic in the primary device, the OPC topic for its standby devices is automatically updated.

Note: Once migration is completed it is recommended to pack the main project and all included projects individually. Packing the database removes deleted records, and re-indexes the database. To pack the project databases, from the Projects activity in Plant SCADA Studio, click Pack.

See Also

Migration of I/O Devices