Skip to content

HardwareReport: show vehicle, frame and configured outputs - #369

Open
j-w9 wants to merge 1 commit into
ArduPilot:mainfrom
j-w9:hardware-report-vehicle
Open

j-w9 wants to merge 1 commit into
ArduPilot:mainfrom
j-w9:hardware-report-vehicle

Conversation

@j-w9

@j-w9 j-w9 commented Oct 17, 2026

Copy link
Copy Markdown
Contributor

Fixes #242.

  • Vehicle section (after Flight Controller): vehicle from the log's build type, plus the frame params with value names (FRAME_CLASS/FRAME_TYPE for Copter and Rover, Q_FRAME_CLASS/Q_FRAME_TYPE for QuadPlane, FRAME_CONFIG for Sub). Plane shows "QuadPlane" when Q_ENABLE is set, with "tilt-rotor" / "tailsitter" from Q_TILT_ENABLE / Q_TAILSIT_ENABLE.
  • Outputs section (after DroneCAN devices): each SERVOn_FUNCTION that is not disabled, with its name. An extra column shows outputs also sent as DroneCAN ESC or servo (CAN_Dx_UC_ESC_BM / CAN_Dx_UC_SRV_BM), counting only drivers assigned to a port (CAN_Px_DRIVER) with CAN_Dx_PROTOCOL = DroneCAN. The column is hidden when nothing is on CAN.

Value names are in a new param_values.json, taken from the current apm.pdef.json for Copter, Plane, Rover and Sub. Function names are kept per vehicle because a few differ (e.g. Plane's Motor7/TailTiltServo). A param file has no vehicle type, so it only gets the Outputs section, using the generic names.

Checked on two Copter logs. The Plane, QuadPlane (tilt and tailsitter), Rover, Sub and CAN cases were checked by calling the functions with test params, as I have no logs for those.

Vehicle and outputs

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.

HardwareReport: show configuration of vehicle and output pins

1 participant