A structured, blackbox-driven PID tuning protocol based on step response analysis. Derived from the methodology implemented in PIDtoolbox (Brian White, MATLAB) and adapted for iterative field use. The protocol requires a .bbl log from a dedicated test flight; do not attempt to tune from a freestyle or racing session …

Betaflight supports four rate mode formulas. They all do the same job — map stick deflection (0 to ±1) to a commanded rotation rate (°/s) — but they parameterize the curve differently. Switching modes changes what the sliders mean, not what the quad feels like if you set equivalent parameters. Overview Mode CLI value …

Rates control how fast the drone rotates in response to stick input. Higher rates = faster rotation = more aggressive feel. A rate profile is shaped by three parameters — RC Rate, Super Rate, and Expo — plus the choice of rate system (Betaflight, Actual, etc.). Common Shorthand Profiles The 533 / 633 / 733 shorthand …

What happens inside Betaflight when you move a slider. The formulas here are derived from pid.c in the Betaflight source. Understanding the math makes the configurator sliders predictable rather than mysterious. The PID Control Loop flowchart LR RC[RC setpoint<br/>°/s] --> ERR GYRO[Gyro measurement<br/>°/s] --> ERR …

Blackbox records every sensor reading, RC input, PID output, and motor command at high frequency. It is the most powerful diagnostic tool available — without it, tuning is guesswork. How the Pipeline Works flowchart LR A([Gyro<br/>8 kHz]) --> B[Betaflight<br/>PID loop] B --> C[Blackbox<br/>logger] C -->|Compressed| …

The Betaflight CLI is the only source of truth for a complete build configuration. Configurator tabs show most settings, but the CLI exposes everything — including defaults that the GUI hides. Before any tune experiment, back up with diff all. After a session, back up again. Why diff all Instead of dump flowchart LR …

A PID controller is the core of what makes a flight controller work. Understanding what each term does — and what breaking it looks like — is prerequisite to any meaningful tuning. The Control Loop flowchart LR P([Pilot stick<br/>setpoint]) --> E{Error<br/>calculation} G([Gyro<br/>actual rate]) --> E E --> PT[P term] E …

A systematic PID tuning protocol based on the Joshua Bardwell / Brian White wobble-test methodology — rewritten to run entirely on free tools: Betaflight Blackbox Explorer, Betaflight Configurator, and Rylo. No PID Toolbox, no MATLAB, no paid subscriptions. This is the practical field protocol. If you want the math …

A propeller is a spinning wing, and like any wing it only makes clean thrust while air flows into it from the front — for a rotor, that means air coming from above and going down through the disk. Feed it clean air and it flies; stop feeding it clean air and it stalls, exactly like a wing yanked to too high an angle of …

533, 633, 733 are community shorthand for three popular freestyle rate profiles, and the number is the maximum rotation rate in °/s — 733 tops out around 730 °/s, 533 around 530 °/s. They're all built the same way in the legacy Betaflight system: a fixed Super Rate 0.70 with the RC Rate stepped up. This snippet gives …

Rates are not just a "how fast does it spin" setting. They shape where on the stick control lives — and understanding the curve lets you tune for precision hover, natural cruising, and explosive tricks, all in the same profile. The Rate Curve Moving a gimbal stick from center to full deflection does not produce a …

Getting good PID analysis results requires a specific flight sequence. Freestyle logs are almost useless for tuning — the inputs are too chaotic, axes overlap, and throttle is never constant. This protocol covers the exact movements that generate the clean, separable data needed for step response analysis, spectral …