Hi Dave! 2011/10/14 Dave Hart <[email protected]>: >> tock# ntpq -p >> remote refid st t when poll reach delay offset jitter >> ============================================================================== >> oGPS_NMEA(0) .GPS. 0 l 6 16 377 0.000 -0.001 >> 0.003 >> +ntp-p1.obspm.fr .TS-3. 1 u 6 64 377 44.396 0.860 >> 1.342 >> +ptbtime1.ptb.de .PTB. 1 u 34 64 377 68.039 2.179 >> 0.698 >> -ntp1.oma.be .PPS. 1 u 43 64 377 52.612 4.312 >> 0.819 >> *canon.inria.fr .GPSi. 1 u 60 64 377 44.358 1.177 >> 0.902 >> -ntp1.nl.uu.net .PPS. 1 u 49 64 377 57.991 3.550 >> 0.989 > > The first one is configured with NMEA with PPS enabled. The second > one is configured with NMEA with PPS disabled, and also with the > PPS/atom driver. I have a system configured similarly to your first, > with the only refclock source NMEA with PPS enabled, running > 4.2.7p214. It shows the 'o' pps peer tally code for NMEA, and has no > association with the * sys peer tally code -- the LAN sources are all > marked with + or space tally codes. Are you using "prefer" in the > ntp.conf for the first one?
This is the configuration for the first one # PPS & NMEA server 127.127.20.0 mode 18 prefer minpoll 4 maxpoll 4 fudge 127.127.20.0 flag1 1 flag2 0 flag3 1 time2 0.400 The other machine has # NMEA only server 127.127.20.0 mode 2 prefer minpoll 4 maxpoll 4 iburst fudge 127.127.20.0 time2 0.315 flag1 0 flag4 1 # PPS (PPS in kernel) server 127.127.22.0 minpoll 4 maxpoll 4 # This is for kernel PPS fudge 127.127.22.0 flag2 0 flag3 1 Many thanks! Cheers, Miguel _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
