Skip to content

Commit 90c2c8b

Browse files
committed
TELCODOCS#2019: Added a diagram to illustrate holdover in a T-GM clock
1 parent 2abcaa5 commit 90c2c8b

File tree

2 files changed

+19
-2
lines changed

2 files changed

+19
-2
lines changed

images/holdover_in_t_gm.png

59.1 KB
Loading

modules/nw-ptp-holdover-in-a-grandmaster-clock.adoc

Lines changed: 19 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
[id="holdover-in-a-grandmaster-clock_{context}"]
77
= Holdover in a grandmaster clock with GNSS as the source
88

9-
Holdover allows the grandmaster (T-GM) clock to maintain synchronization performance when the GNSS source is unavailable. During this period, the T-GM clock relies on its internal oscillator and holdover parameters to reduce timing disruptions.
9+
Holdover allows the grandmaster (T-GM) clock to maintain synchronization performance when the global navigation satellite system (GNSS) source is unavailable. During this period, the T-GM clock relies on its internal oscillator and holdover parameters to reduce timing disruptions.
1010

1111
You can define the holdover behavior by configuring the following holdover parameters in the `PTPConfig` custom resource (CR):
1212

@@ -37,5 +37,22 @@ The T-GM clock reaches the maximum offset in 60 seconds.
3737
3838
[NOTE]
3939
====
40-
The phase offset is converted from picoseconds to nanoseconds. As a result, the calculated phase offset during holdover is expressed in nanoseconds per second, and the resulting slope is measured in nanoseconds per second.
40+
The phase offset is converted from picoseconds to nanoseconds. As a result, the calculated phase offset during holdover is expressed in nanoseconds, and the resulting slope is expressed in nanoseconds per second.
4141
====
42+
43+
The following figure illustrates the holdover behavior in a T-GM clock with GNSS as the source:
44+
45+
.Holdover in a T-GM clock with GNSS as the source
46+
image::holdover_in_t_gm.png[Holdover in a T-GM clock with GNSS as the source]
47+
48+
image:darkcircle-1.png[20,20] The GNSS signal is lost, causing the T-GM clock to enter the `HOLDOVER` mode. The T-GM clock maintains time accuracy using its internal clock.
49+
50+
image:darkcircle-2.png[20,20] The GNSS signal is restored and the T-GM clock re-enters the `LOCKED` mode. When the GNSS signal is restored, the T-GM clock re-enters the `LOCKED` mode only after all dependent components in the synchronization chain, such as `ts2phc` offset, digital phase-locked loop (DPLL) phase offset, and GNSS offset, reach a stable `LOCKED` mode.
51+
52+
image:darkcircle-3.png[20,20] The GNSS signal is lost again, and the T-GM clock re-enters the `HOLDOVER` mode. The time error begins to increase.
53+
54+
image:darkcircle-4.png[20,20] The time error exceeds the `MaxInSpecOffset` threshold due to prolonged loss of traceability.
55+
56+
image:darkcircle-5.png[20,20] The GNSS signal is restored, and the T-GM clock resumes synchronization. The time error starts to decrease.
57+
58+
image:darkcircle-6.png[20,20] The time error decreases and falls back within the `MaxInSpecOffset` threshold.

0 commit comments

Comments
 (0)