Dronelink DJI version 4.5.1 (248) DJI Mini 3 Pro
Tested this build as of today, no anomalies detected other than previous reported IMO. However I've posted an inquiry to Airdata UAV support about the interpretation of flight logs generated over MSDK v5.3 for both .txt and .dat format. Lets see what feedback we'll get....
Comments
8 comments
👍
I tested this version on my RC Pro and it was unstable. The display kept cycling from connected to not connected and the controller could not maintain a stable connection. I did not even risk a take-off. When I switched to the Fly app everything was back to normal. I was surprised as the previous build was much more stable on the RC Pro.
I just noticed that there is a new build (249) so I have downloaded it and updated the app and hopefully will have some time to test it in the next few days.
Chris
Sounds like you had DJI Fly running in the background.
No, pretty sure it wasn't. I swiped up to close out Fly or hit clear all to shut down all the apps so that only Dronelink would be running.
One of the issues that I have is that I use my RC Pro to fly multiple drones so I need to use DJI Fly select the Mini 3 Pro if I didn't previously fly with it to load the correct firmware as Dronelink cannot do this so I am forced to launch the Fly app before running Dronelink in many cases but as I said above I am pretty sure I shut it down before launching Dronelink.
Chris
Sadly, this is not enough, the process is described here.
Thanks Jim, I was not aware of that as I am a long time iOS user and swiping up on iOS shuts down the App.
That was likely my problem then. I will make sure Fly is Forced quit next time on my RC Pro before I launch Dronelink.
Looking forward to testing some more as soon as it stops raining.
Chris
Update on flightlog format from DJI MSDKv5 -> DL -> AirData UAV.
From several flights the appearance of logs seems not correct. They're all about the same interpretation in AirData regardless of upload .TXT or .DAT
However flight logs via MSDKv4 and Mini 2 is flawless.
Hence my understanding that there's a general issue with data format generated from DJI rather than AirData interpretation. Here's the feedback from AirData support:
"Hi Mats,
I have an update regarding your flight log from the Dronelink beta.
The engineering team informed me that the specific log you mentioned is broken.
It seems to be the only affected log. This may just be an anomaly.
Have you been able to upload other flight logs from this app?
Thank you again for reporting this. Please let us know if you require any additional assistance.
Best regards,
Tom"
Ran test flight today from my RC Pro and followed the procedure above to force quit DJI Fly linked above by Jim (thanks Jim) and it solved my problems with the display cycling. Dronelink launched and ran smoothly. I was able to run a small map mission and a pano mission from the OTF prompts. The pano option in the menu where you can choose photo, video etc still does not work. It does nothing. Neither does the 48MP mode seem to work either. Other than that everything seemed to be working quite well. Still have some more testing to do when it stops raining but overall Dronelink seems to be working quite well on the RC Pro controller.
My log auto synced to my AirData account but pretty much all of the fields were blank including the flight map so it was useless. I had to manually locate and and sync the DAT file to recover most of the flight data and then fill in the rest manually (aircraft type and battery).
Chris
Please sign in to leave a comment.