EasyquadtuneGuides
Read the diagnosis before the setting
These guides teach an order of reading a Betaflight blackbox log. They deliberately do not publish tune values: a number copied from someone else's airframe is a guess wearing a decimal point. Each guide names the setting to inspect and the trace that decides it.
Every page here is illustrative of the method, not a tune for your aircraft. Where a chart is shown, it was produced by the same engine that writes the paid report; where a rule is quoted, the threshold is stated so you can disagree with it.
How to read a Betaflight blackbox log: FFT noise and step response
A practical guide to what your Betaflight blackbox log actually measures: how an FFT finds real noise peaks, how step response separates overshoot from droop, and which one to fix first.
Why does my quad wobble on hard stops? A blackbox diagnosis order
A hard-stop wobble is not one fault. Separate low-throttle instability, I-term bounce, propwash and too much gain using the log instead of guessing.
Overshoot vs droop: how to read a Betaflight step response
A step response shows two different faults that look alike: a gyro that overshoots the command and a gyro that settles below it. Read the shape before you change a gain.
Frame resonance or prop noise? Reading a Betaflight blackbox spectrum
A blackbox FFT peak is not a diagnosis. Learn the difference between a fixed frame tone and throttle-tracking prop noise, and what the spectrum cannot tell you.
Betaflight I-term relax: bounceback, droop, and the cutoff direction
I-term relax fixes bounceback but can cause droop in held turns. Why a lower cutoff means stronger suppression, and how to tell which fault your log has.
Quad dips in fast turns: yaw washout, droop, or motor saturation?
A quad that dips or washes out in a fast turn is not automatically under-tuned. Separate yaw washout, pitch droop, propwash, saturation and I-term relax in the log.
When a blackbox log cannot support a tune (and how to fly one that can)
A short, noisy or hover-only blackbox log cannot measure a PID tune. Here is how to recognise an unusable log, what it can still tell you, and how to fly one that answers the question.
Where to start
- Is the log good enough? — logging rate, debug mode and stick manoeuvres decide how much any analyser can honestly claim.
- From log to CLI — the order: header values, traces, then settings.
- Overshoot vs droop — the two opposite failures of the same loop, and why more gain fixes only one of them.
What these guides will not do
They will not give you a PID table for a 5-inch quad. There is no such table that survives contact with a different motor, prop, battery or frame stiffness. What transfers between builds is the order of diagnosis and the shape of the evidence, which is what is written here.
Frequently asked
Do I need a blackbox log to use these guides?
No, but the advice is written for someone who has one. Without a log the guides still explain what each symptom usually means; with a log you can check which one your aircraft is actually doing.
Are the charts on these pages real data?
Where a chart appears it is generated from a real flight log by the same engine that produces the report. The text says which log, and the example is illustrative of the method rather than a recommendation for your build.
Why is there no complete CLI example?
Because a complete CLI for one airframe is not a lesson, it is a paste target. The paid report contains the full script for your log; the guides stop at which setting to inspect.
See the whole pipeline
A real log measured end to end: quality score, step response per axis, FFT peaks and what each profile changes.
Open the worked examplePrefer the interactive screen? Open the in-app demo or read the main tuning guide.
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.