Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AP_Arming_Copter: Allow arming with unhealthy visodom in non-gps modes #29264

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Vabe7
Copy link

@Vabe7 Vabe7 commented Feb 9, 2025

This is essentially the fixed version of #29258, see more info about that at the bottom.

This allows arming in non-GPS flight modes like Stabilize, even if the visual odometry is unhealthy. The behavior is mostly copied from gps_checks.

I compiled one board with (fmuv3) and one without (Kakute F7 Mini) visual odometry. And for both boards I compiled plane and copter. I also tested it on a barebones fmuv3. With:

  • VISO_TYPE=1
  • EK3_SRC1_POSXY = 6
  • EK3_SRC1_VELXY = 0
  • EK3_SRC1_POSZ = 1
  • EK3_SRC1_VELZ = 0
    on Copter 4.5.7. the prearm message visodom unhealthy is shown in Stabilize. With this branch the message disappears in Stabilize, but appears again when changing to Loiter.

I initially only tested it for copter on sitl and fmuv3, after opening the initial pull request I got all the error messages about compiler errors in other vehicles and boards with only 1MB of storage. Realizing my mistake I closed the pull request. Now due to the rebase and force-push I can't reopen the original pull request. I'm sorry about the inconvenience, but on a positive note, I learned a lot about git today...

@Vabe7 Vabe7 force-pushed the allow_arming_with_unhealthy_visodom branch 2 times, most recently from 5b1383f to 2218afd Compare February 10, 2025 12:50
@rishabsingh3003 rishabsingh3003 self-requested a review February 10, 2025 22:17
@rishabsingh3003
Copy link
Contributor

rishabsingh3003 commented Feb 10, 2025

I will test this, I was about to raise a PR myself

@Vabe7 Vabe7 force-pushed the allow_arming_with_unhealthy_visodom branch 8 times, most recently from d9226c4 to 4a7d8bf Compare February 17, 2025 15:32
@Vabe7 Vabe7 force-pushed the allow_arming_with_unhealthy_visodom branch 6 times, most recently from eb1dcb6 to 84dcab9 Compare February 24, 2025 09:56
@Vabe7 Vabe7 force-pushed the allow_arming_with_unhealthy_visodom branch 2 times, most recently from 0b5b9ca to 2978dbc Compare February 28, 2025 12:30
@Vabe7 Vabe7 force-pushed the allow_arming_with_unhealthy_visodom branch from 2978dbc to f702274 Compare March 2, 2025 09:12
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