Spectracom GSG-5 series, User Manual With Scpi Manual

Page: 284 / 378

For QZSS L1SAIF: message type, where 0 means that the modification is applied on the
next message independently of its type
For SBAS: message type, where 0 means that the modification is applied on the next
message independently of its type
pageid – For GPS L1 and L2P signals: page id and 0 (not relevant) when subframe id is 1-3
For GPS L2C and L5 signals: 0 (not relevant)
For Glonass: string id
For Galileo E1 and E5b signals: 0/1 (even/odd)
For Galileo E5a: 0 (not relevant)
For BeiDou: page id
For QZSS L1CA: page id and 0 (not relevant) when subframe id is 1-3
For QZSS L1SAIF: 0 (not relevant)
For SBAS: 0 (not relevant)
startBitPos , endBitPos – positions of bits in a navigation message,
Note: For Glonass the bit count starts from LSB, whereas for other messages the
bit count starts from MSB.
hexstring – Bit pattern to be set in the message
repeat – 0 if the modification should be applied only once
1 if the modification should be repeated on every message
crcflag – 0 if the CRC/parity does not need to be corrected after the modification
1 if the CRC/parity needs to be correct after the bit modification. With L1SBAS and
L1SAIF the preamble will be also maintained.
printflag – 0 if the modified message does not to be logged
1 if the modified message needs to be logged in the execution log. Note that the mes
sage is logged only once even if the modification is repeated on every message (repeat
flag = 1) .
This parameter is optional, the default value is 0.
Example
Set MSB to 1 in 6 bit health (bits 77-82) in subframe 1 of the GPS L1CA message:
SOUR:SCEN:NAVBITS IMM,G23,L1CA,1,0,77,77,1,1,0,1
Example message in the execution log:
268
CHAPTER
6
•
User Manual GSG-5/6 Series Rev. 26
6.3 Command Reference