Closed GoogleCodeExporter closed 8 years ago
But it also makes easier to stop at 0 when you decide to redo all linkages.
For me it's a feature not a bug, but anyway I'm not against the pause, only if
it not means a single byte of flash more.
Last week enhancements took about 1336 bytes which is really a lot,
In my opinion we cannot afford to continue spending flash this way.
BTW doublekeys should be a compile option.
Original comment by romolo.m...@gmail.com
on 18 Aug 2012 at 6:05
Original comment by bson...@gmail.com
on 18 Aug 2012 at 8:03
For the first fly, trims should be at zero (all setting are done by linkage on
model, subtrim and PPMCA), so middle trim stop should not be a problem in this
case.
For a clear indication of middle trim, stop is better then pause.
But, in the idea of and efficient trim setting, a good solution is the
"autotrim" feature of Graupner MX24s / MC24 Black Edition : you put the stick
at the appropriate position to keep the model flying straight, then you active
a monostable switch and the radio transfers the orders of the sticks into the
trims.
Original comment by f.ague...@wanadoo.fr
on 18 Aug 2012 at 8:38
That exists already: Function Switches -> Instant trim.
Original comment by bernet.a...@gmail.com
on 18 Aug 2012 at 8:41
Original comment by bson...@gmail.com
on 18 Aug 2012 at 9:11
Original issue reported on code.google.com by
bernet.a...@gmail.com
on 18 Aug 2012 at 11:35