[time-nuts] NTP, PPS and < 10 us offsets
Mark C. Stephens
marks at non-stop.com.au
Tue May 14 20:47:21 EDT 2013
You might find that questions at lists.ntp.org is a better place to ask.
Personally, I find the palisade driver breaks a whole lot of stuff when compiled in.
And I suspect the palisade refclock driver is no longer maintained.
I have better results using the ripencc driver for palisade varients.
From: time-nuts-bounces at febo.com [mailto:time-nuts-bounces at febo.com] On Behalf Of Miguel Barbosa Gonçalves
Sent: Wednesday, 15 May 2013 10:31 AM
To: Discussion of precise time and frequency measurement
Subject: [time-nuts] NTP, PPS and < 10 us offsets
I am trying to figure out why NTP takes so long to react to oscillator changes... I want it to track the PPS from a Trimble Acutime as closely as possible.
When checking ntptime on startup I see that the NTP daemon is using PLL and starts the adjustment interval at 8 s. It then increases to 16, 32, 64, 128 and stops at 256.
I read in the documentation that this limit should be 128 but is now 256.
--- start from http://www.ntp.org/ntpfaq/NTP-s-config-adv.htm --- intervals 57 says that there were 57 calibration intervals. When PPS pulses are arriving, this number should increase. Each frequency adjustment requires a good calibration interval. The length of the current calibration interval can be found as interval 128 s (128 seconds is the default maximum length). Remaining numbers count abnormal conditions as explained below.
--- end ---
How can I make it stop earlier? At 64 s for example?
time-nuts mailing list -- time-nuts at febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
More information about the time-nuts