AQ board after repair going crazy, dangerous accident
Posted: Sun Jan 04, 2015 2:41 am
Hello everyone,
so, my AQ board has been repaired by Jussi (MCU replaced) and I've tested it today. Unfortunately the results are miserable (again).
After getting the board from repair it seemed to work again (the lights were up, new firmware flashed without issues, everything working alright). I made the setup as usual (motor mixing, radio type, quick level and MAG calibration etc.) and here's what happened:
Accident one
Testing everything at home, without props. Radio connection is good - motors are arming and powering up with throttle stick. The copter is responding to all radio commands. Suddenly it stops responding to radio inputs so I've checked radio connections - everything is as it should be, the Rx is powered up and connection to the board is okay. I couldn't disarm motors or actually do anything via my Tx, but the lights on the board didn't indicate that anything was wrong with the board - the green light was solid. Power reset made the board responsive again. The copter was then powered up for 20 or more minutes until I finished setting up all Ultra ESCs and everything seemed to work without issues again, so I proceeded with testing the hex handheld with props on.
Accident two
The firmware and ESCs are set up, props mounted. We power up the copter, let it initialize. My friend holds the copter above his head, I arm the motors and proceed to increase the throttle slowly, until the copter starts leveling itself. It all took maybe 10 seconds, and then, suddenly, the copter aggressively rolls 45deg left and applies really high throttle, much higher than it should. It would probably flip over if it wasn't for my friend preventing it from rolling any further. I lower the throttle to 0 - no response from the copter - it is still applying almost full throttle. Disarming the motors doesn't work either. Only powering the copter off completely by pulling the battery connector did the trick.
It's only a luck that I've already lost my confidence in AutoQuad during all previous failures of this FC and we performed the test handheld instead of letting the copter hover by itself. Otherwise we would have crashed expensive equipment.
Now, the funny part - what's in the AQ log? Absolutely nothing, the log just cuts off right before the accident happened. The entire accident was not logged, and that leads me to believe that the AQ board just froze, and before it did it applied random throttle to each motor.
Any ideas what's wrong? I think that the board is fucked up and needs replacement.
so, my AQ board has been repaired by Jussi (MCU replaced) and I've tested it today. Unfortunately the results are miserable (again).
After getting the board from repair it seemed to work again (the lights were up, new firmware flashed without issues, everything working alright). I made the setup as usual (motor mixing, radio type, quick level and MAG calibration etc.) and here's what happened:
Accident one
Testing everything at home, without props. Radio connection is good - motors are arming and powering up with throttle stick. The copter is responding to all radio commands. Suddenly it stops responding to radio inputs so I've checked radio connections - everything is as it should be, the Rx is powered up and connection to the board is okay. I couldn't disarm motors or actually do anything via my Tx, but the lights on the board didn't indicate that anything was wrong with the board - the green light was solid. Power reset made the board responsive again. The copter was then powered up for 20 or more minutes until I finished setting up all Ultra ESCs and everything seemed to work without issues again, so I proceeded with testing the hex handheld with props on.
Accident two
The firmware and ESCs are set up, props mounted. We power up the copter, let it initialize. My friend holds the copter above his head, I arm the motors and proceed to increase the throttle slowly, until the copter starts leveling itself. It all took maybe 10 seconds, and then, suddenly, the copter aggressively rolls 45deg left and applies really high throttle, much higher than it should. It would probably flip over if it wasn't for my friend preventing it from rolling any further. I lower the throttle to 0 - no response from the copter - it is still applying almost full throttle. Disarming the motors doesn't work either. Only powering the copter off completely by pulling the battery connector did the trick.
It's only a luck that I've already lost my confidence in AutoQuad during all previous failures of this FC and we performed the test handheld instead of letting the copter hover by itself. Otherwise we would have crashed expensive equipment.
Now, the funny part - what's in the AQ log? Absolutely nothing, the log just cuts off right before the accident happened. The entire accident was not logged, and that leads me to believe that the AQ board just froze, and before it did it applied random throttle to each motor.
Any ideas what's wrong? I think that the board is fucked up and needs replacement.