Sample report

Every section of the report, one real log

The paid report is long on purpose: a verdict without its evidence is a guess with a font. This is the whole structure for the Betaflight 4.2.9 (e097f4ab7) STM32F405 log, with the measured values shown and the tune values withheld.

1. Log quality and coverage

64/100 — Acceptable (Missing Maneuvers). 3 observations passed, 4 caveats recorded.

• Tuning-relevant flight time is 43.1s (dedicated maneuver windows)
• Verified throttle sweep from hover into the high-throttle band to map motor RPM noise
• Verified full-throttle punchout present for TPA breakpoint calculation

What the log could not give us:

• Logging rate is 1719.5 Hz — 1 kHz class; below the 2 kHz class recommended for optimal FFT resolution
• Debug mode set to NONE (GYRO_SCALED or GYRO_UNFILTERED recommended for noise filtering)
• Missing step response stick flicks (quick 50%+ Roll/Pitch flicks) for PID response modeling
• Missing propwash dive (climb above hover, then chop throttle) for D-term tuning

2. Measurements

Axis	Overshoot	Rise (10–90 %)	Settle (±5 %)	RMS error	Confidence
roll	8.6 %	54.9 ms	86.7 ms	0.146	good
pitch	28.9 %	47.5 ms	69.8 ms	0.197	good
yaw	22.4 %	100.6 ms	157.0 ms	0.171	good

3. Spectrum peaks

Frequency	Axis	Type	Amplitude
30.0 Hz	roll	low_frequency	-3.2

4. Diagnostics and their provenance

No structural issue crossed its threshold on this flight. The report says so rather than inventing one.

Each line in the paid report carries the rule that produced it, the measured value, the threshold it crossed, and where in the log it was measured. That is what makes the verdict arguable: a pilot who disagrees can see exactly which number they disagree with.

5. Before → after

Every parameter that moves, with the log's own header value on the left. For Betaflight 4.2 and older the changes are CLI PID integers and filter frequencies, because simplified slider multipliers do not exist in that firmware's log header.

Profile	Values moved	PID / filter / misc	CLI size
Cine	17 of 27	11 / 4 / 2	45 set lines
Freestyle	13 of 27	12 / 0 / 1	45 set lines
Race	13 of 27	12 / 0 / 1	45 set lines

6. The CLI block

Three scripts, one per profile. This is the shape of the Freestyle block; the numeric values are replaced with an ellipsis on this public page.

# Easyquadtune — Freestyle, 45 set lines
# PID integers (Betaflight 4.2 path)
set p_pid_roll = …
set i_pid_roll = …
set d_pid_roll = …
set f_pid_roll = …
set p_pid_pitch = …
set i_pid_pitch = …
set d_pid_pitch = …
set f_pid_pitch = …
# Filters
set gyro_lowpass_hz = …
set gyro_lowpass2_hz = …
set dterm_lowpass_hz = …
set dyn_notch_min_hz = …
# Feel
set iterm_relax_cutoff = …
set anti_gravity_gain = …
save

Cine and Race are emitted from the same log with the same rule set, differing only where the profile's targets differ. A profile switch never re-uploads or re-analyses the log.

7. What the report cannot tell you

• Whether the frame is cracked, a motor bearing is dry, or a prop is bent. The log shows the symptom of that, not the cause.
• Your AUW, prop size or motor KV. A log has no idea what the aircraft weighs.
• Whether the tune feels right to you. It reports what the traces measured.

8. Exports

JSON for the full machine-readable report, an HTML report for sharing, and print/PDF for a notebook. The report is yours whether or not the licence is still active in this browser.

Easyquadtune is not affiliated with Betaflight. Published 2026-10-21. Measurements come from the maintainer's own flight logs; an example is illustrative of the method, not a tune for your aircraft.