Does anyone have the same fault as my loop temperature code does?
Quite often, actually more often than not, the loop temperature reads 213.1 degrees, rather hot I think. Now I'm pretty sure the scrubber doesn't quite generate that amount of heat, so I have ruled that out.
So continuing to cycle through the menu numerous times and the error either :-
1. Repeats itself with a fixed series of numbers, some minor variations.
2. Sometimes new random numbers come up in the sequence.
3. Sometimes the error isn't there and the temperature reads fine.
Heres a typical sequence * is probably OK:-
213.1
129.0
196.1
26.5 *
213.1
26.5 *
213.1
129.0
196.1
26.5 *
213.1
129.0
26.6 *
91.1
32.8
0.4
198.6
193.0
26.5 *
It seems to depend on how slowly I scroll the menus as waiting a few seconds sometimes gets the actual temperature, there must be a timer in the code somewhere -- like resetting back to the root display.
Bringing back some ancient yet fond systems programming memories in a previous life, I would guess that some code is written into the memory where the sensor value would be stored? Hence the repeatable results.
Although I doubt whether its even worth repairing or feasible, I am a little concerned from the pov of verifaction/validation of the code that this sort of thing could be occuring in some other parts of the software.
The water temperature reads fine. 2.01 k and it happens above/below water and any time I can reproduce this.
I would post a photo, but the manage attach button doesn't work.