Menu
Forums
New posts
Search forums
What's new
New posts
New media
New media comments
New profile posts
Latest activity
Media
New media
New comments
Search media
Members
Current visitors
New profile posts
Search profile posts
Log in
Register
Search
Search titles only
By:
Search titles only
By:
New posts
Search forums
Search
Search titles only
By:
Search titles only
By:
Menu
Welcome DJI Spark Pilot!
Jump in and join our free Spark community today!
Sign up
Forums
DJI Spark Forums
Spark Help
Lost Spark - no video footage to help locate
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="BudWalker" data-source="post: 73043" data-attributes="member: 787"><p>There are (at least) 2 sets of coords data that exist in the .DAT. There is the GPS coords that come directly from the GPS receiver. That's the raw GPS data that can be found in the GPS record - DatCon labels these fields GPS(0):Long and GPS(0):Lat. Then there are the latitude and longitude values that can be found in the IMU record, labelled IMU(0):Latitude and IMU(0):Longitude). These are actually computed values that come from fusing the GPS data with IMU data (accelerometers, gyros), and magnetometer data. The .kml that DatCon produces is based on the computed latitude/longitude values, not the raw GPS data.</p><p></p><p>Computing the IMU latitude/longitude values isn't always possible. If not, then DatCon can't create a .kml. NavHealth (formerly known as gpsHealth) is a measure of the confidence that the FC has in the computed latitude/longitude values. It ranges from 0 (no confidence) to 5 (full confidence). There are several reasons that will cause the FC to lower the navHealth value. Insufficient satellites is one reason but low confidence can also be caused by a compass error.</p><p></p><p>Maybe you could provide a .DAT that we could look at. It might also help if you provided the corresponding .txt.</p></blockquote><p></p>
[QUOTE="BudWalker, post: 73043, member: 787"] There are (at least) 2 sets of coords data that exist in the .DAT. There is the GPS coords that come directly from the GPS receiver. That's the raw GPS data that can be found in the GPS record - DatCon labels these fields GPS(0):Long and GPS(0):Lat. Then there are the latitude and longitude values that can be found in the IMU record, labelled IMU(0):Latitude and IMU(0):Longitude). These are actually computed values that come from fusing the GPS data with IMU data (accelerometers, gyros), and magnetometer data. The .kml that DatCon produces is based on the computed latitude/longitude values, not the raw GPS data. Computing the IMU latitude/longitude values isn't always possible. If not, then DatCon can't create a .kml. NavHealth (formerly known as gpsHealth) is a measure of the confidence that the FC has in the computed latitude/longitude values. It ranges from 0 (no confidence) to 5 (full confidence). There are several reasons that will cause the FC to lower the navHealth value. Insufficient satellites is one reason but low confidence can also be caused by a compass error. Maybe you could provide a .DAT that we could look at. It might also help if you provided the corresponding .txt. [/QUOTE]
Verification
Post reply
Forums
DJI Spark Forums
Spark Help
Lost Spark - no video footage to help locate