Udo van den Heuvel wrote: > If the commandline at http://time.qnan.org/ for shmpps really configures > for low-to-high (i.e.: rising edge) then why do I see -180+ ms offset > for my Garmin GPS 18 with rising edge configured? > > i.e.: > server 127.127.20.0 prefer > fudge 127.127.20.0 flag3 1 flag2 0 time1 0.000 > > > flag2 is 0 and there is no time offset compensation. > I see stuff like: > > remote refid st t when poll reach delay offset > jitter > ============================================================================== > 127.127.1.0 LOCAL(0) 10 l 45 64 377 0.000 0.000 > 0.004 > x127.127.20.0 .GPS. 0 l 14 16 377 0.000 -173.72 > 6.702 > (cut) > > This makes me wonder. It also makes me think that ntpd still triggers on > an edge that is allmost 200 ms off, the width of the pulse that I > configured. > So what is the correct way to tell ntpd what's going on? > Is there some peculiarity going on? > Or am I missing something obvious?
As extra info I can mention that so far only with a ntp.conf snippet of: server 127.127.20.0 prefer fudge 127.127.20.0 flag3 1 flag2 1 time1 0.200 (i.e.: high to low, falling edge *plus* 200 ms pulse compensation) I get GPS times that are close enough to the remote ntp servers' times. _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
