Having then read through this forum I then reset the data logger in the Vantage console (removed all power, pulled the data logger out for 20 seconds, replaced and then powered back up) and all appears to be back up and running OK.
My first data logger lasted about 5 years before giving up on me, this one is about 3 years old, is this a sign that it's on its way out as well?
They're not cheap!
Thanks
Dave
--
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/9244ee2d-e630-4fd1-ae09-96e5815c52f8n%40googlegroups.com.
On May 8, 2022, at 2:02 PM, Tom Keffer <tke...@gmail.com> wrote:
Now that I think about it, there is an experiment I've been meaning to try. Right now, the Vantage driver tries 3 times, then gives up and restarts the program from the top.The experiment would be to do something not quite so drastic. Rather than restart the program, try a Vantage "wake up" sequence instead.I've never tried this strategy because there hasn't been a logger regularly showing this error that I could test. But it appears yours does. I'm tied up with something else, but give me a few days to come up with a solution.In the meantime, I've posted issue #772.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEDik39%2BLEOGTnrcMAtW3CorRJqUiGe_96iVFszAm53gbA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/D2A80355-C607-40DC-803C-813ACB968BB4%40johnkline.com.
--
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/ee068372-0940-41fb-bf94-1bacc9505b4en%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/2a464bfa-3671-43d0-89fe-1ed4c17d497en%40googlegroups.com.
I don't see why the patch would stop the "Expected 99, got 0" errors, just make them less traumatic.
For your find_rain_gust_day script, why not just use $month.rain.maxsum and $month.wind.maxtime?
Look in the template NOAA-%Y.txt.tmpl for clues on how to calculate all these things using tags.
--
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/d4d0e037-a7fa-482a-9620-cd2a9f9db9cfn%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/db79e989-3c2b-41d8-9c80-4442a5cd6007n%40googlegroups.com.
I don't know that it's a "timing issue," but it could certainly be a power issue.
The USB power supplies for many RPis can be barely adequate. In particular, the RPi 4 uses a lot of power. It doesn't take much for the power to sag, resulting in errors.
--
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/9d5bf73c-2c97-fd8b-6a14-06dfbeb751d3%40gmail.com.