Naza M latest update

[3DJIM]

Im gonna do more exhaustive testing tomoz if weather holds! .... gulp!! but today it was fine, but so was Ians yesterday!



Jim.

[DaveyLC]

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 :)

[Coyote]

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

[ROVguy]

Not good!

[Coyote]

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.

[mattydred]

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.

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.

[mattydred]

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

[electricmick]

Maybe some of their software engineers used to work for Microsoft, I will wait until they fix it.

Mick

[DaveyLC]

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

[plingboot]

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.

[Gav]

Better stick old version back on I spose

[DaveyLC]

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

<BLAM> merry Christmas!

Lesson to us all, don't chop the throttle in fail-safe mode :D

[Faffer]

So .......

3.1 for Hex is a no fly zone?


Richard

[tomg]

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):

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  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
?

[Randall]

Well thats enough to put me off upgrading my discovery for now sod that !