Skip to content

feat(manual_control): replace stick override threshold with double-flick gesture#27041

Open
gguidone wants to merge 1 commit intomainfrom
gg/rc-override-double-flick
Open

feat(manual_control): replace stick override threshold with double-flick gesture#27041
gguidone wants to merge 1 commit intomainfrom
gg/rc-override-double-flick

Conversation

@gguidone
Copy link
Copy Markdown
Contributor

Solved Problem

RC override was too sensitive: a single frame of sufficient stick velocity triggered an immediate mode switch. This caused accidental overrides from brief stick bumps and possibly objects resting on the stick, RC override had been disabled entirely on most vehicles as a result.

Solution

Override now requires a deliberate back-and-forth roll movement within 0.5s. A stick held at any position, bumped accidentally, or weighted down by an object cannot trigger it, only an intentional snap in opposite directions can.
Commander.cpp is unchanged, it still reads sticks_moving from manual_control_setpoint and switches to POSCTL as before.

Changelog Entry

  • RC override now requires a roll double-flick gesture instead of a single stick movement threshold. Controlled by existing COM_RC_STICK_OV parameter.

Test coverage

  • Fast double-flick right→left and left→right: fires override
  • Single flick: does not fire
  • Stick held statically at any deflection: does not fire
  • Hold right >0.5s then flick left: does not fire
  • COM_RC_OVERRIDE = 0: gesture disabled entirely
  • RC loss mid-gesture: no override fires, failsafe proceeds normally

…ick gesture

RC override during autonomous missions now requires a deliberate roll double-flick (right→left or left→right) within 0.3s instead of a single instantaneous stick velocity threshold. A static deflection or an accidental single bump can no longer trigger the override.
COM_RC_STICK_OV is reused as the deflection threshold for each flick; no new parameters are introduced.
@farhangnaderi farhangnaderi requested a review from MaEtUgR April 11, 2026 01:31
@farhangnaderi
Copy link
Copy Markdown
Contributor

@MaEtUgR You might wanna take a look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants