Guided tuning
From Blackbox set-up to a dialled-in drone: the tool prepares logging over USB, guides you by voice through the test flights, reads the logs and suggests the changes, one at a time and with the reason.
Don’t have your drone to hand? A virtual drone responds like a real one: connection, setup, CLI, firmware and backups, with no risk.
Loading the tool…
How it works
- Prepare. With the drone connected over USB, the tool reads the Betaflight version and the Blackbox settings, suggests the changes needed to log properly (the rate, the unfiltered gyro, the recording mode) and saves a copy of the configuration in your hangar before touching anything.
- Fly. At the field, open the page on your phone. Each test has a voice that tells you what to do and when: slow throttle sweeps, sharp stick snaps with a metronome and sudden throttle cuts. The screen stays on and, when you finish, it asks how the motors feel.
- Analyse. Back home, download the logs from the drone over USB or load them from the card. The tool recognises each flight, measures its noise, response and propwash, and sums it up in five traffic lights.
- Tune. It suggests at most two changes per round, with the reason, the risk and how to undo them. You can apply them with one click or copy them into the CLI.
- Compare. Repeat only the tests that measure what you changed and watch the progress round by round, until everything is green.
The rules the tool follows
Noise first
If the motors come down hot or get too much noise, the first change is always to bring it down. It will never suggest more D with hot motors: that’s the quickest way to burn one.
Few, measured changes
At most two changes per round and never two of the same kind. That way, after flying, you know what each one did. If you don’t like the result, undo it with one click.
Sliders or direct PIDs
If you use Betaflight’s tuning sliders, changes are made with the sliders. If not, the roll and pitch PIDs are changed directly, with the parameter names for your version.
Mechanics matter too
When the lights don’t improve with settings, the tool tells you: it’s often a damaged prop, a loose screw, a bearing or the board’s soft mounts.
Frequently asked questions
Which Betaflight versions does it support?
4.3 onwards, which are the ones with tuning sliders. The chirp test needs 2025.12 or later. With older versions you can analyse logs, but changes have to be made by hand.
Does it work on a phone?
The field copilot does: that’s where it’s used most. The USB connection with the drone needs Chrome or Edge on a computer. If you don’t have one, the tool gives you the commands to copy into the configurator and you can load the logs from the card.
Can anything get damaged?
The tool never spins the motors and, before the first change, it saves a copy of the configuration in your hangar. Every change comes with the command to undo it. Do the tests in an open area, away from people, and only touch the motors with the battery disconnected.
Where do my logs go?
Nowhere: they’re downloaded from the drone and analysed in your browser. Only a summary of each round (the numbers and the changes) is kept in this browser, so you can carry on another day.
I want to understand what P, D and the filters do
Try the PID lab and read the tuning and Blackbox guide. If you want to look at a log in full detail, use the assistant’s Blackbox tab.