duck
duck

Reputation: 186

Why data does not refresh the same way between OSIsoft PI Processbook & PI DataLink?

I'm checking for one PI tag in Datalink & in Processbook. In Datalink I see Compressed Data interrupted few hours ago, in Processbook for the same PI tag I see continuous trend, which looks normal.

I thought the both tools should show the results for the same tags.

Why are they giving different results?

Upvotes: 2

Views: 1857

Answers (2)

Zhengqi Ge
Zhengqi Ge

Reputation: 11

In short, PI ProcessBook caches data from PI snapshot, while DataLink does not.

PI ProcessBook trends update data from snapshot in real time and cache them at the client, so when the archive is somehow interrupted, the client won't be affected unless you hit refresh, which clears the client side cache and pulls data all over again from server archive(for history) & snapshot(for current value).

PI DataLink retrieves data from archive each time you calculate the spreadsheet. It does not cache snapshot values over time to create a history data record or trend. That's the main reason you are seeing this difference between PB and DL.

You could also contact OSIsoft (now part of AVEVA) techsupport for help.

Upvotes: 0

codea
codea

Reputation: 1561

There can be many rasons. What comes to my mind here is that there is an automatic update mecanism in PI ProcessBook, with PI DataLink you need to manually refresh the content.

So for example if the data collection had an issue (e.g. network outage) for many hours and the data was buffered on an interface or a connector node, when the data will flow in the system after network is back then PI Processbook will show changes right away, this is not the case for PI DataLink, it will require a manual refresh of the data in Excel with the PI Datalink Add In.

Upvotes: 2

Related Questions