3.3 Managing References
option to select not just GPS, but also Galileo and/or BeiDou, thus allowing the col-
lection of RINEX3 navigation files and almanac files for the GPS, Galileo and/or BeiDou
constellations. At this time the GLONASS constellation is NOT supported.
Based on accessible and valid GNSS data, VelaSync generates its own ephemeris and
almanac data, and stores it in RINEX files and YUMA files, respectively.
You can also determine how often, or at what time each day the YUMA almanac files will
be created. Also, you can assign a 4-character
erated by this unit so that their location can later be identified. Under
you can determine after how many days the history files will be overwritten.
The files can be remotely accessed via the /pub path on the VelaSync or via the mapped
drive.
Confirming that the A-GPS RINEX Server License is installed on your unit
Navigate to
panel the option
Activating the A-GPS RINEX Server License functionality
If an A-GPS RINEX Server License is installed on your unit, you have to activate it:
1. Navigate to
GNSS
2. In the
the following options:
146
Caution:
Do NOT use GLONASS when operating VelaSync as an A-
GNSS server, since this will likely crash the A-GNSS software.
Note:
RINEX files (ephemeris data) must be updated no later than
every 2 hours, because the ephemeris data is valid for 4 hours.
Note:
YUMA files (almanac data) are valid for day.
TOOLS
>
SYSTEM:
OPT-AGP A-GPS RINEX Server
INTERFACES
>
GNSS
0.
A-GPS
panel, check the box
Station Name
to be used in the files gen-
Upgrade/Backup. In the
must be present.
Reference, and click the GEAR button next to
Generate RINEX/YUMA Files
CHAPTER 3 • VelaSync User's Manual Rev. 3
Record
Duration,
System Configuration
and populate
Need help?
Do you have a question about the VelaSync 1232 and is the answer not in the manual?
Questions and answers