Closed GoogleCodeExporter closed 8 years ago
all apm modes (except manual) are constrained to max throttle.
But if your needing more throttle in stabilize mode, then indeed you should be
upping the throttle_max values. as that is a good indication if it doesnt have
enough power to climb or manuver.
Your max value should allow the plane to climb to the next waypoint altitude,
or to maintain a proper climbout during takeoff.
fbw-a mode is also constrained to max throttle but with max pitch and max bank
included.
I believe the default value is set a bit above mid range, for max power
savings. But usually with sufficient power for the standard platform.
I personally jack that up to 100 for performance vs power savings... as I will
be utilizing auto-takeoff.
Cruise throttle and Cruise speed are also very handy to tweek to your platform.
I am going to close the issue, but feel free to reopen if this doesnt satisfy
or you would like to request an enhancement or assistance in creating another
mode.
Darren
Original comment by Draconis...@gmail.com
on 1 Jun 2011 at 2:35
The code states the following and I do believe that most users think stabilize
does not touch throttle which is not true.
case STABILIZE:
nav_roll = 0;
nav_pitch = 0;
// throttle is passthrough
break;
Whether we should have a big warning in the doc or change the default (you
state that you change this value to 100 as well) as 75 is default.
I consider this as a bug and not a new feature.
Original comment by mbada...@gmail.com
on 1 Jun 2011 at 8:45
Original issue reported on code.google.com by
mbada...@gmail.com
on 31 May 2011 at 9:43