>I want to calibrate the system clock on a number of embedded systems. To >measure the frequeny error, I'm looking for a method that only takes a >few hours.
>I'd prefer to use the frequency value that ntpd writes into the drift >file but my test (see URL above) showed too slow a convergence. I have >to add, I ran the test without the "iburst" server option so updating to >a new ntpd version that supports "iburst" will speed things up. What sort of accuracy are you expecting? The main contribution to changes in drift is temperature. Does your environment have a stable temperature? Are you calibrating your systems in the same location that you will be running them in? (Or calibrating them on a test bench and shipping them to a customer?) If there is any significant daily temperature changes, you will probably have to calibrate over a day or several. You might be able to work out a procedure to calibrate your calibration procedure to account for the current temperature. -- The suespammers.org mail server is located in California. So are all my other mailboxes. Please do not send unsolicited bulk e-mail or unsolicited commercial e-mail to my suespammers.org address or any of my other addresses. These are my opinions, not necessarily my employer's. I hate spam. _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
