Closed GoogleCodeExporter closed 9 years ago
How would be this algorithm:
If the Stick is at its zero Position, then the trim switches work normal.
If a stick is not at zero then the trim switches can trigger your described
behavior.
trigger could be
- a single trim puls
- a long trim pulse (in the desired direction?) (i think i prefer this)
- a sequence of one plus and one minus
instant trim is then added when the according stick returns to zero.
Disadvantage to your proposal: -You need one keypress for each stick-direction
-Detection of the zero position is a little bit fuzzy
Advantage: -The keys are more related to the feature,
-You can selectively use the feature
Possibly we dont need to switch on-off this feature?
Original comment by th...@t-online.de
on 19 Oct 2010 at 6:02
Your proposale does not meet the envisioned result. The proposal was to have a
single key press result in inflight trim correction for all 3 axis. This should
be happening at a moment where you hold the model in a straight flight with the
sticks. Therefore you cannot use trim keys to do this, since these are
(ergonomic design ?) only accessed when you take your thumbs off the sticks. So
you must use the other switches (or a custom "bottom" switch).
You need (even in your proposal) a way to turn it off. Too risky, since you
potentially offset all trims, and potentially with large values.
I do understand your concern about detecting the zero position. Maybe a long
switch activation reads the sticks, and a short press activates the new trim
settings.
Or maybe even simpler: a press reads, and immediatly applies the new settings.
Somewhere in time you (pilot) have to handle the trim change, and why not
immediatly, while you are busy correcting the flight behaviour.
Proposal:
Assign a single switch (menu item: INSTATRIM OFF/TRN/AIL/ etc..)
When activated, immediatly read 3 axis sticks and "add" to inflight trim.
I am not sure whether "add" or "replace" is best for the inflight trim.
Original comment by harm.del...@echostar.com
on 20 Oct 2010 at 9:00
Original comment by th...@t-online.de
on 7 Sep 2011 at 11:04
Original issue reported on code.google.com by
harm.del...@echostar.com
on 12 Oct 2010 at 6:49