Yo Mike! `
On Sun, 19 Jun 2016 15:59:16 -0400 Mike <[email protected]> wrote: > On 06/10/2016 03:17 PM, Gary E. Miller wrote: > > Yo Eric! > > > > On Fri, 10 Jun 2016 03:49:22 -0400 > > "Eric S. Raymond" <[email protected]> wrote: > > > >> That's... very weird. I've never seen it happen. > > But it would explain some old complaints. > > > > Now that we know which Skytraq option it is, I recall always > > selecting the workaround. > > > >> It sounds as though for some crazy reason the GPS is delivering the > >> PPS pulse late. > > Not late, as such. Late in the second, but the time stamp of the > > fix (xxX.940) is pretty close to when actually sent. > > > >> I'm hard put to imagine how gpsmon could screw this up. > > Or Hal with his O-scope. > > > > RGDS > > GARY > I'm seeing this happen now, PPS is good NMEA is off nearly half a > sec... NMEA delivery viewed in gpsmon is 0.011 after top of second. > > *SHM(1) .PPS. 0 l 10 16 377 0.000 -0.002 0.004 > -SHM(0) .GPS. 0 l 9 16 377 0.000 -496.59 6.661 Looking good. Now add a 0.500 fudge to your ntp.conf. Like this: server 127.127.28.0 fudge 127.127.28.0 time1 0.500 refid GPS What do your other chimers in 'ntpq -p show'? Youu still have not confirmmed which PPS edge you are on. The leading or trailing. RGDS GARY --------------------------------------------------------------------------- Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703 [email protected] Tel:+1 541 382 8588
pgpX5PvN9vzuV.pgp
Description: OpenPGP digital signature
_______________________________________________ devel mailing list [email protected] http://lists.ntpsec.org/mailman/listinfo/devel
