
satellites use the
scenario
keyword. Events which apply to a specific satellite indicate
this by specifying
channel NUMBER
or
prn SATID
values. For relpower and abspower
events, it is possible to apply the event to each satellite of a specified constellation: use the
system
keyword
followed
by
the
satellite
system
name
(GPS/GLONASS/GALILEO/BEIDOU/QZSS/IRNSS/SBAS).
The
first
format,
relpower
, defines a change in the
power level
for the whole scen-
ario, a single satellite identified by SATID or channel number, or all satellites in one
constellation.
The
second
format,
abspower
, sets the
absolute power
for the whole scenario, a
single satellite identified by SATID or channel number, or all satellites in one con-
stellation.
The
third
format,
duplicate
, generates a
duplicate signal
from a given satellite,
using a specified delay, Doppler and power level. Duplicate channels require
60 seconds to be created, and are introduced at fixed 30-second intervals. Only 4
Duplicate satellites are allowed to be created at a time. Duplicate events closer
together than 4 seconds are spread apart automatically to maintain 4 second sep-
aration.
SBAS and Interference satellites cannot be duplicated. The optional
CHTARGET
para-
meter specifies the channel to be used. If the channel is used by a satellite, this satel-
lite will be disabled, and the multipath satellite replaces it. If the
CHTARGET
parameter is not specified, the multipath satellite will be created in the first unused
channel. Multipath, SBAS and interference/jamming channels cannot be duplicated.
The
fourth
format,
multipath
, modifies the
multipath parameters
of a satellite. If
the satellite is not a duplicate, it becomes a duplicate satellite, which is reflected in its
SATID
. SBAS and interference/jamming channels cannot have their multipath para-
meters modified.
The
fifth
format,
delete
,
deletes
a satellite. If the satellite is not a multipath duplic-
ate, it will typically automatically re-appear after 1 to 2 minutes. SBAS and inter-
ference/jamming channels cannot be deleted.
The
sixth
format,
navbits
, sets
bits in a navigation message
. The
ENDBITPOS-
STAR1 LSB
of the
HEXSTRING
are used to replace the bits between
STARTBITPOS
and
ENDBITPOS
, so that the
ENDBITPOS
is aligned with the LSB of
the
HEXSTRING
.
Should
ENDBITPOS-STAR1
> length (
HEXSTRING
), the
HEXSTRING
will be
used as a repeating pattern to replace the bits between
STARTBITPOS
and
ENDBITPOS
.
Multiple navbits events may be applied to the same message. Note that a navbits
event is applied to the first message from the event
TIME
with the
SFID
and
PAGEID
specified in the event. For
GPS
the bit count starts with
MSB
, whereas for
Glonass
, the count starts with
LSB
. Only GPS and GLONASS are currently sup-
ported.
3.5 "Select" Menu
User Manual GSG-5/6 Series Rev. 27
55
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...