greattraders

How can I retrieve raw time-series data from a Proficy Historian/iHistorian? Create windows 10 bootable usb.

1. Ge Proficy Historian User Manual

Ideally, I would ask for data for a particular tag between two dates.

4 Answers

There are several different sampling modes you can experiment with.

Jul 23, 2010. Is stored as C: Program Files GE Fanuc Proficy Historian Docs iHistorian.chm and I. Then again the User API and SDK cannot do this either.

• Raw
• Interpolated
• Lab
• Trend
• Calculated

These modes are available using all of the following APIs.

• User API (ihuapi.dll)
• SDK (ihsdk.dll)
• OLEDB (iholedb.dll)
• Client Acess API (Proficy.Historian.ClientAccess.API)

Of these the trend sampling mode is probably what you want since it is specifically designed for charting/trending. Though, lab and interpolated may be useful as well.

Read the electronic book for more information on each sampling mode. On my machine it is stored as C:Program FilesGE FanucProficy HistorianDocsiHistorian.chm and I have version 3.5 installed. Pay particular attention to the following sections.

• Using the Historian OLE DB Provider
• Advanced Topics Retrieval

Ge Proficy Historian User Manual

Here is how you can construct an OLEDB to do trend sampling.

Showing the equivalent methods using the User API and the SDK are complex (more so with the User API) since they require a lot of plumbing in the code to get setup. The Client Access API is newer and uses WCF behind the scenes.

By the way, there are a few limitations with the OLEDB method though.

• Despite what the documentation says I have never been able to get native query parameters to work. That is a showstopper if you want to use it with SQL Server Reporting Services for example.
• You cannot write samples into the archive or in any way make changes to the Historian configuration including adding/changing tags, writing messages, etc.
• It can be a little slow in some cases.
• It has no provision for crosstabbing multiple tagnames into the columns and then carrying forward samples so that a value exists for each timestamp and tag combination. The trend sampling mode gets you halfway there, but still does not crosstab and does not actually load raw samples. Then again the User API and SDK cannot do this either.

A coworker of mine put this together:

In web.config:

In the data layer:

Update:

This worked well but we ran into an issue with tags that don't update very often. If the tag didn't update near the start or end of the requested startDate and endDate, the trends would look bad. Worse, still were cases where there were no explicit points during the window requested--we'd get no data back.

I resolved this by making three queries:

1. The previous value before the start-date
2. The points between startDate and endDate
3. The next value after the endDate

This is a potentially inefficient way to do it but It Works:

And yes, I know, those queries should be parameterized.

Michael--in IP21 there is an 'Interpolated' table, as well as the 'actual' data point table. Does Proficy have that as well?

I mean like this Fight of Characters 7.9s Fight of Characters 7.9o Fight of Characters 7.9k (is k stands for korean version?) Fight of Characters 7.9e (is e stands for english version?) Fight of Characters 7.9c Fight of Characters 7.9 can you help me?coz i've downloaded the bleach max 25 but i don't know what item to buy. Even no character name. Coz there's no word in there!

We wrote a wrapper DLL that looked like this like this:

Some notes are that iFIX will check if the DLL is loaded on startup so you need to do things like dynamically load/unload the DLL so that other applications don't crash. We did this by deleting/adding registry keys on the fly.

Another one is if you poll 10,000 samples and 1 of the samples are corrupted it will drop all 10,000 samples. You need to implement a bad data handler that will start at either side of the bad data and increment in steps to get all data either side of the bad sample.

There are several C header files that contain all of the error codes and the function header for the DLL.

Not the answer you're looking for? Browse other questions tagged c#oledbproficyhistorian or ask your own question.

The Historian Data Collector Manual is intended for people who need to install, use, and maintain data collectors in an Historian archiving system.

The following data collectors are supported with Historian:

For related information about Historian, refer to the following documents:

• Getting Started with Historian

• Using the Historian Administrator

• Using the Historian Excel Add-In

• Migrating Advanced and Classic Historian Data

• Using the Historian OLE DB Provider

• Historian Software Development Kit (SDK) Online Help System