Skip to content
Jetrell edited this page May 21, 2025 · 27 revisions

Setting up Failsafe for RTH

Warning

You can assign an RC mode switch to simulate how a FAILSAFE condition will respond, if the RX signal is actually lost in flight.
FAILSAFE mode will return the aircraft to the home location. But it should not be used in place of RTH mode for manual activation. Functionally, FAILSAFE mode does not work the same as RTH mode in all cases.
So bear in mind, that while the FAILSAFE mode is activated, the FC will behave as if the radio link is lost. This means you will not be able to Disarm.
To regain control, either -

Foreword

The goal is to configure both your flight controller and radio receiver so that failsafe does as you expect in every situation.

For failsafe to work optimally INAV needs to know it's in a failsafe event and not just doing regular RTH. This is necessary for it to correctly handle loss of GNSS signal while returning to home. Or to handle functions that can be operated by stick command in RTH mode. e.g. nav_rth_alt_control_override

This assumes you have regular GNSS navigation modes like RTH working already.

Configuration of receiver

You have several options on how to configure your receiver:

Option one

Set your receiver to NO PULSES/ CUT in the case of radio signal loss.
NO PULSES / CUT is generally best used for modern RX links. The RX will send data via the serial connection, to inform the FC of a Failsafe condition. Or a loss of that data by hardware failure also triggers a failsafe.

Option two

Set your receiver to FS POS. Also set one of the receiver channels to output a value to activate INAV FAILSAFE mode when the radio link is lost.
Set up INAV FAILSAFE mode on that RC channel.

Option three

Set up FS POS so the radio receivers throttle channel outputs a value below the rx_min_usec setting in an RX Failsafe condition. This will trigger INAV FAILSAFE when the RX link is lost.
The throttle channel lower endpoint may need to be temporarily set to the lowest setting allowing the failsafe value to be set low also. Once the receiver failsafe setting has been saved the throttle endpoint can be returned to the normal value.

Configuration of INAV

Go to the Configurator Failsafe tab, and enable RTH as Stage 2 failsafe.

For fixed wing set failsafe_throttle_low_delay = 0 or else it will disarm the airplane in flight when Failsafe triggers, if you have the throttle low for the default time period.

The behavior of RTH can also be configured in Navigation: RTH mode

Loss of GNSS during Failsafe RTH will result in an emergency landing. So make sure the following are set to avoid surprises:

  • nav_emerg_landing_speed - default is 5 m/s. Alter for a fixed wing.
  • failsafe_off_delay - default will disarm after 20s. Increase or decrease to suit the estimated time required, for the general altitude you fly at.
  • failsafe_throttle - The default setting of 1000uS will cause a copter to revert to the DROP procedure if not increased to slightly below hover throttle.

For more information on the way Failsafe operates if GNSS data is lost, see here.

Verifying that failsafe works as intended

Verify that your failsafe works without props:

  1. Remove all props

  2. Go outside, Arm and apply throttle. Walk/run more than 10 meters away from the arming location and then turn off the radio transmitter.
    The aircraft should now try to climb. This can be seen by the motor/s increasing in speed. And in the case of a fixedwing. The elevator will deflect upwards, as if to climb. And the ailerons will also deflect, as if it's turning back towards home.
    Also verify that you're able to regain control by turning on transmitter again, and move the ROLL/PITCH stick more than failsafe_stick_threshold

Note

If you are using a fixed wing without a magnetometer enabled, you will need to run with the airplane before the test. This is because GNSS speed needs to be above a certain threshold to acquire a valid heading. Without a valid heading failsafe will not initiate.

Now, verify that failsafe works while in flight:

  1. Put the props on again

  2. Take off, fly at least 50 meters from the home arming location. Then turn off the radio transmitter.

Tip

Do this over soft grass if its a multicopter. While if it's an airplane, it's better to have some altitude.
To regain control after a failsafe event, you must move the roll/pitch sticks more than failsafe_stick_threshold in order to regain control.


INAV offers additional failsafe safety features

failsafe_min_distance and the action you wish to invoke failsafe_min_distance_procedure

failsafe_throttle_low_delay (Time throttle level must have be low before auto disarm)
This setting could ruin your day with a mid-air disarm. But conversely save you from personal injury if it is forgotten to disarm the craft (not using motor stop also goes a long way to making the craft safer as the spinning propellers are a visible sign the craft is armed and dangerous).

Further reading and settable parameters are available here - https://github.com/iNavFlight/inav/blob/master/docs/Failsafe.md#failsafe_throttle

WIKI TOPICS

Wiki Home Page

INAV Version Release Notes

8.0.0 Release Notes
7.1.0 Release Notes
7.0.0 Release Notes
6.0.0 Release Notes
5.1 Release notes
5.0.0 Release Notes
4.1.0 Release Notes
4.0.0 Release Notes
3.0.0 Release Notes
2.6.0 Release Notes
2.5.1 Release notes
2.5.0 Release Notes
2.4.0 Release Notes
2.3.0 Release Notes
2.2.1 Release Notes
2.2.0 Release Notes
2.1.0 Release Notes
2.0.0 Release Notes
1.9.1 Release notes
1.9.0 Release notes
1.8.0 Release notes
1.7.3 Release notes
Older Release Notes

QUICK START GUIDES

Getting started with iNav
Fixed Wing Guide
Howto: CC3D flight controller, minimOSD , telemetry and GPS for fixed wing
Howto: CC3D flight controller, minimOSD, GPS and LTM telemetry for fixed wing
INAV for BetaFlight users
launch mode
Multirotor guide
YouTube video guides
DevDocs Getting Started.md
DevDocs INAV_Fixed_Wing_Setup_Guide.pdf
DevDocs Safety.md

Connecting to INAV

Bluetooth setup to configure your flight controller
DevDocs Wireless Connections (BLE, TCP and UDP).md\

Flashing and Upgrading

Boards, Targets and PWM allocations
Upgrading from an older version of INAV to the current version
DevDocs Installation.md
DevDocs USB Flashing.md

Setup Tab
Live 3D Graphic & Pre-Arming Checks

Calibration Tab
Accelerometer, Compass, & Optic Flow Calibration

Alignment Tool Tab
Adjust mount angle of FC & Compass

Ports Tab
Map Devices to UART Serial Ports

Receiver Tab
Set protocol and channel mapping

Mixer Tab
Set aircraft type and how its controlled

Outputs Tab
Set ESC Protocol and Servo Parameters

Modes Tab
Assign flight modes to transmitter switches
Standard Modes
Navigation Modes
Return to Home
Fixed Wing Autolaunch
Auto Launch

Configuration Tab
No wiki page currently

Failsafe Tab
Set expected behavior of aircraft upon failsafe

PID Tuning

Navigation PID tuning (FW)
Navigation PID tuning (MC)
EZ-Tune
PID Attenuation and scaling
Fixed Wing Tuning for INAV 3.0
Tune INAV PID-FF controller for fixedwing
DevDocs Autotune - fixedwing.md
DevDocs INAV PID Controller.md
DevDocs INAV_Wing_Tuning_Masterclass.pdf
DevDocs PID tuning.md
DevDocs Profiles.md

GPS

GPS and Compass setup
GPS Failsafe and Glitch Protection

OSD and VTx

DevDocs Betaflight 4.3 compatible OSD.md
OSD custom messages
OSD Hud and ESP32 radars
DevDocs OSD.md
DevDocs VTx.md

LED Strip

DevDocs LedStrip.md

ADVANCED

Programming

DevDocs Programming Framework.md

Adjustments

DevDocs Inflight Adjustments.md

Mission Control

iNavFlight Missions
DevDocs Safehomes.md

Tethered Logging

Log when FC is connected via USB

Blackbox

DevDocs Blackbox.md
INAV blackbox variables
DevDocs USB_Mass_Storage_(MSC)_mode.md

CLI

iNav CLI variables
DevDocs Cli.md
DevDocs Settings.md

VTOL

DevDocs MixerProfile.md
DevDocs VTOL.md

TROUBLESHOOTING

"Something" is disabled Reasons
Blinkenlights
Sensor auto detect and hardware failure detection Pixel OSD FAQs
TROUBLESHOOTING
Why do I have limited servo throw in my airplane

ADTL TOPICS, FEATURES, DEV INFO

AAT Automatic Antenna Tracker
Building custom firmware
Default values for different type of aircrafts
Features safe to add and remove to fit your needs.
Developer info
INAV MSP frames changelog
INAV Remote Management, Control and Telemetry
Lightweight Telemetry (LTM)
Making a new Virtualbox to make your own INAV
MSP Navigation Messages
MSP V2
OrangeRX LRS RX and OMNIBUS F4
Rate Dynamics
Target and Sensor support
UAV Interconnect Bus
Ublox 3.01 firmware and Galileo
DevDocs Controls
DevDocs 1wire.md
DevDocs ADSB.md
DevDocs Battery.md
DevDocs Buzzer.md
DevDocs Channel forwarding.md
DevDocs Display.md
DevDocs Fixed Wing Landing.md
DevDocs GPS_fix_estimation.md
DevDocs LED pin PWM.md
DevDocs Lights.md
DevDocs OSD Joystick.md
DevDocs Servo Gimbal.md
DevDocs Temperature sensors.md

OLD LEGACY INFO

Supported boards
DevDocs Boards.md
Legacy Mixers
Legacy target ChebuzzF3
Legacy target Colibri RACE
Legacy target Motolab
Legacy target Omnibus F3
Legacy target Paris Air Hero 32
Legacy target Paris Air Hero 32 F3
Legacy target Sparky
Legacy target SPRacingF3
Legacy target SPRacingF3EVO
Legacy target SPRacingF3EVO_1SS
DevDocs Configuration.md
Request form new PRESET
DevDocs Introduction.md
Welcome to INAV, useful links and products
iNav Telemetry
DevDocs Rangefinder.md
DevDocs Rssi.md
DevDocs Runcam device.md
DevDocs Serial.md
DevDocs Telemetry.md
DevDocs Rx.md
DevDocs Spektrum bind.md
DevDocs INAV_Autolaunch.pdf

Clone this wiki locally