Eric S. Raymond
esr at thyrsus.com
Mon Nov 25 13:18:21 UTC 2019
Gary E. Miller via devel <devel at ntpsec.org>:
> I just took a quick look at refclock_ubx.c
> An interesting start, but followup messsages today on the list are
> assuming this driver does things that it does not do.
> 1) It does not, ever, config the u-blox. It does not, ever, write to
> the u-blox to query it.
> Configuration is up to the user.
> 2) It decodes UBX-TIM-TM2 (Current time) and UBX-TIM-TIMELS (for the
> leap second). Then does some limited sanity checking.
> It will fail to catch known u-blox time failure modes.
> 3) It does some interesting things with TIO that the comments claim
> improves the time stability. But it does not use KPPS which would
> just work better and simpler.
> Anything that uses KPPS will work much better.
> 4) It does not look at qErr, which combined with KPPS, might eventually,
> theoretically, lead to better time. When CPU time quantization gets better.
> In summary, not an improvement on current u-blox best practice. Maybe,
> eventually, an improvement, with some work (configuration, KPPS, etc.).
So there is nothing you recommend be merged at this time?
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: not available
More information about the devel