Welcome to the Cumulus Support forum.
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 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
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 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
Cumulus 1 to Cumulus MX Davis Vantage Pro2 Cannot Connect
Moderator: mcrossley
-
- Posts: 1
- Joined: Sat 13 Jan 2018 7:21 pm
- Weather Station: Daivs Vantage Pro2 Wireless
- Operating System: Windows 10
Cumulus 1 to Cumulus MX Davis Vantage Pro2 Cannot Connect
I am trying to move from Cumulus 1 (1.9.4) to CumulusMX (3043) and I can't get my Davis Vantage Pro2 to connect. CumulusMX throws the error cannot connect to station. But, Cumulus 1 works just fine. I tried with copying MX over Cumulus 1, I tried fresh CumulusMX with Cumulus 1 data copied over, and also just fresh CumulusMX install. The MX Diag file shows an issue with max baud rate. Attached is my latest diag log. Any ideas?
You do not have the required permissions to view the files attached to this post.
- steve
- Cumulus Author
- Posts: 26701
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Cumulus 1 to Cumulus MX Davis Vantage Pro2 Cannot Connect
Cumulus opens the port with a baud rate of 19200 bps but the system software is saying that the max your serial port can go is 10751. That sounds spurious and it probably needs setting correctly somehow - don’t know how you do that I’m afraid, Google may help.
Steve
-
- Posts: 4
- Joined: Fri 11 Jun 2010 10:08 pm
- Weather Station: Fine Offset
- Operating System: Windows XP SP3
Re: Cumulus 1 to Cumulus MX Davis Vantage Pro2 Cannot Connect
Hi
Im having the exact same problem. Davis Vantage Pro2 with USB link running with the USB to Serial driver.
Only my log file reports max BaudRate to 6644 and after reboot 10864.
/Frederik
Im having the exact same problem. Davis Vantage Pro2 with USB link running with the USB to Serial driver.
Only my log file reports max BaudRate to 6644 and after reboot 10864.
/Frederik
- steve
- Cumulus Author
- Posts: 26701
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Cumulus 1 to Cumulus MX Davis Vantage Pro2 Cannot Connect
You could try the latest drivers from Silicon Labs, might help. I think there’s a link in the FAQ if you don’t know how to find them.
Steve
-
- Posts: 4
- Joined: Fri 11 Jun 2010 10:08 pm
- Weather Station: Fine Offset
- Operating System: Windows XP SP3
Re: Cumulus 1 to Cumulus MX Davis Vantage Pro2 Cannot Connect
Hi
I all ready had latest driver from Silicon Labs installed and it worked with Cumulus v1, but not MX. Changing back to previous driver has solved the problem for me.
I followed this procedure (not sure if all steps are needed):
-Uninstalled driver v10.1.1 "CP210x_Universal_Windows_Driver v10.1.1" from installed "Apps". It is dated 2017-11-15 and for Win 10.
-Uninstalled the virtual COM3 port in "Device Manager".
-Disconnected Davis USB cable
-Installed driver v6.7.5 "CP210x_Windows_Drivers v6.7.5". It is dated 2017-10-13 and for Win 7..10.
-Reconnected Davis USB cable
For info i only tried the x64 drivers. You can check date/version of the current driver in "Device Manager".
Best Regards /Frederik
I all ready had latest driver from Silicon Labs installed and it worked with Cumulus v1, but not MX. Changing back to previous driver has solved the problem for me.
I followed this procedure (not sure if all steps are needed):
-Uninstalled driver v10.1.1 "CP210x_Universal_Windows_Driver v10.1.1" from installed "Apps". It is dated 2017-11-15 and for Win 10.
-Uninstalled the virtual COM3 port in "Device Manager".
-Disconnected Davis USB cable
-Installed driver v6.7.5 "CP210x_Windows_Drivers v6.7.5". It is dated 2017-10-13 and for Win 7..10.
-Reconnected Davis USB cable
For info i only tried the x64 drivers. You can check date/version of the current driver in "Device Manager".
Best Regards /Frederik
-
- Posts: 4
- Joined: Fri 11 Jun 2010 10:08 pm
- Weather Station: Fine Offset
- Operating System: Windows XP SP3
Re: Cumulus 1 to Cumulus MX Davis Vantage Pro2 Cannot Connect
And Steve - Thanks for the help
- steve
- Cumulus Author
- Posts: 26701
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Cumulus 1 to Cumulus MX Davis Vantage Pro2 Cannot Connect
I don’t think 6.7.5 is the previous version, it’s the latest version of a different driver. But hopefully this will be useful for anyone else with a similar problem.
Steve
-
- Posts: 4
- Joined: Fri 11 Jun 2010 10:08 pm
- Weather Station: Fine Offset
- Operating System: Windows XP SP3
Re: Cumulus 1 to Cumulus MX Davis Vantage Pro2 Cannot Connect
The release notes of v10.1.1 shows v6.7.5 as previous version with only this change:
MCUSW-134 | Fixed an issue with handling of IOCTL_SERIAL_SET_WAIT_MASK,
| IOCTL_SERIAL_WAIT_ON_MASK, with the SERIAL_EV_RXCHAR event
| and data arriving from the device into the driver. Previously,
| an indication of arriving data was made before making the data
| available, causing, in some conditions, subsequent requests for
| data after notification of data available to not deliver any data.
A little strange to jump from v6 to v10. Anyway step back worked for me.
/Frederik
MCUSW-134 | Fixed an issue with handling of IOCTL_SERIAL_SET_WAIT_MASK,
| IOCTL_SERIAL_WAIT_ON_MASK, with the SERIAL_EV_RXCHAR event
| and data arriving from the device into the driver. Previously,
| an indication of arriving data was made before making the data
| available, causing, in some conditions, subsequent requests for
| data after notification of data available to not deliver any data.
A little strange to jump from v6 to v10. Anyway step back worked for me.
/Frederik
You do not have the required permissions to view the files attached to this post.