Betaflight, INAV and EmuFlight config check without a log
Paste your diff all output — bbdoctor finds settings that can crash the drone or spoil the flight and gives CLI commands to fix them. No blackbox log needed.
How to get diff all
- Connect the flight controller to the Configurator and open the CLI tab.
- Type diff all and press Enter (dump works too, but it is longer).
- Copy the whole output, starting from the first line: it has the firmware version. Paste it into the field below.
The text is parsed on the server and never stored. Keep your diff all from before the changes: that is your rollback.
What is checked
- Safety: failsafe and GPS Rescue, arming at an angle, runaway takeoff protection, motors on arm
- Motors: protocol and idle throttle, bidirectional DShot and the RPM filter
- Gyro and D-term filters, the dynamic notch
- PID: sliders, dynamic D, suspiciously low and high values
- Rates, throttle limit and Airmode
- Receiver: protocol, stick smoothing, behavior when the link is lost
- Blackbox set-up for analysis and whether the firmware is up to date
FAQ
How is a config check different from a log analysis?
A config only shows settings and does not know how the drone flies. Vibration, filter noise, PID overshoot and battery health show up only in a blackbox log, which the main analysis on the home page handles.
Which firmware is supported?
Betaflight 4.x and 2025.x, INAV and EmuFlight. Rotorflight and Cleanflight are recognized, but there are no rules for them yet.
Is it safe to apply the suggested commands?
The commands are suggestions, not orders. Apply them one at a time and test on the bench without props. Save your diff all from before the changes to a file: it restores everything.