Storing the same input device data in two historians

toast84 · May 2, 2019, 2:10pm

I have successfully created an input device and stored its measurements in a local historian. I am trying to store the same data in a remote OSI PI historian.

I’ve created a PI historian instance. Then, I created a new measurement for the PI historian that uses the same signal reference as the measurement being stored locally. But under “Monitor Device Outputs”, the PI measurements all show “0” for their data.

What am I doing wrong and is there a better way to accomplish this?

ritchiecarroll · May 2, 2019, 2:56pm

The OSI-PI adapter will automatically synchronize metadata. When configured properly, data and metadata should flow into PI.

See the following:

github.com

GridProtectionAlliance/openPDC/blob/master/Source/Documentation/wiki/OSI-PI_Adapters.md

[![The Open Source Phasor Data Concentrator](openPDC_Logo.png)](openPDC_Home.md "The Open Source Phasor Data Concentrator")

|   |   |   |   |   |
|---|---|---|---|---|
| **[Grid Protection Alliance](http://www.gridprotectionalliance.org "Grid Protection Alliance Home Page")** | **[openPDC Project](https://github.com/GridProtectionAlliance/openPDC "openPDC Project on GitHub")** | **[openPDC Wiki](openPDC_Home.md "openPDC Wiki Home Page")** | **[Documentation](openPDC_Documentation_Home.md "openPDC Documentation Home Page")** | **[Latest Release](https://github.com/GridProtectionAlliance/openPDC/releases "openPDC Releases Home Page")** |

# openPDC OSI-PI Adapters

## Minimum Requirements

1. For openPDC v2.1 or newer, the PI AF-SDK is required to be installed on the openPDC server. For openPDC v2.0 or older, the PI SDK v1.4.0 or greater (use 32-bit or 64-bit to match openPDC) must be installed on the openPDC server. For 64-bit installations you must install <b>both</b> the 64-bit SDK and the 32-bit SDK. The GSF OSI-PI adapter library depends on the 64-bit OSI-PI SDK libraries as well as the OSI-PI Buffering Subsystem which is only installed with the 32-bit SDK.
2. Desired PI server connection must be added to the SDK 
3. Access to PI system using PI trust (preferred) or explicit login
    1. Connection must have access to read/write any points mapped to openPDC.
    2. If the metadata synchronization is enabled, connection must also have read/write access to the pipoint database.

## Output Configuration on an Existing openPDC Installation

1. Open the openPDC manager and navigate to **Outputs > Historians**.
2. Click the **Clear** button to create a new historian.

This file has been truncated. show original

toast84 · May 2, 2019, 7:28pm

Hi Ritchie, thanks for responding.

The tags I created were populated in the PI server but the issue is that I can’t seem to reference the data in the measurement.

I wanted to store this tag in both the PPA local historian and my PI server:

So I created a new measurement using the same signal reference.

But when I went to check the output, the measurement does not seem to receive data, it just lists “N/A” for time. The tag is created in the PI server.

Is the signal reference not what I should be using?

ritchiecarroll · May 2, 2019, 8:33pm

If a measurement exists - it will go to all configured destinations, e.g., local PPA historian and OSI-PI - you do not need to create a separate measurement.

The measurement signal ID should be unique in the universe of measurements…

Check your OSI-PI connection string, make sure it contains something like ; sourceIDs=PPA - this will make sure all measurements associated with the local historian PPA also get pushed to PI.

If you update the connection string, be sure to save the adapter record and re-initialize it…

Thanks,
Ritchie

toast84 · May 3, 2019, 8:30pm

Hi Ritchie,

I tried “sourceIDs=PPA” on the historian instance but it did not seem to have an effect. When I ran the “list” command in the console it still showed the source ID as “PI” (my acronym). Is this expected?

However, using InputMeasurementKeys in the connection string did change the values stored.

sricho · January 22, 2020, 1:00am

Hi Ritchie

I found this tread and tried to setup an OSI-Soft connected using openPDC V2.7. However when I got to select the Primary History, the OSI-SOft connector is not an option.

Does the SDK need to be isntalled before OpenPDC is installed to have the historian as an option? or has this option been removed in V2.7?

Regards
Steve

ritchiecarroll · January 22, 2020, 2:47am

It does - you have to install the OSI-PI SDK before the adapter can be loaded - otherwise it’s invisible, i.e., not shown.

aningineer · February 3, 2021, 6:07am

Hi Ritchie,

Thanks for sharing these very useful resources. I’m trying to archive/stream data from my openHistorian system to the PI system. Could you kindly indicate whether openHistorian 2.6.30 might also include the OSI-PI adapter? If so, is there any documentation on which version of the PI system it’s compatible with?

At the moment, the OSI-PI adapter is not showing up as an option in my configuration utility like in the Archiving data to the OSI-PI Historian using the openPDC video. Do I need to install the OSIsoft AF SDK first to get this to show up?

Thanks,
Aninda

ritchiecarroll · February 3, 2021, 6:10am

This adapter is automatically included, however, it will only be visible if the OSIsoft AF SDK is installed on the same system as the openHistorian service.

Thanks,
Ritchie