Skip to content

BetaFPV Air65 — 1S Whoop Build Spec

Betaflight 2026.6.0-alpha
MSP API 1.48

Added 12 September 2026. Configured to match the existing craft on everything a pilot feels, and left at its factory settings on everything specific to its own frame and motors. The port itself is recorded in the setup log.

Flight controller

ItemValue
Board targetBETAFPVG473_V2
Manufacturer IDBEFH
MCU ID002900023235510535303333
MCUSTM32G474, 168 MHz (PLLR-HSI)
Gyro / accelerometerBMI270 (SPI, DMA, locked)
OSDMAX7456, 30 × 13 characters
Onboard flash16 MB SPI (JEDEC 0x00852018) — used for blackbox
Power1S
Both craft report board target BETAFPVG473_V2, so the board name cannot tell them apart. The MCU ID is the only reliable discriminator when a backup file turns up without context. Crafty is 002700443235511330303938.

Reported gyro rate in normal operation is ~3.2 kHz with a cycle time around 314 µs and roughly 36% CPU load. That is lower than the other craft, which runs pid_process_denom = 2.

Different gyro, different firmware

This board carries a BMI270 where the other carries an ICM42622P. That is not a variation this site chose — BETAFPV substitute IMUs as supply allows, and ship a matching firmware build. See Gyro Substitutions and Firmware before flashing anything.

Motors and tune

ItemValue
PID profile nameGF 1219S
Motor protocolDShot300, bi-directional
Motor poles12
motor_idle550
dyn_idle_min_rpm30
Board orientationalign_board_yaw = -135

The PID profile, filter stack, board orientation and accelerometer calibration are the factory values and were deliberately not copied from the other craft. They describe this frame and these motors.

Video

ItemValue
Band / channelRaceband 1 (5658 MHz)
vcd_video_systemNTSC
osd_displayport_deviceMAX7456

The two craft are kept on different Raceband channels on purpose — Crafty sits on channel 3 (5732 MHz) — so both can be powered at once without a video clash.

What is shared

These are pilot settings, not craft settings, and are identical on both airframes: