PI SDK Options
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.
Use the Interface’s default setting
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.
Examples Example 1.1 – single tag query
SQL Statement
(defined in file PI_REAL1.SQL)
|
SELECT PI_TIMESTAMP, PI_VALUE, PI_STATUS FROM T1_1 WHERE PI_KEY_VALUE = ?;
|
Relevant PI Point Attributes
|
Extended Descriptor
|
Location1
|
Location2
|
Location3
|
Location4
|
Location5
|
P1="Key_1234"
|
1
|
0
|
0
|
1
|
0
|
InstrumentTag
|
Point Type
|
Point Source
|
|
|
|
PI_REAL1.SQL
|
Float32
|
S
|
|
|
|
RDBMS Table Design
|
Table T1_1
|
PI_TIMESTAMP
|
PI_VALUE
|
PI_STATUS
|
PI_KEY_VALUE
|
Datetime
(MS SQL Server)
Date/Time
(MS Access)
|
Real
(MS SQL Server)
Number-Single Precision
(MS Access)
|
Smallint
(MS SQL Server)
Number-Whole Number
(MS Access)
|
Varchar(50)
(MS SQL Server)
Text(50)
(MS Access)
|
Note: Location2 is set to zero. This setting makes sure the interface takes just one row from the SELECTed result-set. See Location2 for more details.
Example 1.2 – query data array for a single tag
SQL Statement
(defined in file PI_STRING1.SQL)
|
SELECT PI_TIMESTAMP, PI_VALUE, 0 FROM T1_2 WHERE PI_TIMESTAMP > ?
ORDER BY PI_TIMESTAMP ASC;
|
Relevant PI Point Attributes
|
Extended Descriptor
|
Location1
|
Location2
|
Location3
|
Location4
|
Location5
|
P1=TS
|
1
|
1
|
0
|
1
|
0
|
Instrumenttag
|
Point Type
|
Point Source
|
|
|
|
PI_STRING1.SQL
|
String
|
S
|
|
|
|
RDBMS Table Design
|
Table T1_2
|
PI_TIMESTAMP
|
PI_VALUE
|
Datetime
(MS SQL Server)
Date/Time
(MS Access)
|
Varchar(1000)
(MS SQL Server)
Text(255)
(MS Access)
|
Note: The STATUS column, which is mandatory, is represented by the constant expression '0'.
Dostları ilə paylaş: |