Convert existing DINetwork object references

The following procedure allows you to transition from DINetwork Objects to OPCClient objects, without the need to modify existing IO references.

Note: This procedure assumes that the appropriate communication drivers are already installed in Application Server.

Before starting the procedure, you can view the hierarchy path by expanding the Operations Integration Server Manager in the Operations Control Management Console, and use it a reference to reconstruct the hierarchy path. Note that the hierarchy path can only be viewed when the Galaxy is deployed.

1. In the IDE, undeploy the DINetwork object. In the examples below, the DINetwork object name is PLC_01.

2. Rename the existing DINetwork object to <ObjectName>_OLD, for example PLC_01_OLD.

3. Create a new OPCClient object and give it the same name as the existing DINetwork object. In this example, the new object name is PLC_01.

4. Open the OPCClient object and configure the General tab with the same Server Node and Server Name as the existing DINetwork object. Edit other parameters as needed.

   

5. Move to the Scan Group tab.

   • A <Default> scan group appears automatically.

   • If additional scan groups are defined in the DINetwork object, add them now.

6. Set the Update Interval and Scan Mode for the <Default> scan group to match the configuration of the DINetwork object.

7. If necessary, create new Scan Groups.

8. Enter the Hierarchy Path for the PLC item. Hierarchy Path is used internally to recreate the full path to IO items so you do not have to alter existing IO references. The Hierarchy Path is required for each scan group. There is no need to include the scan group name in the Hierarchy Path. References will be built automatically to include the scan group.

   

9. When you are done editing, save and deploy the OPCClient object. Your existing IO references should begin working immediately. You can verify this in the Object Viewer.