Orolia GSG-5 Series, User Manual With Scpi Manual, Page: 67 / 392

sidered valid for ±3.5 days from the TOA value (Time-of-almanac) listed in the YUMA
almanac.
The scenario is restricted to start times within this range. If a scenario runs beyond this
range of time, no new satellites will be added. If the user specifies a start time outside this
range, a dialog will advise the user that the ephemeris and almanac are dates are mis-
matched. The SCPI error “
Data out of range " will be logged to indicate this issue for
remote control users.
CNAV
You can also provide a file with
CNAV
messages to be used with GPS and QZSS L2C and
L5. The file extension is .cnt (CNAV train), and the file is satellite-specific. The file name
conventions are:
PRN<satid>_y<4digityear>_d<dayofyear>_h<hourofday>.cnt
e.g., PRNG01_y2013_d105_h14.cnt.
Each row of the file should contain:
satSys(A1), satid (I2), 1X, year (I2), 1X, month (I2), 1X, date
(I2), 1X, hour (I2), 1X, min(I2), 1X, sec (I2), 1X, msgid (I2),
1X, [optional] hexmsg (A76)
E x a m p l e :
G01 13 04 15 14 00 00 11 8B04B4ED919863A6671F473A31412695EFF3C
026C0209FF07D601F775FEFE1FF987800000000
The
hexmsg
part is optional, and if not provided, it will be generated by GSG. This enables
for users to specify only the order of messages.
The messages are used in a circular manner, i.e. after the last message is sent, the first mes-
sage will be sent again. The starting message is selected based on scenario start time, i.e., it
can be one of the middle messages in case scenario starts later than the time of the first
message.
Since the same file is used for L2C and L5 message trains which have different message
duration, only the timestamp of the first message is relevant to decide the starting mes-
sage. The week number and tow, as well as CRC, are recalculated by GSG.
SBAS
SBAS message files must follow the following file naming conventions so that GSG can
recognize them:
For EGNOS:
PRN*.ems
For WAAS:
Geo*
3.5 "Select" Menu
User Manual GSG-5/6 Series Rev. 27 51