G'Day, I was flying a 5 battery flight plan when the drone (phantom 3 pro) got to a certain stage and then stopped, it drifted aimlessly for a bit until I hit the stop and return to home button. On relaunch continued with flight plan until battery was exhausted and returned to home as normal, this happened for the next 3 successive batteries, if I return to home and relaunch the flight plan would continue. Any clues?
Please send us your log files so we can give them a look. This has been happening occasionally. The aircraft switches from NaviGo mode to ATTI mode for no reason. If you didn't accidentally flip the PAF switch out of F to A mode this is likely what a few other users have experienced.
DJI says it is caused by a loss of GPS signal which puts the aircraft in ATTI mode.
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
I am having this problem as well. By repeating many times I noticed that the Inspire would abort the mission immediately when it performed a quick yaw to change directions in its flight path.
She will yaw, seem to jiggle and then meander slowly to the south.
I recreated the error by piloting via DJI GO app only. Every time I perform a relatively quick movement via yaw (faster than you would pan while recording video) I get a compass error and the unit goes into ATTI mode for a few moments.
No doubt this why the mission aborts and this is not a Map Pilot error, but I'm very interested to hear other pilot's experience and solutions...
If it happens on a quick yaw it is most likely a hardware problem, usually an overloaded gimbal. You can try reducing the speed of the missing to minimize quick turns and see if that helps.
Update: resolved the yaw/compass error by calibrating compass and IMU in a field far away from metal objects, no mobile devices within 10 feet and used a level during IMU.
As of now the yaw does not trigger ATTI mode and the mission is not interrupted.
To be clear- this was not a Map Pilot software error.
Thanks for the update, Karl. We have had a few people with this issue and we will be pointing them to this thread for directions.
