4.9.0 (284)
Tried the new Beta 4.9.0 (284) and there are two issues using my MA2 with iPad 11 Pro. First is the live feed is not working with my iPad. I can unplug the cable from the i Pad once or twice and it usually fixes the issue. This was an issue with 4.8.3 along with the paths not showing up on map but the 4.9.0 (282) fixed both with my IOS device. A total of 8 missions with that version on four different days without any issues at all with (282). The second issue is with the gimbal pitch. My mission had a -12° pitch set for the entire mission but it ran the entire flight at -4° pitch. I checked the plan and it was all set up correctly. I decided to re-run the exact same mission and this time the gimbal pitch was at -16° instead of the -12°. So something was not setting the gimbal to the proper pitch. I figured I try (283) because I had no fights with that build. It seems this is where the live feed issues started because the same problem where I had to unplug and plug the cable back in to get it working. I ran the same mission again and the gimbal pitch was correct for the entire flight. I went back to (284) one more time and ran the same mission twice and had the same live feed issue but this time the gimbal pitch was correct for both flights. Not sure why on the two other flights it was off but I’ll continue to test (284) and report back of any more incorrect gimbal pitch’s arise. Bottom line is (282) has been flawless and the issues started at (283) and now still present with (284) at least with iPad live feed. Hope that helps to narrow it down. Let me know if there is something you would like me to try that I haven’t already tested.
Comments
9 comments
Flew a mapping mission with it this morning with Galaxy Tab 7FE (Android 14) without any problems
Seems like I was only able to reproduce this if the RC was on and connected to the iPad and Dronelink was already running, and then I turned the drone on. FWIW, this is the same behavior in the current production version (4.8.3, 280), and every single build in the 4.9.0 beta (per my testing at least), so isn't really a regression. Going to add it to the backlog and not hold up 4.9.0.
Hi Jim. It’s not that important but that is different than the way I power up everything. I always power on both controller and drone. When the controller is powered on it automatically opens the DJI Fly app with my MA2. Once ready and no errors are reported I then close the app and open DL. I have never opened the DL app first before powering on either the drone or controller as it is the last thing I do. I am aware of this same issue which started with 4.8.3 as I have mentioned. However, the version 4.9.0 (292) which I mentioned has worked without any problems on all those missions. So at least for me I have had no problems using that build. If that helps to see if something is in that build which is different then great but if not it’s no biggie since I know how to get it working easily. Anyway, I’m sure you will look into this for future fixes. If any strange incorrect gimbal problems arise again I’ll advise you. Thank you Jim, I always appreciate all the work the DL team does. If any way I can help to test anything please advise.
Mini 3 Pro, RC-N1 with a Samsung S20FE5G phone, DL had been working fine with previous version as recent as last week. Upon getting the must update to 4.9.0, I did the update and now the drone will not connect. I follow the start up procedure posted above by Mike , connecting to DJI FLY with no issues. DJI FLY is then force stopped, opening Dronelink 4.9.0 (284), but the drone does not connect. I've done multiple reboots on the phone, controller and drone, but no change as it will not connect.
Hi J. Should not be any issue as far as I know. I don’t have the Mini 3 but there must be something you’re missing because connecting issues are the same. I know many say they force closed the DJI app but about 90% of the time it wasn’t actually done properly. If you click on that message in the DL app it will take you to the DL article on why it’s not connecting. Force closing as per the instructions, granting all permissions, unplugging the cable from the device and then back in are just few common ones. Read the entire article and pay close attention to the one on Force Stop app. You may try deleting the app then installing the APK again and try. Other than that I haven’t seen anyone else reporting this. Good luck and advise if still an issue after checking everything.
https://support.dronelink.com/hc/en-us/articles/360052025194-Why-is-Dronelink-unable-to-connect-to-my-drone
Hi Mike, I tried the link you posted, confirmed all settings, but found nothing amiss. I re-downloaded the 4.9.0 update and re-installed it and got my S20 phone to connect to my drone. My Samsung Tab6 is another story. I tried all that I did to get my phone to connect, including trying the .zip file vs the package extract, but no dice. Such a frustrating experience, I finally get the DL app working on both devices then a new update comes out stating it now is fully supporting the Mini3 Pro and then I have to go through the entire process to get them working again with a 50% success rate. It shouldn't require this much from the end user to do a simple update.
There must be something being missed or a wrong APK. If you have multiple APK’s on the Tab 6 I suggest first removing all of them from the device and delete any Dronelink app you have on it. Then go to the Dronelink download page and install it from there and see if that works. It should work but sometimes it’s a missed step or possibly the APK file.
https://www.dronelink.com/download
Thanks for this Mike. The new version was named "Dronelink DJI" vs the old one named "Dronelink" that added to the confusion. After a couple of uninstalls and reinstall, deleting the old DL app, 8 now have the Tab6 running Dronelink DJI. All good now.
Cool. If you need any help with a plan set up or anything just ask. Fly away and enjoy.
Please sign in to leave a comment.