I am also in PA, and noticed this problem the last time I flew, I want to recalibrate to make sure this is the problem will update later this week,
Fixing DJI's Compass Problem
- Thread starter ianwood
- Start date
cgreer00 said:
With a declination of zero, there is no declination error. The average declination for everyone affected by this issue is 15 or -15. You should rule out other compass related issues e.g. magnetization, bad calibration. I don't think this thread is related to your issue. If you disagree, let me know but please rule out other types of compass issues first.
I'm going to try keep this simple and direct.
I reverted back to 1.08 firmware after updating to 2.0 then 3.0 because the craft would not maintain elevation and overall general decrease in control. After reverting the craft controls the way it used too ie. very good response and feel. It was very easy to revert since the DJI software never uninstalls the previous version of the Assistant software, my PC has versions 1.0, 1.02, 1.08, 2.0 and 3.0. I simply ran the executable for 1.08, plugged in the Phantom, checked for updates and it said I could "update" from version 3.0 to 1.08, seems any variance from the current version is seen as an update, this happens to make things very easy. I do have a lingering issue I will be working on today, that is my Gimbal no longer works, it stopped working after the update to version 3. I have the Zenmuse H3-2D gimabl.
Now before I start getting a bunch of advice please read these clarifications below. PS. I re-calibrated everything via the software after every version update, as well as re-calibrating the craft as well.
1. I have flown my Phantom 2 for 5 months EVERYDAY for an hour at least. This is the only way to become a good pilot.
2. I do lots of low flying over water, very delicate flight patterns, NO room for error.
3. I never update firmware unless I have an issue, don't fix it if it ain't broke.
4. I decided to update from 1.08 to 2.0 for one reason only, I loved the new max descent speed limit since my one and only crash was due to a very high altitude descent in stormy conditions and came down too fast and without enough forward/backward movement and entering into the wobble of death/vortex ring state and the craft plummeted to the ground. I now know that if I enter this state simply back of the throttle and give it forward or backward stick gently.
5. As soon as I updated to 2.0 I began to notice flight control issues, to be specific, the craft would no longer MAINTAIN altitude at hover and also when you moved in any direction the craft would lose altitude, I nearly ditched the craft into the water several times before heading to the backyard for some serious flight analysis. I verified that the craft no longer moved or responded in the same way it had for the previous 200 flights, I was always having to add throttle up to maintain elevation, with no control movement at all the craft would drop several feet and rise and fall slowly over and over, when moving in any direction the craft would lose elevation and lastly when I would do a big pull back shot ie. Backwards and up at the same time it would "hook" left as it flew away, not a hard hook but a hook. I do this type of shot every day and do know that a compass issue will cause the same thing, but remember I recalibrated my compass before each flight just trying to eliminate variables.
6. Next I upgraded to 3.0 just in case these were version bugs, they do occur, I am a programmer and I know how easy it is cause issues with "improvements" and debugging can take time. The flight control issues remained PLUS now my gimbal would not work. I did extensive flight tests, low level, hover, pull backs and all the conditions existed. Keep in mind I performed all tests in exactly the same location as to not introduce any locations variables.
7. Frustrated I got up this morning and decided to attempt a roll back to what IO deemed the last stable version 1.08. I read the forums but there was way too much conflicting and emotional dialog to sort thru so I decided to just give it a whirl. Since the DJI software never uninstalls the previous version of the Assistant software I DID NOT have to locate the installer for 1.08 or uninstall 3.0, all the older versions still existed in an installed state on my PC. I had versions 1.0, 1.02, 1.08, 2.0 and 3.0.
a. I simply located the executable for 1.08 C:\Program Files (x86)\DJI Product\Phantom 2 Assistant_1.08\Phantom2.exe
b. Plugged in the Phantom, checked for updates and it said I could "update" from version 3.0 to 1.08, seems any variance from the current version is seen as an update, this happens to make things very easy.
c. I then recalibrated the controller and went to do some hands on flight tests. Everything is now great again, all the previous issues were gone, no drop in elevation when moving, much more stable hovering and no more J hook on the big pull backs
d. I do have a lingering issue I will be working on today, that is my Gimbal no longer works, it stopped working after the update to version 3. I have the Zenmuse H3-2D gimbal.
8. I truly hope this info is helpful and would love to get your feedback. I love to fly my Phantom and know how hard it must be for DJI to manage hardware and software changes and also know they are trying to beat the governments to the punch at protecting airports and aircraft from careless pilots, I think this is a good thing for the sport.
I reverted back to 1.08 firmware after updating to 2.0 then 3.0 because the craft would not maintain elevation and overall general decrease in control. After reverting the craft controls the way it used too ie. very good response and feel. It was very easy to revert since the DJI software never uninstalls the previous version of the Assistant software, my PC has versions 1.0, 1.02, 1.08, 2.0 and 3.0. I simply ran the executable for 1.08, plugged in the Phantom, checked for updates and it said I could "update" from version 3.0 to 1.08, seems any variance from the current version is seen as an update, this happens to make things very easy. I do have a lingering issue I will be working on today, that is my Gimbal no longer works, it stopped working after the update to version 3. I have the Zenmuse H3-2D gimabl.
Now before I start getting a bunch of advice please read these clarifications below. PS. I re-calibrated everything via the software after every version update, as well as re-calibrating the craft as well.
1. I have flown my Phantom 2 for 5 months EVERYDAY for an hour at least. This is the only way to become a good pilot.
2. I do lots of low flying over water, very delicate flight patterns, NO room for error.
3. I never update firmware unless I have an issue, don't fix it if it ain't broke.
4. I decided to update from 1.08 to 2.0 for one reason only, I loved the new max descent speed limit since my one and only crash was due to a very high altitude descent in stormy conditions and came down too fast and without enough forward/backward movement and entering into the wobble of death/vortex ring state and the craft plummeted to the ground. I now know that if I enter this state simply back of the throttle and give it forward or backward stick gently.
5. As soon as I updated to 2.0 I began to notice flight control issues, to be specific, the craft would no longer MAINTAIN altitude at hover and also when you moved in any direction the craft would lose altitude, I nearly ditched the craft into the water several times before heading to the backyard for some serious flight analysis. I verified that the craft no longer moved or responded in the same way it had for the previous 200 flights, I was always having to add throttle up to maintain elevation, with no control movement at all the craft would drop several feet and rise and fall slowly over and over, when moving in any direction the craft would lose elevation and lastly when I would do a big pull back shot ie. Backwards and up at the same time it would "hook" left as it flew away, not a hard hook but a hook. I do this type of shot every day and do know that a compass issue will cause the same thing, but remember I recalibrated my compass before each flight just trying to eliminate variables.
6. Next I upgraded to 3.0 just in case these were version bugs, they do occur, I am a programmer and I know how easy it is cause issues with "improvements" and debugging can take time. The flight control issues remained PLUS now my gimbal would not work. I did extensive flight tests, low level, hover, pull backs and all the conditions existed. Keep in mind I performed all tests in exactly the same location as to not introduce any locations variables.
7. Frustrated I got up this morning and decided to attempt a roll back to what IO deemed the last stable version 1.08. I read the forums but there was way too much conflicting and emotional dialog to sort thru so I decided to just give it a whirl. Since the DJI software never uninstalls the previous version of the Assistant software I DID NOT have to locate the installer for 1.08 or uninstall 3.0, all the older versions still existed in an installed state on my PC. I had versions 1.0, 1.02, 1.08, 2.0 and 3.0.
a. I simply located the executable for 1.08 C:\Program Files (x86)\DJI Product\Phantom 2 Assistant_1.08\Phantom2.exe
b. Plugged in the Phantom, checked for updates and it said I could "update" from version 3.0 to 1.08, seems any variance from the current version is seen as an update, this happens to make things very easy.
c. I then recalibrated the controller and went to do some hands on flight tests. Everything is now great again, all the previous issues were gone, no drop in elevation when moving, much more stable hovering and no more J hook on the big pull backs
d. I do have a lingering issue I will be working on today, that is my Gimbal no longer works, it stopped working after the update to version 3. I have the Zenmuse H3-2D gimbal.
8. I truly hope this info is helpful and would love to get your feedback. I love to fly my Phantom and know how hard it must be for DJI to manage hardware and software changes and also know they are trying to beat the governments to the punch at protecting airports and aircraft from careless pilots, I think this is a good thing for the sport.
ianwood said:
There might not be any declination error, but this is not just relegated to me. There are others in this thread from the eastern U.S. that are experiencing the same symptoms, and all of them would fall between a declination of 0 and 5. I have recalibrated about 10 times now and it hasn't solved it. Did the advanced calibration as well. This problem did not used to occur, and like others in this thread, has begun somewhat recently. Reading back I see several people stating that things were great and then one day their Phantom 2 just started behaving strangely and doing the J-Hook. Chalk me up in the same boat.
For now I will just run in Atti mode until DJI gets their act together and fixes this problem. Atti is great, no problems at all with the flight and is exactly how one would expect the machine to fly.
In fairness too there have been reports of people not noticing the j-hook until they were informed. Maybe you just didn't noticed it.
Gonzoshots said:
Where are you located? In an area of high declination? I wouldn't necessarily say your problem is directly related to this specific issue BUT someone else did say that they first noticed the j hook after updating from 1.08. Terry and DJI should take note of this fact in their troubleshooting.
cgreer00 said:
Depends on where they are in the eastern US. Everything east of a line between Florida and Michigan ranges from -5 to -20.
Gonzoshots said:
You're at a 10 or 11 declination wise so hooking would be expected. Should be pretty noticeable at the beginning of flight and cleaning up after a few minutes. Try that after a couple of flights on 1.08 and report back.
I am still on 1.08. I take the "let's first see how the others do" approach to firmware upgrades unless I have an overwhelming need. As I've seen from others, the issue is consistent across the three versions.
After reverting back to 1.08 have no more hooking issues, never did at 1.08 only at 2.0 and 3.0
Whether you're right or not about hooking with declination near zero, I don't know. However, you are wrong about the declination in other parts of the Eastern US. Here in NJ it's more than negative 12 degrees, and further east and north the declination is even greater.cgreer00 said:
Others have reported how it's possible to "upgrade" the Phantom 2 Vision firmware from version 3.0 to version 1.08, using Phantom 2 Assistant software version 1.08.
I still had Phantom 2 Assistant 1.08 on my Windows desktop computer, so I just completed that firmware "upgrade".
It sure is nice to have horizontal stability back again! I'd kind of forgotten that prior to firmware version 2.0, my Vision had been pretty darn good at maintaining its horizontal position when yawing. The nice stable flight I just took after re-installing firmware version 1.08 has refreshed my memory.
Yes, I've lost the 3 meters/second maximum descent speed (or at least I believe it's now back to 6 meters/second... I forgot to check, actually), but I can wait for that until the stability issues are fixed.
I still had Phantom 2 Assistant 1.08 on my Windows desktop computer, so I just completed that firmware "upgrade".
It sure is nice to have horizontal stability back again! I'd kind of forgotten that prior to firmware version 2.0, my Vision had been pretty darn good at maintaining its horizontal position when yawing. The nice stable flight I just took after re-installing firmware version 1.08 has refreshed my memory.
Yes, I've lost the 3 meters/second maximum descent speed (or at least I believe it's now back to 6 meters/second... I forgot to check, actually), but I can wait for that until the stability issues are fixed.
Bigbells said:
Ok heard of this down grading firmware So you had no problems doing so might try it my self
I purchased a P2V in a Middle Eastern country and flew it approx 10 times. I performed it's only compass calibration on a large expanse of heavily reinforced concrete whilst wearing a stainless steel watch and with my iPhone at my feet. The P2V performed flawlessly with no J hooking on any of its flights. On returning to eastern Australia I purposely performed a compass calibration in an open field free from any metal/iron/concrete etc., no watch and no iPhone. My first flight produced a large J hook which decreased significantly after approx 5 to 10 minutes of flight time. With my situation I believe compass calibration will have no effect on the amount of J hooking I am receiving. I have not noticed any toilet bowl effects. The only other thing to note is that I upgraded to assistant V2 on return to Australia.
On Vacation said:
Have you tried connecting to you're phantom and having a look what the compass mod value is? I had the exact same J hook problem after updating to v2, when checking the mod value it was around 1630 ( ideally should be below 1600 ) did an advanced calibration etc and the value came down a little but the phantom still had the J hook. Then checked the surface where the advance calibration was done ( with a spirit level) and found it was not quite level, found a level surface redid the calibration and the mod value came down to 1160. Test flew the phantom and it now going straight and true no J hook - happy days again
Add me to the list, Northern Alberta Canada. I rotated my compass to fix, had to, felt like this thing was almost not in control. Had to do this on my Naza V2 F550 as well but it is ok to do it on that craft. I know it isn't the right answer but for now IMO better than flying with it the way it was. Rotating it resulted in it flying MUCH better. The potential for flyway with compass and gps arguing the way it was just did not give me peace of mind enough to fly it confidently. Declination of 18 where I am at.
Attachments
On Vacation said:
The declination in the Middle East is about 2 to 4 degrees so you would not see much of a JHook. The declination of Eastern Australia is 10 to 12 degrees so you should expect to see a JHook. I would say your experience is consistent with what we are generally seeing - and a great example of the problem that is being investigated.
IEATSRT…question for you…which way did you rotate it? Does it matter? I am in New York and getting J-hook to the right and TBE also…been thinking of trying to rotate it but wondering how much it helped and if you feel better with it like that?
NYRangers99 said:
If your declination is negative, you rotate counter clockwise and if positive, you rotate clockwise. If you rotate by the actual amount, you will notice reduced hooking and it will take less time to straighten out. You will also likely notice that it over corrects and starts to hook in the other direction. If you rotate by double the declination, you will fly dead straight right from take off and then it will start to hook in the other direction.
Those have been my results and others have seen similar results. If you want to do some structured testing by rotating the compass, I would like to hear of your results. Just be careful to use a non-magnetized screwdriver! And be very careful to secure the compass properly. The screws will back out if not tightened sufficiently and/or the compass can pop back into the default position. Also, the compass is a 3D device in that is has three sensors (one in each plane). By rotating it, you are effectively putting one plane off axis. How much that matters, I am not sure.
The combination of risks above require that you be very careful in doing this. I believe that most fly aways are caused by compass issues. I nearly had a fly away when I decided to try shimming the compass in the opposite direction.
If anyone wants to try it, use a compass rose to do it. Print one out and put it under the P2 aligning its forward direction with 0 degrees. I'd attach one here but I can't find the one I used for this before... Duh...
Similar threads
