GPS: 770000, 1, 10, 41.0994610, -92.4471590, 0.0000, 711.8800, 702.9700, 19.9400, 195.1000

 

How do I convert the timestamp?  Is altitude in meters?  Is that the 711 or 702?

 

19.9400:  This speed?  In mph?

195.1000: Heading?

 

Views: 326

Reply to This

Replies to This Discussion

More specifically,

 

515000,1,5,41.099739,-92.449402,0,0.71,264.91,0.2,259.85

516000,1,5,41.099762,-92.449371,0,1.16,258.45,0.22,259.85

517000,1,5,41.09977,-92.449402,0,1.16,261.17,0.23,259.85

 

Is that every 10 seconds?

 

 

Here are log details that I have found. Probably someone knows these better?

This can also help: http://diydrones.com/profiles/blogs/better-log-analyzer-for-apm

 

*GPS
Time  , seconds from UTC midnight * 1000
Fix     , has fix? 0=no, 1=yes
Sats   , How many satellites found
Lat     , Latitude in degrees
Long  , Longitude in degrees
MixAlt , Altitude in meters, above sea level, calculated from pressure sensor
GPSAlt , Altitude in meters, above sea level, calculated from gps
GRSpeed ,Ground speed m/s
CRS  , Course in degrees


*ATT
Roll
Pitch
Yaw


*CTUN
ServoRoll
nav_roll
roll_sensor
ServoPitch
nav_pitch
pitch_sensor
ServoThrottle
ServoRudder
AN4


*NTUN:

Yaw
WPdist
TargetBear
NavBear
AltErr
AS
NavGScaler


*PM
looptime
Maincount
G_Dt_max
GyroSat
adcconstr
renorm_sqrt
renorm_blowup
gps_fixcount
imu_health


*CMD
num
wp_id
wp_pl
wp_alt
wp_lat
wp_lng


*MOD
mode

Thank you!  Very helpful.

 

It begs to ask why time is based on "seconds from UTC midnight"?  Why was that chosen?  is there an problem taking the time straight from the GPS?

Reply to Discussion

RSS

© 2019   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service