Data Logs Chapter 6
EuroPak-15a Receiver User Manual Rev 5 99
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
Table 49: Reject Code Values
ASCII Binary Description
GOOD 0Observations are good
BADHEALTH 1Bad satellite health is indicated by ephemeris data
OLDEPHEMERIS 2Old ephemeris due to date not being updated during the last 3 hours
ECCENTRICANOMALY 3Eccentric anomaly error during computation of the satellite’s position
TRUEANOMALY 4True anomaly error during computation of the satellite’s position
SATCOORDINATEERROR 5Satellite coordinate error during computation of the satellite’s position
ELEVATIONERROR 6Elevation error due to the satellite being below the cut-off angle
MISCLOSURE 7Misclosure too large due to excessive gap between estimated and actual
positions
NOEPHEMERIS 9Ephemeris data for this satellite has not yet been received
INVALIDIODE 10 Invalid IODE (Issue Of Data Ephemeris) due to mismatch between
differential stations
LOWPOWER 12 Low power meaning that the satellite is rejected due to low carrier/noise
ratio
NOIONOCORR 16 No compatible ionospheric correction is available for this particular
satellite
BAD_INTEGRITY 17 Bad integrity indicating a large variation between the measured range to
the satellite and the theoretical range computed from the ephemeris
OBSL5 18 Tracking a GPS or SBAS L5 signal that is not used in a position solution
GALL1 19 Tracking a Galileo L1 signal
GALE5a 20 Tracking a Galileo E5a signal
OBSL1 23 Tracking a GPS or SBAS L1 signal that is not used in a position solution
NA 99 No observation (a reject code is not applicable)