Installed the latest firmware (3.10) and software (2.10) last night - WOW!!!!!!
The new interface is MUCH better than the last one and it copied all my settings across - if I hadn't written them all down it wouldn't have copied the data would it!!
The new firmware has a very different feel to the last version.
I have been critical in the past that if I took off as soon as I had flashing greens then it drifted - I had to wait another couple of minutes before taking off to get a good lock.
With the new firmware taking off as soon as the light flashes double green gave an instant lock.
The lights all now give a double flash which is easier to see
Even in 20knots of wind it was ROCK stable
Take off procedure is quite different - up to 50% throttle the motors don't run at all - at 51% they all burst in to life and a gentle climb to 6 feet then it just sits there.
Take off in GPS mode or Atti mode is a complete non event - no skittishness or wobble.
Descent is VERY smooth - no hint of wobble.
I will need to turn the gains down generally as it feels a bit too locked in but it is super-stable.
Very impressive improvement - well done DJI - a highly recommended up date to both software and firmware.
Thanks for that info , I will do that this evening.
Simon.
Yeah thanks for that, I will do the same, I have been in two minds about updating, but if its going to be more stable then bingo! :)
It really is awesome.
the release notes are here - http://download.dji-innovations.com/downloads/nazam-v2/en/NM_release_notes_en.pdf (http://download.dji-innovations.com/downloads/nazam-v2/en/NM_release_notes_en.pdf)
There is one misleading statement - 'do not have flight battery connected during upgrade' - you cant update the firmware unless the battery is connected - what they mean is disconnect the motors or remove the props just in case!!!
Just hit enter when you've changed the field
Quote from: Andy66 on May 10, 2013, 11:56:58 PM
Do you need to write the info to your FC as I cant find the write on the new panel or is there no need?
From what I can tel it just writes it.
I found I had to calibrate the IMU. It would not start up otherwise.
is there an idiots step by step guide for doing the update? (?)
what about the naza dance does that have to be done again?
Oh cool, I didn't even know the update was out :)
Oh I like it so far, mixed the trainer switch into my flight modes so now to calibrate I just flick the trainer switch 11 times without needing manual mode, sweet :)
Ooooo i shall update mine tomorrow
Then, up in blackpool this weekend visiting the old man (the naza has come along with me) but not got my laptop with me doh !
OK - am now convinced. There had been a few scare stories about this upgrade on the Phantom owners Facebook page, as well as on rcgroups, so I was waiting till the dust settled, but reports of smoother descents and better gps lock are very tempting.
I see that forced failsafe rth is also now optionally assignable to the right switch, though am still too chicken to willfully remove control!
Imu and Tx calibration(s) are recommended - and the DJI compass dance for good measure.
done time to test now..... :)
Im all upgraded, just waiting for the weather now.
I did the upgrade last night and well .. not even going to think about indoor testing .. this new way the take off works could prove intresting
Anyone know how the hight it jumps up.
The new sofware on the Pc is much better tho I do think this take off should be an option if you would like it or not.
Just waiting for the weather.
Richard
It doesn't really 'jump up' its just that the motors do nothing up to 50% then at 51% they all burst into life.
Then it will climb if you open the tap but only just lift off if you stick at 51%
Its just a surprise when the motors do nothing until 50% the all burst into song together.
Yea - no issues to report here either...
I downloaded the new 3.1 Assistant, installed new firmware (via the Assistant) to the FC, and then calibrated the Tx (not that it needed it), and did an advanced IMU calibration (didn't appear to need that either, but I could see no harm in doing it).
Just test flown outside, between rain showers, and despite blustery conditions it flew impressively well.
Takeoff feels a bit different - but then again if half throttle is altitude hold, then logically any climbing (including take off) has to be above 50%... so it makes sense to me.
Medium speed descends seem MUCH steadier - so for me the upgrade is worth it for that added smoothness alone...
GPS lock also seems tighter than before. It was interesting watching all four motors working overtime to hold position as gusts swept past... :o
Cheers,
Nick
I got this after naza update ...need to power ON couple times before it will go to proper connection ??...IT"S NOT FAILSAFE...as I got 3 switch setup and failsafe is slower yellow flashing then this ?..
any idea ?
Flashing yellow really fast "NOT FAILSAFE" after NAZA upgrade. (http://www.youtube.com/watch?v=ZOauaSCs6_c#)
Not sure Marcin, I`m reading a few reports of the new firmware cutting motors when the stick is 40 - 45% while trying to descend, any one else having this issue ?
It has changed the way to start the motors with the stick positions. Is there a way to change it?
Decent isn't as wobbly now that's for sure. Had my throttle stick less than %40 but no cut out. Might add an 'idle up' setting on my radio, so there's no chance of a cut out just in case :)
Take off is better too. All good.
Nice looking software but how do you save the calibration changes? :)
Quote from: DaveyLC on May 12, 2013, 04:20:13 PM
Nice looking software but how do you save the calibration changes? :)
It is dead easy you just tap enter when you put in the values and it writes it for you.
Simon,
I can't get the CSC to work :(
Quote from: DaveyLC on May 12, 2013, 04:33:26 PM
I can't get the CSC to work :(
Did u do the full 6min imu calibration? it wont allow csc unless u have :)
Jim.
Ye as above you MUST do the IMU calibration or nothing else will work.
just done mine, i found it reasonably straight forward, and i'm c^%p with IT. that double yellow flash on the video clip looks like atti to me. normal without gps. mine does, just the the same as before upgrade. just need some dry weather (drizzling here) not to windy, then i can try it.
I did the advanced Cali :(
Quote from: DaveyLC on May 12, 2013, 05:32:18 PM
I did the advanced Cali :(
Did you leave it absolutely still until it (advanced IMU cali) completed ??
Mine took 15 minutes to complete.
Mine took less than 5 mins to do and although its not been flown I can start everything up ok.
It took 5 mins or so :) ill try again..
Quote from: quadbod on May 12, 2013, 05:18:44 PM
just done mine, i found it reasonably straight forward, and i'm c^%p with IT. that double yellow flash on the video clip looks like atti to me. normal without gps. mine does, just the the same as before upgrade. just need some dry weather (drizzling here) not to windy, then i can try it.
it's not atti mode...this is something different.
i had a scare with the new firmware today. the motors started and it took off about 4 foot and i couldnt land it again. it looked to me like it was going to do 1 but i ran in and grabbed the quad. motors started going daft and the somehow i got the motors to stop - didnt fly it again after that although the flight b4 this happend was perfect
When I calibrate if I remove The usb lead it all works fine and I can fly but when I power cycle the naza it forgets my calibration settings and I can no longer CSC :(
Bah.. It's a bug http://www.rcgroups.com/forums/showthread.php?t=1880602&page=12 (http://www.rcgroups.com/forums/showthread.php?t=1880602&page=12)
Naza M v3 firmware won't calibrate :( (http://www.youtube.com/watch?v=butId645ygY#ws)
Work around:
Naza-M New v3.10 Firmware RC/TX Calibration Issue & Work-around (http://www.youtube.com/watch?v=eEasHaqlbjg#)
Well the work around appears to be to use sub-trims for the time being until the firmware is updated.
I noticed two things (other than the bug) which are a bit more positive:
1) it appears you don't get any climb rate until you're over half stick which sort of makes sense so half stick is altitude hold anything under is decent and anything over is climb.
2) the decent seems a hell of a lot smoother even in a breeze.
3) as with above in general in GPS mode it just seems to position hold much better.
And finally I like the fact you can assign pos 3 on your flight mode switch to failsafe
I have assigned Failsafe to that third-position, but am a bit concerned that I could accidentally invoke it when switching from GPS to Atti... Or by accidentally flipping down from Atti (thinking I was in GPS?). Well, these things happen... :o
With the previous software, if you forced a Failsafe by deliberately switching off the Tx, you had to switch into Atti mode, drop the throttle to zero, then switch the Tx back on, and finally raise the throttle back to hover...
Am I right in thinking that we can now simply flick back from Failsafe to Atti to quickly regain control?
Cheers,
Nick
I always found just flicking between atti/GPS got it out of f/s before? :)
I thought the only way to force a f/s before was to switch off the Tx? (This is on a Phantom - so not sure if that's different?)
Nah you just had to knock the flight mode channel into a position that wasn't GPS, atti or manual :) before this firmware I had a mix setup to do that
I have failsafe on a 2-pos switch....
so I can just flick it on and off at will....with the new firmware, can I no t do this any more?
Keukpa
Yeah you can still do it the old way :D
Oh balls :( After yesterdays 5 min flight thinking this V2 firmware was spot on, just had a "flight" that consisted of a take off, a Hex going nuts flipping then smashing 5 of the 6 carbon props ! Bugger !!!!!!
Calibrations all gone too :(
I`ve re-flashed mine back to 2.02 firmware now, it was fine so Ill wait til they sort it out
hmmmmm think I may hang on for a week or so....
Im gonna do more exhaustive testing tomoz if weather holds! .... gulp!! but today it was fine, but so was Ians yesterday!
Jim.
Quote from: Coyote on May 12, 2013, 09:10:54 PM
Calibrations all gone too :(
I`ve re-flashed mine back to 2.02 firmware now, it was fine so Ill wait til they sort it out
Did you reverse any channels? If so they would get dropped and you'd be flying a chaos machine :)
Ailerons were reversed yes, but I accidentally did that the other week flying with Paul, I soon worked it out and could still fly it. This was like mega twitchy > going nuts in fractions of a second
Not good!
Very not good !!!!
Got to the field on the way to work, powered up the Hex, 3 red led flashes............ Hmm.......... 2 red led flashes............ Now thinking something is wrong, 1 led flash then off.......... Ok so now I know it's still on 3.10 not 2.02 ! Crap :(
Oh well, let's see how it goes........ Took off, Hex lifted up, held level, everything seemed ok, 1 minute on Hex goes nuts again, crashes inverted, all props destroyed this time. Luckily again Nex is not damaged.
Now I'm worried how I'm going to be able to go back to 2.02 again after it said it was but obviously wasn't.
f**k sake thats s**t ian
i think i got mine back to how it was b4 the update - i deleted the new assistant from pc and opened the 1.8 assistant and plugged it into the quad and redone the setup. led lights look like ther are back to normal so i will try and get out test it later.
Quote from: Coyote on May 13, 2013, 10:42:18 AM
Very not good !!!!
Got to the field on the way to work, powered up the Hex, 3 red led flashes............ Hmm.......... 2 red led flashes............ Now thinking something is wrong, 1 led flash then off.......... Ok so now I know it's still on 3.10 not 2.02 ! Crap :(
Oh well, let's see how it goes........ Took off, Hex lifted up, held level, everything seemed ok, 1 minute on Hex goes nuts again, crashes inverted, all props destroyed this time. Luckily again Nex is not damaged.
Now I'm worried how I'm going to be able to go back to 2.02 again after it said it was but obviously wasn't.
Quote from: Andy66 on May 13, 2013, 11:45:27 AM
Ouch Ian not good fun, must be a glitch on the hex mode?
might not be just hex mode - ive got naza on a quad, did the update and takeoff sounds alot like what ians hex was doing but i ran in and grabbed the quad out of the air b4 it had chance to fly off or smash itself to bits.
hopefully its back to normal now after rolling back the firmware
Maybe some of their software engineers used to work for Microsoft, I will wait until they fix it.
Mick
I recorded a quick video to explain the issue and the work around which may work for Quad's, sounds like there's a different and more serious problem with the HEX setups?
Naza-M New v3.10 Firmware RC/TX Calibration Issue & Work-around (http://www.youtube.com/watch?v=eEasHaqlbjg#)
I updated my original naza/gps to the new firmware last week.
I was using a PPM jeti receiver without any problems on the previous firmware, BUT as i went through the various setting in the new firmware/assistant i noticed that the flightmode was intermittently flicking into failsafe.
I re-calibrated the radio, sub-trims etc etc, but when watching the Naza assistant Tx monitor it keeps flicking in and out of failsafe - no way i was going to attempt a flight so...
Downgraded to the firmware i was previously running - looking at the Tx monitor in that version - everything is rock solid.
Filed a bug report to DJI but don't expect to hear owt.
Better stick old version back on I spose
Quote from: Coyote on May 13, 2013, 10:42:18 AM
Very not good !!!!
Got to the field on the way to work, powered up the Hex, 3 red led flashes............ Hmm.......... 2 red led flashes............ Now thinking something is wrong, 1 led flash then off.......... Ok so now I know it's still on 3.10 not 2.02 ! Crap :(
Oh well, let's see how it goes........ Took off, Hex lifted up, held level, everything seemed ok, 1 minute on Hex goes nuts again, crashes inverted, all props destroyed this time. Luckily again Nex is not damaged.
Now I'm worried how I'm going to be able to go back to 2.02 again after it said it was but obviously wasn't.
How do you think this guy feels? :|
CarbonCore 950 / on DJI's *new* @Naza-M v2 Firmware* v3.10 - CRASH on Vimeo (http://vimeo.com/65691079)
<BLAM> merry Christmas!
Lesson to us all, don't chop the throttle in fail-safe mode :D
So .......
3.1 for Hex is a no fly zone?
Richard
I've not had any problems with the new firmware but may go back to previous to be on the safe side.
I've never understood why DJI in their firmware even considered the risk of stopping the motors automatically midflight (either in immediate or intelligent mode) - this has got to be one of the most risky things to do with any multirotor.
The manual contradicts itself (this from the latest version):
Quote
11. Throttle stick position should always be higher than 10% from cut-throttle during the flight!
14. By using Intelligent mode to stop motors, the motors will start or stop immediately when you
execute CSC. During normal flight conditions, you only have pull throttle stick under 10% will
not stop the motors in any control mode. You have to execute CSC to re-start motors if the
motors stop during the flight.
According to "The Splat Calculator" http://www.angio.net/personal/climb/speed (http://www.angio.net/personal/climb/speed) It takes 4.5s to freefall from 100m (excluding wind resistance) so gotta be quick to restart the motors.
How about:
CSC only ever starts motors
CSC only ever stops motors
?
Well thats enough to put me off upgrading my discovery for now sod that !
Well I just put the old version back on .. checked it about 10 times and test flight
Looks like the older version .. led blinking same .. and motor action normal
ow did you get the old version back on Faffer ? My assistant tells me its on but the LED`s don`t lie, its still 3.10
Problem seems to be in 'intelligent' mode. motors will cut at under 40% throttle if it thinks it's landed:
http://www.rcgroups.com/forums/showpost.php?p=24977334&postcount=19670 (http://www.rcgroups.com/forums/showpost.php?p=24977334&postcount=19670)
from thread:
http://www.rcgroups.com/forums/showthread.php?t=1536553&page=1312 (http://www.rcgroups.com/forums/showthread.php?t=1536553&page=1312)
Been reading through, quite a few folk having motors stop mid-flight.
Setting to 'immediate' throttle cut mode seems to workaround thou.
I just got my new Phantom and updated it with the latest firmware. I am facing the following problems:
1) In Atti Mode: I see the following LED sequence: RED RED RED yellow yellow, now this pattern has no mention in the manual... Any help?
2) The model seems to be very responsive to winds and gains altitude very quickly and is very agile.... What is the problem?
3) Just after 50% throttle all the 4 motors kick in and the model just goes 3-4feet up in the air. Now when I want it to land, it is not responding well before the 50% threshold. At 10-15% throttle, it just comes down fast. It topples over when it just barely touches the ground...
I calibrated the IMU and did the calibration as per the manual. So please help me out here.
I also have a NAZA installed on my F550 with the older version of firmware. That has much better control and response... I cannot understand what is going wrong in the Phantom.
1) That`s indicating No GPS lock ( 3 Red ) and Atti Mode ( 2 Yellow )
Red indications will go to two flashes, meaning some satellites locked, to one flash ( more sats locked ) to no red flashes indicating full sat lock
2) Being too responsive is down to gain settings that you can change in the assistant
Quote from: Coyote on May 14, 2013, 07:17:19 AM
2) Being too responsive is down to gain settings that you can change in the assistant
Sorry, I didn't get you. You mean that the gain is less or high?
If it's too responsive to your stick inputs you need to lower the att gaons. If it's too responsive to wind or height then it's the other gains for roll / pitch / yaw and level need lowering
Well first attempt after a reflash of 3.10 went well, the wind was a stupidity level but the Hex took off and held, nice smooth response, no erratic behavior........
Not holding my breath, but progress at least
Hmmm. I've just seen the update on the DJI website, and thought I would ask on here to see if anyone has tried it. Having seen the responses, I think I'll hang fire on updating for a while first, and see how things pan out.. The less wobble when decending does tempt me though...
Andy
Not wishing to tempt fate but since upgrading to 3.1 I have flown for 104 minutes without issue (14 battery cycles).
Is anyone informing DJI about these problems?? They may have sent out the update and could be blissfully ignorant of any issues.
I've reported along with lots of others; I even posted a nice friendly message commenting on how good the positive aspects of the upgrade have been.. Got piss-all response though not even an email confirmation.
Is it worth knocking up a table to show combinations of motors, ESC's, receivers, batteries, props, transmiter etc to see what combos have the problem and which dont??
Me -
DJI 550 hex copy (RCTimer), RCTimer BL2830/11 1000kva, RCTimer 30amp SimonK ESC's, Spektrum AR9000, Turnigy 5000MaH 4 cells, Graupner 8 x 5 and JR DSX9 MkII - no issues
DJI F450 ARTF kit with Naza v1 + GPS.. RC Gear is DX8 and AR8000 (with satellite and TM1000).
No flight issues so far but haven't been able to save rc calibration settings.
Did they not learn with the S800 fiaso. New firmware for controllers needs to be extensively tested because in the end we are talking thousands of pounds worth of equipment in the air.
Quote from: tomg on May 13, 2013, 10:23:37 PM
I've not had any problems with the new firmware but may go back to previous to be on the safe side.
I've never understood why DJI in their firmware even considered the risk of stopping the motors automatically midflight (either in immediate or intelligent mode) - this has got to be one of the most risky things to do with any multirotor.
The manual contradicts itself (this from the latest version):
Quote
11. Throttle stick position should always be higher than 10% from cut-throttle during the flight!
14. By using Intelligent mode to stop motors, the motors will start or stop immediately when you
execute CSC. During normal flight conditions, you only have pull throttle stick under 10% will
not stop the motors in any control mode. You have to execute CSC to re-start motors if the
motors stop during the flight.
According to "The Splat Calculator" http://www.angio.net/personal/climb/speed (http://www.angio.net/personal/climb/speed) It takes 4.5s to freefall from 100m (excluding wind resistance) so gotta be quick to restart the motors.
How about:
CSC only ever starts motors
CSC only ever stops motors
?
I'm not sure if this will interest anyone but I just did a 'bounce test'.. I killed the throttle, waited for the motors to stop then whack it back to WOT again to see what happens:
Naza v3.10 bounce test (http://www.youtube.com/watch?v=9GqEHpB9gwg#)
i haven't flown mine since doing the upgrade. i'll wait a while to find out from those of you who are (much) more experienced when it's sorted. that may sound a bit selfish, but i don't know enough to set about trying to sort this myself.
Heres my flight test of FW3.1 today, it didnt go so well :(
Naza FW 3.1 (http://www.youtube.com/watch?v=o1YZE-YvGww#ws)
You guys that are having flight problems, have you tried restoring defaults?
I didn't, I re-entered all the gains though. Here's a view from the ground when in GPS mode.
http://m.youtube.com/watch?feature=plcp&v=vgbe5SOR4VM (http://m.youtube.com/watch?feature=plcp&v=vgbe5SOR4VM)
I might re-wind mine...
not flight tested it but stuff the issues or chance of wrecking the Vulcan its not worth it...
DJI Naza 3.1 software.
Hexa ,turnigy plush 45amps,750kv, 1045 carbon props,FY680 + my own gimbal and GP 1.
4 flights while two of them were quite far away.
This is latest flight I did with new software with GPS.
First HEXA range test. (http://www.youtube.com/watch?v=OwgkEdRdpBI#ws)
Nice Marcin! Getting some good range now :D, Ian fingers crossed for ya m8.
First test flights with the v3.10, was blowing a steady 10-15mph gusting to about 25 at times!, watch the big tree blowing about!. So far I like the update the quad has a more locked in feel in both gps and atti, and so far it hasn't dropped out of the sky!........ :-X
This vid is a quick mash up of the 1st 2 flights, just taking it steady and on high alert for a flame out!! Next time out i'll give it some stick!
Jim.
www.youtube.com/watch?v=NgU6S_Agx5o&feature=youtu.be (http://www.youtube.com/watch?v=NgU6S_Agx5o#ws)
Your Gopro 3 looks better in 360 on YouTube then my Gopro 1 in 720 HD ;D
Quote from: marcin on May 15, 2013, 01:48:33 AM
Your Gopro 3 looks better in 360 on YouTube then my Gopro 1 in 720 HD ;D
I used the Gopro 2 for this video!! Didn't want to risk the gp3 in test firmware!
Jim.
ffs.....now it's even more interesting !
Given that people are getting a more 'locked in' feeling with the new firmware and mine was all over the place, Im beginning to think I may have an issue with my Hexa. I really dont feel comfortable with the way its moving about.
Does anyone have any suggestions?
ROVguy - with the last incarnation of the firmware I found I had to wait at least two minutes after getting the green light to indicate a GPS lock to get a really good GPS lock.
My guess is that it went green on about 4 satellites but waiting a couple of mins after getting green locked about 8 - 9 satellites.
Might be worth a try????
Thanks for that, I do note that the LED kept flashing green twice as opposed to once.
DJI Innovations have now released a statement
http://www.rcgroups.com/forums/showpost.php?p=24999163&postcount=789 (http://www.rcgroups.com/forums/showpost.php?p=24999163&postcount=789)
QuoteAbout Naza-M V3.10 Firmware
Since the Naza-M V3.10 firmware has been launched, we received some feedbacks that the aircraft cannot be armed after updating and the center position of the stick is abnormal.
We currently suspended the upgrade of firmware V3.10. And DJI will release new firmware in the very near future.
For those who had already upgraded the firmware V3.10, you can use the Assistant Software V1.8 to restore to firmware V2.02, and you can download the software
mmm glad I have have not had time to fly and had the old version back on before even trying
Ian did you get it back on ok ?
Nope, it said it was the old firmware on the old assistant, but the LED's were double flashing and red LED count down on the GPS lock. I loaded up the new assistant and sure enough it showed V2 firmware was still on it.
Quote from: Coyote on May 15, 2013, 01:58:27 PM
Nope, it said it was the old firmware on the old assistant, but the LED's were double flashing and red LED count down on the GPS lock. I loaded up the new assistant and sure enough it showed V2 firmware was still on it.
cant you put the old assistant on a different computer and plug the hex in.
i tried for about 2 and a half hours to update my new gopro3 on my pc and then give up.
rattling my brain for 10 minutes i had a plan - try it on the mrs laptop - hey presto - worked straight away
worth a try?
I don't have any other computer to try it, but good idea :)
Cant you uninstall the new version then install the old version (after rebooting) ?? I can email you the programme if you cant download it.
I tried that, the old assistant shows V1 firmware being installed as far as its concerned, then reboot and its not, its V2 :(
But second flight done on V2 firmware and no problems again so far
I took my quad out for another test yesterday, it flew great again :)
The new throttle handling confused me at times but I still think its a plus point, just got to get used to it!
So far i like the new fware. The interface is now nicer like the wookong m, which was upgraded also a month or so ago. I much prefer the idle now, as before she was light on the ground after the csc. The props just tick over at anywhere between 0-50% now, which is more 'relaxing'.
My gains are way too low though, although she was stable in the air, she's drifting a lot. I know a lot of folk don't appreciate a too locked in feel, but i like my craft to stop when i centre the stix. Personal pref, specially when filming in tight spots!
Andy
jeez Ian ...I just got flight in deep hills FPV quite far away with hexa and 3.1 soft.
They have launched a new firmware 3.12. Has anyone tested that? Is it worth the upgrade?
Will try it this evening when I get home.
Quote from: rchobbyaddict on May 17, 2013, 12:00:40 PM
They have launched a new firmware 3.12. Has anyone tested that? Is it worth the upgrade?
I've just installed it and the calibration bug is fixed :D yay.
I saw this, seems like the iOSD is now compatible with Naza V1 &2:
http://www.dji-innovations.com/dji-iosd-mark-ii-firmware-2-00assistant-software-2-00-user-manual-2-04-released/ (http://www.dji-innovations.com/dji-iosd-mark-ii-firmware-2-00assistant-software-2-00-user-manual-2-04-released/)
N.B with the addition of the extra hardware of course!
P.S wonder who'll stock the new 'PMU with added canbus support' first?
Quote from: flybywire on May 17, 2013, 12:37:45 PM
I saw this, seems like the iOSD is now compatible with Naza V1 &2:
http://www.dji-innovations.com/dji-iosd-mark-ii-firmware-2-00assistant-software-2-00-user-manual-2-04-released/ (http://www.dji-innovations.com/dji-iosd-mark-ii-firmware-2-00assistant-software-2-00-user-manual-2-04-released/)
Oooo! :o
Hmm, looking at someone's 3.12 flight after they were flying fine on 3.1
First Test with v3.12 = crash! (http://www.youtube.com/watch?v=uuyJ4Nym5LQ#ws)
Not totally convinced its a step forward ........... Lol
This chap has just made a comment that he had 'connected up the motors incorrectly', this caused the flip
Iain
Yes he just replied on RCG it was his own fault .............. phew :)
Just noticed the 'Receiver Advanced Protection' feature. Sounds like it's to prevent flyaways due to a faulty receiver module (freeze or lockup?) or receivers where the failsafe (flight mode) hasn't been correctly set?
(http://s10.postimg.org/mzyr2dnqt/RAP.jpg) (http://postimg.org/image/mzyr2dnqt/)
Just been out with my F550 tonight with 3.12 on it and it flew fine.... well as much as I could tell fine as there was a bit of wind throwing it about.
Video coming soon.
Quote from: Coyote on May 17, 2013, 06:55:30 PM
Yes he just replied on RCG it was his own fault .............. phew :)
yep looks like it. anyone had any yaw issues yet ? I am having one frame wants to yaw to the left.
Tried re calibrating the compass?
Glad to see 3.12 is looking better than 3.1
Lets hope sunday is a good day to get people out to try
Richard
Quote from: Faffer on May 17, 2013, 11:09:24 PM
Glad to see 3.12 is looking better than 3.1
Lets hope sunday is a good day to get people out to try
Richard
hum I have just looked to see if there is an update and mine says 3.10 and NO update so were is 3.12 coming from ?
You need to install the new assistant too :)
Quote from: DaveyLC on May 17, 2013, 11:41:49 PM
You need to install the new assistant too :)
just seen it on DJI site thanks ;)
Dont think im brave enough
Flew a couple of pack on my Naza today with latest 3.12 firmware.. no issue.. didn't feel as spongy as 3.10 .. few people reporting fly away's with 3.10 .. so worth upgrading if you have not rolled back.
I was having issues on centre'ing but all seems to be sorted.
Also updated my Phantom.. did not really notice any difference..
Just uploaded 3.12 now.
Remembers stick centering - Check
No magic blue smoke - Check
Intelligent mode fixed - Yet to be determined
LED sequencing correct - Check
So far so good, no test hover in the front room tonight, the misus would literally kill me :)
Gotta say the one issue I did have that when i did RTH it did not land anywhere near where it set off from. It was at least 10-15ft away?!?! Before it was pretty much on the mark each time.
I was very happy with 3.10 and had no issues but as there was another upgrade/bug fix I installed that too.
Just reporting back to hopefully inspire a bit of confidence for those who had issues with 3.10.
3.12 is just fine - no issues whatsoever - 49 minutes in the air and tried everything - all modes, RTL etc etc - all perfect.
Agree with team FTP though about RTL - it always lands 8 feet West of where the system was armed !!
PS the 49 minutes were not one flight - 7 x 7 minutes !!! The first couple of batts were lots of takeoffs and landings to give it a workout.
I can go with the "lots of take offs"
does take some getting use too!
Iain
So do we think its safe to update ?
my machine is not seeing the new update...
Is anyone else having any probs getting a decent satellite lock on the new firmware with a Vtx running? I have an ImmersionRC 5.8vtx 600mW mounted the the opposite end of the craft from the GPS. Gets a perfect (no reds) lock in under a minute without but as soon as I power up the Vtx I get 2 or 3 reds. I've tried putting the vtx antenna underneath the frame but no difference.
Tempted to try the SAW filter mod - anyone here tried it? Looks damn fiddly.
TomG - I have exactly the same set up as you but my Vtx is within 6 inches of the GPS - no issues whatsoever - full lock within 20 seconds.
Have you got any power/battery cables anywhere near your GPS ?? A pal of mine had a similar problem to you and moved a coupe of wires away from the GPS and problem solved.
Do you know anyone with a similar GPS and/or VTX you could swap with to help identify where the problem lies?
I had that issue when i took the gps off its "stick" and mounted it onto the chassis. Put it back on the stick and all is well
Thanks. I should have added the GPS is on its stick so is about 6cm above the top plate towards the rear of the craft (TBS disco frame). I have the power cables running alongside the battery between the plates and to the current sensor which is in front of the Naza.
I'll post a pic shortly incase I've done anything daft..
Mines taking ages to get a lock too thought it was just me :D
This is the current setup.. the Vtx was previously mounted on the front of the top plate with the antenna pointing up but I've since tried moving it to between the plates (you can just see the antenna pointing down). I can power everything up bar the Vtx and get a perfect lock, plug in the Vtx and get 2 or 3 red flashes which it doesn't recover from.
My general plan with the layout was to try to separate the Vtx / RF noisy stuff at the front from the receiving stuff kept the back of the craft.
(http://s23.postimg.org/bcmiqckjb/IMG_20130518_194351.jpg) (http://postimg.org/image/bcmiqckjb/)
(http://s23.postimg.org/6givynkdz/IMG_20130518_194431.jpg) (http://postimg.org/image/6givynkdz/)
(http://s23.postimg.org/tw0t40453/IMG_20130518_194534.jpg) (http://postimg.org/image/tw0t40453/)
(http://s13.postimg.org/rn2dm6e0j/2013_05_18_20_43_17.jpg) (http://postimg.org/image/rn2dm6e0j/)
This is mine.. I have taken the GPS of ezOSD and mounted on top plate..
VTX is on one of the arms..
Naza GPS on Pole (folding mount)
ezUHF at rear..
Noticed if I get too near with TX it takes time for the Naza GPS to get a lock..
Also some cams emit bad RF.. worth winding the cable going to the FPV cam around a ferrite ring..
Had another flight this morning, no issues on 3.12, everything working just fine, used intelligent cut off as well this time
Thanks Jumpy07, I mounted my vtx in the same position as yours, definite improvement, seems to keep the lock through the flight & the transmitter stays nice and cool. Have a karma on me :)
Test flight at work today outside the office with the Naza-M v2 Firmware v3.12 on a V1 Naza, Seems good so far :) only managed a quick flight more to follow!. I have concluded that the Tarot 650 quad is a great slow flyer but when u push it hard it turns into a bit of a mush pig!!
Anyone else love the sound of a Huey?? Just like bein back in nam ;D
www.youtube.com/watch?feature=player_embedded&v=aM8ge8I2EMU (http://www.youtube.com/watch?v=aM8ge8I2EMU#ws)
Jim.
NIIIICE! That is one stable, smoooooth Quad! Nice work!
Seems to work well on 3.12
Keukpa
Look good Jim :)
I am finding the decent wobble is much better now, big improvement, but if I`m totally honest I`m not really seeing with my Hex a noticeable difference in GPS hold or level flight so far.
There is nothing wrong with it in level or GPS, but it`s no better than it was in the first place really IMO.
I am going to repeat my gain tuning though in case its better on different gains to the old firmware.
Well my Quad is really locked in and is less "sloppy".... apart from that i like it...
OK i fell victim to the 50% Throttle "Have i calibrated my ESCs correctly" debate until i read the small print :'( (but that's between me and you :laugh:
Lol Gundy!! ;D
Jim.
This thread has gone all quiet I see, having just got back from holiday, I'm considering updating my Naza to the latest firmware, am I safe to do so now?
I'm flying it on the Naza v2 and its fantastic...
Edit - how's this for stable!
http://youtu.be/rQDGW_MXWB8
I'm flying with v3.12 and have been since it was released.. No problems here :)
Well slightly randomly mine has started to go slightly mad now when on GPS mode. The quad simply darts off in various directions and ends up listing quite a bit. This of course is making it fairly uncontrollable. Once you flick back into Atti mode it is fine. Hmmmmmm what to do now, done the Naza Dance etc....
Sorry to repost this video but it sort of seems relevant :)
This is how the new firmware handled a landing with 3.5 propellers instead of 4 :D
NAZA w/GPS equip DJI F450 - Standard prop failure and impressive landing by Naza. (http://www.youtube.com/watch?v=Edhino40Gm4#ws)
To be honest I didn't even know I'd lost a prop when it went down and I'm VERY impressed it didn't smash its self to pieces.
Quote from: Teamftp on June 07, 2013, 04:08:45 PM
Well slightly randomly mine has started to go slightly mad now when on GPS mode. The quad simply darts off in various directions and ends up listing quite a bit. This of course is making it fairly uncontrollable. Once you flick back into Atti mode it is fine. Hmmmmmm what to do now, done the Naza Dance etc....
I had a similar thing happen on my quad before I taped up the sides. BUt that was before I updated to latest v.
<iframe src="http://player.vimeo.com/video/65978426" width="500" height="281" frameborder="0" webkitAllowFullScreen mozallowfullscreen allowFullScreen
I was heading toward the copse, but about 20 seconds in the quad 'kicked up at an angle and picked up speed. I didn't have much time to react, so didn't try manual although I could control yaw, but not pitch, forward or back. NAsty.
GoPro got a good dunking (without case!) Still works though.
Taped up the sides?
Andy
Mines now not playing ball :o :o
luckily not bent it yet but she just will not behave.
Mine's awesome on 3.12. Better take offs, much better descents, and easier to land. Mega! :thumbsup:
Is it me or do the hexa's seem to be getting all the problems???
I`m finding the code fine now apart from it twice falling over forward on landing lol Lands level, then oops :)
Anyone had issues with jerky response to control inputs after the upgrade? I've updated mine, but it is very annoying to fly now, very stable yes, but very jerky when trying to do anything other than fly straight and level...
That's on a F330 quad, Jeti rSAT ppm rx, and 3s 3000mAh packs...
Andy
Not really Andy, but I use noticeably lower gains now compared to previous versions.
I think I may have traced the problem, although I need to test fly it after work. The Jeti rSat receiver was set to output a PPM stream that was "direct", i.e. as it is received from my Jeti transmitter. Looking at it on the oscilliscope at work, the timings of the PPM pulse train, was a little erratic (varying between about 19ms and 30ms). I've now set it to "computed" with a repetition rate of 20ms, to remove the erratic timing. The oscilloscope shows a rock steady repetition rate now, so fingers crossed this should sort the jerkiness out!
Cheers
Andy
I was right, changing the PPm repetition rate to a fixed 20ms, has sorted the jerkiness out. It seems the Naza units are a bit fussy when it comes to the PPM input side of things...
Cheers
Andy
I had nothing but problems with PPM with my Naza, I swapped back to PWM and everything worked great.
What radio gear are you using? I've had two 12 minute flights this evening, and the only problem was me getting a bit cocky flying in manual mode :)
Andy
That`s with Chainlink UHF, I have heard of the same issues with Dragon Link too
If you can get the PPM output on an Oscilloscope, i would be interested to see what frame repetition rates you are getting, and whether they are stable or not. Mine was jumping around from about 19ms to 30ms. Set it to 20ms fixed in the Jeti software, and it is behaving itself now...
Andy
I thought this upgrade had settled down so I upgraded my Naza today as I have just fitted it to a new Spidex V2 quad. The upgrade downloaded and installed, it then prompted me to do the IMU calibration, the basic took 30s and the advanced a 2-3 minutes BUT I still can't get CSC to start the motors, even at high idle speed. If I press the "IMU status button" it says I need to do the calibration. I have lost count of the number of times I have been round this doing both the basic and advanced calibrations. Each time I do this I get a variety of different values in the acceleration Z axis, with ERROR appearing frequently.
What am I doing wrong? Any advise?
What are your LED`s doing after bootup ?
Quick flashes of all colours, then 4 green flashes, then normal config for GPS with no satellites.
Here is a quick video http://youtu.be/vZCO9CtQp68 (http://youtu.be/vZCO9CtQp68)
Mick
Well that looks fine, in your GUI in the stick calibration screen, I take it the rudder and aileron / elevator show full travel to the bottom right when your arming it ?
Yes, I have checked that and repeated the stick calibration, still no response. The motors emit beeps and twitch on boot up so I assume the ESCs and motors are OK. As they are new motors I tried an old one and no difference. Baffled.
I would like to revert to the old software to check that it is a problem with my setup with 3.12, how do I do this?
If you flick ino ATTI mode at startup, do you get flashes of the yellow led? 4 quick flashes means the naza unit is warming up, and won't start the motors. You have to wait to get 2 fast flash, and then it will start fine.
Andy
Hi Andy, if it boots up in atti (non-GPS) then I still get 4 slow green flashes then 2 rapid yellow flashes plus the red as it searches for the GPS. the 2 rapid yellow and 0-3 red flashes are repeated.
I raised a support ticket with DJI. Their response was to boot up, wait 5-10min then try CSC. This had no impact, still no response.
That sounds odd. I would maybe try the firmware update again then, and if that results in the same behaviour, get it back to where it came from, or DJI. Hope that helps
Andy
Kinda where I got to. I reverted to 2.1 and the motors started but the control was crap, totally unflyable. Looks like the IMU has been damaged. The reason for the new frame was I crashed the old one but did not think it was too bad; bent arms, broken props etc. It has seen worse. This crash was due to a motor wire failure, the second on that motor type so a major rebuild turned into a new frame, motors and ESCs.
I guess I need to get the Naza repaired or replaced. Sounds expensive.....
Thanks for all your help.
Mick
It looks like it has been fixed.
I got a response from DJI but it did not help, so I raised a support ticket with firstpersonview.co.uk and got an immediate response asking a few questions and asking for screen shots of the accelerations. Mark immediately diagnosed the problem that the Z axis thought is was in a 2.75g location, Saturn perhaps? and proposed a solution of hitting the Naza with a 6" screwdriver handle, then redo the calibration.
IT WORKED!
The calibration worked and the motors now run up and all looks well. I will now have to re-build the quad and flight test it.
Brilliant local service and better than DJI, thank guys.
Strange error, strange fix, but great result :)
GReat result. I think I had the same issue a while ago with my Naza v1. It's the only way I can explain the erratic flying. Happened after I decided to bung my quad on the rack of my pushbike, to transport it to the 'field' (which is a 10 minute hack up an old railway line). I guess the extreme vibes must have really pissed the Naza off, causing the events that baffled me at the time, given that I'd had many trouble free flights and no 'real' crashes to speak of.
I suppose the moral of the tale is; if your quad gets planted, or it's suddenly developed a mind of its own, get the screwdriver out!
Actually, joking apart, it actually works for some faulting hard disks as well. I used to watch old 'Wes' whack the disks with the venerable screwdriver (to the customer's horror), only to have the thing re-appear in Windows again! At least long enough to Ghost it anyhow. (not SSD's though of course!!) so may have a bit of scientific logic. Note to self: Check IMU calibration more often! :D
Cheers
FBW
Flight test completed successfully, all fixed, thanks to Mark at firstpersonview.co.uk Now I like 3.12 firmware.
Mick