You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hia,
So this has been talked about on here before.
It came up during some of the later work on 2.22. Where basically the hardware timer, just activates at entirely at the wrong time or skips a cycle. So it means the heater stays onto the start of the adc cycle (and corrupts the measurement).
At the moment the gui just filters these out mostly as a workaround as I gave up spending time trying to mask it from happening.
I haven't yet had any new ideas on the cause, really hope its actually a software init bug but havent found it
Describe the bug
Since the latest update I noticed live data occasionally spike to 400C
To Reproduce
You can also use this stand-alone script to get values directly:
Expected behavior
Temperature rising more-less gradually
Details of your device:
Additional context
I found it to be easier to reproduce if pinecil was in sleep mode right before activating.
The text was updated successfully, but these errors were encountered: