On the return leg of an otherwise uneventful 7-mile Litchi waypoint mission my Mavic Pro was about a mile away from the launch point when it hit the brakes, paused, then resumed forward motion about half a dozen times before it came to a complete stop with the battery at 30%. Pitching the nose down with a fully forward right stick made no difference, and the drone remained stationary for long enough to become truly worrisome.
Suspecting strong winds aloft that weren’t apparent at ground level, I dropped the altitude from the RTH setting of 200 feet AGL, down to 160 feet, but the Mavic retained that stationary hover. With panic starting to set in, I then gunned the throttle and sent the drone up to 450 feet, before switching to sport mode and applying a full right stick forward to get the nose down and break that stalemate.
Finally, the drone began to move toward home, slowly at first, and then at a respectable clip of 40 mph, BUT while it was speeding towards me, the camera gimbal went wild as it has in the past a couple of times, with the recording toggling on and off numerous times until finally, the drone made an appearance at 450 feet AGL and 20% battery.
Obstacle avoidance had been left active for my flights thus far, but now that I’ve read several Litchi users’ warnings to be sure and disable all obstacle avoidance cameras when flying Litchi missions, I will ensure they are turned off from here on out. I’ll run another flight test with obstacle avoidance turned off along the same route if the weather is fine tomorrow morning, and write back here with my findings.
I must ask though whether any Litchi users that own Mavic Pro1 drones have encountered such random stops during waypoint missions, and whether simply disabling obstacle avoidance pre-flight resolved the issue on subsequent missions. I’ve actually seen this behavior once in the past, but in that case, lowering the altitude to just above treetop level released that parking brake and allowed the drone to resume the waypoint mission, leading me to presume wind was the culprit on that occasion.
Any thoughts on this subject that can be shared would really be appreciated. Today’s flight was a nail-biter for sure, and I am anxious to learn how to go about preventing any recurrences of such uncommanded stops during future waypoint missions.