On 12/21/2015 10:07 PM, Norton Allen
wrote:
On 12/21/2015 9:45 PM, Norton Allen wrote:
On 12/20/2015 3:46 AM, Hal Murray wrote:
Is there anything obvious I am missing in this setup?
Is there any more complete information I could provide that
would help?
I will continue to investigate on the ntpd end.
I switched the mode in ntp configuration from 1 to 0, and it's now
syncing using the "secondary device", 127.127.46.129.
This is giving me results like:
$ ./ntpq -p
remote refid st t when poll reach delay
offset jitter
==============================================================================
*GPSD_JSON(1) .GPSD. 0 l 14 64 7 0.000
10.091 16.467
GPSD_JSON(129) .GPSD. 0 l - 64 0 0.000
0.000 0.000
Pointing ntpd directly to /dev/pps1 now gives me:
$ ./ntpq -p
remote refid st t when poll reach delay
offset jitter
==============================================================================
xGPSD_JSON(1) .GPSD. 0 l 10 64 1 0.000
15.320 0.977
xPPS(1) .PPS. 0 l 9 64 1 0.000
432.069 0.977
So this at least suggests that ntpd is interpreting the PPS signal,
but the offset it pretty extreme. Any strategies for addressing
that?
|