Dronelink crashes when taking High res pictures (Mini 3) (4.7.0)
I have been testing Dronelink beta since version 2.6.0 and I have just updated to 2.7.0 today.
I am using my DJI Mini 3 with a Xiaomi Mi 11 lite 5g.
What I noticed is that since the latest update, the dronelink app gives "cannot take picture" errors, and crashes more often when taking multiple high resolution pictures after eachother.
It feels like the app does not wait long enough for the picture to be stored, before attempting to take the next picture.
An example for this is:
I created a plan, where you taken an AEB picture, followed by a High res picture, followed by an AEB picture, followed by a high res picture etc.
Reason for this is to shoot a panorama with both AEB and in High res, to compare results.
First attempt, it took an AEB picture, followed by a High resolution picture followed by another AEB picture.
When taking the last AEB picture, the app crashed.
Second attempt. it did not crash at the last AEB picture, but instead stopped the mission with a message stating a picture could not be taken.
Third attempt, app crashed again.
4th attempt, mission stopped with the error message again that it could not take a picture.
I understand that there are issues with the DJI SDK that are out of your hands, but it feels like this one is unrelated.
When I receive the "mission stopped due to error" I can just continue the plan, and it goes back to where it previously failed.
I never received this error before on the previous version (2.6.0). (outside from the app crashes).
PS. I was wondering if any of your devlopers have been in contact with DJI yet about the app crash issue.
I noticed that the issue (link: https://sdk-forum.dji.net/hc/en-us/community/posts/17495566595609-mini3pro-with-msdk-5-3-crashes-app-from-time-to-time?page=1 ) has been stale for 28 days.
Is there anything we as a community can do, to help speed this up?
Comments
2 comments
The only thing that changed between the two builds was upgrading from DJI SDK 5.3.0 to 5.4.0, so if there is a regression, sadly it is in their code.
Can you post a screenshot of the error?
We communicate directly with DJI on a weekly basis.
Keep complaining on their forums.
Thanks for the fast response Jim McAndrew.
I will see If I can re-run the mission somewhere this week, and make some screenshots.
Please sign in to leave a comment.