PCo 2.1.4 Setup

[Former Member]

Hi All,

I have PCo 2.1.4 to be connected with an OSI-PI engine in FactoryTalk Historian.

PI-SDK 1.3.5 (Build 343) is installed. PI version is 3.4.375.80.

PCo and FT Historian installed on the same virtual machine (Win 2003, 32bit).

Trying to configure a source system using PI Agent throws an error as follows:

Connectivity Framework Error

Exception has been thrown by the target of an invocation.

Could not load file or assembly 'OSIsoft.PISDK' or one of its dependencies. The system can not find the file specified.

My question is ..

Do I need a "minimum version" of PI-SDK (i.e. 1.3.8 instead of 1.3.5) for PCo 2.1.4, since what's installed cannot be found?

Are there default locations being searched so that the Rockwell default installation path is influencing the PCo setup?

As a 2nd attempt, I defined an OLEDB source system to localhost, using PI OLEDB Provider, targeting the "piarchive" catalog.

Testing the connection to PI succeeds in this second case.

Thanks,

paul.

[jcgood25 · Accepted solution]

From the PCo 2.1 Component Installation Guide on service marketplace:

http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000735008&_SCENARIO=01100035870000000202&_O...

Page 9: "If you want to use the PI agent, you must install PI SDK Version 1.3.6 or later."

[Former Member · Accepted solution]

Looks like FTHISTORAN cannot be updated with a new PI-SDK without breaking something inside, so I dropped the PCo approach with PI agent. Unfortunately, I am running out of the time allocated for this connectivity issue.

Next in mind was to use the UDS 4.0 and the UDS OLE DB approach. Added a new UDS instance, configured it for PI-OLEDB V3.0. Defined the settings (connection string - datalink properties) and tested the connection by pressing the button on the screen. The UDS replies quickly in a small window called Microsoft Data Link : Test connection succeeded!

Wee, one down. MII Portal, dataservers, created and OLEDB one corresponding to the UDS OLEDB instance,

Getting excited, I say it's time to browse the historian using some query templates. Fixed Query, as below:

SELECT "tag", "expr", "time", "timestep", "calcbasis", "value", "pctgood" FROM "piarchive".."pitotal" WHERE tag = 'sinusoid' AND time BETWEEN '-1h' AND ''

Returning the dataset as expected. The only issue I have now is that the number of available connections for this type of connector is limited to 1 (i.e. no pooling) .. so if two clients will want data from PI in the same time.. I'll be in trouble. What would be your suggested approach to use the same dataserver for concurent requests?

Hint when creating the FT dataserver: use an OLEDB dataserver, not an UDC one. It will save you couple of days of suicide thoughts.

[Former Member · Accepted solution]

Hi Paul,

In the UDS Admin Console, select your PI OLEDB instance and then got to View -> Advanced Mode. You will see additional properties listed, including one for Pool Size.

Note also, the Help Documentation does state that the OLEDB Connector is to be used when setting up the Data Server in MII, so perish those suicidal thoughts

Kind Regards,

Diana Hoppe

Edited by: Diana Hoppe on Feb 4, 2011 9:57 AM

[Former Member · Accepted solution]

Following your instructions I was able to configure a datapool of 10.

Now I'm back to PCo business (need to sort it out eventually) and I'm not stressed any longer about getting the data out if the historian for the development ..

Many thanks Diana.

[Former Member · Accepted solution]

Glad to be of service, Paul

- Diana