AnsweredAssumed Answered

Analysis Recalculation ignores PI Point Compression settings

Question asked by ChristophRose on Jul 9, 2020
Latest reply on Jul 31, 2020 by sraposo

I had another post up asking about something related to this, but I keep constantly hitting this roadblock a million times and it is driving me mad. I simply can't believe that this is in any way working correctly or the way it is meant to be.

 

Let's take the example from this KB article create a saw tooth.

Create a new Analysis, with the expression:

DaySec('*')/60

and output it to a new PI Point. The trigger is set to periodically trigger every 10 minutes. I do not start the Analysis yet.

Just to be sure, the PI Point gets a "0" written to it sometime in the past, so that the current snapshot timestamp is from a long time ago.

Now I start the analysis and immediately recalculate the Analysis from 't' to '*'.

The result always looks something like this:

I do NOT get any Out of Order Snapshot or Archive events.

 

There seems to be no way to have the PI Point compression and exception settings applied to the results of a recalculated Anaylsis. Is this correct? Is this the way it's supposed to be?

 

I find this behaviour utterly baffling. Having to work around this behaviour is extremely time and effort intensive. I can't believe that I am the only one who is confronted by this behaviour of the PI System and finds it extremely irritating. The PI System can't be meant to work this way, can it?

Outcomes