VP2+ on Firmware Version: 1.90, running Cumulus 1.9.2 Build 1032 startup was upgraded to Cumulus 1.9.3 Build 1057
startup now gets VP2: LoadCurrentVantageData_V, error = -32701
file attached
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
VP2+ Data Input Appears To Have Stopped
-
optrex
- Posts: 12
- Joined: Tue 16 Feb 2010 9:44 am
- Weather Station: OS 918
- Operating System: Linux with XP Virtualbox
VP2+ Data Input Appears To Have Stopped
You do not have the required permissions to view the files attached to this post.
-
steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: VP2+ Data Input Appears To Have Stopped
The Davis DLL is losing contact with the console, hence the -32701 error, which means "communication error". Unfortunately, that's the only information the DLL gives in this situation.
Is this a USB connection via a virtual serial port? Perhaps it's something to do with your Linux/VirtualBox setup? Could the port be getting powered off? The relevant code in Cumulus hasn't changed between 1.9.2 and 1.9.3, and it's the same Davis DLL.
Note that you have the logger interval in Cumulus set to 1 minute, and the station set to 5 minutes, so you are hitting this issue: http://wiki.sandaysoft.com/a/FAQ#Cumulu ... t_start_up
I think that's unlikely to be related to the communication problem.
Is this a USB connection via a virtual serial port? Perhaps it's something to do with your Linux/VirtualBox setup? Could the port be getting powered off? The relevant code in Cumulus hasn't changed between 1.9.2 and 1.9.3, and it's the same Davis DLL.
Note that you have the logger interval in Cumulus set to 1 minute, and the station set to 5 minutes, so you are hitting this issue: http://wiki.sandaysoft.com/a/FAQ#Cumulu ... t_start_up
I think that's unlikely to be related to the communication problem.
Steve