Data collection steps

Confirm that you can use PI SMT to configure the PI Data Archive. You need not run PI SMT on the same computer on which you run this Interface.

If you are running the interface on an interface node, edit the PI 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 node, the PI trust must allow the interface to write data.

Run the installation kit for the PI Interface Configuration Utility (ICU) on the interface node 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.

Run the installation kit for this Interface. This kit also runs the PI SDK installation kit which installs both the PI API and the PI SDK if necessary.

If you are running the Interface on an Interface Node, check the computer’s time zone properties. An improper time zone configuration can cause the PI Data Archive to reject the data that this Interface writes.

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=#)

• PI Data Archive (/Host=host:port)

  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.

Build input tags and, if desired, output tags for this Interface. Important point attributes and their purposes are:

Location1 specifies the Interface instance ID.

Location2 specifies the event categories for this event.

Location3 specifies the event-type (Simple, Tracking, Condition-related).

Location4 should be set to zero for all points.

Location5 should be set to zero for all points.

ExDesc specifies which attribute(s) and vendor specific attribute identities are to be stored in the PI tag, along with the optional quality and severity directives.

InstrumentTag specifies the OPC AE server source.

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

Confirm that the Interface collects data successfully.

Stop the Interface and configure a buffering application (either Bufserv or PIBufss). When configuring buffering use the ICU menu item Tools | Buffering… | Buffering Settings to make a change to the default value (32678) for the Primary and Secondary Memory Buffer Size (Bytes) to 2000000. This will optimize the throughput for buffering and is recommended.

Start the buffering application and the Interface. Confirm that the Interface works together with the buffering application by physically remo ving the connection between the Interface Node and the PI Data Archive Node. (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.)

Configure the Interface to run as a Service.

Confirm that the Interface runs properly as a Service.

Restart the Interface Node.

Confirm that the Interface and the buffering application restart.