nmea refclock not locking to the pps
Gary E. Miller
gem at rellim.com
Fri Mar 3 20:45:27 UTC 2017
Yo Tony!
On Fri, 3 Mar 2017 01:00:23 -0800
"Tony Hain" <tony at tndh.net> wrote:
> Not clear if this is an ntpsec issue, or comes from upstream, but the
> pps lock on the nmea stream never converges to a reasonable offset or
> apparently itself.
Fiar warning: I always recommend people not to use that refclok.
> # ntpd --version
> ntpd - NTP daemon program - Ver. 4.2.4p5
> # ntpd -V
> ntpd ntpsec-0.9.6+536 2017-02-22T20:26:50Z
That should be a good verion.
> oPPS(0) .PPS. 0 l 7 8 377 0.0000 0.0001
> 0.0001
> xNMEA(0) .GPS. 0 l 6 8 377 0.0000 -52.1062
> 1.4493
> *2001:470:e930:7 .GPS. 1 u 58 64 377 0.8173 -0.9772
> 1.9614
Clearly the PPS got outvoted.
You neglected the most important par of a bug report: your ntp.conf.
I'm guessing you do not have prefer set on your PPS? You'll also want to
set the mib- and max-poll on the PPS to much less than the for the nmea
driver.
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
gem at rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can’t measure it, you can’t improve it." - Lord Kelvin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 455 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ntpsec.org/pipermail/bugs/attachments/20170303/2eef5161/attachment.bin>
More information about the bugs
mailing list