Just an FYI I have ran the Current version with my Inspire 1 and it is getting better every release No more spinning, able to fly larger missions. The only question I have is why is my relative difference between initial and final focal length so large Like 100% to 200% I have done a ton of manual flying and processed thru Pix4D and I am usually under 1% and almost always under 5% What causes this?
I have a phantom 3 advanced and nexus 7. App keeps crashing before I can takeoff. For the second time pix4d bit of help. Thanks
@DDS CAD: We will allow different altitude for advanced users in a later release 
@Justin Adams:
- The sync is not stable at all, you might want to disable it in the settings
- If the pilot app takes over the device, you should disable this in your Android settings
@Justin Cooper: -
- Okay, I’ll look for that.
- Thanks for the suggestion!
- We plan to do that!
- Probably, once Capture is stable for the new drones
- In 2.0.2, you can already do that. It is just that the feedback might be red, but that’s
all - I will look into that!
- You cannot be connected with both apps at the same time.
@Martin:
- The SDK does not give us the name of the images until we download them, so we have to guess
=) - About the 2 folders: what are their names? What is the name of the first and last image of
both folders? That is interesting for guessing the names
- We would like to implement the splitting functionality in the future, yes!
@Bill Jackson: Awesome! The camera model is maybe not correct in your version of Pix4Dmapper.
Please contact support@pix4d.com for that!
@mal: Phantom 3 Advanced is still an alpha, so you probably need to wait for the future releases.
Sorry for that, we are doing our best!
@ Jonas
See the details about 2 missions, their file- and folder-names:
Session 1 started at around 5.30
- Mission_00001.p4d lists DJI_0001.JPG to DJI_0012.JPG which seems right but:
- The 12 files that match this creation date are named DJI_0970.JPG to DJI_0981.JPG in folder 100MEDIA
Session 2 started at around 6.05
- Mission_00002.p4d lists DJI_0013.JPG to DJI_0047.JPG which seems right but:
- The 35 files that match this creation date are named DJI_0982.JPG to DJI_0999.JPG in folder 100MEDIA and DJI_0001.JPG to DJI_0019.JPG in folder 101MEDIA. To be able to use them, I had to rename them using batch rename of Adobe bridge after I sorted them correctly, using the creation date.
One more observation:
Pitch angle listed in .p4d file does not match actual pitch angle at which pictures have been recorded.
Difference is about 45°.
.p4d file states that pictures have been recorded, nadir, with an angle of almost 90°. Actual angle has been at around 45°.
That would be a good feature (user defined flying height).
I plan to use the uav to map roofs for renovations etc. Not houses but large building such as school. It would be great to be a blessing to fly 10’ above such roof to get some really crisp images and a good accurate model or the roof and insulation.
@DDS CAD: noted
@Martin:
- The IMU is wrong in 2.0.2. It is already fixed in 2.0.3!
- Thanks for the names, we will work on improving that!
How or when would we get 2.0.3?
@DDS CAD:
Update
I completed reset my Nexus Device and only loaded the app and ess apps. DJI Pilot was not installed and it appears that it’s working with the following issue:
When you select to see camera view nothing comes up for viewing.
I have not attempted auto flight until we get a stable build.
Thanks,
I too am having the issue of the app crashing. Running on Galaxy S4. App operates fine until I toggle to the P3 (beta) for aircraft choice, then the app freezes up and eventually hard-crashes.
Actually, just tested the same scenario with my Galaxy Tab and as soon as you select the P3P (beta) as an option, the app freezes and hard crashes. It appears to have something to do with the DJI Pilot App being installed as well. If it is running in the background, it will cause the Capture app to hang when assigning the P3 (beta) profile. So, forcing the Pilot app to quit seems to free up the Capture app.
New beta tester here, using the P3P. Normally an iOS user, but found a Nexus 7 II to try this with.
When I first attempted to start a grid mission, I had the same issue Justin Cooper noted: everything had a green check mark except the Ground Station, which said it failed to connect. I followed Justin’s advice and did a “Reset” of all my settings in the DJI Pilot app, then power cycled drone, transmitter, and killed the Pilot app. That fixed it, as he said - all green check marks and was able to start the motors (left the props off because it was dark here before I got to this point).
This made me wonder which of my settings in the Pilot app was the problem. So I power cycled everything again and went back into the Pilot app. I tried turning on the various non-factory settings I typically use one at a time, to see which one was breaking the Capture app’s ability to communicate as a ground station. The offending setting turns out to be enabling IOC. When IOC is enabled, Capture can’t connect the ground station. When it’s disabled, Capture gets all green check marks. This sort of makes sense to me because IOC makes use of the F position on the P-A-F switch just like Capture does. Having IOC enabled probably keeps Capture from being able to use that same mode on the RC controller.
This can be a particularly tricky thing to diagnose because sometimes the Pilot app does not correctly report that IOC was previously enabled on the drone. As with several of the other user settings, the drone can remember how something was set on a previous flight, but the Pilot app does not correctly poll the drone for all of these settings at start-up. Thus, the app may show that IOC is disabled when in reality it is still enabled from a previous flight. My solution to this, if I’m not sure what state the IOC is really in, is just to toggle the IOC enable/disable setting in the Pilot app a couple times until I’m sure it’s really off.
Hope this helps! I’m going to be giving this beta of Capture a really thorough testing next week and the following week, using it to map some (inactive) lava flows in Iceland. Will report back on things that worked and didn’t. One thing I can already tell would be a huge improvement would be better control over the map cache. We’re going to be camping on-site for our field work, in an area that has no cellphone data coverage. This means I’ll need to try to load up the cache with map data for everywhere we’re going to be over the two week period. Just scanning around within the app is a really difficult way to load the cache, and there’s no control over what gets kept if the cache fills up. I’d much rather have some way of drawing regions of interest for the map data I want to cache, maybe also with a way to choose the map zoom levels I’ll need. And I’d want the cached map data to stay on my tablet until I decide I’m ready to delete it.
Thanks for what looks like a very promising start for this app with the P3P!
Jeff
@Martin: Most likely next week
@Tripp: We are still correcting bugs for the next releases. If that does not help for you, we will probably try to identify your own bug specifically!
@Jeffrey: Awesome feedback, thank you! For the cache, we are aware of that and we are thinking about doing something much more practical. If you get nice results of you lava flow, don’t hesitate to share them with us: we are looking for nice projects with the new drones ;-)!
To help work around the issue of incorrect image filenames in the.p4d file, I’ve set the DJI pilot app (file index mode under general settings) to reset (vs. Continuous) and use a blank card for each flight so all images start off with DJI001.jpg
Also, to prevent missed images in high overlap, I’m going to try slowing down the speed a little.
I do like that the aircraft slides in the correct direction rather than wasting time and battery always keeping the most pointed forward. Keep up the improvements, it’ll be a unproductive sable product soon…
I meant to input “it’ll be a productive stable product soon” (no thanks to autocorrect…)
@Vertical Aspect Support: Thanks for the feedback. You are right: if you format the SD card before the mission, then everything is a bit more reliable. Actually, the one thing you should never do is removing only some images from the SD card. Either you format it, or you don’t touch it at all (I mean, you can copy its images) =).
I download and install SDK in phantom3 , download Capture App , Enable Debug Usb , when i start the application say : Please connect to drone Wi-Fi , the remote control working properly , can you help me ? thank’s Marco Garino
I’m also getting battery zero error and can’t use this app. I’m on firmware V01.02.02.21 and using LG G4.
@Marco: which version of the App do you have? Are you in the beta program? Which drone did you select?
@naz naz: as said before, in 2.0.3 you will have the possibility to enable an “advanced mode” in the settings, that will then allow you to click on the hyperlink of the safety checklist and ignore some checks (such as the battery). It already exists in 2.0.2 but it is buggy for the battery.
@Jonas Vautherin: Oh ok. So the 021 firmware causes to this problem? I take same error on DroneDeploy beta app too but there’s no problem on dji pilot app. Also when will u publish 2.0.3?