Stacked thresholds that layer sirens, zero debounce against punch-out sag, an alarm that fires before the first telemetry frame arrives, and the link-quality warning I never wired up.

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 …

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| …

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 …

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 …

This post grew out of the drone detector article, where I mentioned using Sintra for the FPV side of the work. That mention deserves its own treatment, because it raises a question I want to address directly: why am I using an external AI tool for this instead of building my own? Why Sintra, Not My Own AI There are …