Configuration checklist

After the interface software is installed, use PI ICU to configure the interface instance. A standard configuration would include the following steps. For more information about standard UniInt interface configurations, see the PI Universal Interface (UniInt) User Guide. For more information on using PI ICU, see the PI Interface Configuration Utility (PI ICU) User Guide.

1. Create the interface instance on the interface node.

2. Configure security.

   1. Configure the Windows service.

   2. Restrict access for service accounts.

   3. Create and configure a PI identity, PI trust, and mappings for the interface (application name: OPCpE), the buffering subsystem, and the PI ICU applications.

   4. Configure DCOM settings.

3. Configure interface startup batch (.bat) file parameters with the minimal settings:

   • Point source

     Use OPC or an unused point source of your choice.

   • Scan classes

     Set as desired. Scan class 1 is reserved for advise points.

   • Interface ID

     Use 1 or any unused numeric ID.

4. Configure the connection to an OPC server.

   From the OPC Server tab in the OPCInt tab in PI ICU, select the List Available Servers button, then select the server. If the server is on another machine, specify that machine or IP address in the Server Node field.

5. Use the PI OPC Client tool to verify that the OPC server is connected, running, and populated with points.

6. See Operate the OPC DA Interface on how to verify the interface startup and information about OPC server data collection.

7. Define the digital state sets for digital PI points.

8. Build input points and (optional) output points for the interface, and verify that data appears in Data Archive.

   For details on point attributes, see PI point configuration.

9. Configure buffering.

   Stop the interface, then configure and start buffering. Restart the interface and confirm that the service and buffering restart.

10. Configure the following optional features:

    • Performance and health points

      Performance and health points are PI points that track the status and performance of the interface.

      Note: PI Interface for OPC DA does not support scan class performance points.

    • Disconnected startup

      Disconnected startup allows the interface to start even if Data Archive is not available.

    • UniInt failover

      UniInt failover minimizes data loss by enabling a backup interface instance to collect data if the primary interface instance fails.