
receivers must correctly implement the leap second at the proper time.
To configure a leap second for a scenario,
Select
the scenario, then navigate to the con-
figuration
View 2/3
:
Figure 4-6:
Leap Second field
Alternatively, the leap second can be configured in StudioView.
The leap second field can be set to -1, 0 or 1, and indicates a future change in the leap
second value. While
Δ
t
LS
is set automatically based on information in the used ephemeris
data, the value given in the leap second field will impact values related to L
SF
(Leap
Seconds Future).
When the leap second is set to a value other than zero
The following values will be used:
Δ
t
LSF
=
Δ
t
LS
+ value given in the leap second field
WN
LSF
= The GPS week number (8-bit representation) of the week holding the 30th of
June, or 31st of December, whichever comes first with respect to the scenario start time.
DN = Day number of the date described above.
When the leap second is set to zero
The following values will be used:
Δ
t
LSF
=
Δ
t
LS
,
WN
LSF
= WN
LS
– 1, and
DN = 1
Note that downloaded and default navigation data files do not contain any LSF information
(RINEX v2.1). Therefore it is still necessary to set the L
SF
when a leap second change will
occur, in order to ensure correct behavior. The default UTC/GPS offset—as of 2016—is
set to 17 seconds (it will be 18 seconds in 2017).
The four leap second almanac variables are:
WN
LSF
: Week number when the leap second becomes effective
4.8 Leap Second Configuration
User Manual GSG-5/6 Series Rev. 27
119
Summary of Contents for GSG-5 Series
Page 2: ......
Page 4: ...Blank page II User Manual GSG 5 6 Series...
Page 42: ...BLANK PAGE 2 5 Signal Power Level Considerations 26 User Manual GSG 5 6 Series Rev 27...
Page 382: ...BLANK PAGE 6 7 Revision History SCPI Guide 366 User Manual GSG 5 6 Series Rev 27...