On 2014-01-03, David Taylor <[email protected]> wrote: > On 03/01/2014 10:36, Ralph Aichinger wrote: >> Steve Kostecke <[email protected]> wrote: >>> In my experience the NMEA driver displays the '*' talley-code even when >>> PPS is in use. >> >> Mine does not: >> >> remote refid st t when poll reach delay offset jitter >> ============================================================= >> oGPS_NMEA(0) .NMEA. 0 l 13 16 377 0.000 0.000 0.002 >> +bevtime1.me .ATOM. 1 u - 64 337 18.300 1.845 0.649 >> *ts2.univie. .PPS. 1 u 48 64 377 12.073 1.952 0.577 >> +ntp.liwest. 131.188. 2 u 26 64 377 8.482 0.554 1.875 >> >> (ntpd 4.2.6p5) > > Yes, it seems to have been an error in some recent development versions, > but fixed in 4.2.7p408 > > http://bugs.ntp.org/show_bug.cgi?id=2529
For many years I ran a Soekris NET-4801 with a Garmin GPS-18LVC (all of that hardware is currently in storage). It ran FreeBSD 5.3 and an older version of NTP. It _never_ displayed a 'o' for PPS. The only way that you could tell if PPS was being used was to watch the offset/jitter. So this is not just an issue with recent development versions. -- Steve Kostecke <[email protected]> NTP Public Services Project - http://support.ntp.org/ _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
