Cumulus Support

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?

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.

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

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.

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

And Steve - Thanks for the help

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.

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

Ah, OK.