Think I just experienced a Naza flyaway with my Disco Pro.

[CurryKitten]

This would be a lot clearer if it wasn't for the fact that you took-off before a full GPS signal was made.  Although you were flying in ATTI, the fact that a partial GPS signal was there - I don't believe  means that it fails over to the "there's no GPS" mode and simply lands in a failsafe.  Clearly it shouldn't go bonkers either and fly into a wall either.

However, this may fall into the case of flying in an unknown or at least "inbetween" condition, and hence got unsupported/unpredictable results.

I'm not saying that's how it should be, but probably how DJI might view it.  There's certainly a lot to be said for open source FC firmware when you have this sort of situation - it's impossible for us to debug, so we have to speculate, the trust in the FC ebbs away.

[Heliotrope]

There's certainly a lot to be said for open source FC firmware when you have this sort of situation - it's impossible for us to debug, so we have to speculate, the trust in the FC ebbs away.

I'm very glad it's not open source, the number of people with the ability to play around with it properly would be tiny and many who think they could probably couldn't.

I'm sure that DJI have their issues but when you have the massive volumes of kit out there being flown by all sorts of people in countries all over the world any faults are usually identified and DJI have the resources to fix them (as they did last year with Wookong I believe). If Joe Bloggs enters the market and sells 100 units what are the chances of a failure showing up compared to someone selling 100,000 units.

Maybe I'm being short sighted but I can't see too many really useful major developments that we actually need with FC firmware. If what we have now works properly then personally I don't see the need for much more. Yes, I could let my imagination run riot, but the only big change I see coming is the use of Galileo in a few years as opposed to GPS.

[CurryKitten]

I'm very glad it's not open source, the number of people with the ability to play around with it properly would be tiny and many who think they could probably couldn't.

Something being open source doesn't mean the codebase is a free-for-all, people can submit changes/add-ons/features to the cows come home, but whether any of them make it in is determined by the committers on the project.

What it would allow is people to poke around if there is a perceived problem and look for any possible holes in the code that could cause the issue people are seeing.  There wouldn't be a huge number of people that would have the skill, or indeed the motivation to do this... but there doesn't have to be really - just one or two.  See KaptainKuk and the few guys doing branches of the official KK2 code.

I'm sure that DJI have their issues but when you have the massive volumes of kit out there being flown by all sorts of people in countries all over the world any faults are usually identified and DJI have the resources to fix them (as they did last year with Wookong I believe). If Joe Bloggs enters the market and sells 100 units what are the chances of a failure showing up compared to someone selling 100,000 units.

Sure - it's pretty obvious that the higher number of units = higher number of failures.  However, I don't see DJI doing anything about this.  I'm very much on the fence on this one, I've not had any issues on my Naza V1 FC, and I haven't really seen documented flyaways in which all the setup was followed rigorously.  So, perhaps the reports are hyped up, but they are certainly enough to put people off Naza, and so deserves some comment from DJI

[Heliotrope]

KK-  I didn't appreciate that that's how it would work - just shows how little I know which is why I'm happy to rely on DJI, for better or worse!

[dogzilla]

Although you were flying in ATTI, the fact that a partial GPS signal was there - I don't believe  means that it fails over to the "there's no GPS" mode and simply lands in a failsafe.  Clearly it shouldn't go bonkers either and fly into a wall either.

I've read the Naza manual front to back and the only warning about flying without a full GPS lock is that you might encounter some drift.

That being said, flying in Atti mode, the GPS shouldn't come into play whatsoever yet is has done and shifted me into the wall.

Im gonna e-mail DJI anyway and see what they think.

[hiccups96]

I dont think its got anything to do with gps tbh. There are accounts of exactly the same thing happening to Naza's which are not even equipped with gps. If it was a gps issue then flying in Atti mode shouldn't be affected. The most plausible explanation I've read is the Gyro/Acclerometer unit gets its knickers in a twist and and doesn't know when the quad is level anymore.

[DaveyLC]

Its my belief that most fly-aways are caused by one or more of the following:

1) Not allowing the GPS to get a fix before take-off.
2) Compass rotating on the stalk before or during flight.
3) Compass not being mounted high enough on the air-frame.