Crazy Mavic 2 Behaviour

[Rockowe]

To start Normal Flight -
Light wind -
But... Battery Drains quickly (14mins)
- Auto Switches between sport and P- Modes continuously - without Me doing it.

Then Excessive Pitch angle- and wind reports
Then RTH and Auto Land

No Crash but Crazy Stuff -
Whats going On ?

Seems like excessive Wind (Which I didn't notice) Tipped the DISH of the Aircraft, drained the battery and caused sensor problems...
Any thoughts?

 

[4wd]

The switching between P and S is odd but the clues are there, if it really was tilted like that it would have shot off to the side unless it was battling strong wind.
Fighting wind will rapidly drain the battery.
Behind you there looked to be some kind of showery activity which suggests unstable air masses and shear in the area.

 

[Meta4]

Seems like excessive Wind (Which I didn't notice) Tipped the DISH of the Aircraft, drained the battery and caused sensor problems...
Any thoughts?

I can't get that video to load but the best place to look for an explanation is always in the recorded flight data.
Go to DJI Flight Log Viewer | Phantom Help
Follow the instructions there to upload your flight record from your phone or tablet.
That will give you a detailed report of the flight.
Come back and post a link to the report it provides.

 

[Simmo]

You flew out with a tail wind, then turned for home into a headwind.
Look at your airspeeds, heading out you were indeed flat out, coming back, you could only gain half that speed.

 

[brett8883]

To start Normal Flight -
Light wind -
But... Battery Drains quickly (14mins)
- Auto Switches between sport and P- Modes continuously - without Me doing it.

Then Excessive Pitch angle- and wind reports
Then RTH and Auto Land

No Crash but Crazy Stuff -
Whats going On ?

Seems like excessive Wind (Which I didn't notice) Tipped the DISH of the Aircraft, drained the battery and caused sensor problems...
Any thoughts?

We HAVE to have the aircraft logs to be able to tell you anything. Before that everything is pure speculation.

 

[Simmo]

We HAVE to have the aircraft logs to be able to tell you anything. Before that everything is pure speculation.

I dont disagree, however, look at the airspeed in the video!!!
Thats the answer right there without looking at any logs!

 

[brett8883]

Couple of thoughts too though. The RTH was a smart RTH triggered by the drones calculation of how much flight time remained and how long it was gonna take to get home. On the smart battery status bar which is on the hud of the camera view in the app it shows how much flight time is left and how much time it’s gonna take to get home. At 8 minutes the writing was on the wall that it was gonna be an emergency landing coming in because your indicated time to home was higher than your flight time remaining.

What it didn’t sound like you realized is that your drone was going through battery the entire time like crazy. You either took off with less than a full charge or you went through 20% in 3 minutes, 35% in 5 minutes, 50% in 8 minutes 75% in 11 minutes and 90% in 13 minutes. I just want to point out that the drone saved you from a horrible situation by initiation the RTH when it did because it doesn’t sound like you were aware that a major issue was happening.

That wind warning it gave you was a code red wind warning but you didn’t seem to think was a big deal. That’s was the point at which you should have turned around.

At 10% battery the drone went into a force landing that can’t be canceled so you don’t fall out of the sky and kill someone.

The switching from sport to p mode is a mystery and we need the logs to have any hope of figuring that out.

We also need the logs to figure out if this was in fact wind related or a motor issue possibly.

 

[brett8883]

I dont disagree, however, look at the airspeed in the video!!!
Thats the answer right there without looking at any logs!

That’s ground speed not air speed which doesn’t tell us much. It does suggest a wind related issue but If he was flying with a tail wind out he wouldn’t have been going through as much battery as he was so quickly.

 

[Simmo]

The resultant ground speed, indicates airspeed, especially when he is at full constant throttle.
Switching from P to S is the FC trying to get more attitude to fight the wind I believe. @sar104

 

[sar104]

The resultant ground speed, indicates airspeed, especially when he is at full constant throttle.
Switching from P to S is the FC trying to get more attitude to fight the wind I believe. @sar104

There is no mechanism for the FC to self-select flight modes, so something else is going on. Without the flight logs there is not enough information from which to draw any conclusions.

 

[Rockowe]

WOW - Thanks guys for all your carefully thought out Replies...

So META4 and sar104 suggested that the Flight Log may be helpful

so Here is a Link to that Report... Flight Upload (batt Drain - Tilt Angle - switch p switch s)

… Maybe we can resolve this here

 

[sar104]

That is strange - it was indeed switching back and forth during the flight without any movement on the RC mode switch:



That's going to require a look at the DAT log to figure out.

Mobile device DAT file: How to retrieve a V3.DAT from the tablet

 

[brett8883]

That is strange - it was indeed switching back and forth during the flight without any movement on the RC mode switch:

View attachment 69244

That's going to require a look at the DAT log to figure out.

Mobile device DAT file: How to retrieve a V3.DAT from the tablet

Did you see the RTH reason was "OutOfControlGohome?" I've never seen that before. Well haven't seen a lot of things but didnt know that was even a thing.

Also look at the roll attitude vs aileron.

 

[sar104]

Did you see the RTH reason was "OutOfControlGohome?" I've never seen that before. Well haven't seen a lot of things but didnt know that was even a thing.

Also look at the roll attitude vs aileron. View attachment 69249

RTH was initiated by 22 seconds of lost uplink - hence the out of control flag. I don't see anything strange in the roll data - it was very windy - around 30 mph.

 

[Rockowe]

That is strange - it was indeed switching back and forth during the flight without any movement on the RC mode switch:

View attachment 69244

That's going to require a look at the DAT log to figure out.

Mobile device DAT file: How to retrieve a V3.DAT from the tablet

Thanks Brett and SAR
Here is the DAT file...
Just Click the Link and save the .doc as .DAT Click Here to Download from one of our Servers

 

[brett8883]

RTH was initiated by 22 seconds of lost uplink - hence the out of control flag. I don't see anything strange in the roll data - it was very windy - around 30 mph.

Yea that makes sense now. Thanks

 

[sar104]

Thanks Brett and SAR
Here is the DAT file...
Just Click the Link and save the .doc as .DAT Click Here to Download from one of our Servers

I'm not sure what was going on there. The event stream turns into a morass of app and RC connection errors that were obviously causing the mode switching. For example - starting at around 190 seconds:

190.738 : 12523 [L-GEO]lost app, clear app_pos_info
191.097 : 12541 [L-RC]rc_connect:1=>0
191.097 : 12541 [L-SYS]app lost connection!
191.097 : 12541 [L-GEO]lost app, clear app_pos_info
191.097 : 12541 [L-RC]rc_func_disable @ [253103 ms]
191.097 : 12541 [L-SEND DATA]app connect changed:last(1) != current(0)
191.317 : 12552 [L-RC]rc_connect:0=>1
191.317 : 12552 [L-SYS]app connected!
191.317 : 12552 [L-RC]rc_resume @ [253323 ms]
191.317 : 12552 [L-RC]set rc_resume_lock
191.317 : 12552 [L-SEND DATA]app connect changed:last(0) != current(1)
192.594 : 12616 [L-RC]rc_connect:1=>0
192.594 : 12616 [L-SYS]app lost connection!
192.594 : 12616 [L-GEO]lost app, clear app_pos_info
192.594 : 12616 [L-RC]rc_func_disable @ [254603 ms]
192.594 : 12616 [L-SEND DATA]app connect changed:last(1) != current(0)
192.774 : 12625 [L-RC]rc_connect:0=>1
192.774 : 12625 [L-SYS]app connected!
192.774 : 12625 [L-RC]rc_resume @ [254783 ms]
192.774 : 12625 [L-RC]set rc_resume_lock
192.774 : 12625 [L-FMU/LED]type:0, normal flash action:
192.774 : 12625 [L-FMU/LED]c0:0,15;c1:0,3;c2:0,13;c3:2,3;c4:0,10;c5:0,3;c6:0,10;c7:0,3
192.774 : 12625 [L-SEND DATA]app connect changed:last(0) != current(1)
193.273 : 12650 [L-RC]clr rc_resume_lock
193.871 : 12680 [L-FDI]NS(0) GPS(0): fault on , height_drift
193.892 : 12681 [L-RC]rc_connect:1=>0
193.892 : 12681 [L-SYS]app lost connection!
193.892 : 12681 [L-GEO]lost app, clear app_pos_info
193.892 : 12681 [L-RC]rc_func_disable @ [255903 ms]
193.892 : 12681 [L-SEND DATA]app connect changed:last(1) != current(0)
194.211 : 12697 [L-RC]rc_connect:0=>1
194.211 : 12697 [L-SYS]app connected!
194.211 : 12697 [L-RC]rc_resume @ [256223 ms]
194.211 : 12697 [L-RC]set rc_resume_lock
194.211 : 12697 [L-SEND DATA]app connect changed:last(0) != current(1)
194.570 : 12715 [L-FMU/LED]type:0, normal flash action:
194.570 : 12715 [L-FMU/LED]c0:0,1;c1:0,3;c2:0,1;c3:2,3;c4:0,3;c5:0,3;c6:0,1;c7:0,3
194.710 : 12722 [L-RC]clr rc_resume_lock
195.249 : 12749 [L-RC]rc_connect:1=>0
195.249 : 12749 [L-SYS]app lost connection!
195.249 : 12749 [L-GEO]lost app, clear app_pos_info
195.249 : 12749 [L-RC]rc_func_disable @ [257263 ms]
195.249 : 12749 [L-SEND DATA]app connect changed:last(1) != current(0)
195.309 : 12752 [L-RC]rc_connect:0=>1
195.309 : 12752 [L-SYS]app connected!
195.309 : 12752 [L-RC]rc_resume @ [257323 ms]
195.309 : 12752 [L-RC]set rc_resume_lock
195.309 : 12752 [L-SEND DATA]app connect changed:last(0) != current(1)
195.808 : 12777 [L-RC]clr rc_resume_lock
196.706 : 12822 [L-RC]rc_connect:1=>0
196.706 : 12822 [L-SYS]app lost connection!
196.706 : 12822 [L-GEO]lost app, clear app_pos_info
196.706 : 12822 [L-RC]rc_func_disable @ [258723 ms]
196.706 : 12822 [L-SEND DATA]app connect changed:last(1) != current(0)
196.851 : 12829 [L-VISION][VIO]receive vio data befor current ts||
196.965 : 12835 [L-RC]set rc_resume_lock
196.965 : 12835 [L-SEND DATA]app connect changed:last(0) != current(1)
197.464 : 12860 [L-RC]clr rc_resume_lock
198.023 : 12888 [L-RC]rc_connect:1=>0
198.023 : 12888 [L-SYS]app lost connection!
198.023 : 12888 [L-GEO]lost app, clear app_pos_info
198.023 : 12888 [L-RC]rc_func_disable @ [260043 ms]
198.023 : 12888 [L-SEND DATA]app connect changed:last(1) != current(0)
198.063 : 12890 [L-RC]rc_connect:0=>1
198.063 : 12890 [L-SYS]app connected!
198.063 : 12890 [L-RC]rc_resume @ [260083 ms]

Whatever Android device you were using was not playing nicely with the RC.

 

[sar104]

To start Normal Flight -
Light wind -
But... Battery Drains quickly (14mins)
- Auto Switches between sport and P- Modes continuously - without Me doing it.

Then Excessive Pitch angle- and wind reports
Then RTH and Auto Land

No Crash but Crazy Stuff -
Whats going On ?

Just to clear up any confusion - you never had "light wind".

 

[Rockowe]

I'm not sure what was going on there. The event stream turns into a morass of app and RC connection errors that were obviously causing the mode switching. For example - starting at around 190 seconds:

190.738 : 12523 [L-GEO]lost app, clear app_pos_info
191.097 : 12541 [L-RC]rc_connect:1=>0
191.097 : 12541 [L-SYS]app lost connection!
191.097 : 12541 [L-GEO]lost app, clear app_pos_info
191.097 : 12541 [L-RC]rc_func_disable @ [253103 ms]
191.097 : 12541 [L-SEND DATA]app connect changed:last(1) != current(0)
191.317 : 12552 [L-RC]rc_connect:0=>1
191.317 : 12552 [L-SYS]app connected!
191.317 : 12552 [L-RC]rc_resume @ [253323 ms]
191.317 : 12552 [L-RC]set rc_resume_lock
191.317 : 12552 [L-SEND DATA]app connect changed:last(0) != current(1)
192.594 : 12616 [L-RC]rc_connect:1=>0
192.594 : 12616 [L-SYS]app lost connection!
192.594 : 12616 [L-GEO]lost app, clear app_pos_info
192.594 : 12616 [L-RC]rc_func_disable @ [254603 ms]
192.594 : 12616 [L-SEND DATA]app connect changed:last(1) != current(0)
192.774 : 12625 [L-RC]rc_connect:0=>1
192.774 : 12625 [L-SYS]app connected!
192.774 : 12625 [L-RC]rc_resume @ [254783 ms]
192.774 : 12625 [L-RC]set rc_resume_lock
192.774 : 12625 [L-FMU/LED]type:0, normal flash action:
192.774 : 12625 [L-FMU/LED]c0:0,15;c1:0,3;c2:0,13;c3:2,3;c4:0,10;c5:0,3;c6:0,10;c7:0,3
192.774 : 12625 [L-SEND DATA]app connect changed:last(0) != current(1)
193.273 : 12650 [L-RC]clr rc_resume_lock
193.871 : 12680 [L-FDI]NS(0) GPS(0): fault on , height_drift
193.892 : 12681 [L-RC]rc_connect:1=>0
193.892 : 12681 [L-SYS]app lost connection!
193.892 : 12681 [L-GEO]lost app, clear app_pos_info
193.892 : 12681 [L-RC]rc_func_disable @ [255903 ms]
193.892 : 12681 [L-SEND DATA]app connect changed:last(1) != current(0)
194.211 : 12697 [L-RC]rc_connect:0=>1
194.211 : 12697 [L-SYS]app connected!
194.211 : 12697 [L-RC]rc_resume @ [256223 ms]
194.211 : 12697 [L-RC]set rc_resume_lock
194.211 : 12697 [L-SEND DATA]app connect changed:last(0) != current(1)
194.570 : 12715 [L-FMU/LED]type:0, normal flash action:
194.570 : 12715 [L-FMU/LED]c0:0,1;c1:0,3;c2:0,1;c3:2,3;c4:0,3;c5:0,3;c6:0,1;c7:0,3
194.710 : 12722 [L-RC]clr rc_resume_lock
195.249 : 12749 [L-RC]rc_connect:1=>0
195.249 : 12749 [L-SYS]app lost connection!
195.249 : 12749 [L-GEO]lost app, clear app_pos_info
195.249 : 12749 [L-RC]rc_func_disable @ [257263 ms]
195.249 : 12749 [L-SEND DATA]app connect changed:last(1) != current(0)
195.309 : 12752 [L-RC]rc_connect:0=>1
195.309 : 12752 [L-SYS]app connected!
195.309 : 12752 [L-RC]rc_resume @ [257323 ms]
195.309 : 12752 [L-RC]set rc_resume_lock
195.309 : 12752 [L-SEND DATA]app connect changed:last(0) != current(1)
195.808 : 12777 [L-RC]clr rc_resume_lock
196.706 : 12822 [L-RC]rc_connect:1=>0
196.706 : 12822 [L-SYS]app lost connection!
196.706 : 12822 [L-GEO]lost app, clear app_pos_info
196.706 : 12822 [L-RC]rc_func_disable @ [258723 ms]
196.706 : 12822 [L-SEND DATA]app connect changed:last(1) != current(0)
196.851 : 12829 [L-VISION][VIO]receive vio data befor current ts||
196.965 : 12835 [L-RC]set rc_resume_lock
196.965 : 12835 [L-SEND DATA]app connect changed:last(0) != current(1)
197.464 : 12860 [L-RC]clr rc_resume_lock
198.023 : 12888 [L-RC]rc_connect:1=>0
198.023 : 12888 [L-SYS]app lost connection!
198.023 : 12888 [L-GEO]lost app, clear app_pos_info
198.023 : 12888 [L-RC]rc_func_disable @ [260043 ms]
198.023 : 12888 [L-SEND DATA]app connect changed:last(1) != current(0)
198.063 : 12890 [L-RC]rc_connect:0=>1
198.063 : 12890 [L-SYS]app connected!
198.063 : 12890 [L-RC]rc_resume @ [260083 ms]

Whatever Android device you were using was not playing nicely with the RC.

Iv seen this before Only in SPORT mode - … Where im whacking it out - (RH stick full Fwd) .
As Soon as I get to an area that there's interference or Distance Limits- … the connection is LOST and when connects, first goes to P then Quickly to sport...

Possibly in Gusty Wind, - and at distance limits (like in this case) the Roll or Pitch attitude compromises connection … and when regains attemps P-Mode Switching to S-Mode... and repeats as the DISH tilts...

On return - and closer this does not occur...

Excellent analysis SAR (and Brett) - I think that solves the Questions -
On the other issues, The Battery drain - … is Gusty Wind related - and Sport Mode

It Seems also Like the Mavic 2 Is Hard-Wired LIMITED to 72km/h No Matter what the SPort-Tilt angle is-
The Mavic 1 - sometimes could get a Ground speed of 90-100km in previous Tests...

Thanks Everyone...
Appreciated

 

[Rockowe]

Just to clear up any confusion - you never had "light wind".

WOW That's AWSOME SAR - I remember looking at those wind layouts - (during a trial Phase)

I must have been in the Eye of the Storm feeling very little wind - at H position (or U on the Map)
… because clearly there was some serious Flows over the Whole route (in the AirData Maps) like 30mph and more-

Explains a Lot - ALso Explains the DISH Tilt - and could well explain that angle messing with SIGNAL Transfer.

You have cool tools - … and Know how to read them Quickly ...
Pretty Cool !