|Re: [chrony-users] Setting up Chrony with PPS|
[ Thread Index |
| More chrony.tuxfamily.org/chrony-users Archives
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Setting up Chrony with PPS
- From: Deven Hickingbotham <devenh@xxxxxxxxxxx>
- Date: Mon, 11 Apr 2016 13:10:30 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pacbell.net; s=s2048; t=1460405418; bh=lR743WfRQkn6ZEqF/vACEM1x65AdfnuxLMygfk2P23Y=; h=Subject:References:To:From:Date:In-Reply-To:From:Subject; b=sClzKOV3JsiUgly7T+AVaylmEON1AONjcZVUIC2xaLdijHPNR79/x7Mgr6G6Gl8gdE0d0nC79Udg0KPxEHCbmKYUqXAFPLXs6P+W2WBVvksxQzyLPE2THmROSqxtlisDAWucco1p+9nLZ2AB8RNfkyw7T4H9uonDvhoEo079xx3WMz3p6uDvU+fr/ODMLLaRVZly5LtFAdk5zDhmjmi/Vgz2jY4F/jdjeFmmVWHl4I6mVyuS/2T1CcJi71E9mttXLVIjWWD2LAcTK/Ee8pkdbnQLaTS5xRjOnOpJ/53ohFKdhK88nxZzWSKH9Os9UgsX6IZ0YKnQ6T4UiGIPtwmduQ==
On 4/10/2016 11:30 PM, Miroslav Lichvar wrote:
Hm, did the configuration of the GPS change? Maybe it's giving fewer
NMEA sentences than before? It looks like the NMEA samples are now
~400 ms off from the expected offset and PPS can't lock to them.
You could try changing the SHM offset to 0.1 and maybe increase the
delay to 0.6 or so, but I'm not sure if that will be enough if the
NMEA offset is changing so much over time.
Yes, but I didn't expect that it would affect chrony. The update rate
was increased from 1 per second to 10 time per second (since this didn't
affect the PPS signal, I didn't expect it to impact chrony).
Changing the update rate back to 1 per second corrected the issue, but I
need an update rate of at least 5 per second (preferably 10).
Would it be correct to assume that different update rates require
different chrony offsets and delays? And if so, what values should I try?
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.