User Manual

USER GUIDE
129
its present location. This condition could be caused by bad compass
calibration, a loose or rotated compass, high wind, or a configuration
problem. Note: You must disarm and rearm the multirotor before RTH
will function again, once this message appears. The MicroVector
rebooted due to low voltage from the MicroVector’s power source. This
could be caused by overheating, a loose connection, or low battery.
RTH Engaged: Move sticks to
cancel
RTH has been triggered by the mode/submode switches, either
intentionally, or due to the receiver commanding this switch
combination during failsafe.
RTH Engaged: Too Many Rx
Glitches
RTH has been triggered because the receiver is no longer sending
signals to one or more channels.
RTH Engaged: Bad Rx Pulsewidths
RTH has been triggered because the receiver is sending invalid pulses
(too short or too long) to one or more channels.
RTH Engaged: Rx Failsafe Detected
RTH has been triggered because the MicroVector has detected that the
receiver is in failsafe.
Rudder Issue: Rerun Wizard!
When you ran the Receiver Analysis Wizard, the MicroVector did not
detect correct movement of the rudder input. Check your wiring and
settings and run the wizard again.
S.BUS Error Detected!
The MicroVector detected a communication problem with the S.BUS
TM
link. This could be caused by a loose connection, a power problem, or an
issue with your receiver.
Submode Input not Detected!
You configured a submode switch, but the MicroVector did not detect a
signal at the submode input during boot.
Throttle Failsafe Incorrect!
You have selected “Throttle Failsafe” method of receiver failsafe
detection, but the MicroVector detected that your receiver’s throttle
failsafe position is either too close to, or higher than, your normal
throttle off position. Please read section 6.13.1 - ‘Selecting the Failsafe
Detection Method’ for more info on throttle failsafe detection.
Throttle Issue: Rerun Wizard!
When you ran the Receiver Analysis Wizard, the MicroVector did not
detect correct movement of the throttle input. Check your wiring and
settings and run the wizard again.
Too much movement - aborting!
You invoked the “Record Flat Level Mounting” or “Rezero Gyros”
command, and the MicroVector detected that the model was moved
during the operation.
USB Mode - Outputs Disabled
The MicroVector’s outputs are disabled whenever the USB cable is
connected, and they remain disabled until AFTER you disconnect the
USB cable AND reboot the MicroVector.
Warning: Too much vibration
The MicroVector has detected that the vibration levels are too high,
which can cause control issues.