- Joined
- Jun 14, 2015
- Messages
- 9
- Reaction score
- 2
- Age
- 63
I don't know why DJI hasn't pull off the 1.2.6 firmware from the website, I was planning to get the Phantom 3 Pro, but now I've decided on the Yuneec Q500 4K
Ya... I'm at 1.2.6I don't know why DJI hasn't pull off the 1.2.6 firmware from the website, I was planning to get the Phantom 3 Pro, but now I've decided on the Yuneec Q500 4K
It appears there's a holiday today in the US? Can't get though.
Ya, but that's nuts what it did. I shouldn't expect the way it acted.
I don't think that the Android app has the joystick position. Only IOS.
That's full of crap. Software engineers are always making a downgraded version of an IOS app for Android users. Or the Android users have to wait extra time to get the same features, even though the version numbers are the same and released at the same time!
So why are you posting on a Phantom forum? You have no experience with a Phantom 3, don't even own one, and went with another brand. Oh, you just wanted to diss DJI publicaly. Gotcha!I don't know why DJI hasn't pull off the 1.2.6 firmware from the website, I was planning to get the Phantom 3 Pro, but now I've decided on the Yuneec Q500 4K
I always turn on the controller>app>P3 in that order. You said you did a compass calibration?, at an old saw mill?, could there have been buried metal where you calibrated? Also, did the app tell you that "the home point has been updated, please check it on the map" This is something you should do EVERY time, to make sure the home point is actually where you are. It sounds like a compass error due to bad calibration, especially if you didn't get the home point set message. ( I only calibrate if my new flight area is 75-100 miles from the last)
The compass on the p3 is very sensitive , even if you have done a cali first, if you take of anywhere near metal it will throw a compass error. I do mean anywhere near metal ie 10 or 15 Myts away it will throw the craft into p atti.
I can answer that question-- my post was for information only-- not for argument purposes.Then what's the use of having the drone locking onto a million satellites for positioning if its going to ignore it due to some stupid magnetic anomaly.
This is a very good question, is their a priority setting for sensors?Then what's the use of having the drone locking onto a million satellites for positioning if its going to ignore it due to some stupid magnetic anomaly.
I was planning to make my P3A takeoff from my car roof, I guess I shouldn't do that.FOR WHAT IT IS WORTH:
Very sensitive --YES!-- I had a successful filming flight of a construction site. Landed, put in a new battery and had an assistant walk around close to the heavy equipment getting video with the camera. He approached a piece of equipment to about 20 ft, and the screen immediately showed a compass error-- didn't loose video, but the compass error message stayed on.. When the ground video was completed, we reset the controller, installed a new battery and powered up. No error-- Took off, went up to about 30 ft and the Phantom started flying away from me on its own, I could control it with maximum opposite input on the sticks, but as soon as I eased off, it took off again. Immediately initiated RTH, that activated and it returned were I took it off and I landed it, manually, but it was very unstable descending. When I got to 6 inches, initiated CSC.
I have also powered up the Phantom on the end gate of my pickup and immediately it generates a compass error as does flying in my back yard which is small and surrounded by chain link fence.
I believe we all have to be very cognizant of anything that will cause compass error metal or magnetism. Compass errors are probably the primary cause for most fly aways. By the way, the edges of my IPad Air 3 is magnetic and I am careful to make sure the Phantom is not powered sitting to close to the controller.
Nooooooooooooooooooo! don't do it--- don't do it-- don't do it!!!!!!!!!!!!!!!!!!!!!I was planning to make my P3A takeoff from my car roof, I guess I shouldn't do that.![]()
We use essential cookies to make this site work, and optional cookies to enhance your experience.