If you use timer functions to manage sample interval, it is possible to have 10ms jitter. Priority task is initiated every 10ms very accurately, but when code is executed within any given priority task interval can vary with position of the code in the task sequence and varying amount of time taken to complete each part of the task sequence from one interval to the next. So it is possible that sometimes you could have the ms timer saying something like 59ms when you would expect 60ms (because it's been 6 times through the 10ms task). In cases like this, you would wait for the next task (so 10ms later). I think it's safer to use a task interval counter and multiplying the counter by the task interval (10ms).
Why not just remove these? And, in fact, why do we even have this driver anymore? The conductivity sensor driver has P10 and P19 covered, pressuresensor has others covered and fpgaFP will have PCB temps covered I think and so what's left for this driver to read?
I see this component also being used in treatment adjustments (which do not have the extra rectangle) so best to discuss if we may make all the same or leave
