Started when console was blocked from signal for a while by picture frame.
Running a VP1 with original Serial Logger and Ser/USB converter. It was flawless until now.
I was out of date on version when it started, I updated and it didn't fix it. The problem causes non existent solar readings when signal was blocked. That part cleared up.
https://youtu.be/HfABYLxcNqM
Welcome to the Cumulus Support forum.
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
Strange Temp gauge behavior
Moderator: mcrossley
-
mcrossley
- Posts: 14388
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Strange Temp gauge behavior
Please switch on debug and data logging then post the latest MXdiags file after 10 minutes.
-
davidmc36
- Posts: 2
- Joined: Mon 18 Jul 2022 7:16 pm
- Weather Station: Davis VP2 Plus
- Operating System: Windows 7
Re: Strange Temp gauge behavior
Sorry, I guess I missed the opportunity to inspect. The situation has gone away.
I will be sure and initiate logs before posting an issue.
My uneducated first guess is that filling data logs with "Clean" data at new day roll-over removed the problem.
Thank you for your attention and patience.
I will be sure and initiate logs before posting an issue.
My uneducated first guess is that filling data logs with "Clean" data at new day roll-over removed the problem.
Thank you for your attention and patience.