On Fri, Nov 9, 2012 at 8:59 PM, Adam Dosch <[email protected]> wrote: > All, > > I'm looking for some guidance on how to further troubleshoot an issue I've > seemingly always had with several Motorola Oncore UT/GT+ receiver modules > that I use for some hobbyist time keeping fun. From day one tinkering with > this receiver module, I don't think I've ever been successful in getting the > 1PPS source to not be a falseticker. [...] > remote refid st t when poll reach delay offset > jitter > LOCAL(0) .LOCL. 8 l 8h 64 0 0.000 0.000 > 0.000 > *GPS_ONCORE(0) .GPS. 0 l 8 16 377 0.000 -1.184 > 0.265 > xPPS(0) .PPS. 0 l 39 64 377 0.000 -1.121 > 0.045 > +nist1-lnk.binar .ACTS. 1 u 44 64 377 32.239 4.060 > 0.684 > +nisttime.carson .ACTS. 1 u 58 64 377 39.005 -3.028 > 0.245 > -nist1-chi.ustim .ACTS. 1 u 49 64 377 86.275 5.273 > 1.751
I would suggest removing the external S1 servers from the configuration to see if their relatively wide range of offsets is a contributing factor. If the PPS is still excluded as a falseticker. > ------------------------------- > ntp.conf > ------------------------------- > > ### Kernel PPS Selection > enable pps > pps /dev/oncore.pps.0 hardpps I believe both of the above lines are ignored by your recent 4.2.7 ntpd. There should be syntax errors in syslog at each ntpd startup confirming that. > > server 127.127.30.0 minpoll 6 > fudge 127.127.30.0 time1 0.1988 > > # shmpps (PPS refclock) > server 127.127.22.0 minpoll 6 > fudge 127.127.22.0 time1 0.00055 Like Mr. Taylor, I would also suggest minpoll 4 for both the Oncore and the PPS, and I note the # shmpps comment is out of date (it's the PPS/ATOM driver). Also, this isn't the best list for the discussion. If the above suggestions don't help, please consider posting to [email protected] a similar message describing the modified configuration as a starting point (no external servers, minpoll 4 on the refclocks). Cheers, Dave Hart _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
