FPV Drone Build Documentation: Photo Log, Wiring Notes, and Configuration Backup — 2026

Your flight controller dies six months after the build and you cannot remember which UART you wired the GPS to. You grab a replacement FC, open Betaflight, and stare at a blank configuration — no backup, no wiring notes, no photo of the solder joints. This scenario is avoidable. A build documentation routine takes 10 minutes during the build and saves hours of reverse-engineering later. Here is how to do it systematically.

The Documentation Toolkit: What to Capture and When

Build documentation is not a blog post. It is a recovery manual for future you, written while the build is fresh in your hands, at the exact moment you route each wire and set each parameter.

Step 1: Photo Log — The Visual Reference

Take photos at six specific points in the build. Do not skip any of them — a missing photo at step 3 means you have no reference for which pad your receiver signal connects to.

1. Dry fit photo: All components placed on the frame with no wires connected. This captures the physical layout — ESC orientation, FC orientation, receiver placement, VTX location, capacitor position. If you ever need to rebuild the stack from scratch, this photo is your blueprint.

2. Bottom-side solder joints: After soldering the ESC power leads, capacitor, and battery leads. Take this photo from directly above or at a slight angle that shows every pad. This catches cold joints and verifies that positive and negative are on the correct pads.

3. Receiver wiring close-up: One macro photo of the receiver showing which wire goes to which pad. CRSF has 4 wires — swapping TX and RX on the UART means no stick input and you will not know which is which without a photo.

4. VTX and camera wiring: Focus on the VTX pad labels. If you are using SmartAudio for VTX control, the audio wire must go to a specific TX pad. A photo tells you which pad you used.

5. GPS and buzzer connections: These are typically the first things to get ripped off in a crash, and the pad assignments are the hardest to remember. Photo these.

6. Completed build — top and bottom: Two wide shots showing the final routing of every wire and the position of every component. Useful when you need to replace a motor and want to follow the original wire path through the frame.

Save these photos in a folder named after the build: ~/Documents/FPV Builds/2026-05-15 Apex 5-inch/. Store them locally. Cloud storage is fine as a backup, but you want them available offline — the moment you need them is usually at the field, with no cell service, holding a broken quad.

Step 2: Wiring Notes — The Textual Reference

While the build is fresh, write down the UART assignments and any non-obvious wiring decisions. A text file is fine. A markdown file in the same folder as your photos is better.

Template:

Build: Apex 5-inch Freestyle
Date: 2026-05-15

Flight Controller: SpeedyBee F405 V4
ESC: Skystars KM55A BLHeli_32

UART Mapping:
- UART1: Serial Rx (CRSF receiver)
- UART2: ESC Telemetry (T pad to R2)
- UART3: VTX SmartAudio (TX3)
- UART4: GPS (TX4/RX4)
- UART5: Not used
- UART6: Not used

Motor Order:
- Motor 1: Rear Right (CW)
- Motor 2: Front Right (CCW)
- Motor 3: Rear Left (CCW)
- Motor 4: Front Left (CW)

Notes:
- Capacitor: 1000uF 35V Panasonic low-ESR on XT60 pads
- Receiver: TBS Crossfire Nano RX (5V from FC 5V pad, NOT VBAT)
- Buzzer: VIFLY Finder Mini on BZ+/BZ- pads
- GPS harness routes under FC through the stack gap

This file takes 3 minutes to write and will save you 30 minutes of probing with a multimeter when you need to replace something.

Step 3: Betaflight Configuration Backup — The Digital Reference

Betaflight’s “diff all” command exports every non-default setting. This is your most important backup because it captures the tune, the modes, the OSD layout, the UART configuration — everything you set that is not factory default.

1. In Betaflight Configurator, go to the CLI tab
2. Type diff all and press Enter
3. Copy the entire output
4. Save it as CLI-backup-YYYY-MM-DD.txt in the build folder
5. Every time you change a significant setting (new rates, PID adjustment, filter change), generate a new backup and date it

A “diff all” backup is also portable. If your FC dies and you replace it with the same model, loading the diff restores your configuration exactly. If you switch to a different FC model, the diff still works for settings but you will need to manually reassign UARTs and resource mappings.

Bonus Step: Flash with Configurator Version Note

Betaflight Configurator versions are not backward compatible. A backup made with Configurator 10.9 will not load on Configurator 10.7. Note which version you used. If your computer dies and you reinstall everything, you need to install the same Configurator version to restore your backup cleanly.

Documentation Quality Checklist

Documentation Element	Time to Create	Value When You Need It	Failure Mode If Missing
Dry fit photo	30 seconds	Identifies component placement	Wrong ESC orientation after rebuild, motor order reversed
Solder joint close-ups	2 minutes	Confirms pad assignments and joint quality	Probing pads with multimeter to find which UART has continuity
UART assignment notes	3 minutes	Directly maps every connection	Trial-and-error enabling Serial Rx on wrong UARTs
CLI diff all backup	1 minute	Restores full configuration	Re-tuning from scratch, re-setting all modes and OSD
Completed build photos	30 seconds	Shows wire routing	Wires routed through wrong frame gaps, pinched under standoffs

What Builders Get Wrong About Documentation

Mistake 1: “I’ll remember it.” You will not. Six months and three builds later, you will not remember which UART you wired the VTX SmartAudio to on this specific quad. The human brain is bad at this. A photo is perfect at it. Take the photo.

Mistake 2: Making the backup after the first crash. If the FC is dead, you cannot pull a diff. The backup must happen before the crash — that is the whole point. Make it part of your build checklist: soldering → smoke test → configuration → backup → maiden flight. The backup goes before the maiden, not after.

Mistake 3: Storing backups only on the FC’s onboard flash. Betaflight can store a backup on the FC’s flash chip. The flash chip is on the same PCB that gets destroyed in a crash or submerged in water. It is not a real backup. Export to your computer.

Mistake 4: Saving only a CLI dump instead of a diff. A dump exports every setting including defaults. When you restore a dump to a different FC model, the default values from the old FC overwrite the defaults on the new FC — and those defaults can be incompatible. A diff exports only your changes and leaves the new FC’s defaults intact. Always use diff all.

Mistake 5: Not documenting what you changed during the tune. Comparing the last known-good diff to the latest one is how you figure out which change caused the problem. If all you have is the latest backup, you have no baseline. Version your diffs: CLI-backup-2026-05-15-initial.txt, CLI-backup-2026-05-20-pid-change.txt, etc.

⚠️ Regulatory Notice: The build documentation practices in this article should be followed in accordance with the latest 2026 drone regulations in your country or region. Always verify local laws regarding drone construction, registration, and remote ID requirements. Regulations vary significantly between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities.

Related Guides

A well-documented build starts with a clean physical construction. Our FPV Drone Wire Management guide covers routing techniques that make your documentation photos actually readable. Before you document, make sure your build is worth documenting. Our FPV Drone Pre-Flight Checklist covers the verification steps before that maiden flight.

Build Component Pick

The flight controller at the center of your build determines how easy it is to wire cleanly and document clearly. The uavmodel SpeedyBee F405 V4 has large, clearly labeled pads with a logical UART layout and a dedicated ESC telemetry connector — less time tracing pad labels means more time flying.