[chrony-users] 'fallbackdrift' and temporarily connected ref-clocks |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-users] 'fallbackdrift' and temporarily connected ref-clocks
- From: simon@xxxxxxxxxxxxx
- Date: Fri, 17 Jul 2020 10:57:44 -0600
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mungewell.org; s=default; h=Content-Transfer-Encoding:Content-Type: Message-ID:Subject:To:From:Date:MIME-Version:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=vPdi94wUEayzKt4rPpezFubjI0YZieL7CpMTXi0G/P4=; b=NnvfO/+eSC0Q6OaIC1XpNQ9MIn Cozzc3yq+Cxi4b6EOicpngEzHeFKRV0Xk9e5Z2Pj1b7VzuNftX7vO2TkCmtDXZEKQ1c1nqthnoHqX LOZSRAiXg1DzaKEqxl+mOmLZkfvSwN55C4lZzsxuN28x5fr/IwZNc4gETyX4jpNomqJ5izuDaXkVh x4l6EuVtp05yqGm4Pgv0Um8MOZvxjm5Ny2iUwuy/GjRMiARBpRsudEtmz6xrZuMLJDrCv3yqHLtHU C88U9idOfP0zY3lCe7cS2go5slfab5/dAvEP61gCEzmf35JDMYv7kcSEcW/9GRohy1RmwLLFJfTmG 2PehRh/Q==;
I am experimenting building a DIY SMTPE TimeCode system, based around
Chrony and libLTC.
An external TimeCode generator would be temporarily connected as 'LTC'
(previously connected long enough to build good drift files) and local
time would be 'JamSynced'. Once the generator is removed local time
would freewheel, maintained by Chrony's drift calculations.
The TimeCode is injected via SHM, 'chrony.conf' reads
--
local stratum 10 orphan
fallbackdrift 6 7
log refclocks
refclock SHM 0:perm=0666 trust refid LTC
refclock SHM 1:perm=0666 noselect refid MON
--
Note: I have set a 2nd source 'MON' so that I can monitor drift after
'LTC' has been removed.
I am confused about 'fallbackdrift'; if my understanding is correct the
above will cause the real time drift corrections from 'LTC' will be
dropped between 16s and 32s.
Q. Is this understanding correct?
Q. Is there a better way to handled a disappearing ref-clock?
From looking at the refclock logs of a trial run, at the point of
removal I see:
--
2020-07-16 23:13:20.001717 LTC 0 N 0 -1.958000e-03 -1.717746e-03
3.700e-08
2020-07-16 23:13:21.000135 LTC 1 N 0 -3.720000e-04 -1.357082e-04
3.700e-08
2020-07-16 23:15:34.191050 MON 6 N 0 -1.910500e-01 -1.910500e-01
3.700e-08
2020-07-16 23:15:35.003651 MON 7 N 0 -3.651000e-03 -3.651003e-03
3.700e-08
2020-07-16 23:15:36.002157 MON 8 N 0 -2.157000e-03 -2.157003e-03
3.700e-08
--
And using 'Chronyc/sources' I can confim that 'LTC' is dropped, '*'
changes to '?' and my reported Stratum drops to '10'.
--
chronyc> sources
210 Number of sources = 2
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
#* LTC 0 4 360 86 +61us[ +405us] +/-
1223us
#? MON 0 4 0 - +0ns[ +0ns] +/-
0ns
chronyc> sources
210 Number of sources = 2
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
#? LTC 0 4 0 147 +61us[ +405us] +/-
1223us
#? MON 0 4 0 - +0ns[ +0ns] +/-
0ns
chronyc> tracking
Reference ID : 7F7F0101 ()
Stratum : 10
Ref time (UTC) : Thu Jul 16 23:15:49 2020
--
Q. Is there a (better?) way to confirm drift compensation source?
Some (considerable) time later, I can see that local time has drifted
off.
--
2020-07-17 15:08:17.129213 MON 1 N 0 -1.292130e-01 -1.292133e-01
3.700e-08
2020-07-17 15:08:18.127694 MON 2 N 0 -1.276940e-01 -1.276943e-01
3.700e-08
2020-07-17 15:08:19.126076 MON 3 N 0 -1.260760e-01 -1.260763e-01
3.700e-08
2020-07-17 15:08:20.124516 MON 4 N 0 -1.245160e-01 -1.245163e-01
3.700e-08
2020-07-17 15:08:21.123108 MON 5 N 0 -1.231080e-01 -1.231083e-01
3.700e-08
2020-07-17 15:08:22.121534 MON 6 N 0 -1.215340e-01 -1.215343e-01
3.700e-08
--
Cheers,
Simon.
--
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.