Naza M V2 wont start motors unless...

[onzabikes]

Hello,

After 1.5 years away from flying I dusted off my DJI F550 running a NAZA M V2 and the DJI E300 setup to find the motors won';t start up...

Plugged it into the naza software, done an update, calibrated the radio many times, all tabs are green when sticks centered, none of it has made any difference. I get the normal start up tone/beeps when I plug the battery in.

After a lot of searching most peoples issue seems to be they';ve got the throttle reversed or something similar but that';s not the issue with mine, as I said it was flying fine for a year till I put it on the shelf 1.5 years ago.

It';s a Futaba radio, the throttle isn';t reversed on the radio which I know can be an issue for some.

I';ve got an F450 too with exactly the same setup and that is flying fine with the futaba radio.

When I try to start the motors, the LED just flashes green fast when the sticks are in the start up position. And it will do that every time I put the sticks in the start up position, so it knows I';m trying to start but won';t let me.

Apart from that the LED status is fine, outdoors once it';s got full sat lock it just flashes green. Indoors I get 2 green flashes and 3 red flashes for poor signal. If I move the throttle to the middle then I get 1 green flash.

Doesn';t mattery if I';m in GPS, Atti or manual.

Now for the weird part... The only way I can get the motors to start up is if I try start the motors straight after I';ve plugged the battery in and it';s done it';s start up tone. If I leave it a few seconds longer and let it get sat lock or do a compass calibration etc, the motors won';t start up... Once I start the motors up straight after the start up tones I can stop/start the motors as many times as I like, even after it';s got sat lock etc.

This obviously isn';t a fix as in the field by the time I';ve done the compass calibration and got sat lock then it';s been too long. Just seems weird that I can start the motors if I start it within a couple seconds of plugging the battery in, but any longer and it won';t work... almost like once it';s properly started up, it finds a problem and prevents the motors spinning up.

I have taken a video of the issue however I';ve found this video on YouTube of someone having exactly the same problem. If you go 45-50 seconds in, you';ll see when he puts his sticks in the start up position, he too gets a rapid flashing green every time he tries it, same as my situation.

https://youtu.be/wS_3ec0_CeY?t=45s

I';d really appreciate some help getting this sorted, happy to provide any screenshots etc if required.

I look forward to checking out the rest of this forum too!

Many thanks
Josh

[ched]

I have a F450 with a Naza lite (with ';updated'; FW) and have had a couple of issues arming. I was able to plug in flight battery and connect Naza to PC and then I could see errors. My issues were reported as throttle issues I think. I solved by recalibrating tx but looks like you have tried that one.
Actually the issues weren';t permanently solved by recal as my tx (FlySky i6) had a dodgy yaw pot. Replaced the pot and all is well.

If your F450 is OK with your tx maybe its the rx having issues. Could you swap they rx and see if the fault moves with the rx?

Good luck and let us know how you get on.

[onzabikes]

Thanks for your reply, I think I';ve just figured it out after reading through the Naza manual. In short it was an IMU calibration that was needed, despite the software telling me it was fine.

In the manual it describes my problem:

"At the first motors start, the system will check the sensors Bias and you are asked to keep the aircraft stationary (no need of horizontal level). If you cannot start the motors and the LED blinks Green 6 times quickly, it means that the sensor error is too big. Please connect the assistant software, enter the "Tools" - > IMU calibration, carry out basic calibration.
Note: after the first successful motors start, this checking will be disabled and it is no need any more to keep the aircraft stationary during starting motors."

It says that it only does this check once when the motors spin up, so I guess that';s why I could spin the motors up fine as many times as I liked if I tried to do it right after I plugged the battery in. It obviously wasn';t finding an error quick enough so I could bypass it by turning the motors on quick.

I haven';t been out to fly yet to confirm it';s all fine but I can now spin the motors up fine on the bench no matter how long I leave it to warm up...

[ched]

That';s great news. Thanks for posting your solution, it will probably be handy for others in future.
Happy Flying