| Re: [chrony-users] Re: Locking PPS refclock with NTP source |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Re: Locking PPS refclock with NTP source
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 29 Aug 2017 15:55:00 +0200
- Authentication-results: ext-mx05.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx05.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com DFB083295
On Tue, Aug 29, 2017 at 02:58:20PM +0200, Thibaut BEYLER wrote:
> Thanks, this is working indeed, but should i get good results (like, not
> more than a few of micros from my gps time) with these settings ?
You should get the same results as if the PPS refclock was locked to a
NMEA source for instance. The lock option is mainly useful to speed up
the initial synchronization and allow the noselect option to be
specified with the NMEA or other low quality refclocks.
> Right now it is locking on PPS (*) but my clock seem worse (offset to utc)
> than when using only the ntp server as source.
Can you please post the output of "chronyc -n -m sources sourcestats" ?
What hardware and what PPS driver (e.g. serial, gpio) do you use?
Typically, on a x86_64 machine with a GPS PPS and real serial port the
offset should be stable to a microsecond or better.
--
Miroslav Lichvar
--
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.