Betaflight setup for a tiny whoop: first-flight checklist
TUNING // FIELD_REPORT

Betaflight setup for a tiny whoop: first-flight checklist

Published
Updated
Read time4 min read

Most Betaflight guides assume a 5-inch with room to arm outdoors. A tiny whoop needs a shorter path: bind the radio, confirm failsafe, set one arm switch, and fly the stock PIDs. This checklist is for a first flight on a whoop AIO, not a Blackbox masterclass. For filter and PID work, see Betaflight tuning basics.

If you haven’t practised on the sticks yet, do that first in the free online FPV simulator. Time in the Configurator doesn’t fix panic yaw.

Before you plug USB

Betaflight setup for a tiny whoop: first-flight checklist: Before you plug USB

CheckWhy
Props offAn accidental arm still hurts, ducts or not
Firmware already flashed by the manufacturerWhoop BNFs usually arrive ready
ELRS radio bound or bind button reachableELRS whoop receiver notes
1S pack charged, connector matches (BT2.0 or PH2.0)Connector guide

Ports and receiver (5 minutes)

  1. Connect USB and open Betaflight (the web app at app.betaflight.com in Chrome or Edge, or the desktop Configurator). Trouble connecting? See Betaflight not connecting.
  2. Ports: on BNFs the receiver UART is usually already set. If you built from parts, enable Serial RX on the UART the receiver is wired to. Boards with a built-in SPI receiver don’t use a UART at all.
  3. Receiver tab: protocol CRSF for ELRS. Move the sticks and watch the bars. If nothing moves, fix the bind before anything else (ELRS setup checklist). Some boards only power the receiver with a battery plugged in (props off).
  4. Check each stick moves the right bar (roll, pitch, yaw, throttle). If two are swapped, fix the channel map. Mode 2 itself is set on the radio, so keep the mode you trained with in the sim.

Modes that matter on day one

Keep it minimal:

ARM               → a switch you will never bump by accident
ANGLE or HORIZON  → for the first packs (optional, but kinder indoors)
BEEPER            → finds the whoop when it vanishes under furniture

Skip extra modes and fancy switch combinations until you have ten clean packs. Add turtle mode (Flip Over After Crash) on its own switch once arming feels routine; whoops land upside down a lot.

Failsafe check

With props off and a battery in, arm on the bench, then switch the radio off. The motors should stop within a second or two and the OSD should show a failsafe. Betaflight’s default (drop) is right for a whoop. Don’t fly until this works; see failsafe scenarios.

OSD and warnings

Betaflight setup for a tiny whoop: first-flight checklist: OSD and warnings

Turn on a small set of OSD items: battery voltage, flight mode, link quality and craft name. Whoop packs sag hard, and voltage on screen beats guessing when the quad goes soft. If you use Angle mode, calibrate the accelerometer (Setup tab) with the whoop sitting level on a flat table.

Rates: start stock, then soften if needed

Stock whoop rates are usually fine after sim practice. If the quad feels twitchy:

  • Lower the roll and pitch rates slightly
  • Add a little Expo so the centre of the stick is calmer for indoor lines

Don’t chase freestyle rates on day one. The goal is a hover and gentle figure-eights in a safe room, or on a terrace where flying is actually allowed. See apartments and terraces in India.

First pack procedure

  1. Props on (check direction), ducts intact, canopy secured.
  2. Arm in a clear space and throttle up slowly to a hover.
  3. Land, disarm, and touch the motors: warm is fine; too hot to hold is not.
  4. Fly two more short packs before you change any PIDs.

If it vibrates or yaws on its own, stop and inspect the hardware. Don’t try to tune your way past a bent prop. The first 10 flights after a new build guide still applies at whoop scale.

Bench

Need a BNF, a radio or spare 1S packs? The Bench and Grind Lab keep whoop parts compatible. Practise in the browser simulator when weather or housing-society rules keep you grounded.

See also

Discussion

Comments aren't open on this post yet. Share it with your build group, or start a thread on X.