Table of Contents
Advertisement
Data Logs
Recommended Input:
LOG TRACKSTATA ONTIME 1
Example Output:
#TRACKSTATA,COM1,0,64.5,FINE,1048,507426.700,00000028,228E,0;
SOL_COMPUTED,SINGLE,0.0,24,
5,0,8105C04,25052294.167,3388.063,40.188,63.560,7.209,GOOD, 1.000,
...
2,0,1305C2B,21433408.821,1310.921,43.913,514.040,0.000,OBSL2, 1.000,
...
26,0,1305D6B,24444419.776,2365.217,31.530,1506.520,0.000,OBSL2,
1.000
*cd40e0aa
ASCII
GOOD
BADHEALTH
OLDEPHEMERIS
ECCENTRICANOMALY
TRUEANOMALY
SATCOORDINATEERROR
ELEVATIONERROR
MISCLOSURE
NOEPHEMERIS
INVALIDIODE
LOWPOWER
NOIONOCORR
BAD_INTEGRITY
OBSL5
GALL1
GALE5a
OBSL1
NA
EuroPak-15a Receiver User Manual Rev 5
Table 49: Reject Code Values
Binary
0
Observations are good
1
Bad satellite health is indicated by ephemeris data
2
Old ephemeris due to date not being updated during the last 3 hours
3
Eccentric anomaly error during computation of the satellite's position
4
True anomaly error during computation of the satellite's position
5
Satellite coordinate error during computation of the satellite's position
6
Elevation error due to the satellite being below the cut-off angle
Misclosure too large due to excessive gap between estimated and actual
7
positions
9
Ephemeris data for this satellite has not yet been received
Invalid IODE (Issue Of Data Ephemeris) due to mismatch between
10
differential stations
Low power meaning that the satellite is rejected due to low carrier/noise
12
ratio
No compatible ionospheric correction is available for this particular
16
satellite
Bad integrity indicating a large variation between the measured range to
17
the satellite and the theoretical range computed from the ephemeris
18
Tracking a GPS or SBAS L5 signal that is not used in a position solution
19
Tracking a Galileo L1 signal
20
Tracking a Galileo E5a signal
23
Tracking a GPS or SBAS L1 signal that is not used in a position solution
99
No observation (a reject code is not applicable)
Description
Chapter 6
99
Advertisement
Table of Contents
