Mavic Pro Crashed

[Val972]

Hello,
I just crashed my Mavic pro and I was wondering if you could help me to understand what happened.
Here the log :


I was fliying next to my office and when i put the sport mode I lose control, the drone fell and start spinning the last warning i had was « motor current error » ?

Thanks

 

[Fly Dawg]

I just crashed my Mavic pro and I was wondering if you could help me to understand what happened.

We will need the device dat for this one. @112 meters altitude Really??.....

You will need to see this link: Retrieve a V3 DAT From Mobile Device
Share the .dat file back here....

Wow....your control inputs are rediculous........but as stated we need the .dat.

 

[Val972]

Here is the .dat file

 

[Fly Dawg]

@Val972 This looks like a major ESC failure.......You may need to take this up with DJI, if applicable. All of the motors simply shut down.......

 

[RayOZ]

Did you visually see the drone when it happened? Looks like you might have crashed into the building. It’s abt 120m high, cos you flew past it and the downward sensor picked it up. Then you flew below 120m before it cuts out.

 

[Simmo]

For all motors to shut down, wouldn't that be a Flight controller issue?
@sar104

Oo! I have an idea!!

Edit: Nah! I thought of an unintentional CSC, but nup!

 

[Val972]

Yes I saw the drone when it happened, even the camera was working during the crash, unfortunately I was not recording.
It’s a small 4-storey building so I was a hundred meter over it.

 

[Racin8de]

Hello,
I just crashed my Mavic pro and I was wondering if you could help me to understand what happened.
Here the log :


I was fliying next to my office and when i put the sport mode I lose control, the drone fell and start spinning the last warning i had was « motor current error » ?

Thanks

Looks like you had a motor warning, did a propellor break or come off. Was one missing when you located the drone? Sorry just trying to help, get it fixed. I crashed mine had to replace two front arms and the main board.. I hope you get her fixed, but sorry that happened...GL

 

[BudWalker]

For all motors to shut down, wouldn't that be a Flight controller issue?
@sar104

Oo! I have an idea!!

Edit: Nah! I thought of an unintentional CSC, but nup!

It was the Flight Controller that stopped the motors because the MP was tumbling. From the event log stream

64.900 : 5380 [L-FMU/MOTOR] Stop. reason:roll over or atti fail

The data is a bit ambiguous but it looks like a propulsion issue with either the left back or left front. The gyroZ data indicates the left back, but gyroX and gyroY say it was the left front.


The speed data indicates the left front


About 9 secs before the incident the left back was commanded 100% several times. But, then immediately before the incident it was the left back that was commanded 100%.

Also, note the vibration that started 9 secs before the incident.

 

[Fly Dawg]

The data is a bit ambiguous but it looks like a propulsion issue with either the left back or left front.

That portion was confusing to me. All pointed to Left rear to start, then the other 3 followed.

 

[easyheimer]

Sorry this happened. Following to see what DJI’s response is.

 

[new2mavic]

It was the Flight Controller that stopped the motors because the MP was tumbling. From the event log stream

64.900 : 5380 [L-FMU/MOTOR] Stop. reason:roll over or atti fail

The data is a bit ambiguous but it looks like a propulsion issue with either the left back or left front. The gyroZ data indicates the left back, but gyroX and gyroY say it was the left front.
View attachment 88598

The speed data indicates the left front
View attachment 88599

About 9 secs before the incident the left back was commanded 100% several times. But, then immediately before the incident it was the left back that was commanded 100%.
View attachment 88600
Also, note the vibration that started 9 secs before the incident.

May I know what software was used to produce these charts ?

 

[BudWalker]

May I know what software was used to produce these charts ?

Sure, I use CsvView and DatCon. Both are free and can be obtained here

CsvView Downloads

datfile.net

and
DatCon Downloads

 

[swededrone]

Gents, what about this one, what caused the crash?
Attaching the .DAT

Best regards
Swededrone

 

[sar104]

Gents, what about this one, what caused the crash?
Attaching the .DAT

Best regards
Swededrone



View attachment 96994View attachment 96995

There was a problem with the right rear motor or prop starting at 464 seconds - motor control maxed out and the current jumped substantially, with no increase in motor speed. Then, at 492 seconds, the motor showed overspeed and the motor control was dropped, suggesting that perhaps the prop detached. The problem at 464 seconds was accompanied by significant vibration as shown by the accelerometers, maybe suggesting a prop problem was the underlying cause.

 

[swededrone]

There was a problem with the right rear motor or prop starting at 464 seconds - motor control maxed out and the current jumped substantially, with no increase in motor speed. Then, at 492 seconds, the motor showed overspeed and the motor control was dropped, suggesting that perhaps the prop detached. The problem at 464 seconds was accompanied by significant vibration as shown by the accelerometers, maybe suggesting a prop problem was the underlying cause.

View attachment 97006

View attachment 97007

View attachment 97008

WoW thanks a mill for your as always to the point analysis!

 

[swededrone]

WoW thanks a mill for your as always to the point analysis!

@sar104 Small update. The vendor has replaced the HW following their own internal data analysis. So thank's again for helping me out here with a second opinion if the results would differ. And the replacement was NOT refurbished

 

[sar104]

@sar104 Small update. The vendor has replaced the HW following their own internal data analysis. So thank's again for helping me out here with a second opinion if the results would differ. And the replacement was NOT refurbished

Great. Did they say what their analysis showed?

 

[swededrone]

Great. Did they say what their analysis showed?

They only tell you it it's a pilot error. Otherwise never.

Here is the last video

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

 

[MAvic_South_Oz]

They only tell you it it's a pilot error. Otherwise never.

Here is the last video

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

Acro mode ??
Hopefully since it's been fully covered under warranty, you can laugh about it now.

I didn't see the original txt file (if it was posted), but looks like it was lucky to have crashed in a clear area ?
Did you recover the drone ?