Владимир О.
Nov 26 2013, 06:11
Добрый день!
Для получения этой информации не нужно SDK - в сообщениях $PSTMTS есть запрошенная Вами информация.
Кусок лога со включенными сообщениями ST:
$GPRMC,060419.000,A,6001.28678,N,03019.24672,E,0.1,0.0,261113,,,A*69
$GPGGA,060419.000,6001.28678,N,03019.24672,E,1,06,3.3,059.15,M,18.0,M,,*6B
$GNGNS,060419.000,6001.28678,N,03019.24672,E,AA,06,3.3,0059.2,18.0,,*59
$GPVTG,0.0,T,,M,0.1,N,0.1,K,A*0D
$GPGST,060419.000,14.0,35.9,10.8,90.7,24.2,28.6,24.6*58
$GNGSA,A,3,31,21,16,,,,,,,,,,5.0,3.3,3.8*24
$GNGSA,A,3,78,79,81,,,,,,,,,,5.0,3.3,3.8*2A
$GPGSV,1,1,04,13,12,355,,16,17,310,34,21,38,207,47,31,26,242,42*71
$GLGSV,1,1,04,81,28,263,35,78,36,223,38,80,10,347,,79,47,302,41*61
$PSTMTG,1768,194674.9993,6, 120238294, 9,-48030.0000*2A
$PSTMTS,1,31,149075648.51,-50802.04,1,42,74105,1,23994496.34,-7316011.61,9343046.77,1157.08,125.56,-2898.32,99015.17,12.36,0,0.00,0.00,0,0,0,0,*0A
$PSTMTS,1,21,148572226.09,-45331.23,1,47,72607,1,24793245.94,5152386.89,9390120.28,-1075.80,365.73,2770.99,-99009.94,10.48,0,0.00,0.00,0,0,0,0,*02
$PSTMTS,1,79,3074788.21,-52318.42,1,38,69412,1,23382179.25,379676.68,10080497.03,1401.48,79.50,-3256.92,6683.16,10.37,0,0.00,0.00,0,0,0,0,*29
$PSTMTS,1,86,2430160.14,-48063.54,1,41,66334,1,9729917.54,-8080292.51,22183716.35,2985.76,556.75,-1098.63,3794.76,8.10,0,0.00,0.00,0,0,0,0,*0C
$PSTMTS,1,76,3858008.90,-45275.04,1,35,64569,1,18727366.45,-11447141.18,13049389.44,-1316.56,1211.49,2952.97,28293.19,11.29,0,0.00,0.00,0,0,0,0,*39
$PSTMTS,1,16,149741578.03,-44586.15,1,34,45343,1,3764613.62,-18066723.79,18937516.28,1346.44,2010.36,1680.50,-72168.99,13.54,0,0.00,0.00,0,0,0,0,*02
$PSTMSBAS,1,0,124,21,189,00*1C
$PSTMSBASMCH,0,124,21,189,00*47
$PSTMSBASMCH,1,126,,,00*77
$PSTMCPU,73.02,0,52*6f
Описание сообщения:
$PSTMTS
This message is repeated for each satellite tracked and used for the calculation of a fix
NMEA message list bitmask: 0x200
Format:
$PSTMTS,<dsp-dat>,<SatID>,<PsR>,<Freq>,<plf>,<CN0>,<ttim>,<Satdat>,<Satx>,<Saty>,<Satz>,<Velx>,<Vely>,<Velz>,<src>,<ac>,<difdat>,<drc>,<drrc><predavl>,<predage>,<predeph>,<predtd>,<cr><lf>
Parameter Format Description
dsp-dat Decimal, 1 digit DSP data available:
0 = satellite not tracked
1 = satellite tracked
Sat-ID Decimal, 2 digits Satellite Number (PRN)
PsR Decimal, 10 digits Pseudo range
Freq Decimal, 8 digits Satellite tracking Frequency Offset
Plf Decimal, 1 digit Preamble Lock Flag
0 = Navigation data stream preamble not locked
1 = Navigation data stream preamble locked
CN0 Decimal, 3 digits Satellite Carrier to Noise Ratio ( in dB )
Ttim Decimal, 6 digits Track Time of Satellite ( in seconds )
Satdat Decimal, 1 digit Satellite Data available Flag
0 = Sat. Ephemeris not available or unhealthy Sat.
1 = Sat. Ephemeris available and healthy Satellite
Satx Decimal, 10 digits Satellite Position , X-Coordinate
Saty Decimal, 10 digits Satellite Position , Y-Coordinate
Satz Decimal, 10 digits Satellite Position , Z-Coordinate
Velx Decimal, 8 digits Satellite Velocity , X-Coordinate
Vely Decimal, 8 digits Satellite Velocity , Y-Coordinate
Velz Decimal, 8 digits Satellite Velocity , Z-Coordinate
Src Decimal, 6 Digits Satellite Range Correction
Ac Decimal, 3 Digits Atmospheric Correction
Difdat Decimal, 1 digit Differential Data available Flag
0 = Differential Corrections not available
1 = Differential Corrections available
Drc Decimal, 3 digits Differential Range Correction (from DGPS Station)
Drrc Decimal, 3 digits Differential Range Rate Correction (from DGPS Stat.)
predavl Decimal, 1 digit Prediction available Flag
0 = Predicted Ephemeris not available
1 = Predicted Ephemeris available
predage Decimal, 1 digit Age of predicted Ephemeris (in hours)
predeph Decimal, 1 digit Number of satellites ued for prediction (1 or 2)
predtd Decimal, 1 digit Time distance of Ephemeris calculated from 2 Sats.
Only valid if <pred-eph> = 2
Note: <pred-xxx> fields are only included within the message if the AGPS software module has been included.
Прошу прощения, но в сообщениях не могу сохранить нормальное форматирование...