@Bruno: We will think about that. Maybe we could have something in the advanced mode.
@EVANDRO: And you are using the “high overlap” option, right?
@Lene: We could upgrade our drones without problems =/. Maybe you should try DJI’s support. Let us know when you have news!
@Keenan: That sounds bad. Do you have the “Drone is not flying” message? Did you update to 1.4.0010? 1.4.0005 should still work, by the way…
@Joseph: Capture 2.0.4 supposedly supports the latest public firmware (that DJI Go asks you to install). At least it is working on all our drones. I still don’t know if somebody else could make it work.
@Martin: Difficult to debug without having the tablet, actually. Even more if the App does not crash “properly” (freezes are not easy to understand). How is the App when you don’t plug the USB cable at all? I observe that mine is slower as soon as I connect to the drone, which might mean that there is something happening with the communication to the drone. Depending on the phone, the USB Accessory implementation might be different, too.
@Ted: When it always crashes like that, I have to kill DJI Go. Did you try doing this? Try to unplug the USB cable so that the phone is not recognizing the DJI accessory, then “swype it away” from the list of running apps, and also go to the “App Info” of DJI Go and hit “Force stop”. Does that help?
@Jonas. No I don’t have the drone is not flying message. I get thus with both the Inspire 1 and Phantom 3 Pro. I even tried two different tablets: A galaxy tab 4 10.1 and galaxy tab s
and both drones are on 1.4.10. Both controllers are on the latest firmware as well. Also I’m not sure if this helps but when I use the dji fo app, I can’t get into any if the intelligent flight mides either. Just the course lock
@Keenan: Don’t you have the same takeoff checklist as alex (see image above)? With the “Drone is not flying” message?
@alex: It says that the drone is not flying. If you click on it, it will explain that you should takeoff manually. We will try to make it clearer, but it is true that it is not intuitive. That comes from the new firmware, actually… Can you try to takeoff manually?
Well I have some good news… I factory reset one of my android tablets (Galaxy Tab S) and just installed the bare necessities that I need like Outlook, DJI GO and Capture, and it worked. I took off, and was able to start a mission. I don’t have a good reason why it suddenly worked… it just did
Overnight I was able to get the app to go into Grid Mission once. I had closed everything (powered all off) and then brought rc on, tablet on and p3p on.
I opened up capture and it worked, Yey! Now I closed all and tried again and poof, nothing, would not stay opened. Grid Mission would start and then die. I would make sure that it was cleaned out and try again, and it would come up and stay on little longer or little shorter amount of time (always less than 10 seconds) and then die again. Gave up at this point and went to sleep.
Something to note, when I plug the RC into the tablet, Android asks if I want to use DJI-GO or LITCHI and if so once or always. It never asks about Capture. When it asks, I clear the page and go directly to Capture and start it. And then select Grid Mission and wait for it to die.
I wish that I had found something solid that would repeat each and every time the same, but no luck.
I am standing by to try any suggestions they you might come up with and I will still be tinkering with it as I can.
@axel: We will try to make this clearer in the future releases. If the drone is not flying, then we cannot open the ground station. Usually, you should try to fix one error at a time, starting with the ones you understand. Then it should be the case that the weird ones (like the “groundstation opening”) get solved =). I hope it will work!
@Keenan: I would guess that you still had Capture 2.0.3 before. With your new install, you got Capture 2.0.4… Happy to read that it works!
@Ted: I really think it is linked to DJI Go. When Android asks for something different than Capture, you should *always* say “Cancel” if you want to use Capture. Capture will ask for that when you go in the Map View (by clicking “Grid Mission”).
Well done. I did exactly what your link showed and it is ‘now’ working. I did not fully understand / appreciate the significance of the “Force Stop” as compared to just using the app manager to get rid of it.
As soon as the rain stops, I will be out to test it. Yes, my luck, ready to test and now having some rain / sprinkle in Tucson. Go figure.
@Ted: Yes! That is not a good fix, I know, but that is what we have for now. We will try to improve that because it is extremely annoying! Let me know if you can fly!
@Jonas, I wish it were that simple, but I did have 2.0.4. I still haven’t tested the Inspire, only the P3P. I hope to test the Inspire tonight. I will let you know how it goes.
2.0.4 on the Nexus 9 also freezes without being connected to the RC. Mission planer opens but then map or satellite pictures get loaded really slow and at around 60% the tablet is dead and needs a forced reboot.
@Keenan: Don’t forget that you need to “ignore” the battery level for the Inspire 1. For that, enable the “Advanced mode” in the Settings, then in the preflight checklist, click on the battery line (that has the red cross) and check “ignore”. DJI will fix the battery level issue in the next firmware, normally.
I promise not to forget… So I was thinking about the whole mission way point limitation that you have to take off then you can start the mission. I have an idea that might be able to help… I hope. I am not sure how your developers implemented the take off part, however there is a take off method in the SDK called startTakeOff that is a part of the DJIMainController class. Can you call that? then upload the mission? Or were you already using it and DJI effectively disabled it.
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.