What steps will reproduce the problem?
1.Curves can be used in place of expo to provide different expo values on
either side of stick neutral, reducing complexity of the firmware
2.Curves are also used for throttle to match the power output of the motor or
engine, which are typically non-linear with stick input
3. The two 9 point curves currently provided are insufficient to use with
sophisticated programming for advanced aircraft such as "stick switches" where
an increased rate could be added at the very end of stick travel.
4. In addition, the curve points are fixed at 4 points on either side of
neutral. An option to either move the fixed points, or add points would allow
for increase flexibility in programming. In the "stick switch" example above,
a curve could come in at 90 or 95% of stick movement.
5. Recommend a minimum of 6 total, 9 or 17 point curves
What is the expected output? What do you see instead?
This could replace issues 16 and 18.
What version of the product are you using?
V1.346-thus
Please provide any additional information below.
Original issue reported on code.google.com by jalowe1234@gmail.com on 2 Jul 2010 at 5:13
Original issue reported on code.google.com by
jalowe1234@gmail.com
on 2 Jul 2010 at 5:13