Forget this - I was looking at raw packet data instead of returned data.
On Sunday, 7 March 2021 at 6:57:47 pm UTC+10 Cameron D wrote: > For those who do not live in North America or Europe, the Oregon WMR300 > offers no correction to clock drift beyond manually prodding the console > touch-pad. > Mine drifts by about 90 seconds per year - not much, but enough to be > irritating. > Moreover, the loop packet data reports time only to the nearest minute, or > archive interval (not sure which, as my archive is 60 seconds). > I am proposing an option in the driver to ignore the console time and > simply use the system timestamp in loop packets, with a one second > resolution - this seems to be what the Davis driver uses. > Does anybody know of any potential problems if I do this? One I can see is > drift between time in the stored history and live database archive records, > but I am happy to live with this for my purposes. For those on a 300 second > archive interval it would be even less of a problem. > -- You received this message because you are subscribed to the Google Groups "weewx-development" 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-development/8ef254b9-2d99-4667-96b6-d3e87a77042fn%40googlegroups.com.
