GRAUPNER mx-16 ifs, Programming Manual

Page: 121 / 132

121 Programming example: model helicopter
other menu settings which you entered separately for
each fl ight phase (see page 78).
For example, if the motor run is limited by the fueltank
size or battery capacity, you should set the stopwatch
to count down. Enter the maximum possible motor run
time, e. g. “5 min.”. The transmitter’s piezo buzzer now
starts emitting warning sounds starting at “30 s” before
“zero”, as described on page 53. You could assign the
transmitter control switch “C3” to this timer, by fi rst
activating switch assignment and then turning the throt-
tle limit control from its idle position in the direction of
full-throttle:
5:00
SEL
3
2
pitch min
clock front
C3
phase 2 hover
autorotat.
With the stopwatch halted, press the CLEAR button
at the basic display, so that the stopwatch switches to
“Timer” function. The timer then starts automatically
when you move the throttle limit slider towards full-
throttle, and stops again when you move the limiter back
to the idle range.
Suggested refi nement: speed governor
At some time you may wish to install a speed governor
(regulator) in your helicopter, e. g. the mc-Heli-Control,
to try fl ying with a system rotational speed which is
automatically maintained at a constant value. It makes
sense to couple the individual rotor speeds with the
fl ight phases, as this enables you to carry out further
fi ne-tuning.
The basic requirement when programming the transmit-
ter is to install and program the speed governor exactly
in accordance with the manufacturer’s instructions.
Of course, the
mx
-16iFS provides further facilities to
allow you to implement different rotational speeds in the
individual fl ight phases. A practical suggestion, which
includes the throttle limiter function, can be found in the
section starting on page 81.
If you have set up your helicopter as described in this
programming example, you will fi nd that it is capable
of carrying out extremely challenging fl ight tasks even
though it is not suitable for competition work.
We suggest that you should not make use of additional
functions until your model is fl ying perfectly, so that you
will be in a position to recognise and appreciate any
improvements. Whenever possible, it is always best to
implement additional refi nements one at a time, other-
wise you won’t know which change has brought about
any improvement. Bear in mind that the good pilot is
not recognised by the number of complex functions with
which he can cope, but by the results he can obtain
when fl ying a relatively simple set-up.