New Beta version 2.2.0 (141)
Downloaded newest Beta for MA2 and tested today. Two mission's I’ve used before failed right after takeoff. Everything loaded fine and when I started the missions it would ascend and immediately fail and close app. Never even flew the approach and to first waypoint. Just about 25 feet up and failure. I Tried two different missions which have always worked with Beta 2.1.0 (137). Restarted my IPad before flights to refresh as I always do. The app closes so quickly I could not read the error message. I tried screen recording but it closed way to quick to see it. Tried several times with no luck. I wish I could give you the message but several attempts and it didn’t work.
Using IPad Mini 5 as always and I don’t believe it has anything to do with it. I even deleted the TestFlight and Dronelink Beta before updating it. If it’s on my end I would like to know any suggestions. Hopefully it’s not the newest release. I didn’t have any more batteries charged before it got dark to try older version and build. I may try the older version tomorrow but it indicates extremely windy here.
Try sending link to one of my mission. Seems like I have hard time getting them to work. Hope this does.
Thanks Jim.
Mike....
https://app.dronelink.com/wyldwestaz/mavic-air-2/plan/tymRMjzut1o9XdbaBiOC
Comments
15 comments
Thanks for the report.
Not sure if it's appropriate to piggyback on your post--I apologize if it is--but I just flew my first successful test on Mavic Air 2 and Dronelink 2.2.0 (build 141) yesterday. I was using a Galaxy S5 FE 5G and Android 11.
https://app.dronelink.com/pericles-s--nacionales/mapping/plan/LCzVTzpexmnfCl6Vx6H6/6San3Bh8gZvSWcC7dSDr
Just tried again with version 2.2.0 (141) on IPad Mini 5 with MA2. Just as it starts mission and ascends up the app closes and voice prompt says mission failed. No message or error since it closes immediately. I tried again on my iPhone 8 Plus and same issue. Then tried to go back to version 2.1.0 (137) which had work great overall. Same thing happens. It’s Really strange because the same missions have worked before on both devices. I’m not sure what else I can do at this point. I triple checked every mission to see if any red error issues popped up but nothing. Since it’s is doing the same thing on both devices I don’t believe it’s on my end. Even if it had any camera command issue it would always indicate the SDK error and never closed the app.
Any suggestions. Otherwise I’ll wait and see.
Thanks, Mike....
Can you post a link to the mission?
I Tried about 4 of my missions which have worked before. I’ll try sending one of them.
Thanks Jim...
https://app.dronelink.com/wyldwestaz/mavic-air-2/plan/XAAEnLA9Htq8VSUeG2de/3ejjjKlTcPMvbuKAhF8V
This short screen recording won’t really help but it shows how it just closes with no message .
https://youtu.be/aqXJuMy6yIk
Hey Jim, Any idea of what could be wrong ? Never had this happen until recently. Since it’s both devices and I know they are powerful enough to work I’m not sure why it keeps shutting down the app after takeoff. Again, I’m using IPad Mini 5th generation and IPhone 8 Plus. Tried the last two version, builds (137) and newest (141). Frustrating since it has always worked for last couple months. Not sure what else to do and hoping you can find something in the app which is causing the issue.
Thanks Jim.
Mike........
I ran that exact mission plan today without issues. It looks like you were using firmware 01.01.0610 and I was on version 01.00.0460, so I may need to upgrade to be able to reproduce it. Did you update the firmware recently? Also, I noticed the flight mode flash APAS before the screen recording ended. What it should say is Joystick. Has yours always said APAS?
The firmware I’m using just came out January 26th. I always update firmware when a new one comes available. It may be the first time I used Dronelink tho with this version since I don’t use it that often. If I remember correctly it always said Joystick. Don’t remember it indicating APAS this time but maybe it did. Not sure but it obviously has the obstacle avoidance bypass which is what that is obviously. I almost always have it setup to bypass obstacles, not just brake and I don’t remember seeing that. Maybe the newer firmware is affecting it somehow. I have no idea how software or firmware effects stuff like this. I leave that for the smart people like you.
Firmware Version 01.00.0460 was released in November and there have been at lest a couple more since then. If this could be an issue I can try to find an older version to downgrade. Unfortunately DJI doesn’t keep older versions in DJI Assistant 2 anymore. They stopped doing this many firmware upgrades ago.
Thanks again Jim. I’m sure your extremely busy working on all of the Dronelink stuff. Please let me know what may help when you can.
Mike........
I tried it with the upgraded firmware and it did not crash :(
In fairness I never saw the flight mode go through APAS. I saw GPS, TakingOff, GPS briefly, and then Joystick.
One thing to note is the mission plan attempts to set the shutter speed without setting the camera into manual mode first (so the mission plan was disengaging because of that, but not crashing).
Have you tried deleting and reinstalling the app?
Yes, the first thing I do is delete app and reinstall. I’ve done it at least twice. I Delete the Dronelink app, restart iPad, then download from TestFlight app. Puzzling since it does the same on both devices.
I don’t see a command to switch from Auto to manual camera settings. Usually I always set to manual in DJI fly app along with the ISO, etc. The Dronelink app seems to always use whatever settings were last set in DJI Fly app. I have it setup to automatically open the Fly app when I start up drone.
For now I’ll just remove all camera commands and try again to see if app stays open and it fly’s mission. If it stays open and works I’ll check Dronelink app settings before I start the next mission to see if it’s in Manuel camera settings mode. Maybe it somehow was switching to Auto which I didn’t notice. Still strange it actually closes the app though.
Thanks Jim.
Are you on a beta version of iOS?
As for the command:
Yes. Beta only app installed. Just tried deleting the app and reinstalling it again. I Shut down IPad first and restarted it then downloaded the Beta App version 2.2.0 (141). Copied the same mission and deleted just all the camera commands and just flew the mission path and It worked. Then I ran the same mission with all the same commands in original mission and it worked. Really strange Jim. I tried several different missions last week and even deleted the app and reinstalled as I stated in original post. I usually restart my device before any mission and even before using the DJI Fly app. I like making sure everything is refreshed. Usually no issues.
There is One thing I have noticed over the last couple months. After I fly and complete one mission, either on the second or third mission it will close the app right after take off. It seems that if I want a mission to not fail and close the app, I need to shut down my IPad and restart to refresh it. Then the missions work. Not sure if it just gets bogged down after few missions or what. I know this App uses a good amount of resources and power but I was under the impression the IPad Mini 5 should work without issues overall. Your a lot smarter than me with this stuff but, I do know that computers and programs, software etc, can do things for unknown reasons sometimes. No such thing as perfect.
Thanks for your time Jim. I’ll just continue to try and make sure everything is either new, refreshed, or restarted before use and hope it continues to work great. Your personal efforts to assist me is really appreciated.
Mike.......
On the fly CIRCLE.
Hi.
1. Is it possible to move the "Mark" button to reveal a description? (You can see in the picture 2)
2. After clicking "Mark", GPS coordinates also overwrite content (photo 1).
Smartphone Xiaomi Redmi Note 8 Pro.
Thanks for the bug report. In the future please post to a new thread.
Ok, tnx.
Please sign in to leave a comment.