UAV DevBoard pilots,
I am putting the most recent releases of MatrixNav and AileronAssist back on line. I briefly reverted to the previous releases while I investigated a system issue that I just ran into.
I just bought an EasyStar, ready to fly, with radio, servos, ESC, and radio already installed. I did some flying with MatrixNav. Most of the time it worked fine, but once in a while there were problems that popped up at random. Once in a while the firmware believed the radio signal is lost, and reverts to return to launch mode. Sometimes the elevator will work in only "bang-bang" control mode, responding to manual control by going either full up or full down. Typically, the problems arise at random, after about 10 minutes of flying.
After some investigation, I discovered a system issue that a few of you have already run into. It turns out that low battery voltage will cause a "brownout" situation for the CPU. It turns out there was a problem with the ESC. Although the CPU did not reset, some of the hardware configuration registers reverted to their default values. This will cause the firmware to think the radio signal is lost, and it will go into return to launch mode. This will happen with any of the releases of MatrixNav or AileronAssist.
When I have some time, I will take a closer look at handling low battery voltage.
In the meantime, be sure to use good batteries and a quality ESC.
Altitude hold is now available as an option in the most recent releases of the control and navigation firmware for the UAV DevBoard, MatrixNav1.7, and AileronAssist1.6. Both are available from the UAV DevBoard home page
The altitude hold function has been tested by both Sid and myself. According to Sid, it is "precise".
During my tests, AileronAssist was able to hold my Goldberg Endurance in a turn at a 45 degree bank angle, at constant altitude, for 30 minutes.
Next, I am going to implement waypoints.