Arrive with a recovery plan
Identify the aircraft and flight-controller hardware. Find the manufacturer’s instructions and the Betaflight documentation appropriate to the installed version. Understand how the aircraft is supposed to be powered for each operation before connecting it.
For setup and motor-related bench work, follow the documented propeller-removal precautions. A computer connection is not a reason to treat the machine as harmless, and some components may require separate power under specific conditions.
Record what is already there
Note the current firmware, board identification, and relevant configuration. Save the backups supported by the installed software before making changes. Keep the original files with a date and a meaningful description.
A factory configuration can contain settings specific to the aircraft. Do not replace it with someone else’s complete configuration because the frame looks similar. Your objective is to establish what the existing setup does and what actually needs attention.
Observe before changing
Check that the displayed aircraft orientation makes sense when you move the physical aircraft. Examine the documented receiver and mode information. Work through the manufacturer’s setup checks rather than skipping to advanced tuning.
When an observation is wrong, write down what you expected and what you saw. Change one relevant item, verify the result, and record the change. This process produces a useful setup record instead of an unexplained collection of edits.
Know when a version difference matters
Interfaces and configuration details change. An old screenshot can still illustrate an idea while being a poor guide to the exact controls on your screen. Match documentation and instructions to the software version and hardware you actually have.
If you cannot identify the board, the correct target, or the intended setup process, stop and resolve that uncertainty first. “Flash something and see” is not an efficient diagnostic method.
MAKE IT USEFUL
Your next small job.
Create a dated baseline folder containing the hardware identifiers, firmware version, supported backup files, and your first observations.
Go straight to the source.
These official resources support the next step. Hardware, firmware, and local requirements can differ.