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 Discussions
Spark is gone :( Pls help analyzing flight record
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="Sparkz71au" data-source="post: 51127" data-attributes="member: 7299"><p>G'day.</p><p>Do you have a matching MCDatFlightRecord? Look in (android device):\DJI Spark\Android data\DJI\dji.go.v4\FlightRecord\MCDatFlightRecords for a file called 18-05-21-22-24-43.dat or similar. Most likely to be the most recent/last time stamped *.dat file(?). The time stamp may be slightly different. There may be additional information available to 'decode' - can you upload the *.dat file?</p><p></p><p>I looked at the *.txt log with various 'decoders'. The data from the right controller stick input is missing - ie horizontal movements forward, back, left or right. Maybe DJI changed the data format in 4.2.14 - strange.</p><p></p><p>Only positive throttle inputs exist within the recorded logs. It seems that you ignored the verbal atti mode warning at about 1:09 min & pushed the left stick up? About 30 seconds later another input was received to raise height. Negative throttle movements are not shown anywhere within the log. Either the log is wrong or you did not reduce the throttle to below 'hover'. Another mystery.</p><p></p><p>I can't explain the source of magnetic interference & the yaw errors - Spark was initially 123 m AGL & 3 m from home when the error(s) occurred. The kp index solar flares / magnetic interference history available on the 'net does not indicate any 'alarms' during the indicated time frame.</p><p></p><p>The only relationship I can think of, after searching & discovering many other threads with similar problems - mainly in sports mode or after sudden changes in direction, the compass/IMU may loose calibration & a yaw error is produced. Otherwise it might be the firmware complaining that a 10 degree turn took 350 degrees. Or the Spark wiring, under load, interferes magnetically with the compass. Or the DJI Go 4 app (4.2.14) has major bugs with the current aircraft firmware The GPS data is recorded in the log(s) until it disconnected but Spark had no idea which way was North, thus floated with the wind or flew at 7.9 m/s - unknown reasons for another 661 seconds as last reported in the logs. </p><p></p><p>Anyway, Spark had 661 seconds of battery left, including 57 seconds to land. Travelling at the last known speed and direction, Spark could have landed 5000 - 5800 meters away (3.1 - 3.6 miles) in a South-West direction from the home point.</p><p></p><p>I looked on google earth - check if Spark landed near Mt Hamilton Cemetery or Helen Detwiler Jr Elementary School. Maybe ask the Hamilton Police Service for lost & found or post a reward at the school.</p><p></p><p>It could have landed anywhere if the wind changed direction & speed.</p><p>I can't explain the horizontal speed compared to the wind conditions & height. Looks like Spark panicked & quickly tried to fly away towards South China. ;-)</p><p></p><p>I noticed your Spark was flying towards John C. Munro Hamilton International Airport. Anything could have happened - Spark may have been above the official height limit for the NFZ & may that have forced Spark to land at any distance? </p><p></p><p>Supply your *.txt or *.dat log file to DJI & request further support. It may be covered by warranty?</p><p></p><p>Good luck!</p><p>.</p></blockquote><p></p>
[QUOTE="Sparkz71au, post: 51127, member: 7299"] G'day. Do you have a matching MCDatFlightRecord? Look in (android device):\DJI Spark\Android data\DJI\dji.go.v4\FlightRecord\MCDatFlightRecords for a file called 18-05-21-22-24-43.dat or similar. Most likely to be the most recent/last time stamped *.dat file(?). The time stamp may be slightly different. There may be additional information available to 'decode' - can you upload the *.dat file? I looked at the *.txt log with various 'decoders'. The data from the right controller stick input is missing - ie horizontal movements forward, back, left or right. Maybe DJI changed the data format in 4.2.14 - strange. Only positive throttle inputs exist within the recorded logs. It seems that you ignored the verbal atti mode warning at about 1:09 min & pushed the left stick up? About 30 seconds later another input was received to raise height. Negative throttle movements are not shown anywhere within the log. Either the log is wrong or you did not reduce the throttle to below 'hover'. Another mystery. I can't explain the source of magnetic interference & the yaw errors - Spark was initially 123 m AGL & 3 m from home when the error(s) occurred. The kp index solar flares / magnetic interference history available on the 'net does not indicate any 'alarms' during the indicated time frame. The only relationship I can think of, after searching & discovering many other threads with similar problems - mainly in sports mode or after sudden changes in direction, the compass/IMU may loose calibration & a yaw error is produced. Otherwise it might be the firmware complaining that a 10 degree turn took 350 degrees. Or the Spark wiring, under load, interferes magnetically with the compass. Or the DJI Go 4 app (4.2.14) has major bugs with the current aircraft firmware The GPS data is recorded in the log(s) until it disconnected but Spark had no idea which way was North, thus floated with the wind or flew at 7.9 m/s - unknown reasons for another 661 seconds as last reported in the logs. Anyway, Spark had 661 seconds of battery left, including 57 seconds to land. Travelling at the last known speed and direction, Spark could have landed 5000 - 5800 meters away (3.1 - 3.6 miles) in a South-West direction from the home point. I looked on google earth - check if Spark landed near Mt Hamilton Cemetery or Helen Detwiler Jr Elementary School. Maybe ask the Hamilton Police Service for lost & found or post a reward at the school. It could have landed anywhere if the wind changed direction & speed. I can't explain the horizontal speed compared to the wind conditions & height. Looks like Spark panicked & quickly tried to fly away towards South China. ;-) I noticed your Spark was flying towards John C. Munro Hamilton International Airport. Anything could have happened - Spark may have been above the official height limit for the NFZ & may that have forced Spark to land at any distance? Supply your *.txt or *.dat log file to DJI & request further support. It may be covered by warranty? Good luck! . [/QUOTE]
Verification
Post reply
Forums
DJI Spark Forums
Spark Discussions
Spark is gone :( Pls help analyzing flight record