Asle Frantzen

Filtering away "IO Timeout" for PI Point DR?

Discussion created by Asle Frantzen Champion on Jul 9, 2013
Latest reply on Jul 10, 2013 by rdavin

I'm stuck with a task where I need to filter away some "IO Timeout" in a PI Point Data Reference.

 

My initial idea was to use a Performance Equation tag and check for bad values there. If a bad value occured I'd just use the PrevVal(...) as value. But my client wants as much configuration as possible in AF, since that can be configured in the templates, which equals less work later when adding new equipment to the hierarchy. Now there's no problem detecting a bad value in AF, but the question is what to do when I find it.

 

So I did some tests to see if I was able to get the timestamp for the latest archive value / snapshot in AF, but with no luck. If I could get that I could use it as a relative time to another attribute, and configure that with TimeMethod=Before to get the last value, and keep using that.

 

 

 

So I'd like to hear if anyone would have any other suggestions for me, before going to the (perhaps) overkill step of creating a custom data reference for the job.

Outcomes