This morning after updating readings from my WS-1090, I got the above message. Cumulus reports all 0s for current readings. However, the console readings for both inside and outside data are there.
After spinning the console batteries,I checked the voltages and they all read more than 1.5 volts.
Has anyone seen this error before? (Current outised temp is -1.3 celsius.)
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
Error 32701, console battery 0V
-
daqddyo1
- Posts: 41
- Joined: Mon 05 Nov 2012 12:27 pm
- Weather Station: WS-1090
- Operating System: Windows7
- Location: Thornhill, ON Canada
Error 32701, console battery 0V
The truth is out there.
-
daqddyo1
- Posts: 41
- Joined: Mon 05 Nov 2012 12:27 pm
- Weather Station: WS-1090
- Operating System: Windows7
- Location: Thornhill, ON Canada
Re: Error 32701, console battery 0V
Yeah!!! Problem fixed.
I don't know how it happened but after reading the error message which included: "..check your settings", I saw that the console type had changed from easy offset to another type. when correcting this and restarting, everything worked again.
I don't know how it happened but after reading the error message which included: "..check your settings", I saw that the console type had changed from easy offset to another type. when correcting this and restarting, everything worked again.
The truth is out there.