Phantom 4 pro error when resuming flight
Lately when mapping with our Phantom 4 Pro it works perfectly until something stops the flight, ie. too far off course/ taking manual control for any reason or changing a battery.
It will fly back to the last known point, then it throws up a camera will not start error or camera will not focus error.
This happens whether you try to continue the flight from midair, or even after flying back, landing, rebooting everything then attempting to continue. It is most inconvenient when this happens on a job site.
Have been doing this work for a long time and have tried everything possible I can think of.
Any assistance appreciated however this appears to be a bug with DL and the P4P. Samsung Galaxy Note 10+ is the interface.
Gareth
Comments
7 comments
Can you share the mission plan that is causing the issue?
Sure will upload when I get back in the office. Just FYI this happens on every mission plan with the P4P. Am testing our Spark and Mavic Mini today as well to see what happens and will report back.
Cheers
Hi,
Apologies for late reply. Following onto the above, we have since tried to replicate the issue with 2 other models of DJI UAV and haven't had any issues. With both Android and Apple devices.
Please find attached the link to the flight :
https://app.dronelink.com/sky-map-nz/mission/ViP5Jv1KGQTL5MjAUxkA
or if that doesn't work:
https://app.dronelink.com/sky-map-nz/public/plan/3WmPN9D2A9oeKkPCHsQM
Attached is screen shot showing one of the 9 errors of this flight, they alternated between "Camera start failure" and "Camera focus failure"
As said this only occurs if the flight is interrupted, works perfectly from the start.
Thanks,
Gareth
Also to confirm, this has happened on multiple flight plans - the above was simply a test where it failed again.
It did not use to do this when we first started use DL.
Can you try to reproduce it on the latest beta (158)? I removed the auto-focus commands from maps.
Thanks Jim,
Weather finally gave us a chance to test today and it worked as it should with no error repetition.
Seems to have solved that.
Cheers
Great 👍
Please sign in to leave a comment.