Update: PROBLEM IDENTIFIED AND SOLVED! After following the above routine for several days and re-reading the Davis Vantqge Pro 2 Console manual I noted it recommends the console not be located outside. Though my mine is located in my upstairs bedroom, away from the elements, it does get a bit chilly there. During winter months it can drop down into the upper 50s in my bedroom. So with that in mind I decided to inclose the console in a foam box with the lamp on to see if I could raise and stabilize the temperature of the console and it worked. I was able to keep the temp within the box between 72 and 66 degrees and the crashes stopped. This also explains why I could not bring the system back up till later in the day when the temps rose. Don't know if this is particular to my console or if all Davis consoles act this way but I will share this with Davis support. Yippie! Add this to the tool kit. Thanks everyone for you input and suggestions. On Saturday, January 29, 2022 at 2:56:30 PM UTC-10 Timothy Bryan wrote:
> Update: Since my last post, I tried making a wireless connection to my > WeatherLinkLive unit but could not get it to work. > > I have recently started running weewx again via the console and the > (faulty?) data logger. All works well for a while (about 12 hrs) then it > stops and I get a message saying weewx ‘can’t wake the console.’ As stated > above, I usually discover the failure upon waking. I then stop weewx then > start it again and again getting the same ‘can’t wake the console’ error > message. However, I have discovered that if I allow the pi and console/ > logger to sit (still powered up) for about 12hrs., then stop and start > weewx, it will work properly for about 12 hrs until the routine repeats > itself, back filling the data from the previous down time. This pattern > has repeated itself for 4 days. > On Saturday, January 15, 2022 at 1:57:19 PM UTC-10 Timothy Bryan wrote: > >> At this point after installing weewx on different Rpis on several >> occasions with the same results, like Vince I am fairly convinced the >> problem is with the logger and for now I'm going wait till I can swap it >> out and see if it makes a difference. If I'm lucky my friend will loan me >> an extra logger he has. Standby. I might also explore setting up weewx to >> take data from my WeatherLink Live device but from what I have read so far >> that could be an even deeper rabbit hole to dive into with my limited (but >> growing) knowledge base...At any rate I really appreciate everyone's help. >> Thank you so much! >> >> Aloha and Mahalo, >> >> Tim >> On Saturday, January 15, 2022 at 11:22:07 AM UTC-10 Greg Troxel wrote: >> >>> >>> Timothy Bryan <[email protected]> writes: >>> >>> > Addendum to last message. This just happened when I Stopped weewx then >>> > started it again. >>> >>> I see a lot of starting and stopping and it's really hard to separate >>> what happened before you did that, or if systemd did that by itself. >>> >>> I am suggesting that you change things so that: >>> >>> you are really really sure that only one thing is trying to read the >>> console >>> >>> systemd does not start and stop weewx >>> >>> nothing does anything about changing USB device attachment >>> >>> It may well be that your logger is broken. But there's a lot going on >>> in the logs that makes me suspicious. >>> >> -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/82d323ab-fa13-4162-b96e-afc9b8d9bfefn%40googlegroups.com.
