removed throttle integrator until I have more time to deal with the data
tweaked control loops to be more like RC1 for Max to try. They fly great BTW
tweaked config to be more better.
Mavlink - only cosmetic tweaks
git-svn-id: https://arducopter.googlecode.com/svn/trunk@2254 f9c3cf11-9bcb-44bc-f272-b75c42450872
The trunk is unstable, so please be careful. I've made a lot of changes based on the Sparkfun challange. Most include how we handle things like altitude, but the mission scripting has also been updated as well.
git-svn-id: https://arducopter.googlecode.com/svn/trunk@1920 f9c3cf11-9bcb-44bc-f272-b75c42450872
this makes it possible to allow a GCS to override RC input values for
non-HIL setups. This gives a way for a GCS to set an arbitrary switch
value, or set a precise PWM value for any control.
git-svn-id: https://arducopter.googlecode.com/svn/trunk@1789 f9c3cf11-9bcb-44bc-f272-b75c42450872
setting parameters via mavlink only saves them in memory. We need to
use AP_Var::save_all() to save them permanently
git-svn-id: https://arducopter.googlecode.com/svn/trunk@1748 f9c3cf11-9bcb-44bc-f272-b75c42450872
This allows MAVLink commands to override the RC input values. See the
discussion on the mavlink list.
git-svn-id: https://arducopter.googlecode.com/svn/trunk@1738 f9c3cf11-9bcb-44bc-f272-b75c42450872
this fixes the build with HIL_MODE_ATTITUDE and MAVLink enabled. Basic
MAVLink operation works.
git-svn-id: https://arducopter.googlecode.com/svn/trunk@1737 f9c3cf11-9bcb-44bc-f272-b75c42450872
