- PI DATALINK 2013 INSTALL KIT ARCHIVE
- PI DATALINK 2013 INSTALL KIT SOFTWARE
- PI DATALINK 2013 INSTALL KIT WINDOWS
PI DATALINK 2013 INSTALL KIT WINDOWS
There are two ways to authenticate this connector with the PI Server: PI Trust or Windows Integrated Security. The Seeq OSIsoft PI Server connector only reads data.
PI DATALINK 2013 INSTALL KIT ARCHIVE
The Seeq OSIsoft PI Server connector accesses data from the PI Data Archive another connector accesses PI AF Servers. You can run Seeq Server as a Windows Service (see Secure Configuration Options (SSL/TLS) article) using those credentials, which will dictate the way that Seeq logs in to PI. Once you have proven out connectivity to the PI server using the instructions above, you will likely want to establish a more secure and supportable connection method, including the use of a Windows Service for running Seeq Server.Īs a best practice, it is recommend that you create an ActiveDirectory domain account that has read-only access to PI and the tags that you wish to appear in Seeq. You should see a new connection appear in Seeq Workbench, and the PI Server's tags will be indexed and available for use in Seeq. Just change the Enabled field to true and save the file. Otherwise duplication and other hazards will ensue. Note that the Point IDs (an integer number, observable in the System section of the PI Server Management Tools' Point Builder section) in the two servers must be identical (for identical tags) in order for this strategy to work. This field can be changed independently of the Id field, which is useful if you have separate "test" and "production" PI Servers and want to switch between them without causing duplication in Seeq. In Seeq Server version R20.0.38.05 and later, there is a PIServerID field that corresponds to the PI Server ID. OSIsoft best practices recommend that you preserve this identifier if you move servers, as explained in this OSIsoft article. In Seeq Server version R20.0.38.04 and earlier, the Id field corresponds to the PI Server ID. It is possible for Seeq to pick up this integer, which is incorrect, if not connection has been made. Prior to the first connection, the ID is set to an integer. This ID is properly set on the client side, the Seeq Server in this case, only after a successful connection has been made. Each PI Data Archive Server is assigned a Unique ID this ID is defined and stored on the Server. Here's a detail on PI Data Archive Server connections you need to be aware of. Always connect to the PI Servers to verify the configuration is correct.
You will also need a service account that has rights to read data from the PI Data Archive servers you will be connecting to.įor best results, you should install the PI AF Client first and then configure connections to all your PI Data Archive Servers that Seeq will access. So, it is important to install the PI AF Client which includes all required SDKs and the PI System Explorer. The PI System Explorer is used to configure connections to both the PI Data Archive servers and to the PI Asset Framework servers. It may not necessarily be installed if only PI ProcessBook is installed. The AF SDK is always installed on a machine if the PI AF System Explorer client application is installed.
PI DATALINK 2013 INSTALL KIT SOFTWARE
The OSIsoft PI Connector utilizes OSIsoft's Asset Framework Software Development Kit (AF SDK) to communicate to the PI Server. Provided the above AF client is installed, data can be accessed from PI Server version 3.2.357 (PI 3.2 SR1) or later. Version 2.7 or later is required to support some new features such as filtering out "Excluded" or "Hidden" attributes from Seeq. This can be downloaded from here: Note a login to OSIsoft support is required.
We recommend installing the latest version from OSIsoft. Release Date: ) or later version must be installed on the Seeq Server. OSIsoft Components: PI AF Client 2012 SP2 ( Version 2.