Skip to content

frontend: require local arming before motor tests - #4098

Open
Daniiiil1 wants to merge 1 commit into
bluerobotics:masterfrom
Daniiiil1:codex/guard-motor-test-arming
Open

frontend: require local arming before motor tests#4098
Daniiiil1 wants to merge 1 commit into
bluerobotics:masterfrom
Daniiiil1:codex/guard-motor-test-arming

Conversation

@Daniiiil1

Copy link
Copy Markdown

Summary

  • track whether the PWM setup page successfully armed the vehicle
  • send MAV_CMD_DO_MOTOR_TEST only while that page owns the arming state
  • keep motor controls disabled and explain the state when the vehicle was armed elsewhere
  • clear ownership whenever the vehicle disarms or this page requests disarming

This prevents opening PWM Outputs on an already-armed vehicle from immediately starting the periodic motor-test command loop.

Closes #3545

Validation

  • yarn eslint --max-warnings=0 --ext .vue --ignore-path .gitignore src/components/vehiclesetup/PwmSetup.vue
  • yarn stylelint src/components/vehiclesetup/PwmSetup.vue
  • yarn build
  • git diff --check

The repository pre-push hook could not start because Docker is unavailable in this local macOS environment. No hardware test was performed.

Signed-off-by: Daniil Mordanov <mordanovdania@gmail.com>
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.

Motor test page should check if it was responsible for arming the vehicle before sending motor test commands

1 participant