DJI Mavic, Air and Mini Drones
Friendly, Helpful & Knowledgeable Community
Join Us Now

Help w/ Logs Expert Code Readers )Sry it's a Spark

DDS

Well-Known Member
Approved Vendor
Joined
May 16, 2019
Messages
624
Reactions
840
Location
New Jersey USA
Have a client who sent in a crashed drone

Replaced the downward Vision as well as the 3d sensor (cleared error 40003) . Past the test flight so sent back

From there the drone went rogue and flew away and was not recovered.

See attached files any help will be appreciated
 

Attachments

  • DJIFlightRecord_2021-02-08_[17-29-48].txt
    28.9 KB · Views: 10
  • 2021-05-03_16-49-07_FLY186.DAT
    508.4 KB · Views: 6
  • Like
Reactions: dirkclod
These 2 logs aren't connected ..?

The first clearly covers a loss of thrust incident with the typical spiraling down movement ... looks like a loss of thrust for the front right.

1622582186359.png

1622582203054.png

The second log, the .DAT, shows a different story ... at 95,5sec into the flight the craft suddenly goes to ATTI mode, still with 15 sats locked. The craft is still right above the launch point. It starts to drift with the wind & all stick movements made thereafter was confusing as they drove the craft further away in the wind direction until the connection eventually was lost at 109,5sec. The craft would have drifted with the wind until the battery was depleted & it autolanded or crashed into something

Here the flight path into a northern direction, green bar shows yaw direction & blue compass direction & these 2 agrees well ... so the ATTI mode wasn't due to a yaw error due to a power on in a magnetic disturbed location.

1622581546298.png

Wind at ground level ...

1622581701682.png

Here all stick movements together with the only craft movement that stood out, the pitch axis ... but those movements correlates well with the full pitch stick commands made just when we see the excessive pitch.

1622581819902.png

The DAT log event stream indicate that the reason for the ATTI mode was a IMU error.

1622581868796.png
 
  • Like
Reactions: DDS
The eventLog stream also shows several entries like this one.

33.409 : 1425 [L-DBG1]fan_speed: 0, ctrl_out: 100 ||

I looked at some other Spark .DATs which all showed fan speed > 0. E..g
11.763 : 375 [L-DBG1]fan_speed: 244, ctrl_out: 100 ||

I'm guessing that the fan wasn't connected. Maybe the cpu over heated causing FC errors.
 
Last edited:
  • Like
Reactions: DDS and slup
Thank You will cover this one strange how it cleared the flight test w/ no issues...
Do you have the .DAT from the test flight?
 
Lycus Tech Mavic Air 3 Case

DJI Drone Deals

New Threads

Forum statistics

Threads
131,653
Messages
1,564,984
Members
160,519
Latest member
fuckyoupaymenowww