Surely that would not explain why nearly all the archive/WU records are timed at 10 minute intervals rather than the selected 5 minute interval. It looks almost as though, when there are possible delays in loop records being emitted, if 'the window when an archive should be taken' is missed because no loop or rec received an attempt is not made until the next record 'window' rather than when the next loop is received. ie loop records received outside a record creation 'window' do not trigger record creation. I am assuming that there is such a thing as an archive creation window somewhere within the bowels of weewx - the frequency is set in weewx.conf, but the window size/duration is fixed somewhere/somehow and I am guessing it is set to either 60 seconds or maybe 60 seconds-archive delay.
On Sunday, 16 October 2016 15:19:38 UTC+3, Tom Keffer wrote: > On Sat, Oct 15, 2016 at 7:38 PM, mwall <mw...@users.sourceforge.net > <javascript:>> wrote: > >> >> i'm stumped. >> >> > Me too. What do you think of my theory that the console is > (occasionally) waiting more than 5 minutes to emit a LOOP packet? > > -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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.