Firmware CLI parameter reference

The settings a flight controller's CLI accepts, release by release: name, type, range or value list, default, and what each release added, removed or renamed.

Check a diff all against any release in the CLI checker: unknown or renamed settings, values out of range, and lines that only restate the default. It runs in your browser; nothing is sent.

How the figures are read

• Names, types, ranges and value lists come from the release's src/main/cli/settings.c at the tagged commit; each row points to its line.
• Defaults come from the firmware itself: each release is built for the simulator (SITL), booted on an empty EEPROM, and asked get over its CLI; every default is then traced to the source line that sets it. Where the default depends on build options or a board's config, no figure is printed and the page says so.
• Renames are listed only where the firmware's own pull request says the old and new name are the same setting. Any other vanished name counts as removed.
• A section page is published once it has 10 or more complete settings.

Files

All releases in one archive (.zip, 95 KB), or one params.json per release from each firmware's page (Betaflight index.json). The files are derived from GPL-3.0 firmware source and are GPL-3.0 themselves; the component dataset stays CC BY 4.0.