Skip to content

AUTOTUNE

nflyernz edited this page Oct 19, 2026 · 2 revisions

AUTOTUNE

Purpose: Examine authoritative ArduPlane AUTOTUNE session evidence in one DataFlash BIN, including active axes, runtime gain changes, completion milestones and save or restore evidence.

← Wiki Home

What you need

  • One ArduPlane DataFlash .bin or .BIN log containing the tuning period.
  • Supported AUTOTUNE mode and tuning records if you expect session details.
  • The APT desktop GUI. See the README installation instructions if needed.

Run AUTOTUNE Review

  1. Click Choose BIN… beside Source BIN:.
  2. Select the required aircraft BIN.
  3. Open AUTOTUNE from Overview or select the AUTOTUNE tab.
  4. Click Analyse.
  5. Review the detected sessions and axis evidence in the report panel.
  6. Click Docs for the in-app description and glossary.

If no supported session boundaries are present, APT reports No authoritative AUTOTUNE sessions found. It does not manufacture a session from isolated gain values.

Read the report

Sessions and termination

The report identifies each bounded AUTOTUNE session and shows:

  • Start and end positions in log-relative time.
  • Duration and termination reason.
  • Association with one or more detected flight windows.
  • Whether the normal stop was observed.
  • Relevant configuration captured at session start.

An interrupted or incomplete interval remains identified as such rather than being promoted to a normal completion.

Configured, selected and active axes

These labels describe different evidence:

  • Configured at session start — axes enabled by applicable configuration.
  • Selected — axes selected for the observed tune.
  • Tuning activity observed — axes with retained AUTOTUNE rate-process (ATRP) records.

A selected axis is not automatically an active axis. For each axis, the report can show the number of activity records, positive and negative demand periods, total observed demand time, longest demand period, and action-state transitions.

Runtime gains and completion

For an active axis, APT can show entry and final observed runtime values for FF, P, I, D, RMAX and TAU. It also lists gain-limit events and firmware completion milestones with their logged times.

Runtime gains describe values observed during execution. They are not automatically the values stored for the next flight.

Save, restore and parameter persistence

The report keeps several forms of persistence evidence distinct:

  • Save requested on exit or a completion milestone describes firmware save intent.
  • Restore path inferred describes evidence consistent with restoring earlier values.
  • Parameter-save records observed lists supported logged parameter writes and their triggers.
  • Runtime gain continuity observed links supported gain evidence from an earlier session.
  • Evidence unavailable for exit save/restore means the log cannot support a stronger conclusion.

A completion milestone or save request alone should not be described as proof that every tuned gain was persistently saved. Review the parameter-save records and any evidence warnings.

AUTOTUNE session with active axes, runtime gains and parameter-save evidence

The session separates configured and active axes, runtime gains, completion milestones, save requests and the actual parameter-save records observed for Roll and Pitch.

Limitations

AUTOTUNE Review reports firmware records; it does not judge tune quality, recommend gains or prove that the manoeuvres were flown safely. Missing messages, unsupported firmware and incomplete session boundaries limit what can be concluded.

The report also cannot guarantee that a requested save survived every later reset or parameter change. Use the recorded save observations, subsequent configuration and normal operational checks together.

Related information

Clone this wiki locally