mirror of
https://github.com/iNavFlight/inav.git
synced 2025-07-13 11:29:56 +03:00
Wrong documentation regarding failsafe mode and skipping stage 1
According to @digitalentity this is wrong. Stage 1 cannot be bypassed by Failsafe mode and is threated the same way as example No pulses
This commit is contained in:
parent
eeaa20af43
commit
799833d1ce
1 changed files with 0 additions and 2 deletions
|
@ -25,8 +25,6 @@ __Stage 2__ is entered when your craft is __armed__ and __stage 1__ persists lon
|
||||||
|
|
||||||
__Stage 2__ is not activated until 5 seconds after the flight controller boots up. This is to prevent unwanted activation, as in the case of TX/RX gear with long bind procedures, before the RX sends out valid data.
|
__Stage 2__ is not activated until 5 seconds after the flight controller boots up. This is to prevent unwanted activation, as in the case of TX/RX gear with long bind procedures, before the RX sends out valid data.
|
||||||
|
|
||||||
__Stage 2__ can also directly be activated when a transmitter switch that is configured to control the failsafe mode is switched ON (and `failsafe_kill_switch` is set to OFF).
|
|
||||||
|
|
||||||
__Stage 2__ will be aborted when it was due to:
|
__Stage 2__ will be aborted when it was due to:
|
||||||
|
|
||||||
* a lost RC signal and the RC signal has recovered.
|
* a lost RC signal and the RC signal has recovered.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue