System errors are associated with positive error numbers. Errors related to PI are associated with negative error numbers.
Error Descriptions
On Windows, descriptions of system and PI errors can be obtained with the pidiag utility:
\PI\adm\pidiag –e error_number
To access the PI SDK settings for this Interface, select this Interface from the Interface drop-down list and click UniInt – PI SDK in the parameter category pane.
Disable PI SDK
Select Disable PI SDK to tell the Interface not to use the PI SDK. If you want to run the Interface in Disconnected Startup mode, you must choose this option.
The command line equivalent for this option is /pisdk=0.
This selection has no effect on whether the Interface uses the PI SDK. However, you must not choose this option if you want to run the Interface in Disconnected Startup mode.
Enable PI SDK
Select Enable PI SDK to tell the Interface to use the PI SDK. Choose this option if the PI Server version is earlier than 3.4.370.x or the PI API is earlier than 1.6.0.2, and you want to use extended lengths for the Tag, Descriptor, ExDesc, InstrumentTag, or PointSource point attributes. The maximum lengths for these attributes are:
Attribute
|
Enable the Interface to use the PI SDK
|
PI Server earlier than 3.4.370.x or PI API earlier than 1.6.0.2, without the use of the PI SDK
|
Tag
|
1023
|
255
|
Descriptor
|
1023
|
26
|
ExDesc
|
1023
|
80
|
InstrumentTag
|
1023
|
32
|
PointSource
|
1023
|
1
|
However, if you want to run the Interface in Disconnected Startup mode, you must not choose this option.
The command line equivalent for this option is /pisdk=1.
Introduction Background
The Batch interface reads batch data from different types of data sources, interprets their contents, and builds the corresponding objects in the PI Server Batch Database (BatchDB). In order for this process to work, each data source must contain specific recipe events in a predictable order.
Note: The PI Batch interface is not appropriate for all types of recipes generated by a Batch Execution System. It is designed for recipes that constrain a unit to run a single unit procedure at a time.
This document is meant to be informative enough for the potential user to make the assessment that the interface is appropriate for their environment; it does not delineate the low-level technical aspects of the event file or Batch Execution System (BES) logic.
Objectives
The goals of this document are two-fold. Firstly, to outline the Batch interface logic and PI Server Batch Database objects. Secondly, to make recommendations regarding recipe configuration and BES operations that are compatible with the PI Batch interface logic.
Share with your friends: |