• State Not Answered
  • Replies 5 replies
  • Subscribers 3 subscribers
  • Views 370 views
  • Users 0 members are here
Options
Related

Is there a better formula to get the max value?

Llegz

Currently we have this formula set up. It basically just gets the Max value of the 3 raw tags to get the count.
Current Formula to get the Max.png
Our issue is for some reason it doesn't match the count of the Raw tags and the Analysis tags.

Analysis tag count:
Analysis Tag Count.png
Raw tag count:
Raw tag Count.png
 

and also whenever I checked in Preview Result it gives me 348 count.

We have tried backfilling it and it works but it keeps on recurring so I don't think backfilling always would be efficient.

 

Can you guys help me or suggest what else can be done to get a more accurate readings.

Parents
  • 0

    Correct, in your case it shouldn’t make any difference.

     

    So, we’re running out of things to check now, but since you say a backfill always seems to fix the issue I would suggest that you could have out of order data coming into your three raw tags.

    Analyses will only trigger on new snapshot events. If any of your input tags have data with earlier timestamps than the current snapshot value, they will go directly to the archive. These events would then not trigger the calculation to run in normal runtime, but they will be included during backfills (since those are triggered by events already in the archive).

    What is the interface type your input values come from? You need to check how out of order data are processed, and you may also need to configure this in the system of origin (dcs/scada). At this point I’d say it’s probably better to open a support ticket with AVEVA to see what they recommend.

Reply
  • 0

    Correct, in your case it shouldn’t make any difference.

     

    So, we’re running out of things to check now, but since you say a backfill always seems to fix the issue I would suggest that you could have out of order data coming into your three raw tags.

    Analyses will only trigger on new snapshot events. If any of your input tags have data with earlier timestamps than the current snapshot value, they will go directly to the archive. These events would then not trigger the calculation to run in normal runtime, but they will be included during backfills (since those are triggered by events already in the archive).

    What is the interface type your input values come from? You need to check how out of order data are processed, and you may also need to configure this in the system of origin (dcs/scada). At this point I’d say it’s probably better to open a support ticket with AVEVA to see what they recommend.

Children
No Data