© MOBATIME
83 / 124
801203.10
8.8.3
Leap Second alert notification on DTS 4210 outputs
The DTS 4210 announce a pending leap second adjustment by the following methods:
-
NTP Packets
provides leap second indication within at least 1 hour before occurrence
-
PTP Packets
provides leap second indication within at least 1 hour before occurrence
-
Redundant link
provides leap second indication within at least 1 hour before
occurrence
-
DCF-Outputs
provides leap second indication within at least 1 hour before occurrence
8.8.4
Leap Second correction mode
A Leap Second will be inserted always in one step.
The sequence of dates of the UTC second markers will be as the following
(Example end of the year):
+1 Second
December 31, 23h 59m 59s
December 31, 23h 59m 59s
January 01, 00h 00m 00s
-1 Second
December 31, 23h 59m 57s
December 31, 23h 59m 58s
January 01, 00h 00m 00s
8.8.5
Leap Second Status indication
The DTS 4210 shows the following information about a leap second
-
Leap second status (no Leap Second planned, Leap Second pending)
-
Leap second time & date (if pending, otherwise none)
-
Leap second adjust direction (-1, +1, if pending)
-
Leap Second source (Manual, GNSS, Redundant-Link, PTP, DCF)
-
Time & date of last implemented Leap second (since the last reboot)
A Leap Second implementation is also logged in the dts log file (/var/log/dts.log) on the
device.
Please see chapter 7.6 how to make a ftp connection to the device.
Implementation in MOBA-NMS
