Vantage Pro suddenly stopped working

[Kevin Smolkowski]

After years and years, at 3am the other morning my Vantage Pro stopped posting to CWOP.    I've done all the usual, reboot PC, replace the USB-Serial cable, still nothing.   Not sure how else to troubleshoot, the logs "look like" it's reading data from the unit.   Any help appreciated.

Mar 16 07:04:27 pvweatherbox weewx[7369] INFO __main__: Starting up weewx version 4.1.0

Mar 16 07:04:27 pvweatherbox weewx[7369] DEBUG weewx.manager: Daily summary version is 2.0

Mar 16 07:04:27 pvweatherbox weewx[7369] DEBUG weewx.drivers.vantage: Gentle wake up of console successful

Mar 16 07:04:27 pvweatherbox weewx[7369] INFO weewx.engine: Clock error is 0.13 seconds (positive is fast)

Mar 16 07:04:27 pvweatherbox weewx[7369] INFO weewx.engine: Using binding 'wx_binding' to database 'weewx.sdb'

Mar 16 07:04:27 pvweatherbox weewx[7369] INFO weewx.manager: Starting backfill of daily summaries

Mar 16 07:04:27 pvweatherbox weewx[7369] DEBUG weewx.drivers.vantage: Getting archive packets since 2021-03-14 03:00:00 PDT (1615716000)

Mar 16 07:04:27 pvweatherbox weewx[7369] DEBUG weewx.drivers.vantage: Gentle wake up of console successful

Mar 16 07:04:29 pvweatherbox weewx[7369] DEBUG weewx.drivers.vantage: Retrieving 513 page(s); starting index= 1

Mar 16 07:04:29 pvweatherbox weewx[7369] DEBUG weewx.drivers.vantage: DMPAFT complete: page timestamp 2021-02-26 11:30:00 PST (1614367800) less than final timestamp 2021-03-14 03:00:00 PDT (1615716000)

Mar 16 07:04:29 pvweatherbox weewx[7369] DEBUG weewx.drivers.vantage: Catch up complete.

Mar 16 07:04:29 pvweatherbox weewx[7369] INFO weewx.engine: Starting main packet loop.

Mar 16 07:04:29 pvweatherbox weewx[7369] DEBUG weewx.drivers.vantage: Gentle wake up of console successful

Mar 16 07:04:29 pvweatherbox weewx[7369] DEBUG weewx.drivers.vantage: Requesting 200 LOOP packets.

Mar 16 07:04:29 pvweatherbox weewx[7369] DEBUG weewx.drivers.vantage: Gentle wake up of console successful

[gjr80]

Hi,

I suggest you edit weewx.conf, set debug = 2, save weewx.conf and restart WeeWX. Let WeeWX run for a few archive periods and then take an extract from the log covering the entire WeeWX startup through until the few archive periods have passed. It’s important to get the entire startup sequence as it has important config info. Post the log extract here and we can see exactly what is (or is not) happening. If you need help obtaining and posting the log extract you might find the Help! posting to weewx-user wiki article helpful.

Gary

[Tom Keffer]

No need. This is pretty clearly a case of memory corruption on the logger. The clue is

Mar 16 07:04:29 pvweatherbox weewx[7369] DEBUG weewx.drivers.vantage: Retrieving 513 page(s); starting index= 1

Mar 16 07:04:29 pvweatherbox weewx[7369] DEBUG weewx.drivers.vantage: DMPAFT complete: page timestamp 2021-02-26 11:30:00 PST (1614367800) less than final timestamp 2021-03-14 03:00:00 PDT (1615716000)

It asks for 513 pages, then proceeds to get ... nothing.

See the section Corrupt station memory for how to clear the logger.

-tk

--
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 weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/7790cbaa-9f25-4091-bee8-f721cd363b6fn%40googlegroups.com.

[Paul R Anderson]

Per Tom's answer of Corrupt station memory...

You mentioned issue began at " 3 A.M.  the other morning" Daylight Saving Time in most of the US began on Sunday, March 14, 2021 at 2:00 A.M wonder if some weird issue may have happen due when your system clock jumping forward. Note that normally WeeWX handles this just fine :) 

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEDBDM-FrhM03_TSnktyoqhbZ9G1HivDGdqvJAYR5pweAg%40mail.gmail.com.

[Kevin Smolkowski]

It was odd that it happened right at 3AM,   but thanks to you all I have it working again.  I dumped the memory and cleared it and that seems to have fixed it all up.