3.2 System Time
3.2.3.3
Leap Second Correction Sequence
The following is the time sequence pattern in seconds that SecureSync will out-
put at UTC midnight on the scheduled day (Note: This is NOT local time midnight;
the local time at which the adjustment is made will depend on which Time Zone
you are located in).
A. Sequence of seconds output when
B. Sequence of seconds output when
3.2.3.4
Configuring a Leap Second
To manually correct the System Time for a leap second:
1. Navigate to
198
dition NTP does NOT indicate Leap Seconds. The Sync state indicates Leap
Seconds by indicating sync can be 00b, 01b, or 10b.
PTP Packets
provide leap indication with a 12-hour notification window.
Some
IRIG formats
provide leap second notification indicators.
Note:
It is the responsibility of the client software utilizing either the
Data Formats or NTP time stamps to correct for a Leap Second
occurrence. SecureSync will make the correction at the right time.
However, because computers and other systems may not utilize the
time every second, the Leap Second correction may be delayed until
the next scheduled interval, unless the software properly handles the
advance notice of a pending Leap Second and applies the correction
at the right time.
Second"):
56, 57, 58, 59, 60, 0, 1, 2, 3 ...
Second"):
56, 57,
58,
0, 1, 2, 3, 4 ...
MANAGEMENT> OTHER: Time
agement screen will be displayed. In the lower left-hand corner, the
Second Information
will be empty, unless:
a. A leap second is pending, and SecureSync has obtained this inform-
ation automatically from the GPS data stream.
adding a second
subtracting a second
panel will show if a leap second if pending. This panel
CHAPTER
("positive Leap
("negative Leap
Management. The Time Man-
•
3
SecureSync 2400 User Manual Rev. 5.2
Leap