Maximum altitude reached after battery swap, 95’
I’ve spent the past three days trying to pinpoint the reason why my missions won’t resume after a battery swap. Drone ascends to 95’ and indicates maximum altitude reached and suggests to increase the max altitude. Max altitude is set to just under 400’ and I checked in the app which indicates the same. I’ve flown several missions to trying to diagnose the issue but no luck. The telemetry is indicating altitude at zero on take-off on each battery swap and 95’ when it fails.
I Refreshed the firmware on drone and controller and calibrated the IMU and compass. Tried again and after swapping the battery it stops at same 95’. I’ve shut down the app, drone and controller and started all back up. Resumed the mission but same issue at 95’. The only way I can finish the mission is to shut everything down including my iPad then restart. Once that’s done it will resume and complete the mission. I’ve done this three times with battery swaps and every time it fails resuming unless I shut down everything to include the iPad. I deleted the DL app and reinstalled Beta version 4.2.0 (228) and still an issue.
At this point I’m not sure what else to do. Haven’t tried with previous Beta versions yet. Hopefully you can find something in the Beta version I’m using. I can try a previous version to see if it works but thought I’d check with you first. I haven’t done any battery swaps for awhile so not sure if it is just this version. I haven’t seen any other post about this so seems strange. All the missions I ran where from 150’ to 225’ altitude and ran fine until the battery swap. Please let me know.
Comments
47 comments
What drone was this with Mike? Wondering if I can test the same scenario?
Opps, I forgot. MA2.
Would you mind posting one of the missions where this problem occurred? I would also like to test this.
Hi Nicolas. It’s not mission specific. It’s an issue when swapping batteries with any plan. I ran a few different plans and same issue occurs with any battery swap. 🤙🏼
Here is one of them I ran which I just threw together real quick just to test at home. This is a copy of the actual mission I ran.
https://app.dronelink.com/wyldwestaz/home-missions/plan/073h2grZbA31jFmX6NPo/upO0kQsww20nh0OiNd9t
So Mike, what you're saying is, if you start that mission (or any mission), and during the mission perform an RTH to change the battery (so for testing purposes turn off the drone and after a short time turn it back on again), when relaunching the mission the drone will only go to 95 feet?
When this happens is it on a mission you've uploaded to the drone or are you flying Virtual sticks, if the latter I'll give it a whirl with the mini2
Yes. It was a Normal battery swap without turning off controller or shutting down app. Just turning off the drone, put new battery in. Once ready to go I resume and it starts and ascends to 95’ and stops with the max altitude. It’s my MA2 so they don’t have onboard capability, just virtual stick. I thought of trying with my MM but way too windy today. Hopefully it’s not my drone but since it works at 150’ to 225’’ on first leg of any of the several missions I’ve flown to test it I don’t think it’s the drone. Never know though.
Ok Mike, I'll hopefully give it a go tomorrow for you, see if i can replicate it with the Mini2
Nicolas. Just checked Airdata which indicates after the battery swap the RTH altitude set to 141’ which is correct. The Max altitude gets set to 98’ which is strange. The DJI Fly app doesn’t even have a beginner mode switch for the MA2 which limits to (30m) 98’ but it seems like for some reason that’s what it’s doing. Really strange.
Max altitude was set at 397’ as it indicates in Airdata during the initial leg of the plan. After shutting down everything to include my iPad it sets to 397’ correctly again. It only happens after a normal battery swap and sets to 98’.
First screen shot is at start of mission. Second screen shot is after the battery swap. I’m not sure what the “Data Recorder File Index” is but it’s (29) with correct altitude at 397’ and (28) when setting to 98’. Not sure if this helps.
Thank you for the data that is very helpful! I just got back from testing your mission with a battery swap and I was able to reproduce the exact same behavior on my Mini 2 with iPad (Dronelink 4.2.0). We will continue to investigate this and keep you updated here.
Thanks Nicolas. That’s actually good to hear. At least I know it’s not me or my drone. As always DL is quick to respond and I’ll be waiting for a fix. 😬
Very cool that it is repeatable. Mike - it's not you! : )
Just tried this here in the UK and couldn't replicate it, bought it back several times, turned off and on the lasy occassion actually had to change the battery, flown with mini2, Samsung Galaxy Tab 7FE 5G and Dronelink 4.2.0, so this tends to point to something that affects it state side or with the apple devices
Thanks Martin for testing. It was only when the low battery triggered an RTH automatically for a swap and then resuming the mission. It may react differently when manually pausing, returning and then resuming. Thanks for the info and time spent testing. 🤙🏼 I’m sure they will get it sorted out.
Hi Mike, no problems mate, happy to help, the final execution was after an auto rth and actual battery change
🤙🏼. Thanks.
Just confirmation can't replicate on Android, mission accomplished
I’m going out in a few minutes to try the previous Beta version 4.1.1 build (227) just to see if it works. If so then I’ll just use it until they get 4.2.0 ironed out eventually for me. 😬
That sounds an idea Mike
Flew two battery swap missions. Download previous Beta version 4.1.1 (227). Battery swap worked perfectly as usual. Downloaded back to the 4.2.0 (228) and flew another mission with a battery swap and same problem at 95’ max altitude. Does seem as though it’s something with the latest Beta version. Maybe this will help to narrow down the issue. Again, it’s a MA2 using iPad. No big deal so I’ll keep using 4.1.1 (227) until a fix.
this just got me today on a mission flying with iOS
Definitely an iOS problem then, that's 3 of you that have reproduced it
Yep. One of the very few IOS have had. Just use the previous version as I did Tony and it should work.
And I had my kid run me my android tablet. What a morning.
Flew with M3E and mission kept failing.
Switched to M2P with Apple Mini Tablet...got bit on the battery swap.
Flew with M2P and Tripltek tablet with Dronelink, and all good.
I need to charge more or test more! : )
Lol…. Definitely not for the occasional hobbyist. From what I’ve seen over the last two years I don’t think most hobbyist use DL much. They probably don’t use more then 10% of what DL can offer. I’m still learning new ways to set up plans and new functions and how they work all the time. I probably only use 30% of what’s available.
I'm a hobbyist, and love digging around and seeing how i can do things, and when you start using Dronlink with other programs like google earth, things get really interesting, and this community is a great place to get and give help
I got a similar number of warnings "Maximum Altitude reached" when I swap batteries, with heights of about 30m reporting the same after an in-mission battery swap. It's happening regularly and this is on my MM2 using DL kernel 228. I could have sworn this was not present in prior releases. What I've done to work around it is switch to the native DJI App, manually fly to the height I am going to fly, and then switch back to DL, and then it's alright.
Looks like there is plenty of confirmation already, but I can also say that this morning I got the same error message. On DJI Mini 2 with iPhone 14 after a low battery auto RTH and battery swap. Cold and windy anyway so went back home and had leftover turkey.
As I stated in my other comment, version 4.1.1 (227) is working fine so if wanting to do battery swaps I’d suggest using the previous version for now. You can still use 4.2.0 (228) but if performing battery swaps you will more then likely need to shut done and restart everything to include your IOS device. Once you do that you can go to the missions tab and click to resume it just like any other partially flown mission.
This should be corrected in 229.
Thanks Jim. I’ll be waiting for the update.
Please sign in to leave a comment.