Re: Reading time offset from ntp variables using ntpq

In article <N8GdnTnGn4MPC2nenZ2dnUVZ_s6dnZ2d@xxxxxxxxxxx>,
Richard B. Gilbert <rgilbert88@xxxxxxxxxxx> wrote:

The four timestamps are:
Reference: the time the local clock was last set. (This makes no sense
to me but that's what the RFC says! It would make more sense if it were
the time the reply was received by the client.)

Reference time is the time on the *server* when the last change in best
offset measurement happened. It can be relatively far in the past and is
useless for the current purpose. It is not a time on the local machine.

Originate: the time the request packet left your system
Receive: the time the request packet arrived at the server
Transmit: the time the reply packet departed the server

The measurement takes a finite time to make (delay I think, but it might
be twice delay). Basically it takes between Originate and Originate + delay
(the client receive time isn't recorded here). Therefore you cannot state
one specific time at which the measurement was made. Using any of the
latter 3 should be OK as long as you always use the same one. Note that,
as the clock isn't being disciplined, Originate may differ drastically
from Receive and Transmit (i.e. by offset).

I think you asked how I measured the standing frequency error to calibrate
to 30 seconds a year. At the time, the office didn't have internet
access, so I used a radio controlled wristwatch and ran the command
"netdate localhost" on an exact second. To get the exact second, I typed
all of the command except for the carriage return, then got my finger
tapping lightly in time with the seconds, and, once I had the rhythm, did
one final hard tap. That seemed to be repeatable to better than 100ms.
(I think I first forced the watch to update.)

The final fine tuning was done over about a week. I'd now do ntpdate
over a baseline of about a week. In that case, I then set the drift
value, so subsequent calibrations were of the residual error. Nowadays,
I use ntptime, to set the kernel parameters, and don't run ntpd at all.
When I'm correcting phase, I make sure my modem is idle before issuing
the ntpdate command. I don't use ntpd in one shot mode because I don't
want the frequency disturbed.
.

Relevant Pages

  • Re: New impoved facts part 1v03
    ... >> relative to any inertial reference system. ... > will be zero wrt to the SOS but it may need stating in wrt a passing bus ... "the SOL" is defined as I explained above and that's why I ... > Yes I am familiar with the method of measurement of the SOL by Fizeau but ...
    (sci.physics.relativity)
  • Re: Measurement of pitch
    ... measurement of the frequency of a sound wave, ... of these reference units in the quantity to be measured. ... vibrating string seems as good as anything. ... This is what the Pythagoreans had. ...
    (sci.physics)
  • Re: Wa tis "imaginary signal" in "physical reality" context was [Re: Conversion of data to complex n
    ... I'm also afraid that engaging in this thread is to go slumming intellectually. ... I think the idea of an instantaneous measurement isn't really to the point here. ... By that, I don't mean there isn't a time scale or time base but, rather, there is no point in time that is identified as a *reference* point in time. ... I suppose that one could provide a time base as a dimension reference and say that frequency is a dimension - we just don't usually talk in those terms. ...
    (comp.dsp)
  • Re: Download a new book on quantum mechanics and relativity.
    ... > interactions is defined by lorentz transforms that define the geometry ... > a reference tick rate or a standard measure of distance. ... >>by a single eigenvalue of the Casimir operator of mass. ... > directly conflict with what your theory defines as measurement. ...
    (sci.physics.relativity)
  • Re: Reading time offset from ntp variables using ntpq
    ... Type the command except the CR. ... Listen to WWV and swiggle the second finger to the tick. ... The measurement takes a finite time to make (delay I think, ... Basically it takes between Originate and Originate + delay ...
    (comp.protocols.time.ntp)
Loading