Tuning Copilot
The Tuning Copilot turns your flight log into concrete, conservative PID tuning advice. It reads the attitude- and rate-tracking quality the analysis already computed, decides whether tuning is safe and worthwhile, and — when it is — proposes specific gain changes plus a ready-to-load ArduPilot .param file.
It appears as a card on the flight view for multirotor flights, and it is included free with every analysed flight.
LogHat never writes to your aircraft. Every suggestion is something you review and apply yourself in Mission Planner or QGroundControl. Always re-fly in STABILIZE at low altitude before any AUTO mission.
What it looks at
The copilot is driven by metrics extracted during analysis:
- Attitude RMSE (roll / pitch / yaw tracking error, in degrees)
- Rate-loop RMSE (how well the rate controllers follow demand)
- Vibration levels
- AutoTune status — whether AutoTune has ever been run on this airframe
Safety gates come first
Before it proposes anything, the copilot checks for conditions where tuning would be the wrong fix. If any of these fire, it returns no suggestions and tells you what to resolve first:
- A CRITICAL mechanical or electrical safety alert
- Vibration above 30 m/s/s (fix mounts / props / notch filter first)
- A physical motor imbalance (check CG, arms, prop wear)
- Compass interference (re-calibrate first)
- Significant battery sag (pack health first)
- A probable-crash signature on the flight
This prevents the classic mistake of chasing gains when the real problem is mechanical.
The suggestions
When tuning is safe, the copilot proposes per-axis changes to the rate-loop P gains. Each suggestion shows:
- The parameter (e.g.
ATC_RAT_RLL_P), the current value, and the proposed value - The percentage change — hard-capped at ±25% per call for safety
- A plain-English reason tied to the specific telemetry that drove it
- Whether running AutoTune would be a better choice than manual changes
Grounded in real cases
The suggestions are accompanied by references retrieved from LogHat's Vector AI crash-knowledge corpus and ArduPilot parameter documentation — so you can see the reasoning behind a recommendation, not just a number.
Exporting the .param
The card gives you two one-click actions:
- Export .param — downloads a standard ArduPilot parameter file containing only the suggested changes, each annotated with its previous value and rationale as comments. Load it via Mission Planner → Config → Full Parameter Tree → Load.
- Copy — copies the same
.paramtext to your clipboard.
Scope
The Tuning Copilot currently supports multirotor (Copter) airframes. Plane and VTOL tuning is planned for a future release; for those vehicle types the card explains that tuning suggestions are not yet available.
Next: Vector AI — ask your flight data anything in plain English.