Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
When I tested the code I would get something inaccurate for the very first reading that I did immediately after boot--attributed this to garbage on ADC channel after boot. After that first reading I consistently saw ~91deg F and, as expected, I could watch it jump up when radio activity occurred.
I'm curious what the difference could be on your end. Keep me posted if you figure out what's going on. And let me know if I can help out at all.
I also saw something inaccurate for the first reading; so I looked at the second reading and it was also high but not as high as the first. I attribute this to MCU heating during a busy boot, maybe I'm wrong.
I'm getting 103 F but my target is in a warm location, so the combined heat could be matching yours, but probably both are higher than actual, maybe not, the die temp could really be that high.
I'm most interested in relative temperature change. So accuracy tuning has become a very low priority.