Mavic Mini propeller guards Payload Mode causing Dronelink "Contol Override" error?
Trying to fly a test mission in the back yard and the last test mission unexpectedly gained altitude and ran into a tree, the resulting crash tore the gimbal from the rubber mounts and severed the ribbon cable. Replaced the cable and decided to install the propeller guards to prevent a similar disaster. Now when I fly the mission it stops half way with the "Control Override" error, if I start the mission again from that point it displays the "Unable to take control" error. When I fly manually with the DJI fly app with the propeller guards installed it briefly flashes up a message during flight that it has automatically activated "Payload mode" and place some limits on the aircraft (have not been quick enough to capture the message). I suspect this restriction happens during the mission causing the "Control Override" error. Does this make sense, any work-around other than taking off the propeller guards? Mavic Mini with iPhone 12 Pro.
Comments
4 comments
First, sorry to hear that you has a crash. When you say it gained altitude unexpectedly, are you saying you think there is a bug that caused the crash, or you just didn't understand what the mission plan was going to do? If you think a bug caused the crash, please email support@dronelink.com with the details.
On the control override message, we have an article that discusses several causes for this, and it sounds like we need to update it to include payload mode. I will look into it further but my guess is virtual stick is not supported in payload mode, just like it isn't supported in tripod or sport mode.
Update: I was able to fly a mission with payload mode enabled, so it must have been due to one of the other issues listed in the article.
I did review that article before posting, none of the items on the list seemed to apply to my short low altitude flight. I have seen other posts that mentioned logs, are there logs of the flight that would shed light on what caused the error? The crash seems to be caused by Dronelink getting incorrect altitude information from the SDK causing it to command the drone to climb when it is already at the correct altitude, will do some more troubleshooting on that issue.
https://support.dronelink.com/hc/en-us/articles/360052025254-Does-Dronelink-generate-flight-logs-
Please sign in to leave a comment.