[chrony-users] refclock local with OCXO |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-users] refclock local with OCXO
- From: Stephanie Wilde-Hobbs <hi@xxxxxxxxxxxx>
- Date: Wed, 28 Jun 2023 19:31:29 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stephanie.is; s=key1; t=1687973490; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=cGKK1ALba/ceXjdm5iGRG2D360NxertUVMQUzVRb70A=; b=jM0nFO7V+wrfQawIGkqFGTiDrLGy0ZgDjYk7T4mP9e9ofxRG207DPHoL8Ygxs/RxlFj7pf 12AHGazal9Xi29IHhF5yrcC3HL1/UmZF3rZ5pW6pqUJEcsTCbcZrEDYvmEYvgrzMlEx5oS GdXlQ8wkeV2P5QgrZAXr5L8tId3HEW91aTtbLBMvjIx6JiupPvyccm1JuwxWDmhutW8fbZ FLuvx+HThvKLKr8mu/xdeyQ0vQ1T5U3Vyq1SJ8WT09aD2mPJ9wMW3xZ+l76EsENkvD+6hP jYRog1K8UfZ/6M8Kn3WhSw18aiyrBgAT93SlasUMDg1ZM0XCFt5pBLMZubBm8A==
Hi,
I am working on accurate timekeeping for a machine which would be
difficult to get GPS signal to, and I want to ask a few questions about
using an OCXO as a PPS source. As I understand it from the
documentation, this should be possible by configuring a PPS refclock
(for example on an i210) and then setting the `local` attribute.
However an OCXO is fundamentally different from the other refclocks as
it will have a small frequency error in one direction causing the phase
of the PPS signal to wander, whereas a GPSDO should always have the same
phase relative to UTC. Before buying hardware I want to make sure: will
chrony will measure and correct for the frequency error and long-term
drift in the OCXO using connected NTP servers? If so, how will I monitor
this frequency error to make sure the process is happening properly?
Thanks,
Stephanie.
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.