AP_Arming_Copter: Allow arming with unhealthy visodom in non-gps modes #29264
+33
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
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...