I can confirm that the newest release of the DJI Phantom 3 Professional Firmware v1.7.0060 will limit the Capture mission flight height to 300 feet, or 100 meters.
This is not safe in many situations. This limit needs to be increased to allow missions at 499’
Any height above 300 feet, once the missions has successfully uploaded, the craft will just hover, and not begin the mission.
I also noticed the gimbal went to about a 30 degree forward tilt from vertical. This makes looking at the camera view very important to prevent wasted missions, as the user can still manually point the camera to vertical manually.
Does anyone know of a way to roll my DJI firmware back one version…I do have the older files on my PC.
I have successfully rolled my firmware back…that was easy.
I still have the behavior of no permitted flights above 300 feet. Can you, or anyone please confirm if this is a new behavior? I have no height restrictions on P Mode flight, or F Mode flight when done manually, and have found no setting in the DJI Go app that could cause this either.
This really appears to be a deliberate restriction imposed by version 2.11.
@John, there are settings for distance and altitude limits in the GO app, you have to be connected to the P3P for any changes to take effect. If you recently updated the GO app maybe it defaulted to 300’, all my camera settings got reset and I had to go through everything and set it back. I will be flying tomorrow and will try a small flight over 300’, will let you know what happens.
@ John, I can confirm your findings. Set a mission at 330’, put the drone about 30’ in the air, got all green checks, held for 3 seconds to take off, and drone just hovered at it’s current position, waited a good 30 secs to a minute before I aborted and landed. Set the altitude to 180’, again put the drone 30’ in the air, again got all green checks, held for 3 seconds and this time it flew the mission as expected. I’d say this was purposely done or is a bug in Capture as none of the other apps that I use displayed this behavior.
Jonas, I will be sticking with 2.08 for now as it seems way more stable on my devices, a Samsung Tab A running Android 5.0.2 and a Nvidia Shied K1 running Android 5.1.1. On the Shield the Capture App 2.1.1 is no longer in the usb tray along with the other apps, I get the Allow the app Pix4Dcapture to access the usb accessory? box AFTER I start Capture. I had a ton of issues getting connected to the P3P, after several restarts of the P3P, the RC, capture, and a reboot of the shield, it finally connected but still got the could not fetch media list from drone message. It also showed the drone 29,000,000 ft away. After several more restarts and a few resets of the grid it seemed to work. See this video https://onedrive.live.com/redir?resid=60AF121B7DC78CDA!9645&authkey=!AKbCXd9PWklV3kM&ithint=video%2cmp4
Also another issue I don’t remember having with 2.0.8 is it now seems to be interfering with Universal Ground Control Station (UGCS) app. When I start UGCS, the Allow the app Pix4Dcapture to access the usb accessory? box appears and when I click cancel UGCS closes. I had to uninstall Capture for UGCS to work properly. Must say I’m pretty disappointed with 2.1.1 with the connection issues and the 300’ altitude issue, hopefully you can get these resolved quickly.
Jonas, I would also like to add that my test flight also did not create a screenshot, gpx file, or a p4d file, just a log and csv file. For me another reason to stay with 2.0.8 even though that p4d file is useless I still like the screenshot and gpx file.
We don’t deliberately limit the maximum altitude (it would not make sense to allow you to select an altitude in the UI and not allow you to fly it ;-)), so it is a bug. I am not completely sure where it comes from, actually, but it is also definitely related to a firmware update.
We will keep that in mind for SDK3, that we are integrating right now. Actually, we must set an upper limit in SDK3, so it might be a side effect for SDK2 (and DJI stopped supporting SDK2). We’ll put SDK 3 in the beta channel quite soon (hopefully 2-3 weeks). For now, our iOS version is more advanced as it has SDK3 already ;-).
Well I appreciate the communication. I would try possibly the opposite. Maybe weekly updates on where you are at. And yes sometimes you will have to tell us bad news and give us a new ETA, but it’s going to happen. Other times you will tell us good news. It should hopefully give everyone a better respect of what is going on and the hard work that goes into it.
You can’t make everyone happy, but you can try to make everyone less unhappy. Keep up the great work and I look forward to the next update
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.