Aeroquad 32 won't arm

This site is best viewed in a modern browser with JavaScript enabled.

Aeroquad 32 won't arm

dave-cz-

Hello everybody,
I'm trying to bring my old AQ32 flight controller to life after several years in a drawer, everything seems OK, I can see RC input sliders move with TX sticks, I can make all motors spin in test mode, but I can't arm the FC.
Please see attached some screens from configurator.
Of course I try it with USB disconnected and throttle at zero. The heartbeat LED is signalling "Normal (disarmed)". When I change flightmode to Autotune, the LED is signaling illegal mode (so I can see RC is working). There must be something I'm still missing.
Thanks for any advice.

aq32-flightdata.png

aq32-rcinput.png

aq32-flightmodes.png

aq32-armingsettings.png

yds

dave-cz- When I change flightmode to Autotune, the LED is signaling illegal mode (so I can see RC is working). There must be something I'm still missing.

Is the AutoTune module checkmark enabled?

configuring an AutoTune mode without the module enabled will do what you're describing..

dave-cz-

Forget about autotune, my question is not about autotune. I mentioned it only to demonstrate my RC input is working by initiating erroneous state by purpose. (But yes, autotune was enabled anyway)
The controller won't arm in any mode. I tried arming in Leveling, Horizon and Acro. Whenever I flip arming switch, it does literally nothing. Heartbeat LED just keep blinking Disarmed state and nothing happens.

raemin_bis

Neutral for throttle should be much lower (~400). Not sure this will solve your issue though. Generally speaking this error is due to a configuration the sytem considers as unsafe.

Maybe you could have a look at the log on the ground station?

dave-cz-

I agree it must be something in configuration, only I can't see it. I definitely try to adjust neutral for throttle.

Will it log anything even with no SD card inserted or it is necessary to insert SD card to be able to get any logs?

dave-cz-

Problem solved. I erased the board, uploaded firmware again and started configuration wizard from the scratch. Working OK after that. I don't know, what I have done wrong before.
Anyway, thanks for help. :-)