Whats the idea behind removing failsafe channel fallback settings? How should I accommodate this?

[undiplomatic]

Good day,

I've just switched from Betaflight to iNav and am learning the ropes. I've done a lot of my iNav settings and tested the quad in my garage only.

I notice that iNav doesnt have channel fallbacks, ie a way to set what each channel should do in event of signal loss. As I'm using my DJI Air Unit as receiver (over SBUS), that means that each channels holds its last value if RC signal is lost, though somehow iNav does identify that signal is lost and triggers failsafe.

Whats the idea behind having removed fallback settings? I'm guessing that the delay period before full failsafe procedures are started should be short enough that the fallbacks dont matter?

[Jetrell]

This might help answer some questions about how INAV uses Failsafe .

If you require a certain channel to default to a specific position. INAV has a Programming (PLC) tab.. You can select a channel, and what postion you wish it to OVERRIDE too, in a failsafe condition.

[sensei-hacker]

If I'm reading your question correctly, it's probably answered best by looking at the Failsafe tab in Configurator.

That wiki page is certainly related, by may not EXACTLY match your question.

Failsafe options include:

Land safely

Fly home and then land

Fly home and hover overhead

Fly home while making sure to go AROUND the clump of trees, not flying into the trees

Given the available options, "set the roll stick to 1350" isn't likely to be better. You COULD do that, as Jetrell mentioned, but it's not presented as a likely option because one of the other choices is probably better.

[undiplomatic]

The channel fallbacks only engage for a short period to see if the signal comes back, before engaging land/return to home etc. Betaflight calls this Stage 1, iNav calls it Failsafe_delay.