Skip to content

Conversation

landswellsong
Copy link
Contributor

Something popped up after flight-testing #30810

If the mount is set up in a way that the default mode is MAV_MOUNT_MODE_RETRACT, the RC switch becomes unusable since it can either retract or go to the default mode (which is again retracted).

This change flips the switch logic when the mount is retracted by default and when the switch is high the mount goes to RC targeting. The idea behind that is that since the default parameter is used up a reasonable guess is that since the user uses RC to open/retract the mount, they are likely having a transmitter-only (or primarily transmitter) setup. The MAVLink code path is unaffected.

Tested in SITL.

If the mount is configured to be retracted by default, the high switch position sets the mount to RC targeting.
@landswellsong
Copy link
Contributor Author

Hmm I'm not sure if my code relates to the falling tests, I just ran it locally and it passed:

>>>> PASSED STEP: test.Copter.AC_Avoidance_Proximity_AVOID_ALT_MIN at Sun Aug 10 16:13:02 2025
elfy@hobontica ~/src/ardupilot (pr/universal_mount_retract)*$ 

Should I just ignore them?

@peterbarker
Copy link
Contributor

Hmm I'm not sure if my code relates to the falling tests, I just ran it locally and it passed:

>>>> PASSED STEP: test.Copter.AC_Avoidance_Proximity_AVOID_ALT_MIN at Sun Aug 10 16:13:02 2025
elfy@hobontica ~/src/ardupilot (pr/universal_mount_retract)*$ 

Should I just ignore them?

We've merged a fix for that one.

@peterbarker peterbarker requested a review from rmackay9 August 12, 2025 01:51
@landswellsong
Copy link
Contributor Author

Flight tested the changes, works as I intended it to.

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