@Matt: Let me know if it is better when 2.0.5 is released! …
As I’ve deadlines to stick to for my uni dissertation and need to gather data, I was wondering as Nexus 9 has problems can anyone suggest an alternative Android device which works with P3P and is as cheap as possible to keep things moving until 2.0.5 is available?
ahí una nueva actualización de Phantom 3 Professional Firmware v1.4.0010 , esta versión sirve para pix4d??? se puede usar ???
hí a new update Firmware Phantom 3 Professional v1.4.0010, this version serves to pix4d ??? It can be used ???
My Dji go app showing message to update p3 pro firmware update. My P3p has beta firmware of 1.4.0001. I cannot update to current version. Is there any way I can update to current firmware version from beta?
Have to say everything is definitely heading in the right direction. Running latest firmware on P3P, latest Capture app on a Samsung Galaxy Tab A, Android 5.02 Flew 2 sites last week. One was 65 acres, took 6 flights, all grids were red (too large), just ignored it, landed with 18-20% battery. Picture numbering was mismatched with p4d files so didn’t use the p4d files, 1460 pics processed on Amazon Web Service instance with gpu however the driver was not up to date and couldn’t see anything in the ray cloud, downloaded and opened on my machine, pretty impressive and accurate. Some of the site already had been surveyed, matched pretty well with the point cloud. I used a Trimble R10 GNSS receiver to set 12 GCPs. Second site was 30 acres, 2 flights, again grids red, ignored, landed with 18-20% battery. Set 6 GCPs. And again picture numbering was mismatched with p4d files, this time I renumbered the pics in Adobe Bridge and was able to use the p4d files. Processing now, everything seems fine. My biggest request at this time would be to somehow in the capture app to say this is the area I want to fly, this is the largest grid I want to use and then the app creates how ever many missions it takes to cover the site. I fly mission 1, land, change battery, app automatically moves to mission 2 and so on.
A point cloud animation of the 65 acre site can be seen here http://1drv.ms/1Ky0GDG A few more requests, 1) The ability to save missions, for instance this site will be flown 3 more times over the next year, it would really be helpful to load my previous flights. 2) The ability to input lat/long or coordinates for either the end of each flight line or the 4 corners of the grid, most sites I’m on are undergoing some development and no longer match the map making it harder to setup my grids. 3) Compass calibration in Capture so that I don’t even have to open DJI GO. 4) It would be nice to have a radar in one of the corners showing the home point and which way the drone is facing.
@Martin: I will check for the first waypoint then. For the UI, we are working on it too, so I will just add your request to the current work!
@vicente: Capture supports 1.4.0010 
@Giljae: Did you use the firmware from http://www.dji.com/product/phantom-3/download?
@Mike Racz: Fellow surveyor here that has been testing as well. I have not had chance to test on the latest firmware and versions of the software but did over a month ago. I set GCP’s with our test site using a Trimble R8 on a VRS network. The elevations in the data seemed to be with in .2 of a foot. How are your results looking?
@Support
I’m having a lot of trouble uploading my missions to the cloud. As a result I have been using the files directly off the drone and I feel like the bad GPS inputs directly on the files are making my projects look horrible. Quiet bad output, no way I could approach a customer with my current models.
Is there a way to do this manually without uploading and downloading the files from the cloud? Can I import the mission with the more accurate GPS location somehow? There needs to be a way to do this without relying on upload/downloading the files for every project. Takes way too long for projects with 1,000+ photos.
So I had this massive area to fly and capture vertical imagery and decided to use your app. I had tested it twice before in wide open areas so was confident enough with it. I calculated that I would need 10 flights to cover area and had everything planned out. Weather was perfect wind was 3m /s. The first 3 grids flew flawlessly and I had the slave controller set up with the DJI GO app running so I could see al the waypoints appearing on screen plus I could change camera settings to RAW and change shutter speed on the fly !!! The fourth flight started perfect with the Inspire flying straight up to 100m and then to waypoint 1. About half way along line one it seemed to brake sharply and I could hear the motors rev even though she was 100m up and about 250m away from me. I put it down to her trying to keep at 7m/s speed. Second line flew perfectly and then on line 3 it started to do it constantly. Like as if someone was constantly forward and backing on the right stick. The bird looked really unstable and the tiltmeter was showing blue going in all directions. I had to cancel the flight and bring her down manually. No issues here. Job cancelled and she hovered perfectly and I brought her home totally as expected. Checked all props and locks etc and re-took off and completed this flight manually as only had a few more photos to capture.
Moved location to area 4 and again, this time half way along line 1 the same thing, all over the place back and forward. Had to fly grid manually. Fifth area decided to reduce bird speed to 5m/s to see if that would make a difference and the only difference was the jerking didn’t look as extreme and the bird didn’t look in danger of flipping or a prop flying off !!! Ended up then flying all remainder of my grids manually without a flaw.
Hopefully someone else has seen this and either has a solution or its a known issue with the DJI waypoints and will be fixed. BTW all compass calibrations etc were done.
Thanks
Paul
Hello Pix4D Support
Yesterday I took the first flight using Capture application. My settings in the application are: height 30m, overlap: high
Manual take-off and up to 25m high, start the mission. The first line flew well after about 5 minutes (2/3 of mission) the Phantom entered in autolanding without knowing why, after landing i saw battery remaining 65%.
After landing manually, i change the battery, take off again and restart the mission. Again came the same problem …
Do you know why this problem occurs?
Phantom 3P with 1.4.0010
Samsung Galaxy S4
DJI GO App disabled.
Thanks,
Adrian
@ Adrian Dragan, my guess would be the wifi battery seems low so maybe the capture app figured you would lose connection (and no pictures would be taken) before the mission finished so flew home, again only a guess. But I would like to see the capture app start continous picture capture if the connection is lost.
@ Andrew Giles I haven’t had time to do a thorough check yet, I want to classify the terrain points, bring it into cad, create a surface and do a cut/fill report between that surface and the conventional one. I did do several spot checks and I was within a tenth horizontally and vertically, that was just clicking on a point in the cloud, several times if needed till it was where I wanted on the pic (for instance corner of catch basin).
My Equipment:
Phantom 3 Professional with 1.04.0010 firmware
HTC One M8 with Capture 2.0.4
After getting things working the Phantom flew the grid perfectly, with far greater accuracy than I could do manually, even with about 10 mph of wind. However, I ran into a few issues:
First issue: I had the DJI Go and Drone Deploy apps installed on my phone in addition to the Capture app. After plugging the phone in to the remote and starting the Capture app, after opening the Grid Mission I would get a box popping up asking something along the lines of if I wanted to start up DJI Go automatically when plugging in this USB device. I would click “cancel” but the app would exit the Grid Mission page and go back to the main menu. This happened several times so I uninstalled the DJI Go app, but the same thing happened with the Drone Deploy app so I uninstalled that one too and finally I was able to enter the Grid Mission page successfully.
Second issue: I initially tried taking off manually with switch in “F” position as per the instructions, but the aircraft behaved erratically. The first time, as soon as the motors started they immediately revved up and the aircraft pitched backwards, causing a prop strike before I could shut it down. The second time, the motors increased power slowly even though I wasn’t increasing the throttle on the remote control, so I again shut down the motors. This was after pressing the “Start” button in the app but before pushing the “Press and hold (3 s) to takeoff” button. I found that if I took off in “P” mode, then switched to “F” and started the mission, things worked fine.
Third issue: Running into an odd issue with processing, and I’m not sure if it’s being caused by Capture or by Pix4D itself. I manually downloaded the images from the SD card to my computer and started a new project in Pix4D. The initial Quality Report shows an odd warp in the DSM even though I was flying over a flat field. Camera Optimization shows an alert of 81.53% relative difference between initial and optimized internal camera parameters. Looking at the RayCloud, it’s apparent that the camera points are far closer to the surface than they should be. Note that I did not use GCPs. Not sure what’s going on here, but here’s a link to the Quality Report:
https://drive.google.com/file/d/0B1IaV2z0T5cfZTl0bEJFRmFTT2c/view?usp=sharing
@Scott I’ve had all 3 issues on the inspire. If I start motors with the switch in f position they start up lively and the craft then shuts down. Weird !! Same with the apps so I’m using an old nexus 7 with just the Pix4d app on it and it works fine (except from my post earlier about erratic flying). Thirdly try running the processing with the leading parameters ticked in the matching options (I think) that will solve your optimisation issues oh and set GPS accuracy to low on photos.
I have done all the steps as defined for Inspire 1, but the Press and hold to takeoff button still does not work. All my boxer are ticked except for low battery level, but I select it and tick the ignore box. The other problem is Ground Station Connection Failed, should this be ticked? is this why I can not start the mission? It looks like the samples also has this?
I have the Galaxy S tablet running DJI Go app and Capture app latest version and firmware 1.04.0010
@ Anton van Wyk
One thing Anton, make sure the DJI Go App is not running
@Jonas
I am experiencing the exact same problem and I have the exact same configuration. I am using the Galaxy Tab S, firmware 1.04.0010, latest firmware on RC (1.3.2). It appears the issue may be hardware specific, or probably operating system version specific. Jonas, ca you confirm what hardware your development team tests with and which Android versions they test with?
Now I also have a Galaxy Tab 4, I may try that and see if I have better luck. If I do, that would point towards a hardware/OS version issue.
I am still having troubles with the capture software on a Nexus 9 Tablet, also I see there is a new Beta firmware out for the Inspire (V01.05.00.11) does everyone recommend avoiding that for the time being or will this along with the new SDK help solve some of the issues and so would be work upgrading to?
Regards,
@ Paul Moran
If I understand correctly, then during the flight mission, you can exit the Capture app and open DJI GO app? and Shooting does not stop?
@Jonas @Pix4D Support
Some good news, I was finally able to get the Capture app to work with the Inspire 1. I had to completely uninstall it and delete the data associated with it.
I have successfully flown the Inspire 1 with capture app with the latest beta firmware 1.05.0011. I will try the P3P next.
I finally got everything working but it kept saying the mission grid was too large. At first it said maximum size was 250m x 200m which is very very small. But I still changed it to 240m x 190m which is smaller than the maximum and tried again. Then the error again said it is to large and the maximum was size was 220m x 175m. Even smaller. So I cancel again and went back and made the grid about 150m x 100m. Then it gave the error again and said the grid was too large, again. I still had 87% battery and the mission would have taken about 3 to 6 minutes. Everything else was green check. Can you please allow for a MUCH larger grid. Thank you.