Auto landing after several seconds of ascending

[spyrorx]

My mavic 2 pro starts auto landing after several seconds of ascending. It doesn't happen on low speeds ascending (<1.5m/s). Why is that?

 

[Yorkshire_Pud]

Post the flight log for an affected flight.

 

[slup]

Most probably battery related, in the long full speed ascent, the voltage sags below the "low voltage auto landing" threshold.

The log will tell us the facts...

 

[spyrorx]

I'm trying to upload the logs (the .txt file) but it doesn't work. Am I doing something wrong?

 

[slup]

I'm trying to upload the logs (the .txt file) but it doesn't work. Am I doing something wrong?

Go here & upload your .txt mobile device flight log, come then back to this thread & share the link they
provide in a new post --> DJI Flight Log Viewer | Phantom Help

 

[spyrorx]

Log attached.

Link: DJI Flight Log Viewer - PhantomHelp.com

 

[slup]

This wasn't battery voltage related... your log instead shows several "Downward sensor errors" which possibly can be the reason. The .TXT log doesn't spell out the exact reason for the auto landings, instead only a generic reason with a number (other 42).

Perhaps the mobile device .DAT log can give more regarding the respons to the downward sensor error which leads to a auto landing.

The mobile device .DAT log is located in the same place as the .TXT log you've already shared, but in a sub-folder there called MCDatFlightRecords. The correct log ends with FLY036.DAT. Retrieve it and attach it to a new post here in this thread.

 

[spyrorx]

There were 2 FLY036.DAT files, both attached

 

[slup]

No, sorry... nothing in the .DAT log clearly explain why the auto landing gets initiated. Below is a copy from the DAT log event stream when the first auto landing starts at 381,795sec. So we have errors coming from the downward sensor (ultrasonic) & IMU errors... in the log it's also several shorter compass errors & GPS errors.

Difficult to say what's causing the auto landing unfortunately.

380.836 : 20483 [L-FDI]ULTRASONIC(0): fault on, stuck
380.856 : 20484 [L-FDI]fatal error: no ns with level < 4 !!!
380.996 : 20491 [L-FMU/LED]action changed. imu error:ns_abnormal(3)
381.180 : 20500 [L-N_MIS]Exit mis 3. New mis 11
381.180 : 20500 [L-N_MIS]Switch new mis 11 req 14 from mis 3 req 2
381.795 : 20531 [L-RC]Start landing. rc vib!

 

[spyrorx]

No, sorry... nothing in the .DAT log clearly explain why the auto landing gets initiated. Below is a copy from the DAT log event stream when the first auto landing starts at 381,795sec. So we have errors coming from the downward sensor (ultrasonic) & IMU errors... in the log it's also several shorter compass errors & GPS errors.

Difficult to say what's causing the auto landing unfortunately.

380.836 : 20483 [L-FDI]ULTRASONIC(0): fault on, stuck
380.856 : 20484 [L-FDI]fatal error: no ns with level < 4 !!!
380.996 : 20491 [L-FMU/LED]action changed. imu error:ns_abnormal(3)
381.180 : 20500 [L-N_MIS]Exit mis 3. New mis 11
381.180 : 20500 [L-N_MIS]Switch new mis 11 req 14 from mis 3 req 2
381.795 : 20531 [L-RC]Start landing. rc vib!

OK. Thank you