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

ArmingChecks: disallow arming via parameter #21742

Merged
merged 2 commits into from
Jun 22, 2023
Merged

ArmingChecks: disallow arming via parameter #21742

merged 2 commits into from
Jun 22, 2023

Conversation

MaEtUgR
Copy link
Member

@MaEtUgR MaEtUgR commented Jun 20, 2023

Solved Problem

The carrier is maintaining or showcasing the vehicle powered but not armed and wants to make sure it's not accidentally armed.

Solution

  • Add parameter COM_ARMABLE defaulting to allow arming which can be set to false to disallow arming

Changelog Entry

For release notes:

Feature: New parameter: COM_ARMABLE if set to 0 arming is disallowed

Documentation: Parameter reference is automatically updated. Safety chapter does not specifically exist or does it?

Test coverage

  • I tested this in Simulation. Like expected it does prevent arming when disallowed but does not failsafe when the parameter is set in air.

Context

image

 COM_ARMABLE is set to "Disabled" will prevent arming.
 This allows to set the parameter when ground demoing a drone or
 if it's in maintenance for safety reasons.
@mrpollo
Copy link
Contributor

mrpollo commented Jun 20, 2023

Fun, we just enabled DEMO mode 🎉

@dagar
Copy link
Member

dagar commented Jun 20, 2023

We should do this lower level so that it can't be overridden by force arming (eg commander arm -f or command with magic value).

@MaEtUgR
Copy link
Member Author

MaEtUgR commented Jun 22, 2023

We should do this lower level so that it can't be overridden by force arming

Why would we do it differently than other checks? Force arming is not normally done or am I wrong? We should keep that one purely for the developer.

command with magic value

Is this necessary to keep? Don't we need a consistent way to enable/disable all checks and then it's obsolete?

@MaEtUgR MaEtUgR merged commit 20d0661 into main Jun 22, 2023
78 of 84 checks passed
@MaEtUgR MaEtUgR deleted the maetugr/com-armable branch June 22, 2023 11:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants