Rockwell Automation FactoryTalk Historian SE 3.0 UniInt Interface User Guide - Manual (Page 34)

Historian Point Configuration
28
For Windows-based interfaces, PI SDK support is available beginning with version 3.2.0 of
UniInt. UniInt uses the PI SDK to support the following features:
 Extended descriptors and instrument tags up to 1 kilobyte in length, or 1023 characters
(UniInt 3.2.0). Starting with version 4.1.0 of UniInt, if version 1.6.x or greater of the PI
API is installed on the interface node and the Historian Server is version 2.x or greater,
UniInt will use the PI API functions that were released with PI API 1.6.x to get
instrument tags and extended descriptors of up to 1023 characters.
 Full 32-bit values for excmin and excmax (UniInt 3.4.4).
 Multi-character point source characters (UniInt 3.5.0). Starting with version 4.1.0 of
UniInt, if version 1.6.x or greater of the PI API is installed on the interface node and the
Historian Server is version 2.x or greater, UniInt will use the PI API function for
retrieving points with a multi-character point source.
With the PI API prior to version 1.6, the extended descriptor was limited to 80 characters, the
instrument tag was limited to 32 characters, excmin and excmax were limited to 16-bit values
(0 – 65,535), and only single-character point sources were supported.
Check the documentation for your particular interface to see whether the PI SDK is enabled
or can be enabled. If the PI SDK is enabled, the following message will be written to the log
file.
The PI SDK is enabled
If the above message is printed, the version of the PI SDK being used will also be printed. If
the PI SDK is not enabled, the following message will be written to the log file.
The PI SDK is disabled
“Known Servers” Table
In order for the PI SDK to be able to connect to a particular Historian Server, the Historian
Server must be configured in the PI SDK‘s ―Known Servers‖ table. The ―Known Servers‖
table can be edited using the \pipc\pisdk\AboutPI SDK.exe
utility. Since the PI
API uses the pilogin.ini file for its Server list, Server information must be configured
in two different spots for PI API / PI SDK hybrid applications.