AutoQuad FC fw v6.6


It's been a while since I've posted an update on the progress of the AutoQuad flight controller.  The event that we've all been waiting for has arrived with ST Micro's announcement and subsequent release of their STM32F4 product line.  As expected, the micro-controller is pin for pin compatible with their STM32F2 series which the AQ v6.1 hardware was designed for.  This meant it was a drop-in replacement.  The most important new feature of the chip is the implementation of ARM's Cortex M4 core with a hardware FPU!  This means that we can now do floating point operations in a single clock cycle.  All forms of add / subtract / multiply / integer conversion, etc are single clock cycle instructions with the divide and square root instructions taking 14 cycles.  This is a significant step forward for math hungry applications like AutoQuad.

As soon as I could get my hands on one (around November I think) I had it on a board working to port my ground Unscented Kalman Filter code to fit into the 168MHz MCU.  With some optimizations, it ended up fitting with processing room to spare.  The current version leaves ~40% idle time during flight.  The filter is interesting because it brings all of the important estimated states and observations under a single mathematical model.  This means that each observation can influence any number of state estimates if there is determined to be co-variance between them.  The theoretical performance improvements over my old fixed gain techniques is high.  17 states and 16 process noise terms are estimated at 200Hz observed by 13 sensor measurements.

A benefit to using such a filter onboard is that it can adapt to changing variance of sensors and measurements on the fly.  This removes the need to do ground based flight calibration simulations which was a drawback to the original fixed gain methods.  Once you have a calibrated IMU, it can provide accurate state estimates "out of the box."  While this is nice, the biggest improvement is the accuracy of the state estimates it can produce.  States like 3D accelerometer bias and 3D rate gyro bias are critical to accurate attitude estimates which is the only way that you can propagate acceleration measurements through velocity and position estimates with any kind of accuracy.

Other than the upgrade of the MCU, the hardware is mostly unchanged from the original v6.1 layout.  However, there have been a lot of new features added to the firmware since last year.  What I call DVH (dynamic velocity hold) allows the pilot to control the craft's velocity in 3 dimensions while AQ handles everything else.  Let go of the sticks and the machine holds position.  AQ now speaks mavlink so it can be configured and controlled from any ground station that supports the protocol.  A comprehensive parameter set has been established that allows configuration of almost all aspects of operation.  Gimbal support and expanded mission capabilities have been added.  1-wire support for pre and post flight communications with ESC32.  Too many more to list here.

With the help of Max Levine I created this video to demonstrate the autonomous mission capabilities of the current firmware (version 6.6):

If you use the uBlox LEA-6T as the onboard GPS module, AQ can record raw satellite observations to its uSD card along with the normal flight log.  With this data and data from a local base station, you can use post RTK to get extremely accurate position and velocity estimates (~ centimeter accuracy.)  In fact, I use the RTK velocity estimates as an absolute data point in scoring the filter's performance in the ground simulations used to tune the variance and noise parameters used by the UKF.  Future work might include onboard RTK calculations using a linux based application processor mounted on a daughter board.  This would bring the system's performance to an entirely new level.

Here is what the actual flight path looked like of the flight shown in the above video using post processed RTK:


I need to thank the small group of people who have worked very hard to test, write utility software and interfaces, create documentation and generally improve the AQ  platform.  It is still very far from a finished, polished flight controller, but it has come a long way because of their help.

As with ESC32, I have decided to release the AutoQuad FC firmware under an open source license.  It can be found at:

I would also like to invite anyone interested to participate in a public beta test of the system.   Sensor calibration, setup and configuration is still a lengthy and sometimes tedious process so I would discourage anyone who thinks they can bolt the board to a frame and start flying as that is not at all what you should expect.  I have authorized manufacture and sale by ViaCopter and Flyduino who are taking orders in a few days.

E-mail me when people leave their comments –

You need to be a member of diydrones to add comments!

Join diydrones


  • Hi Bill,


    I was thinking and research with the parallel PID controller, What do you use as a setpoint for the velocity and angle ? For the angle you probably use the angle setpoint of the joystick.

    Do you use a second order trajectory generator ?

  • Joe: It's probably best to ask these sorts of questions on the AQ forum.

    AutoQuad Forum • Autonomous Multi Rotor Vehicle Controller
  • Will the development of the modified versions of the QGroundControl and Android ground stations be open?


  • After reading through the wiki, I can simplify my questions - it'd be nice if it behaved like a real wiki with history so you can see what has changed...

    Will the development of the modified versions of the QGroundControl and Android ground stations be open?

    Since the beta board is missing the extra pressure sensor, are any of the A/D pins broken out on the ST to feed external sensors?
    Will future pcb runs include the missing pressure sensor, or breakout the A/D's (if unavailable)?


  • Developer


    Please read the wiki, before commenting...  

    When to recalibrate:

    Static & dynamic recalibration: when an AutoQuad board is repaired. Change of the IMU sensors and/or the MCU.
    Dynamic recalibration: change of frame, change in layout like rewiring powercables, change in ESC’s or their position, installation of large iron masses in the proximity of the flightcontroller

  • as a user, i cannot agree with such calibration, when i uninstall gamble camera, i need recalibration and consume whole 24 hours , crazy, wish you could simplify the calibration process and enhance code strength to support the slight slew.

  • Well, it's not just board-to-frame.  It's also the resulting thrust-vector from motor mounting tollerances, etc.  What happens if you have a rough landing and just slightly tweak the frame or an arm?  Gotta throw it out?

    But I agree, I think some of the complaints about APM are probably because we try to be so adaptive, it allows sloppy building, etc.

  • @RL
    If you follow the DJI recommended mounting method (a very thin piece of double sided tape) i think you'd struggle to get out by anywhere near that much. Versus the hoards of people who seem to slam an APM on the coffee table and say "that looks about right" it seems to work well. But enough about DJI, this is an AQ thread and I have my tracking number :) Tupperware is standing by!!
  • @Crasher, re: leveling

    Well that seems stupid.  So what happens with a Wookong or Naza if your mechanical mounting has the board slightly off-level?  Nothing is perfect, and it's pretty easy to have a 1-2° error on leveling.

  • @beatforevet
    Because it's big maths! Blame Intel/AMD for that not AQ!
This reply was deleted.