GMV MAGICGNSS, Руководство пользователя

Страница: 30 / 44

UNCLASSIFIED
Code:
Date:
Issue:
Revision:
Page:
GMV-magicGNSS-MAN-0002
05 July 2018
1
2
30 of 44
magicGNSSUT  GMV 2018; all rights reserved UNCLASSIFIED magicGNSS User Terminal Manual
Example:
$PGMVA,084854.00,3748.23268630,S,14458.01523430,E,9,09,0.0,45.496,M,4.672,M,,,4.285554
,3.993219*68
GPGGA, PGMVA and PGMVP are all sent in real time via local TCP port and TCP client according to the
configuration options (as seen in the Configuration panel).
PPP File-based Outputs
Nominally the PPP Engine generates the following information:
 Observation RINEX (RINEX v3.03) logging information for all the received measurements,
even if they have not been used in the process execution.
 Input navigation RINEX (RINEX v3.03)
 SBAS EMS 2.0
 Standard NMEA file containing positioning data (GPGGA)
 Proprietary NMEA extension file containing positioning and integrity data (protection levels)
(PGMVP)
 PPP Positions file
 KML file containing positioning data and landmark positions
 Navigation Corrections file, containing information about navigation data and corrections, per
satellite and epoch
 PPP Summary files containing measurements residuals both by satellite and by iteration, in
addition to information related to measurement outlier detection and rejection.
 PPP Indicators file containing information of the PPP process on an epoch basis.
 PPV Indicators file containing information of the pre-processing and validation of the
observation measurements.
* Debug option shall be only activated on helpdesk request to investigate potential issues or
improvements.
Further information about the output files generated under the Info option, is provided next. For
standard format files, links to the formats descriptions are provided. For relevant proprietary formats,
detailed descriptions are included.
 Observation RINEX (RINEX v3.03) logging information for all the received measurements,
even if they have not been used in the process execution. The generated output file follows
the RINEX 3.03 standard format, which can be consulted here:
https://kb.igs.org/hc/en-
us/article_attachments/202583897/RINEX_303.pdf . File naming convention following the
mentioned standard directives.
 Input navigation RINEX (RINEX v3.03). As for the observation RINEX files, see format at
https://kb.igs.org/hc/en-us/article_attachments/202583897/RINEX_303.pdf . File naming
convention following the mentioned standard directives.
 Receiver clock estimation RINEX (RINEX v3.03). As for previous files, see format at
https://kb.igs.org/hc/en-us/article_attachments/202583897/RINEX_303.pdf . File naming
convention following the mentioned standard directives.
 SBAS EMS 2.0. See format here: http://www.egnos-pro.esa.int/ems/EMS_UID_2_0.pdf . File
naming convention following the mentioned standard directives.
 Standard NMEA file containing positioning data. For further information about NMEA format:
https://www.nmea.org/content/nmea_standards/nmea_0183_v_410.asp . File naming
convention: GPGGA_yyyymmdd.txt, e.g. GPGGA_20180119.txt.
 Proprietary NMEA extension file containing positioning and integrity data (protection levels).
Format. File naming convention: PGMVA_yyyymmdd.txt, e.g. PGMVA_20180119.txt
 PPP Positions file, containing the following information:
Parameter Description Units
Year Year of position solution
Mth Month of position solution
Day Day of position solution
Hou Hour of position solution
Min Minutes of position solution