| Re: [chrony-users] Help with GPS timesync/config |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Help with GPS timesync/config
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 30 Mar 2020 09:45:32 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1585554340; 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: in-reply-to:in-reply-to:references:references; bh=E7b/XkdjFV3r2Gooa4Y0E4zOihKFJ/D/mSA+29j9kgs=; b=H8BsQ0woir9WaDZs2X4VhvArieg5QuK+3vbFrcz8rIiDXA5yTuxed7N/DlHaUpnGIJ5eUQ iLG1AKXmddqpiwTPum3ruhu7xF0kC3z00P0Lp15p9M7co7uWTGGaWCdskRchahmF3IAWNb n0XH2FMseIiizuA+buwt65FGKkE9sXE=
On Thu, Mar 26, 2020 at 12:41:07PM -0600, Dave Hajoglou wrote:
> =>If I remove the lock NEMA then the pps source is seen and processed and
> that's when I get the flapping where it selects first NEMA, the GPS refid
> then falls into the majority sync error. This is a weird one as it won't
> process the PPS if I lock it. Does that have to do with the fact that the
> PPS is from GPIO rather than serial?
That shouldn't matter, but what is important is the offset between the
two refclocks. If it's too large (close or over 0.4s) the locking
wouldn't work. Try adding "offset 0.25" to the SHM refclock line and
see if that helps. You can measure the offset of the SHM refclock
against an NTP server.
--
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.