I found the solution to my large GPS offset. It turns out that I needed
to enable PPS signal processing in the GPS driver:
fudge 127.127.20.0 flag1 1
I had somehow gotten the misimpression that if I was using the separate PPS
driver (server 127.127.22.0), that meant I didn't need or want to deal with
PPS in the GPS driver. But no.
My "ntpq -p" output is much saner now:
remote refid st t when poll reach delay offset jitter
==============================================================================
oGPS_NMEA(0) .GPS. 9 l 6 8 377 0.000 -0.008 0.002
xPPS(0) .PPS. 8 l 3 8 377 0.000 -0.008 0.002
+liberation.rich 10.0.229.53 5 u 8 16 377 2.131 -5.080 3.003
+whodunit.richw. 10.0.229.114 4 u 12 16 376 2.325 -4.996 8.129
*iknow.richw.org 171.64.7.89 3 u 14 16 376 9.099 -6.797 8.415
I still seem to be several milliseconds different from the Stanford campus
time source; this is going to require further investigation.
--
Rich Wales / ri...@richw.org / ri...@stanford.edu
Wikipedia: http://en.wikipedia.org/wiki/User:Richwales
Facebook: http://www.facebook.com/richwales
_______________________________________________
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
