Reading Blackbox without drowning
TUNING // FIELD_REPORT

Reading Blackbox without drowning

Published
Updated
Read time6 min read

Blackbox is a mirror, not a magic wand. It shows what the flight controller sensed and did, not whether your prop was bent. Start with three traces and one question: is this mechanical or tuning? Most pilots drown because they open a full-session log and try to fix twelve problems at once. One manoeuvre, one change, one comparison.

When NOT to log (or not to trust logs)

Reading Blackbox without drowning: When NOT to log (or not to trust logs)

SituationWhy logs mislead
Bent prop, loose motorGyro noise dominates, filters and PID look "wrong"
Motors heat-soakedNoise floor up; afternoon log ≠ morning tune
Several changes last sessionYou can't tell what did what
Logging rate too lowNoise peaks smeared; you guess wrong
Fresh pack vs tired packVoltage differs; the full pack always looks best

Fix props, tighten the stack and let motors cool. Logging a bent quad just records noise you'll try to fix with D, and then you'll be buying motors.

Setup: logging that helps

Before analysis:

  1. Logging rate: 2 kHz is a good default for most quads; go higher only if you need it and have the storage
  2. Debug mode: GYRO_SCALED logs unfiltered gyro next to filtered, which is what you want for noise checks
  3. One deliberate move per log: one hard corner, one flip, one punch-out
  4. Notes: prop type, pack number, air temperature; you'll forget otherwise

Betaflight Blackbox Explorer, PIDtoolbox or PID-Analyzer all work on the same ideas. The tool matters less than discipline.

Trace 1: Gyro (filtered vs raw)

Gyro is the FC's record of how the quad actually moved. Compare unfiltered and filtered gyro on roll or pitch.

PatternLikely meaningNext step
Spiky raw, smooth filteredFilters working hardIf stick feel is mushy, you may be over-filtered
Spikes on throttle punchesOften prop/motor/mechanicalInspect props, bearings, bell play
Constant fuzz all throttleESC noise, loose mount, bad bearingMechanical; see tuning after a crash
Spikes only one axisFrame resonance or loose cameraCheck that arm, mount, standoff
Raw and filtered both wildSevere mechanical or desyncLand; bench test motors

Common mistake: cranking D because the gyro line looks "busy" without checking whether the quad felt bad at that moment. Line it up with stick input and throttle.

Trace 2: Setpoint vs gyro (roll/pitch)

Setpoint is the rotation rate your sticks asked for; gyro is what the quad actually did. This is the core tracking view.

PatternLikely meaningKnob direction
Actual lags setpoint on snapsP low, FF low, or over-filteredSmall P or FF bump; check filters
Actual overshoots then settlesP high or D lowReduce P slightly or add D carefully
Oscillation on settleP/D balance or mechanicalDon't just add D; find the buzz source
Tracking good in hover, bad in turnsPropwash / throttle regionSee propwash tuning
Slow wobble (a few Hz)Often I-term, or P too high on a heavy quadAdjust I or P in small steps

Zoom in on one flip or one 180, not the whole pack. Line up the setpoint step with the moment you felt washout.

Trace 3: Throttle

Throttle ties problems to power ranges:

  • Punch-outs: prop/motor load, ESC noise, filter stress
  • Mid-throttle cruise: frame resonance, bearings
  • Falling throttle in turns: classic propwash zone

If ugly traces only appear when throttle drops in a hard turn, you're in propwash territory, and "more P everywhere" isn't the answer.

The motor RPM trace (with bidirectional DShot) confirms ESC telemetry is sane. Erratic RPM alongside gyro fuzz means fix telemetry before tuning the RPM filter. See RPM filter and bidirectional DShot.

Trace 4: PID sum and motors (when ready)

Reading Blackbox without drowning: Trace 4: PID sum and motors (when ready)

When basics are clear, look at PID sum and per-motor outputs:

  • Motor saturation: one motor pinned while others aren't → twisted motor or arm, damaged motor or wrong motor order
  • Oscillation in PID sum: a tune issue, if the mechanicals are clean
  • One motor working much harder than the rest: crash damage, a weak motor or an ESC channel fault

Don't start here on day one; gyro, setpoint and throttle answer most field questions.

Learn traces in order: gyro → setpoint vs gyro → throttle → PID sum. Note prop type, pack number and manoeuvre in your phone; you won't remember which file had "the weird split-S."

Workflow

1. One bad manoeuvre per log; don't fix everything at once
2. Compare before/after ONE change (save a CLI diff!)
3. Land when motors are hot; tired hardware gives misleading logs
4. Ask: did this trace look bad when the quad felt bad?
5. If no → look at rates, video or pilot input; if yes → one knob

A/B comparison tips:

  • Same battery type at a similar voltage
  • Same named manoeuvre: "left-hand power loop," not "sort of a loop"
  • Overlay logs in Explorer if your tool supports it
  • Write the change on paper: "FF roll +5" not "tweaked stuff"

Symptom → trace → action map

In the air you feelLook atOften fix
Sloppy snapsSetpoint vs gyro on rollFF, P, or filter reduction
Buzz after flipGyro settle regionD + filter, not more P
Nose drop in diveThrottle + pitch trackingMix habit, I, or tune, also camera angle
Mid-throttle humUnfiltered gyro at cruise throttleMechanical first, then RPM filter
Gets worse each packCompare pack 1 vs pack 4 logsHeat, hot climate filters

Common mistakes

  • Analysing a 6-minute log without zooming in on events
  • Changing PIDs because the gyro looks noisy when the quad feels fine
  • Ignoring throttle; propwash depends on it
  • No baseline log before changes
  • Logging a quad with a known bent prop "just to see"

When to stop staring at logs

If traces look mediocre but the quad feels great, stop tuning. Good enough beats perfect on a Sunday.

If traces look fine but it feels bad, check rates, camera angle, video antenna and radio link before another PID pass.

If both look and feel bad and the mechanicals check out, follow the order in Betaflight tuning basics: filters → P → I → D → FF.

Mechanical check before PIDs: noise tied to one motor means inspect that corner; spikes at one throttle point suggest prop or ESC; ugly only when the stick moves points to the tune. Swap props, re-log, then open Configurator.


Blackbox rewards patience. One trace, one question, one change, then fly again. Your logs should get shorter because the quad stops misbehaving, not because you stopped looking.

See also

Discussion

Comments aren't open on this post yet. Share it with your build group, or start a thread on X.