Data collection steps

The data collection steps below are required.

1. Confirm that you can use PI SMT to configure Data Archive.

   You do not need to run PI SMT on the same computer on which you run this interface.

2. If you are running the interface on an interface computer, edit the Data Archive’s Trust table to allow the interface to read attributes and point data.

   If a buffering application is not running on the interface computer, the PI trust must allow the interface to write data.

3. Run the installation kit for the PI Interface Configuration Utility (ICU) on the interface computer if the ICU will be used to configure the interface.

   This kit runs the PI SDK installation kit, which installs both the PI API and the PI SDK.

4. Run the installation kit for this interface.

   The kit also runs the PI SDK installation kit which installs both the PI API and the PI SDK if necessary.

5. If you are running the interface on an interface computer, check the computer’s time zone properties.

   An improper time zone configuration can cause the Data Archive to reject the data that this interface writes.

6. Run the ICU and configure a new instance of this interface.

   Essential startup parameters for this interface are:

   • Point Source (/PS=x)

   • Interface ID (/ID=#)

   • Data Archive (/Host=host:port)

   • Scan Class (/F=##:##:##,offset)

7. Use a data source-specific connection tool to confirm connection between the interface computer and the device.

8. If you will use digital points, define the appropriate digital state sets.

9. Add the X, Y, and Z states to the system digital state set.

10. Build input tags and, if desired, output tags for this interface.

    PtSecurity must permit read access for the PI identity, group, or user configured in the PI trust that is used by the interface. DataSecurity must permit read access (buffering enabled) or read/write access (unbuffered) for the PI identity, group, or user configured in the PI trust that is used by the interface.

    Note: When buffering is configured, the DataSecurity attribute must permit write access for the buffering application’s PI trust or mapping. DataSecurity write permission for the interface’s PI trust is required only when buffering is not configured.

11. Start the interface interactively and confirm its successful connection to the Data Archive without buffering. (The DataSecurity attribute for interface points must permit write access for the interface’s PI trust.)

12. Confirm that the interface collects data successfully.

13. If output points are required, confirm that output points update the correct values in the data source. Create an output point whitelist file for the interface instance.

14. Stop the interface and configure a buffering application (either Bufserv or PIBufss).

15. Start the buffering application and the interface. Confirm that the interface works together with the buffering application by physically removing the connection between the interface computer and the Data Archive computer.

    Note: The DataSecurity attribute for interface points must permit write access for the buffering application’s PI trust or mapping. The interface’s PI trust does not require DataSecurity write permission.

16. Configure the interface to run as a Windows service. Confirm that the interface runs properly as a service.

17. Restart the interface computer and confirm that the interface and the buffering application restart.