Skip to content

vehicle-setup: allow testing all configured ArduSub motors - #4135

Draft
Daniiiil1 wants to merge 1 commit into
bluerobotics:masterfrom
Daniiiil1:codex/allow-testing-all-ardusub-motors
Draft

vehicle-setup: allow testing all configured ArduSub motors#4135
Daniiiil1 wants to merge 1 commit into
bluerobotics:masterfrom
Daniiiil1:codex/allow-testing-all-ardusub-motors

Conversation

@Daniiiil1

Copy link
Copy Markdown

What changed

  • detect configured ArduSub motor functions by their MOTOR<n> enum name instead of the numeric MOTOR1..MOTOR8 range
  • include the non-contiguous MOTOR9..MOTOR12 functions
  • default the displayed direction to forward if a firmware does not expose the corresponding direction parameter

Why

ArduPilot assigns MOTOR9..MOTOR12 to values 82–85, outside the contiguous 33–40 range used by MOTOR1..MOTOR8. The existing numeric range check therefore hides configured motors 9–12 from the PWM motor-test UI.

Matching the enum member name also avoids accidentally treating MOTORTILT as a numbered motor and naturally supports future numbered motor functions added to the enum.

Closes #4010.

Validation

  • bun --cwd core/frontend lint
  • bun --cwd core/frontend build
  • git diff --check

The repository-wide pre-push hook could not run in this environment because Docker is not installed; the frontend-specific checks above passed.

@CLAassistant

CLAassistant commented Aug 12, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@Daniiiil1
Daniiiil1 force-pushed the codex/allow-testing-all-ardusub-motors branch from 993c519 to 950d4c0 Compare August 12, 2026 06:29
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.

vehicle-setup: pwm-outputs: allow testing all configured motors

2 participants