Maybe i worded that wrong. What I meant is the craft has to be further than 10 meters from its home point for home lock to work. if it reenters that 10 meter zone it switches itself to course lock. At least I think that is how it worksLandy said:
Fixing DJI's Compass Problem
- Thread starter ianwood
- Start date
I am in Vancouver British Columbia and am running Version 2.0 on my Phantom 2 Plus and I am encountering the same problems with "toilet bowl" after launching and "J Hook" and the course lock problem. Like you say after 4-5 min of flight it clears up.
I really don't want to lose Version 2.0 due to the slowing down of dropping altitude and DJI slowing it down in Version 3 but what can you do I guess. I would like to have this cleared up.
Please add me to your list of people affected by this problem.
Jason
I really don't want to lose Version 2.0 due to the slowing down of dropping altitude and DJI slowing it down in Version 3 but what can you do I guess. I would like to have this cleared up.
Please add me to your list of people affected by this problem.
Jason
Flying in the Seattle area - declinatino 16.5 deg. Having the exact problem. It does seem to improve the longer the flight, but very unpredictable. Thanks Ian and all for the work. I'm looking forward to firmware upgrade. Flying a P2V+.
Ron
Ron
KassioLM said:
If the majority say it works, they should release it.. Hell, anything is better than trying to contend with the J hook, TBE flying conditions now.. They should release it, then tweak up whatever problems arise in the course of usage..
- Joined
- Sep 4, 2013
- Messages
- 2,219
- Reaction score
- 7
obiwan_pierogi said:
I totally get the anticipation here, but generally releasing a first-rev firmware that hasn't been thoroughly tested can be disastrous, especially for a flying machine. Unforeseen impacts may not just be minor tweaks. I think it benefits everyone for DJI to be extremely thorough about the effectiveness and impact of this fix, so people get the best possible, most stable solution they deserve. This may mean it could take several weeks if DJI needs to analyze data, make tweaks, send out to beta testers again or expand the beta pool moving forward...It's so imminent right now, why not push them to do it right down the homestretch?
ElGuano said:
I totally agree.
I have been involved in some major software programs and as they get more complex and it gets easier and easier to get unintended consequences from a minor tweak. DJI can rush a fix to the testers because the liability is limited but for a general release they need to take a reasonable amount of time to be sure it doesn't have shocking surprises. But I too am eager to get the update.
ElGuano said:
I just got a new PV2+ ... I'm almost afraid to fly it, as it is that uncontrollable.. I don't think you can get anything more disastrous than this from DJI.. Any upgrade would be an improvement.. As I told the dealer: had I not had some experience with the PV2, I would probably have crashed it on the first flight.. As Of now, I'm trying to get in a few flights anyways, as the dealer only has a 20 day refund.. So I at least have to check to make sure it is operational, even if it flies crappy. They could release what they have, but then keep working to come up with an all encompassing upgrade that fixes all the problems
fly close and careful and wait till the end of your battery and see how it flies then. thats how it will fly when they fix the issue. that should also make you not so worried
Will this future update include the FC40?
It suffers from the same issue.
It just a P2 with a P1 battery ;p
It suffers from the same issue.
It just a P2 with a P1 battery ;p
I wouldn't get my hopes up to see the fix out soon . I bet it will take 1 and a half months. DJI has version 3.05 and they should release it to the general public and make any tweaks to the 3.05 as needed if needed.
DJI has done this with all their other firmwares so this current fix is no different. Lastly it's not going to be a perfect fix and the phantom will never fly perfectly ... It's a "Toy" . Everyone in the past has been ginny pigs to the firmwares that DJI releases so again DJI release the firmware.
DJI has done this with all their other firmwares so this current fix is no different. Lastly it's not going to be a perfect fix and the phantom will never fly perfectly ... It's a "Toy" . Everyone in the past has been ginny pigs to the firmwares that DJI releases so again DJI release the firmware.
Hi had the opportunity to compare a P2V and a P2V+ today.
Both exhibit exactly the same issue. Being in Auckland NZ, the magnetic declination here is +19.5°, so pretty bad. One thing I noticed is that in hover (once the system had settled down) I was getting a very slow yaw movement. I wonder if this is the same issue?
Finally, I noticed that if I ran initially for a couple of minutes, then landed and ran a compass calibration (without ever cycling power) the J-hook settled down quite quickly after this calibration?
Certainly this issue won't stop me from flying. It's not really a big deal once you are used to it and know what to expect. You can even compensate for it with a short right roll.
That said, it will be good when DJI release an update to address this.
Cheers.
Rob.
Both exhibit exactly the same issue. Being in Auckland NZ, the magnetic declination here is +19.5°, so pretty bad. One thing I noticed is that in hover (once the system had settled down) I was getting a very slow yaw movement. I wonder if this is the same issue?
Finally, I noticed that if I ran initially for a couple of minutes, then landed and ran a compass calibration (without ever cycling power) the J-hook settled down quite quickly after this calibration?
Certainly this issue won't stop me from flying. It's not really a big deal once you are used to it and know what to expect. You can even compensate for it with a short right roll.
That said, it will be good when DJI release an update to address this.
Cheers.
Rob.
Results from the 3.05 beta test flight. The first back and forth is the biggest one and you can see a little curve at the end. It's much much smaller than normally and doesn't swirl at all. The second, third and fourth pass are pretty much arrow straight as you can see.
ianwood said:Results from the 3.05 beta test flight. The first back and forth is the biggest one and you can see a little curve at the end. It's much much smaller than normally and doesn't swirl at all. The second, third and fourth pass are pretty much arrow straight as you can see.
Ian what app are you using to put your flight on google earth like that?!?
Ian,ianwood said:
What happened on the next flight? Did it remember what it learned on this one or did it repeat the first circuit offset behavior?
I don't know. I'll tell you tomorrow. But, it doesn't need to remember anything given that it flies straight pretty much right away. Look at the image you'll see it's even more straight then when I flew in Chicago.
As for Google Earth data, I take the raw CAN bus data files from the OSDII and parse them with an excessively complicated script I wrote. It outputs CSV of all the known data types and then KML for Google Earth. Working on a Dashware export as well.
As for Google Earth data, I take the raw CAN bus data files from the OSDII and parse them with an excessively complicated script I wrote. It outputs CSV of all the known data types and then KML for Google Earth. Working on a Dashware export as well.
I new you were CIA Ian.
I'll fly with you and shoot some video. Send me a pm if you're interested.
I'll fly with you and shoot some video. Send me a pm if you're interested.
Similar threads
