AnsweredAssumed Answered

Setpoint Tags that hardley ever change go BAD until I force a read.

Question asked by pegentry on Oct 31, 2018
Latest reply on Nov 5, 2018 by jyi

We have some setpoints that hardly ever change that they want as tags, they keep on going BAD until I click my client tool and read it, then it shows up with updated value and timestamp.

Any knowledge on the best way to handle these?

I've set compression and exception like below, thinking it would at least log a value every 8 hours, but it goes BAD before that:

 

       

compressingcompdevcompmaxcompmincompdevpercentexcdevexcmaxexcminexcdevpercent
002880000060000

Outcomes