FPV Tutorial

Betaflight First Setup Checklist for a New FPV Build

0
Illustration of a four-motor FPV drone without propellers beside a laptop and a separate USB cable.

Configure a new FPV build in a fixed order and verify the result after every step. Keep the propellers removed for all bench configuration and motor testing. Betaflight labels, defaults and CLI variables can change between releases, so use the documentation for the installed firmware and Configurator version.

1. Record hardware and make a backup

Before changing settings, record the flight-controller model, firmware target, firmware version, ESC firmware, receiver protocol, video system and GPS model. If the board already contains a configuration, save a backup. Betaflight documents diff all as a way to capture non-default settings across profiles; do not blindly paste a backup from one firmware version or board target into another.

RecordWhy it matters
FC target and firmware versionprevents flashing or restoring settings to the wrong hardware
diff all or supported backuppreserves UART, receiver, modes, OSD, rates and tuning changes
ESC firmware/protocolaffects motor protocol and available telemetry features
Receiver/video/GPS modelsfixes protocol, UART, voltage and firmware assumptions

2. Verify board orientation and sensors

Move the aircraft by hand while watching the model preview. Pitch, roll and yaw in the preview must follow the real frame. If they do not, stop and correct board/sensor alignment before continuing. Calibrate the accelerometer on a level surface when the build uses it.

Do not use software rotation to hide an unexplained mounting or sensor problem. Confirm the physical FC arrow, actual mounting orientation and firmware settings agree.

3. Configure ports and peripherals

Assign each UART from the wiring plan. Typical assignments include serial receiver, GPS, VTX control or digital video MSP/display communication. Do not enable two functions on one port unless the exact documentation supports sharing.

After saving and rebooting, verify each device:

  • Receiver produces channel movement.
  • GPS communicates and reports plausible status outdoors when required.
  • VTX or digital video control uses the intended UART and protocol.
  • ESC telemetry/current sensing appears only if wired and configured.

4. Configure the receiver

Choose the receiver mode and provider that match the exact protocol. In the Receiver tab, verify channel order and direction, center points, endpoints and switch behavior. Betaflight safety guidance describes common expectations around centered and endpoint values, but the transmitter and protocol documentation remain authoritative.

Confirm:

  • Roll, pitch, yaw and throttle move in the correct direction.
  • Throttle reaches the expected low state for arming.
  • Arm and prearm switches use deliberate, non-overlapping ranges.
  • Receiver link quality/telemetry fields are present only when supported.

5. Configure arming and essential modes

Set ARM on a deliberate switch. Consider PREARM where it fits the operating method. Add ANGLE only when the build and pilot require self-level assistance. Use Betaflight’s reported arming-disable flags, OSD warnings or Configurator status to diagnose a refusal to arm; do not disable safety checks simply to clear an error.

Common arming blocks include invalid receiver data, throttle not low, the aircraft outside the permitted angle, calibration in progress or a failsafe state. Correct the cause.

6. Verify motor protocol, order and direction (props off)

Select the motor protocol supported by the ESC and FC. Betaflight’s current Setup Guide notes that modern builds commonly use DShot, but the appropriate DShot rate depends on hardware and configuration.

With propellers removed:

  1. Connect the battery safely.
  2. Use the Motors tab confirmation.
  3. Raise each motor individually at the minimum value that produces smooth rotation.
  4. Confirm the motor number matches the diagram.
  5. Confirm each motor spins in the direction selected by the props-in/props-out setting.
  6. Correct mapping or direction using supported tools, then repeat the test.

The software “reversed” mixer setting tells Betaflight which pattern to expect; it does not by itself reverse an ESC motor that spins the wrong way.

7. Configure battery monitoring and OSD

Select the battery cell-count behavior, voltage scaling and current-sensor source supported by the hardware. Compare displayed voltage with a trusted meter before relying on warnings. Current calibration requires an appropriate measurement method; do not invent a scale from another board.

Show useful OSD fields such as battery voltage, warnings, link quality/RSSI where supported, flight time and current/capacity only when calibrated.

8. Configure and test failsafe

Betaflight recommends flight-controller-based failsafe and states that the receiver should send no data on signal loss. Select the Stage 2 procedure appropriate to the aircraft and operating environment. GPS Rescue requires a correctly installed, configured and tested GPS system; enabling the option is not proof that return behavior is safe.

Test failsafe on the bench with propellers removed. Confirm the receiver link is valid, raise throttle enough for the test logic when required, then remove the radio link and verify the expected warnings and Stage 2 behavior. Restore the link and confirm the aircraft does not unexpectedly re-arm.

9. Final props-off verification

  • [ ] Saved configuration backup and firmware/target record.
  • [ ] Model preview follows real frame movement.
  • [ ] Receiver directions, endpoints and switches verified.
  • [ ] Motor number, order and direction verified with props removed.
  • [ ] Battery voltage reading compared with a meter.
  • [ ] OSD warnings visible.
  • [ ] Failsafe tested with propellers removed.
  • [ ] No hot component, damaged wire or loose hardware after powered tests.

Only then fit the verified propellers in the correct positions, move to a clear test area and perform a restrained low-risk first hover according to local rules and operating conditions.

Related WXBMW paths

Use the FPV Builds index, flight-controller guide, ESC guide and radio/receiver compatibility guide. When the verified build needs hardware, browse flight controllers, ESCs or radio receivers by the exact interface, voltage, firmware and protocol requirements above. For an exact board and peripheral configuration review, contact WXBMW.

Official references

Next step after this guide

Turn This Guide into a Complete FPV Build

Use the guide to define the required specifications, verify the aircraft-level Build path, then compare current WXBMW parts. Recheck voltage, mounting, protocol, connector and load compatibility before ordering.

1 · GUIDEKeep the specification checklist from this tutorial.
2 · BUILDVerify the complete system in Beginner FPV Build.
3 · PARTS OR INQUIRYCompare listed WXBMW parts or request an exact specification match.

No in-stock WXBMW option is shown for this exact category right now. Use the specification-match request instead of assuming a nearby item is compatible.

Leave a Reply