After the initial error with a large time difference the Davis console is "corrected" to the time of the Pi/weewx. I still get time adjustments, but they are much smaller. It's screwing up how data is viewed on the console with references to midnight: time of max/min T, Daily rainfall etc.
On Thursday, March 22, 2018 at 5:58:01 AM UTC-7, Tom Keffer wrote: > > What happens after 60 seconds? Does the same error occur? > > -tk > > On Thu, Mar 22, 2018 at 5:35 AM, Matt <matt...@gmail.com <javascript:>> > wrote: > >> I set the correct time on my Davis then restarted my weewx >> >> Mar 21 23:29:10 raspberrypi weewx[1746]: restx: StationRegistry: >> Registration not requested. >> Mar 21 23:29:10 raspberrypi weewx[1746]: restx: Wunderground-PWS: Data >> for station KCAMARIN10 will be posted >> Mar 21 23:29:10 raspberrypi weewx[1746]: restx: PWSweather: Posting not >> enabled. >> Mar 21 23:29:10 raspberrypi weewx[1746]: restx: CWOP: Data for station >> EW6666 will be posted >> Mar 21 23:29:10 raspberrypi weewx[1746]: restx: WOW: Posting not enabled. >> Mar 21 23:29:10 raspberrypi weewx[1746]: restx: AWEKAS: Posting not >> enabled. >> Mar 21 23:29:10 raspberrypi weewx[1746]: engine: Starting up weewx >> version 3.6.2 >> Mar 21 23:29:10 raspberrypi weewx[1746]: engine: Clock error is -25228.35 >> seconds (positive is fast) >> Mar 21 23:29:10 raspberrypi weewx[1746]: vantage: Clock set to 2018-03-21 >> 23:29:11 UTC (1521674951) >> Mar 21 23:29:11 raspberrypi weewx[1746]: engine: Starting main packet >> loop. >> Mar 21 23:29:15 raspberrypi weewx[1746]: vantage: LOOP try #1; error: >> Expected to read 99 chars; got 0 instead >> Mar 21 23:29:20 raspberrypi weewx[1746]: vantage: LOOP try #2; error: >> Expected to read 99 chars; got 0 instead >> Mar 21 23:29:30 raspberrypi weewx[1746]: vantage: LOOP try #3; error: >> Expected to read 99 chars; got 0 instead >> Mar 21 23:29:38 raspberrypi weewx[1746]: vantage: LOOP try #4; error: >> Expected to read 99 chars; got 0 instead >> Mar 21 23:29:38 raspberrypi weewx[1746]: vantage: LOOP max tries (4) >> exceeded. >> Mar 21 23:29:38 raspberrypi weewx[1746]: engine: Caught WeeWxIOError: Max >> tries exceeded while getting LOOP data. >> Mar 21 23:29:38 raspberrypi weewx[1746]: **** Waiting 60 seconds >> then retrying... >> >> >> On Tuesday, March 20, 2018 at 5:35:36 PM UTC-7, Matt wrote: >>> >>> Hi All, >>> I did a search on this forum regarding time problems, but didn't see any >>> answers to my question. >>> >>> Is it possible that WeeWx is changing the time on my Davis console? If >>> so, do I need to change one of the time sync settings or Vantage driver? >>> My weather data is making it to the web just fine, but my console time >>> keeps getting messed up. >>> >>> Thanks in advance >>> Matt >>> >> -- >> 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 <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
