Configuration Files

The Configuration Files section lets you store and organize firmware configuration snapshots. This is useful for keeping a history of your tune iterations, comparing settings across versions, or archiving known-good configurations for quick restore or reference.

Uploading a configuration file

Scroll to the Configuration Files section in the detail view. You'll see an upload form at the top:

• Config Name — A label for this snapshot (e.g., "High Acro", "Racing Tune v2", "Conservative PID", "Baseline_2025-02-15")
• Select File — Click to choose a file from your computer

Accepted file types: .txt, .csv, .json, .bbl, .ini, .conf, .config, .xml, .yaml, .yml, .dump

Both the Config Name and the file are required. Fill in both and click the Add button to upload.

Managing your configurations

Once uploaded, each config appears in a list below the form. For each entry, you see:

• Config Name (bold) — The label you gave it
• Filename (subtitle) — The original filename
• Download button (arrow icon) — Click to retrieve the file to your computer
• Delete button (red trash icon) — Click to remove it from your records. A browser confirmation dialog appears before deletion.

Best practices

• Descriptive names: Use clear, meaningful Config Names like "Race Tune - High PID Gains" or "Conservative - Smooth FPV". Avoid generic names like "config.txt" or "backup".
• Date your uploads: Include a date in the name (e.g., "PID_2025-02-15") to track when changes were made. This helps you remember the order of iterations.
• Archive known-good configs: Keep a snapshot of settings that fly well, even if you later modify them. Being able to quickly restore a known-good config is invaluable for troubleshooting.
• Use the diff viewer: Store at least two versions of a config so you can later compare them side-by-side to see exactly what changed between iterations. See Config File Diff Viewer for details.