How can we improve PI Connectors?

Retrieve data even it's not changed on OPC server

Currently Connector configured to rertieve event on change and not based on a scan class like interfaces.The Connector suscribes to the changes, and when a change comes in to the server, the data will be sent to PI connector. We need option to retrieve the data every certain minutes even data is the same and is not changed on OPC server.


33 votes
Sign in Sign in with OSIsoft
Signed in as (Sign out)

We’ll send you updates on this idea

Saken shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

We understand that for slow changing points, values might not change often and thus there is a need to collect values at certain time intervals as opposed to on change. However, scanning at frequent intervals leads to increased load on the server and thus can lead to performance degradation. We are discussing how best to solve this problem with PI Connector for OPC UA.


Sign in Sign in with OSIsoft
Signed in as (Sign out)
  • suyp commented  ·   ·  Flag as inappropriate

    If I understand this correctly, the solution provided by PI Connector for OPC UA version 1.3.x requires you to maintain a csv file with all your opc server tags. That is impossible when your opc server have over +100K tags.

  • Gabriel Michaud-Verreault commented  ·   ·  Flag as inappropriate

    This functionality is available in the PI Connector for OPC UA version 1.3.x - available on the Tech Support website. Look for DataChangeTrigger in the User Guide. It explains how to set a subset of tags to update everytime the timestamp updates. In conjunction with SamplingInterval, you can define the data retrieval rate, and when is the data going to be sent to PI.

  • ADRL commented  ·   ·  Flag as inappropriate

    This functionality is necessary for Industry, we had it using one concurrent product, I hope you will implement it asap.

  • David Benco commented  ·   ·  Flag as inappropriate

    Since it also has to do with unchanged data updates, allow "exception reporting" capabilities where a tag can mimic trend-like behaviors, which are useful for things such as Set Points.

Feedback and Knowledge Base

Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status