Knocking the baud down to 9600 seems to have resolved whatever was causing those CRC issues. Looks like it's adding records.
Jan 8 17:54:07 MYSERVER weewx[1155]: vantage: Getting all archive packets Jan 8 17:54:07 MYSERVER weewx[1155]: vantage: gentle wake up of console successful Jan 8 17:54:07 MYSERVER weewx[1155]: vantage: Retrieving 11 page(s); starting index= 0 Jan 8 17:54:07 MYSERVER weewx[1155]: manager: added record 2016-01-07 16:30:00 EST (1452202200) to database 'weewx.sdb' Jan 8 17:54:07 MYSERVER weewx[1155]: manager: added record 2016-01-07 16:30:00 EST (1452202200) to daily summary in 'weewx .sdb' Jan 8 17:54:07 MYSERVER weewx[1155]: manager: added record 2016-01-07 17:00:00 EST (1452204000) to database 'weewx.sdb' Jan 8 17:54:07 MYSERVER weewx[1155]: manager: added record 2016-01-07 17:00:00 EST (1452204000) to daily summary in 'weewx .sdb' Jan 8 17:54:07 MYSERVER weewx[1155]: manager: added record 2016-01-07 17:30:00 EST (1452205800) to database 'weewx.sdb' Jan 8 17:54:07 MYSERVER weewx[1155]: manager: added record 2016-01-07 17:30:00 EST (1452205800) to daily summary in 'weewx .sdb' and so on. Well, interesting I suppose! Glad it's working! :) On Sunday, January 8, 2017 at 11:30:16 AM UTC-5, Jared wrote: > > Hi there, > > Just curious if anyone else has a similar setup and could offer some > pointers. > > My first weather station was an Acurite 5-in-1 hooked into the > WeatherDisplay software. Both pieces had their issues, and the Acurite > kept breaking, so now I've got a new Davis Vantage Vue with USB WeatherLink > device and I want to try out WeeWX. I don't have a dedicated server for > this, but I do have an Ubuntu VM which is up full time. The host is > running Windows 10 x64 version 1607, and it has correctly identified the > USB device as a "Silicon Labs CP210x USB to UART Bridge (COM3)". The > console is set to output at 19200 baud, and the Davis WeatherLink software > on the host sees the Vantage Vue console in serial mode on COM3 at 19200 > baud. So it's communicating on the Windows 10 host and serial seems to be > working. > > The VM is running Ubuntu Server 14.04.4 on VirtualBox. I have the Serial > Port specified as a "Host Device" on COM3, IRQ 4, I/O Port 0x3E8. The port > seems to be there and configured correctly, but I'm not sure data is > flowing. > > *setserial -a /dev/ttyS2* > returns: > > /dev/ttyS2, Line 2, UART: 16550A, Port: 0x03e8, IRQ: 4 > Baud_base: 19200, close_delay: 50, divisor: 0 > closing_wait: 3000 > Flags: spd_normal skip_test > > weewx.conf is configured to use /dev/ttyS2 at 19200, but /var/log/syslog > shows (this is with debug =1 in weewx.conf): > > Jan 8 10:44:18 MYSERVER weewx[1128]: vantage: driver version is 3.0.9 > Jan 8 10:44:18 MYSERVER weewx[1128]: vantage: Opened up serial port > /dev/ttyS2; baud 19200; timeout 4.00 > Jan 8 10:44:22 MYSERVER weewx[1128]: vantage: retry #0 failed > Jan 8 10:44:26 MYSERVER weewx[1128]: vantage: retry #1 failed > Jan 8 10:44:30 MYSERVER weewx[1128]: vantage: retry #2 failed > Jan 8 10:44:34 MYSERVER weewx[1128]: vantage: retry #3 failed > Jan 8 10:44:34 MYSERVER weewx[1128]: vantage: Unable to wake up console > Jan 8 10:44:34 MYSERVER weewx[1128]: import of driver failed: Unable to > wake up Vantage console (<class 'weewx.WakeupError'>) > Jan 8 10:44:34 MYSERVER weewx[1128]: engine: Unable to load driver: > Unable to wake up Vantage console > Jan 8 10:44:34 MYSERVER weewx[1128]: **** Exiting... > > Articles I've read said you should be able to use a command like *minicom > -b 19200 -D /dev/ttyS2* or *screen /dev/ttyS2 19200* and send a TEST > string to the serial port and it should return TEST back. That's not > happening in my case, so I think either the port is not configured > correctly, or this test is invalid for some reason (i.e., maybe that's not > how the Vue console connection works?). > > Any help would be appreciated. > > Thanks. > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
