Hi, Nickolay Orekhov <[email protected]> wrote: > 2011/12/29 Nickolay Orekhov <[email protected]> > > Yes, you are right. Your system is synced with PPS and gets seconds from > NMEA. > You can set time1 to make NMEA offset closer to reality ( and to PPS ). >
Having NMEA offset close to zero, or leaving it at 350 ms, is there a difference how it affects the system clock if the pps pulse is working? > By the way, if you have only two clock sources, NMEA + PPS and offset > between them is bigger then "mindist" they > will be marked as falsetickers and there'll be no sync. > You might want to increase it by specifying: "tos mindist _value_" in your > ntp.conf. > > Default mindist is 0.001s, so as a wild guess, I can suppose that you set > your clock to "true" or already increased mindist or > you have another one source, NTP maybe, otherwise they will be > falsetickers. > You are right; I forgot to point that I have set clocks to "true", otherwise they would become falsetickers which now makes sense given the large offset NMEA+PPS are only sources are available. I'll try 'tos mindist' later and see what happens. Next thing to figure out is when I restart ntpd, the PPS offset goes back to -350 ms and ntpd starts adjusting it to zero (and NMEA offset goes up to ~350 ms. That seems to take hours. It looks like the system clock runs away as soon as ntpd stops. Tomi _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
