Create a new instance of a PI interface

Install the PI interface you want to configure.

Install any ICU controls available for the interface, if not already installed.

Run PI ICU and choose Interface > New Windows Interface Instance from EXE. You can also click the Create new interface instance button on the toolbar.

The Configure a New Interface dialog box opens.

Click Browse to browse to the interface executable (.exe) file for the new interface.

From the Host PI Data server/collective list, select the PI Server or PI Server collective to which the interface will send data.

If you specify a collective, then from the Collective Member list, select the specific collective member to which the interface will send data.

If you have the information available, enter the optional settings in the Interface name, Point Source, Interface ID # and Service ID fields.

Click Add to add the interface.

In the Confirmation dialog box, click OK.

The interface appears in the Interface text box in the main ICU window.

Select the proper Type for the interface on the main ICU window, if it is not selected automatically.

Complete configuration of the interface by filling in the desired fields on the PI ICU page window.

For details on which attributes are required by a particular interface, see the appropriate PI interface user guide.

Use PI ICU and an application to create the PI points needed to configure and run the PI interface.

Available applications include:

• Point Builder tool in PI System Management Tools (PI SMT) - see the "Point Builder" topic in the PI Server user guide.

• PI Tag Configurator add-in to Microsoft Excel (included with PI SMT) - see the "Use worksheets created in PI Tag Configurator" topic in the PI Server user guide.

• PI Builder add-in to Excel - see the "PI Builder" topic in the PI Server user guide.

  Note: After PI ICU has been used to configure a PI interface, all subsequent configuration changes should be conducted in PI ICU. PI ICU will prompt you if the command line parameters stored in the Module Database do not match those stored in the PI interface batch file (.bat file).