The way weewx works, the driver blocks until a data packet is ready. Weewx cannot do anything else --- archive data, run reports, etc. --- until the packet is ready and the driver unblocks.
So, I suspect that your Observer is not offering up a data packet until 45 seconds or so after the top of the minute. None of this is affected by the archive delay. That's just a minimum delay, to make sure that reports are not run any earlier than after that delay. Of course, this is all theory. It would be easier to diagnose if you posted your log. -tk On Sun, Sep 4, 2016 at 4:51 PM, Louis De Lange <[email protected]> wrote: > I am running weewx on a FreeBSD box with a AmbientWeather Observer on > Interceptor driver very succesfully. > > I notice strange behaviour on the start timing of StdArchive - I have > archive delay set to the default of 15secs but according to the log the > StdArchive process triggers around 46 secs after the top of the minute, > approx 30 secs late. I checked the time setting on the server and it is > within 1 sec of the real time. > > One thing to note - the Interceptor driver ignores the loop packet time > from and instead timestamps the loop data with the current server time, but > I dont think this has any effect. > > Does anyone have any idea why StdArchive executes later than the > archive_delay setting would suggest > > -- > 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]. > 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
