New user - MA2 Beta
Apologies up front, this could be entirely user error...just starting with Dronelink.
I am using MA2, setup a mission to fly vertically 100 feet, horizontally about 200 feet, then drop down to 35 feet and do a mapping of a solar panel.
I had to bail out of a previous mission when my drone appeared to be flying into a tree...it got very close, and maybe this is normal behavior?
Above mission, flew correctly until it needed to descend to 35....it did descend, and then just stopped. Was unable to pause the mission and only way to get out of it was to hit RTH on smart controller.
Thank. you
Comments
3 comments
Flying into an obstacle is definitely not normal behavior, but at the same time the drone will do what you program it to do. Did the drone do something different than what the mission previewer showed you? Can you share a link to your mission plan and tell me which part of the mission preview is unexpected or behaved differently in the real world?
It was definitely poor planning. The tree was higher than the altitude I had indicated for the mapping. Unfortunately I had already modified the mission plan. Again, apologies...new to Dronelink, I will be more diligent with my feedback in the future. Very happy to have someone addressing the MA2 for this type of functionality. My first impression was that the mission disabled sensors and was overriding "normal" safety...I did not specifically program for that however.
As you say, it will do what I program it to do. The more concerning part was that it froze and would not allow me to pause the mission. Completely unresponsive except for the RTH button. All worked out fine in the end...
Assuming you were on Android, we just fixed a bunch of issues with app performance / hangs. Having said that, beta or not, you should always be prepared to take control.
Please sign in to leave a comment.