Auto Land 10%

[White Shadow]

I just watched a video how a P4P+ was set to RTH @ 10% the person was operating the drone over the water the headwinds were strong as a result took longer for the unit to come back. There are so many variables .

Is there a setting to change this? I agree there is a risk ... Trying to build knowledge..
Thank you

 

[Paul2660]

At 10% battery the drone should start a auto landing. You can avoid this by continually keeping upward stick pressure. This will keep the drone on the air. And you can fly it but it’s not an easy task.

I don’t think you can override the 10% remaining kick in for Autoland ie have it kick in at less than 10%

If you want to try flying while the auto landing process is going on I would go to a good field and fly until the drone kicks in auto landing. Then apply stick pressure which will keep the drone airborne even though the DJIGO4 app is screaming at you.

I say do this in a safe place to practice as a lot is going on. Also remember once you let off the stick the auto landing will continue.

Several videos out there were pilots have continued to fly the drone even when the 10 percent remaining auto landing has started.

Unless drone is nearby it’s very risky as that last 10% can go very quick depending on flying conditions.

Paul C

 

[White Shadow]

Hey Paul,
Thats what happened to the operator in the video I saw the app kept trying to land while he was trying to bring it in from out to sea. It looks like if the auto land did not keep activating he may have brought it back.

Way to risky for me....
Thank you

 

[Fly Dawg]

I just watched a video how a P4P+ was set to RTH @ 10%

You have to remember that that battery percentage is based on a calculated value and NOT what you see on your screen as remaining battery percentage. It could actually be more or less than that as calculated by the FC. If the FC calculates that there is not enough remaining battery for RTH it will land where it is at that point. Never ever set your RTH value less than 28%..IMO....this will give you a bit of room for error. That said, at long distance, it is a risk that you take. Auto land will initiate for a variety of reasons, not just the calculated RTH.

 

[White Shadow]

@Fly Dawg
That's what happened in another video I saw the Drone just started to land on the operator looks the drone was to far out.

The video I saw when the drone was over the water between head winds and Auto land really contributed to the poor guys drone going in the ocean.

Great info you provided.
Thanks all.

 

[Paul2660]

What Fly Dawg said is critical. That percentage will always vary by conditions.

After watching one of Drone Guy Billy’s videos where he literally flew a MP2 to the last bit of charge, I wanted to try it during the last 10% when auto landing has kicked in. It’s not an easy process due to everything that’s going on and something I do not want to do unless it’s an emergency. But wanted to practice it.

Paul C

 

[White Shadow]

can you see your flight logs on DJI website like the DJI Go 4 App ?
Thank you

 

[Fly Dawg]

What Fly Dawg said is critical. That percentage will always vary by conditions.

I was just about to correct the post. Either "Low Battery" or "Critical Battery" are both again as I said calculated values. These two you can set in the app, but do not depend on the accuracy. These are "Fail Safe" generic numbers that you set. They should in theory be close to correct but they can vary, and at times by a larger number than you would think.

 

[White Shadow]

thank you

 

[Fly Dawg]

can you see your flight logs on DJI website like the DJI Go 4 App ?

Not that I know of. Your best bet is to sync with Airdata, or upload individual flights to the Phantom Help Viewer. Airdata has gotten much better in detail than previously, however I prefer to see the actual values as opposed to the " Graphic Displays". I make better sense out of graphs than what is presented by a visual representation.

 

[Fly Dawg]

@Dast ......Just a note for you. When you answer posts, it would be better to use quotes or a direct response as opposed to a generic follow up. That way others know whom you are referring to.

 

[Meta4]

I just watched a video how a P4P+ was set to RTH @ 10% the person was operating the drone over the water the headwinds were strong as a result took longer for the unit to come back. There are so many variables .
Is there a setting to change this? I agree there is a risk ... Trying to build knowledge..

The last 10% is not as strong or reliable as the first 10%.
You should always aim to be back and on the ground before you get to 10%.
If you are flying in a risky location, make that 20 or even 30%.
You need a comfortable safety margin.

 

[White Shadow]

Got ya..
Thanks guys

 

[sar104]

Just to clarify - the low battery and critically low battery settings in the GO app are not used to initiate RTH or auto landing - they are purely informational. The FC continuously computes two variables during flight, SMART_BATT:goHome% and SMART_BATT:land%, based on distance from the home point and altitude above the home point, respectively. It will initiate RTH when the battery level falls below SMART_BATT:goHome%, and it will initiate auto landing when it falls below SMART_BATT:land%.

 

[With The Birds]

Just to clarify - the low battery and critically low battery settings in the GO app are not used to initiate RTH or auto landing - they are purely informational. The FC continuously computes two variables during flight, SMART_BATT:goHome% and SMART_BATT:land%, based on distance from the home point and altitude above the home point, respectively. It will initiate RTH when the battery level falls below SMART_BATT:goHome%, and it will initiate auto landing when it falls below SMART_BATT:land%.

This issue is still an area of uncertainty for many (me included). I haven’t flown down to my critical battery % in recent times but from memory (set at 10%) my phantoms would always try and land at this point. Low battery warning will always issue at % value set in go and is a user selectable information only alarm. Auto GO home (if enabled) will initiate based on distance from home point and determined % to make it back (presumably the FC determined value you have informed us of). It seems the real unknown is behaviour at critical- specifically whether it may initiate above 10% (or higher value set) with increased altitude and whether you might fly down below 10% (default minimum) without auto land commencing.

 

[Loz]

This issue is still an area of uncertainty for many (me included).

Agree - MSinger set me straight on this (as Sar described above) some months ago - I mean the ‘informational only’ nature of the battery user settings in the app, which I did not know, previously thinking it was a setting to trigger AC behaviour - it’s not. An explanation of the relationship (if any) between these user settings and actual AC FC behaviour would be useful (please). I note that FC calculates RTH activation based on altitude and distance from home. In summary what’s the point of the user settings (and the app wording suggests setting not indication to pilot - but that could just be DJI wording something poorly) if the AC may RTH or land outside those battery pilot settings in the app?

 

[With The Birds]

Agree - MSinger set me straight on this (as Sar described above) some months ago - I mean the ‘informational only’ nature of the battery user settings in the app, which I did not know, previously thinking it was a setting to trigger AC behaviour - it’s not. An explanation of the relationship (if any) between these user settings and actual AC FC behaviour would be useful (please). I note that FC calculates RTH activation based on altitude and distance from home. In summary what’s the point of the user settings (and the app wording suggests setting not indication to pilot - but that could just be DJI wording something poorly) if the AC may RTH or land outside those battery pilot settings in the app?

I thought at the time (and my view hasn’t changed) the responses you received with respect to the critical battery level setting were probably incorrect.

What I can say with certainty is that all my phantoms have commenced autolanding at 10% (when set as the critical setting). This has been demonstrated with the 3 and 4 on more than several occasions to be consistently demonstrated.

 

[sar104]

This issue is still an area of uncertainty for many (me included). I haven’t flown down to my critical battery % in recent times but from memory (set at 10%) my phantoms would always try and land at this point. Low battery warning will always issue at % value set in go and is a user selectable information only alarm. Auto GO home (if enabled) will initiate based on distance from home point and determined % to make it back (presumably the FC determined value you have informed us of). It seems the real unknown is behaviour at critical- specifically whether it may initiate above 10% (or higher value set) with increased altitude and whether you might fly down below 10% (default minimum) without auto land commencing.

I think I can clear up all those uncertainties. SMART_BATT:land% always starts at 10% at zero altitude - the FC's target is to be on the ground at 10%. It's independent of your critically low battery setting - I've tested with that set higher and it makes no difference, as expected. As the aircraft climbs the value goes up, also as expected. The graph below shows the SMART_BATT:land% as a function of altitude for a Mavic (I don't have the exact data for a Phantom).

 

[With The Birds]

I think I can clear up all those uncertainties. SMART_BATT:land% always starts at 10% at zero altitude - the FC's target is to be on the ground at 10%. It's independent of your critically low battery setting - I've tested with that set higher and it makes no difference, as expected. As the aircraft climbs the value goes up, also as expected. The graph below shows the SMART_BATT:land% as a function of altitude for a Mavic (I don't have the exact data for a Phantom).

View attachment 106938

Thank you- explains why my phantoms consistently tried to land at 10%, that was my setting and I was at or below 30m altitude (had allowed the phantom to drop to 10m or less hoping damage might be minimised if the battery switched off before I made it home.

 

[Bellaflys2016]

Dustin Dunnhil from YouTube flew a MP2 6 miles away and returned home and lended on 0%. I have no idea how he did that but I watched. I almost lost mine with less then 10% because it said auto landing and before I could do anything I lost contact and that was the worst 5 minutes of my life running down the street fearing the worst. Luckily it landed in an in the middle of the street at an intersection and everyone apparently just drove around it. I was seriously lucky.