We operate 7 DJI Phantom 4 Pro V2.0 drones. Each one has a dedicated tablet device that runs the drone software (Samsung Galaxy Tab A7 Lite, running Android v12). We are using Ctrl+DJI (version 1.9.10) and Pix4Dcapture (version4.11.0) to plan and execute automated flights. We also run DJI GO 4 (version 4.3.52) to perform basic maintenance - such as compass and IMU calibration.
Two of our drones are currently experiencing a situation where a mission is planned, passed to the drone, the drone launches, flies to the start point, orients itself for the first run of photos and then stays in that position, ie: the mission itself does not commence. The status on the pix4D screen says “Going to mission…” and the drone does not switch to “Flying mission”. We end up terminating the flights (after giving 5-8 minutes for the situation to self rectify - we’re optimists) using the RtH function.
"a mission is planned, passed to the drone, the drone launches, flies to the start point, orients itself for the first run of photos, and then stays in that position, ie: the mission itself does not commence. "
It seems like an issue between the drone and our app? Do the devices used to fly those two drones happen to be Andriod devices? Sometimes the drone manufacturer’s original app is not selected as default if there are multiple image acquisition apps in one device.
I tried to fly a mission again today and took a couple of screen shots of when the drone arrived at the start of the mission. These two shots were taken a minute or so apart - and the drone was just hovering, aligned with the mission flight line but not commencing the mission.
This is the first shot, when the drone had just arrived at the Start point.
We also had the same issues with a Phantom 4 Pro. Usually if I brought it home and re-started everything I could get it to work. Sometimes the message would also say “Waiting for interaction” or something similar to. I had asked Pix4d multiple times if there were issues and the most common answer was that there was a problem with the drone. We also had more issues with the drone continuing with the flight and ignoring controls with eventually ended in the drone crashing. Still not sure of the exact source of the error as all checklist were followed on each flight.
These cookies are necessary for the website to function and cannot be switched off in our systems.
They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences,
logging in, or filling in forms. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site.
They help us to know which pages are the most and least popular and see how visitors move around the site.
All information these cookies collect is aggregated and therefore anonymous.
If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partner (Google).
They may be used by Google to build a profile of your interests and show you relevant adverts on other sites.
They do not directly store personal information but are based on uniquely identifying your browser and internet device.
If you do not allow these cookies, you will experience less targeted advertising.
