Periodic incorrect date from a Davis Vantage Pro 2

[P Black]

Hello,

I am in the process of migrating from wview to weewx.  Yes I know I am very late to the game.

The issue I have with wview is that the Davis Vantage Pro 2 periodically generates a future date that then hangs any further data collection.  The fix usually involves:

 sudo service wview stop

 vpconfig /dev/ttyUSB0 cleararchive

remove the bad data from the sqlite and mysql databases

 sudo service wview start

Then if I am late to catch this issue, I have a lot of missing data.

I plan to start installing weewx in the next few days on a raspberry pi 5 with a 1TB NVMe and run using the mysql (mariadb) database choice after migrating my existing database to the new setup.

Assuming that the date issue is a Davis glitch and not wview, is there a software check in weewx to determine if the date is wrong and either delete the data for that time or correct it to the correct time and then log?  I assume that the clear archive would also have to be automatically performed (how is that done by software)

PS: I have tried the usual shutdown the Davis, remove batteries and still the bad date occasionally occurs.  The Davis is the wireless version purchased 2011.  Also, it must know when I am not around as the bad event occurs during my away times.

Stay healthy,

Pat

[Tom Keffer]

I have never seen the Vantage emit a bad date. What does happen is either

1. The computer lacks a clock, so it synchronizes the Vantage to the wrong time. There is a check in WeeWX to avoid starting up with a clock that's really off, but the best protection is to install a real-time clock in the computer.

2. The logger memory gets corrupted. This is pretty rare, but seems to be triggered by power outages (although not always). The symptom is that WeeWX fails to download any new data, so your webpage doesn't change. See the Wiki article Wiki generates HTML pages, but does not update them for details. This sounds the closest to the situation you describe, but with WeeWX it does not result in a record being downloaded with a bad date. Perhaps wview does something different in this situation. The problem can always be solved by clearing the logger memory. If you do a memory dump first, it does not result in loss of data.

Hope that answers your question.

--
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/fe2e2e08-bf5b-4da4-a511-7926ede968afn%40googlegroups.com.

[P Black]

Tom,

Thank you.  It gives me some hope that the time warp will not be an issue with the new system.  The old used a Raspberry PI 3B with an added clock and the new is a RP5 with built-in clock.  I do use a battery backup and have not noticed any correlation to voltage drops and the date mix-up.  Should have some time in the next couple weeks to load the software and begin transitioning the database.

Thanks,

Pat

[Tom Keffer]

Be sure to read the wiki notes on Moving the wview database.

Welcome to WeeWX! You may be the last of the wview users!

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/0ba660b1-cb93-4efb-aeb8-189a7266aa6dn%40googlegroups.com.

[P Black]

All,

Weewx has been running great after the transition from my previous software.  It too though experienced a periodic crash due to a future date occurrence from the Davis Pro2.

After several months of being too busy to really look at the system, I finally got around to viewing reports and find there has been no future date crashes.  The only changes to my setup since the porting to weewx were the replacement of the anemometer hardware and the temperature/humidity board.  If it continues to work well, then that future date glitch appears to be caused by some combination of those bad hardware add-ons.

Stay healthy,

Pat