Rockwell FactoryTalk Historian
.NET AGENT
Overview
The OSIsoft PI connector enables Seeq to access data from Rockwell FactoryTalk Historian. Since Rockwell FactoryTalk Historian is built on OSIsoft PI, it will appear to Seeq as an OSIsoft PI server.
Prerequisites
Seeq currently supports FactoryTalk Historian 5 and later. Contact Seeq support if you need support for earlier versions.
In some circumstances, a FactoryTalk license will limit the number of anonymous applications that can connect. If there are no anonymous licenses available, Seeq's attempts to connect to the PI server will timeout. The PISDK logs on the server will show "Maximum Number of Anonymous Connections (0) exceeded".
In these circumstances, the customer will need a 490050-FAQ: FactoryTalk Historian SE Advanced Server Option license procured from Rockwell.
Once a license is obtained it needs to be loaded in the FactoryTalk Activation Manager:
See additional pre-requisites for the OSISoft PI connector here.
Configuration
There is no additional configuration for Rockwell FactoryTalk Historian aside from what is required to configure the OSISoft PI Connector.
Known Issues
There are no known issues for connecting to Rockwell FactoryTalk Historian. Please report any issues you find to our support portal.
Troubleshooting
In some circumstances, a FactoryTalk license will limit the number of anonymous applications that can connect. If there are no anonymous licenses available, Seeq's attempts to connect to the PI server will timeout. The PISDK logs on the server will show "Maximum Number of Anonymous Connections (0) exceeded".
In these circumstances, the customer will need a 490050-FAQ: FactoryTalk Historian SE Advanced Server Option license procured from Rockwell.
Once a license is obtained it needs to be loaded in the FactoryTalk Activation Manager:
If you are running into other issues with connecting to or access data from Rockwell FactoryTalk Historian, view our guide for troubleshooting datasource issues.
Performance considerations
Connecting to Rockwell FactoryTalk Historian does not have any special performance considerations. View our guide on optimizing datasource performance for general guidance.