3.0 general flying ok?

Joined
Feb 3, 2014
Messages
120
Reaction score
0
Ok, so I understand that a lot of people will be disappointed with the flight restrictions and I sympathise with any who are actually limited in there flying area's due to this especially where a sanctioned flying field is within one of the zones. For me personally I don't care about the restricted area's I don't ever see them being an issue for me.

Only thing I do disagree with is forced controller initiated landings or altitude changes in any situation, ok extremely low batt auto landing (its going to fall out of the sky anyway) and RTH but under no circumstance should the controller decide to change it's flight path without confirmation from the person in control and in fact I am sure certain authorities would disagree with the device irreversibly limiting or removing control in anyway from the person in control.

Anyway... aside from this are there any other issues with general flying with 3.0 over 2.0? or is it a safe update from that point of view?
 
I don't know that anyone's been able to test this yet due to the ridiculous firmware update process...

I agree with you - under no circumstances should the P2 take it upon itself to remove control from the user. I anticipate the first time this happens and the P2 "automatically lands" on someone's head, it's DJI that's going to get sued.
 
markab said:
Ok, so I understand that a lot of people will be disappointed with the flight restrictions and I sympathise with any who are actually limited in there flying area's due to this especially where a sanctioned flying field is within one of the zones. For me personally I don't care about the restricted area's I don't ever see them being an issue for me.

Only thing I do disagree with is forced controller initiated landings or altitude changes in any situation, ok extremely low batt auto landing (its going to fall out of the sky anyway) and RTH but under no circumstance should the controller decide to change it's flight path without confirmation from the person in control and in fact I am sure certain authorities would disagree with the device irreversibly limiting or removing control in anyway from the person in control.

Anyway... aside from this are there any other issues with general flying with 3.0 over 2.0? or is it a safe update from that point of view?


Worked like a charm for me. Check out my other post on what issues I did have after upgrading to 3.0..
 
I just got my new Phantom 2 and have not downloaded the assistant software yet so I do not know what firmware is currently on the unit. If it is version 2, will I absolutely have to upgrade to version 3 before I can fly my new Phantom 2 ?
 
Phantom2inVA said:
I just got my new Phantom 2 and have not downloaded the assistant software yet so I do not know what firmware is currently on the unit. If it is version 2, will I absolutely have to upgrade to version 3 before I can fly my new Phantom 2 ?

There is absolutely no requirement to update your firmware whatsoever.

Fink
i-LgFpTrs-M.gif
 
mysticalice said:
I don't know that anyone's been able to test this yet due to the ridiculous firmware update process...

I agree with you - under no circumstances should the P2 take it upon itself to remove control from the user. I anticipate the first time this happens and the P2 "automatically lands" on someone's head, it's DJI that's going to get sued.


what do you mean by ridiculous firmware update process? it's always been a breeze for me.
 
Good to hear, Flyer...which controller are you using?
 
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.
 
Thanks a million for the tip Gonzoshots!

I downgraded to 1.0.8 using the Phantom 1.0.8 app, then upgraded to 2.0.0 and calibrated the Tx. 7th channel and IOC works like a charm again :)
 
night shifts, other work, rain, weather .... hell I havent even had time to fly with v2.00 yet **** it ..... at least i know not to upgrade from what Ive read so far ... ??
 
OK pilots my Gimbal Tilt Swicth problem has been solved thanks to the folks at DroneFly, the asked me to simply re-calibrate the X1 (Gimbal Switch) using the Assistant Software, go to Basic, then RC, then go to the Sticks Monitor and click Start in the X1 calibration, articulate the gimbal switch, then click Finish and all will be well.
 
It is really odd, because my Phantom flies the same for me as it did with 1.0.8. My gimbals had an issue once I first updated but it was fixed just by calibrating my RC first then the Phantom. Every time I update my Phantom, I perform an advanced calibration and the re calibrate the compass before a flight.

Firmware 3.0 seems just fine on my phantom, hovers right where it should and flies just as smooth as she always had before. Wish I could control the gimbal pitch and speed,but I guess that is for the H3-3D only..
 

Recent Posts

Members online

No members online now.

Forum statistics

Threads
143,086
Messages
1,467,525
Members
104,965
Latest member
cokersean20