If you’re looking to set up a timing system for indoor whoop races, this is a great option.

🧩 Parts List

Here’s what I used for my build:

• Nuclear Hazard Fission Kit — nuclearquads.com/shop

• 1–8 RX5808 Modules — RaceDayQuads link

• Raspberry Pi 5 — Amazon link

• Micro SD Card (32GB) — SanDisk 2-Pack on Amazon

• 3D Printed Case — use the STL files from the official instructions

⚙️ Build Overview

The kit comes with everything you need except the Raspberry Pi, SD card, and receiver modules.

Assembly was straightforward — the YouTube build video clearly shows each step.
I followed the same written instructions here.

A few notes from my build:

• Make sure your RX5808 modules are fully seated before tightening the case.

• Double-check all solder joints — make sure the pins are soldered cleanly, and test each connection with a multimeter to confirm continuity and ensure there are no bridge connections between pins.

• Use heat-set inserts for the fan screws (included in the kit).

• The fan should blow outward to keep air moving across the board.

💡 Pi OS Setup

Follow the official Pi OS installation guide.
For this build, I recommend using Raspberry Pi OS (64-bit) for the best performance with the Pi 5.

I used Raspberry Pi Imager v1.8.5 — download here.
This version still allows uppercase characters in your username, which newer releases block.

🧭 Step-by-Step Setup

1. Open Raspberry Pi Imager v1.8.5
   You’ll see three options:

   • CHOOSE DEVICE

   • CHOOSE OS

   • CHOOSE STORAGE

     

2. Select your Device

   • Click CHOOSE DEVICE

   • Select Raspberry Pi 5 (or your model if different)

     

3. Select the Operating System (OS)

   • Click CHOOSE OS

   • Scroll down to Raspberry Pi OS (64-bit)

   • Choose the Lite (headless) version if you’re running without a monitor, or Desktop if you plan to use the GUI.

     

4. Choose your SD Card Storage

   • Click CHOOSE STORAGE

   • Select your microSD card (make sure it’s the correct one—everything will be erased)

     

5. Apply Custom Settings

   • When prompted, choose EDIT SETTINGS or YES to apply custom OS options.

     

6. Enter Setup Information:

   • Hostname: nuclearhazard

   • Username: NuclearHazard

   • Password: nuclearhazard

   • Wi-Fi SSID: Enter your home network name if you want the Pi to connect automatically

   • Wi-Fi Password: Enter your Wi-Fi password

   • Time Zone: Set your local region

   • Enable SSH: Turn this ON and select “Use password authentication”

     

     

7. Write the Image

   • Click SAVE, then confirm WRITE

   • The imager will flash the SD card and verify it automatically

This version still allows uppercase characters in usernames, which newer versions block.

Next: power, find the IP, and SSH in

Quick checklist (bench)

• Props off (not a drone — but habit).

• Make sure XT60 is connected and the kit is powered from the battery / adapter.

• Confirm the Pi is booting: status LEDs on the Pi should blink, fan runs, RX modules seated.

• If using an external router, power that up and place it near the timer.

1) Find the NuclearHazard IP address (pick one method)

A. Mobile (easy, GUI)

• Install a network scanner app (Fing on iOS/Android is common).

• Connect your phone to the same Wi-Fi network (or connect the travel router’s SSID).

• Scan the network and look for the hostname nuclearhazard or find a new device with the Raspberry Pi MAC vendor (Broadcom / Raspberry Pi Foundation).

• Note the IP (e.g. 192.168.1.42).

B. Desktop: quick ARP or ping sweep (Windows / Mac / Linux)

• Open a terminal or PowerShell on a machine on the same LAN.

• If you know your subnet (example 192.168.1.0/24) try:

  • ping -c 1 nuclearhazard (Mac / Linux)

  • ping -n 1 nuclearhazard (Windows PowerShell)

• Or run a network scan:

  • nmap -sn 192.168.1.0/24 (shows live hosts)

  • arp -a (then look for a new IP / the raspberry pi MAC)

• If you don't have nmap installed:

  • macOS: brew install nmap

  • Linux: sudo apt install nmap

  • Windows: download Angry IP Scanner or use PowerShell Test-Connection script.

C. From your router admin page

• Log into your travel router or home router admin page.

• Look for “Connected devices”/DHCP leases and find nuclearhazard.

2) SSH into the Pi

Open terminal / PowerShell and run (replace <ip> and <username> with what you set in the imager — if you used nuclearhazard as the hostname but a different username, use that username):

• macOS / Linux / Windows PowerShell:

ssh <username>@<ip>
# example:
ssh NuclearHazard@192.168.1.42

If you enabled SSH and used password auth, type your password when prompted.

If you get “connection refused”:

• Confirm Pi has power and booted.

• Confirm SSH was enabled during imaging (or re-flash with SSH enabled).

• Check firewall on router (unlikely on local LAN).

🖥️ Software Installation (Command Line)

The official guide gives two setup options. I recommend the command-line install method since it’s easier to control if something fails.

From the guide:

curl -s https://nuclearquads.github.io/files/nhpisetup.sh | bash -s nuclearwifi
curl -s https://nuclearquads.github.io/files/nhpisetup2.sh | bash

However, I ran into issues where the full command wouldn’t execute correctly — parts of the script were getting cut off.
To fix it, I downloaded the setup file manually and ran it in three smaller sections.
I’ll include those three code snippets in the next section for anyone who runs into the same problem.

#!/bin/bash

# Define the log file name and location
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
LOG_FILE="$SCRIPT_DIR/nhpisetup.log"

# Redirect all output to the log file
exec > >(tee -a "$LOG_FILE") 2>&1

# update and install dependencies
sudo apt-get update
sudo apt-get upgrade -y
sudo apt-get install python3-venv python3-dev libffi-dev python3-smbus build-essential python3-pip git scons swig python3-rpi.gpio default-jdk-headless libjpeg-dev libopenjp2-7-dev -y

# setup pi
sudo raspi-config nonint do_serial_hw 0
sudo raspi-config nonint do_serial_cons 1
sudo raspi-config nonint do_i2c 0
sudo raspi-config nonint do_ssh 0
sudo raspi-config nonint do_spi 0
sudo raspi-config nonint do_wifi_country US

echo "\
dtoverlay=miniuart-bt
dtparam=i2c_baudrate=75000
dtoverlay=act-led,gpio=24
dtoverlay=gpio-led,gpio=26,label=pwrled,trigger=default-on
#dtoverlay=gpio-fan,gpiopin=4
dtparam=act_led_trigger=heartbeat
dtoverlay=spi0-0cs,no_miso

[pi5]
dtoverlay=uart0-pi5
dtoverlay=i2c1-pi5
dtoverlay=uart3-pi5

[pi4]
dtoverlay=gpio-shutdown,gpio_pin=19,debounce=5000
dtoverlay=uart4

[pi3]
dtoverlay=gpio-shutdown,gpio_pin=19,debounce=5000
core_freq=250

[pi02]
#dtoverlay=gpio-shutdown,gpio_pin=19,debounce=5000
core_freq=250

[all]
" | sudo tee -a /boot/firmware/config.txt

echo 'SUBSYSTEM=="tty", KERNEL=="ttyAMA0", SYMLINK+="serial0"' | sudo tee /etc/udev/rules.d/99-serial0-fix.rules

python -m venv --system-site-packages .venv
echo "
VIRTUAL_ENV_DISABLE_PROMPT=1
source ~/.venv/bin/activate" | sudo tee -a ~/.bashrc
source ~/.venv/bin/activate

# for VRxC flashing and pi 5 led
# python -m pip install esptool --break-system-packages 
pip install rpi5-ws2812 esptool pillow

wget https://rotorhazard.com/install.sh
sh install.sh

# git way
#git clone --depth 1 --branch v4.1.1 https://github.com/RotorHazard/RotorHazard.git
# in case a single commit is needed to fix something
#cd RotorHazard
#git fetch origin a759846b12011a394422af9c00b1b89423a3dd70
#git cherry-pick a759846b12011a394422af9c00b1b89423a3dd70

echo "[Unit]
Description=RotorHazard Server
After=multi-user.target
[Service]
User=NuclearHazard
WorkingDirectory=/home/NuclearHazard/RotorHazard/src/server
ExecStart=/home/NuclearHazard/.venv/bin/python server.py
[Install]
WantedBy=multi-user.target" | sudo tee -a /lib/systemd/system/rotorhazard.service

sudo chmod 644 /lib/systemd/system/rotorhazard.service
sudo systemctl daemon-reload
sudo systemctl enable rotorhazard.service

sudo apt-get install iptables -y
sudo iptables -A PREROUTING -t nat -p tcp --dport 80 -j REDIRECT --to-ports 5000
sudo iptables -A PREROUTING -t nat -p tcp --dport 8080 -j REDIRECT --to-ports 80
sudo iptables-save
echo iptables-persistent iptables-persistent/autosave_v4 boolean true | sudo debconf-set-selections
echo iptables-persistent iptables-persistent/autosave_v6 boolean true | sudo debconf-set-selections
sudo apt-get -y install iptables-persistent

echo '#!/bin/bash

# Define the file path containing SSID and password
WIFI_CONFIG_FILE="/home/NuclearHazard/wifi_config.txt"

# Read SSID and password from the configuration file
SSID=$(awk "NR==1" "$WIFI_CONFIG_FILE")
PASSWORD=$(awk "NR==2" "$WIFI_CONFIG_FILE")

# Validate SSID and password
if [ -z "$SSID" ] || [ -z "$PASSWORD" ]; then
  echo "Error: SSID or password is empty in the configuration file."
  exit 1
fi

echo "Attempting to connect with SSID: $SSID and password: $PASSWORD"

# Attempt to connect to the WiFi network or start a hotspot on failure
if nmcli dev wifi connect "$SSID" password "$PASSWORD" ifname wlan0; then
  echo "Successfully connected to WiFi network: $SSID"
  echo "Run the following command to remove the current Wi-Fi network: sudo nmcli connection delete id \"$SSID\""
  exit 0
else
  echo "Failed to connect to WiFi network: $SSID. Starting hotspot instead."
  nmcli dev wifi hotspot ifname wlan0 ssid "NuclearHazard" password "nuclearhazard"
  if [ $? -eq 0 ]; then
    echo "Hotspot created with SSID: NuclearHazard"
  else
    echo "Failed to create hotspot."
    exit 1
  fi
fi' | sudo tee /home/NuclearHazard/hotspot.sh
sudo chmod +x /home/NuclearHazard/hotspot.sh

echo 'ssid
password' | tee /home/NuclearHazard/wifi_config.txt

echo "[Unit]
Description=Hotspot Service
After=NetworkManager.service
Wants=NetworkManager.service

[Service]
Type=simple
ExecStartPre=/bin/sleep 20
ExecStart=sudo /home/NuclearHazard/hotspot.sh
WorkingDirectory=/home/NuclearHazard/

[Install]
WantedBy=multi-user.target" | sudo tee -a /etc/systemd/system/hotspot.service

sudo systemctl enable hotspot.service

sudo reboot

#!/bin/bash

sudo systemctl stop rotorhazard.service

# cd ~/RotorHazard/src/server
# pip install -r requirements.txt
# python -c "import Config; Config.Config(None, 'config.json', 'cfg_bkp')"
sed -i 's/"ADMIN_USERNAME": "admin"/"ADMIN_USERNAME": "NuclearHazard"/' ~/rh-data/config.json
sed -i 's/"ADMIN_PASSWORD": "rotorhazard"/"ADMIN_PASSWORD": "nuclearhazard"/' ~/rh-data/config.json
sed -i 's/"SHUTDOWN_BUTTON_GPIOPIN": 18/"SHUTDOWN_BUTTON_GPIOPIN": 19/' ~/rh-data/config.json
sed -i 's/"hue_0": "212"/"hue_0": "100"/' ~/rh-data/config.json
sed -i 's/"sat_0": "55"/"sat_0": "75"/' ~/rh-data/config.json
sed -i 's/"timerName": "RotorHazard"/"timerName": "NuclearHazard"/' ~/rh-data/config.json
sed -i 's/"LED_COUNT": 0/"LED_COUNT": 100/' ~/rh-data/config.json
# mkdir rh-data
# wget "https://nuclearquads.github.io/files/config.json" -P ~/rh-data

sudo systemctl start rotorhazard.service

🟢 LED Strip Build

To add LED gate feedback, you’ll need to make a short adapter cable.

Parts used:

• JST-XH male cable (I used a cut 2S balance extension cable)
  Amazon link

• JST-SM 3-pin male connector (for the LED strip)
  Amazon link

My wire layout for the JST-SM connector:

• Red — 5V

• Green — Signal

• White — Ground

You’ll need to solder the JST-XH cable (from the timer) to the JST-SM connector (for the LED strip).
Make sure the wires are soldered in the correct order and test with a multimeter before powering on to confirm proper voltage and signal lines.

LED Strip Recommendation:
I used these 5V WS2812B LEDs — BTF Lighting 5mm strip.
They’re bright and easy to work with. The timer’s power output can light up about 24 inches (2 ft) of LEDs — perfect for RaceGOW gate lengths made from 2-ft PVC pipe.

📶 Improving Wi-Fi and Enclosure

The built-in Wi-Fi hotspot on the timer works, but the signal is pretty weak — especially once you enclose the board.
I recommend adding a small travel router to keep your connection stable:
🔗 GL.iNet GL-SFT1200 Travel Router

For the enclosure, I found it essential to isolate the receiver modules from stray VTX signals.
If the lap timer is left exposed, it will constantly pick up random transmissions and trigger false lap reads.

To solve this, I mounted the entire timer inside a Rubbermaid Brilliance 4.7-cup Tupperware container and lined the inside with aluminum tape.
The aluminum layer blocks unwanted RF noise so the timer only detects a VTX when it’s directly in front of the receiver.

You can also use an aluminum bucket for a quick setup, but I wanted something portable and clean for travel when hosting whoop events.

• Aluminum Tape: link

• Container: Rubbermaid Brilliance Medium Deep, 4.7 Cup

🔌 Power Options

For power, I’m using an Anker Prime 20,000mAh power bank.
It runs the Pi and LED system for about five hours, making it a compact and reliable solution for race days.

You’ll also need a XT60 to USB-C adapter to power the timer through its USB-C input: XT60 Female to USB-C Adapter

Alternative Power Option:
You can also run the system through a PoE injector kit and a 5.5mm DC to XT60 cable if you prefer to power from a DC supply or wall adapter.

• PoE Injector Kit

• 5.5mm DC to XT60 Adapter

🧩 Final Thoughts

After completing the build, I added a small USB-A cooling fan to help keep the Pi and receiver modules cool inside the case.
Here’s the fan I used:
🔗 SCCCF 40mm USB Fan on Amazon

It fits nicely on the lid and runs directly from the Raspberry PI. Combined with the ventilation holes and aluminum lining, it keeps everything at a stable temperature even during long sessions.

Overall, this was a fun project and a great way to build a portable FPV lap timer setup for whoop racing events.

Now I can bring the system to every meetup and easily track laps — it adds a whole new layer of excitement to our indoor races.

The build wasn’t too difficult; the most challenging part was soldering the RX5808 modules, which require a bit of patience and a steady hand.

Once those were done, the rest of the setup — installing the software, wiring LEDs, and tuning the enclosure — came together smoothly.

It’s satisfying to have a fully self-contained, field-ready lap timing system that runs off a power bank and can travel to any event.
This build definitely levels up the experience for both pilots and spectators at our Bay Area Micro Racing meetups.

🎥 Demo Videos

I recorded several demo runs showing how the timer and LEDs behave during a race.

1. Three-Pilot Track View
The LED strip shows a rainbow cycle when idle.
Once ready, it turns orange, then green at the start.
Each pilot is assigned a color — in this race I was blue, and every gate pass flashed blue three times.

2. First-Person Flight Test
This video shows the same race from the FPV feed — you can see LED flashes synced perfectly with each gate pass.
The lap timer detects each lap in real time while giving instant LED feedback for confirmation.

🧰 Notes Before Configuration

Once the hardware and LEDs are set up, not much configuration is required.
In the next section, I’ll cover my configuration settings and how I tuned LED behavior.

I used this video by Joshua Bardwell as a reference for setting up the software interface and adjustments:

🔧 Build Update – Final Enclosure & Portability Improvements

After running the lap timer for a bit, I decided to rework the enclosure to make everything more compact, durable, and event-ready. Fitting all the components into a small case took some time, and I ended up adding a few extra parts to get everything working cleanly and reliably.

Shielding & Signal Control

The inside of the enclosure is fully lined with aluminum tape, which made a big difference for RF shielding. This helps block unwanted VTX signal bleed and ensures the lap timer only triggers when the quad actually flies in front of the gate. After testing, false reads were no longer an issue.

To further improve connectivity, I replaced the travel router’s stock WiFi antennas with laptop-style internal WiFi antennas. This noticeably improved range and stability, especially in crowded indoor environments like gyms or event spaces.

Power & Networking

Everything is powered through a single USB-C input, which splits power to both the NuclearHazard unit and the travel router. This keeps the setup simple and clean—one cable in, everything powers up.

The travel router is configured to:

• Connect to my home WiFi (or venue WiFi when available)

• Broadcast its own network at the same time for laptops, tablets, or phones to connect to the lap timer UI

I also added:

• A panel-mounted Ethernet port for hardwired connections

• A dedicated external LED output, making gate setup and cable management easier

Cooling & Durability

The enclosure is mostly waterproof, with the only major opening being the cooling fan. I added a small USB fan to keep airflow moving, and so far thermals have been solid even during long race sessions.

Overall, I’m really happy with how this version turned out. It’s compact, clean, and feels solid. Most importantly, it’s now a fully portable lap-timing solution that I can easily bring to the whoop events I organize to add structure, competition, and excitement.

🧩 Additional Parts Used in This Update

• IP65 Project Enclosure (Zulkit)
  https://www.amazon.com/Zulkit-Waterproof-Electronic-Junction-Enclosure/dp/B07RT6NWTR

• Dual-Band Internal WiFi Antennas (IPEX1, 2.4 / 5GHz)
  https://www.amazon.com/Antenna-2-4GHz-Connector-Various-Length/dp/B0F6377H24

• RJ45 Panel-Mount Coupler (Shielded)
  https://www.amazon.com/PENGLIN-Coupler-Shielded-Connector-Bulkhead/dp/B09Z2977RZ

• Aluminum Foil HVAC Tape (for shielding)
  https://www.amazon.com/ETERART-Aluminum-Temperature-Foamboard-Insulation/dp/B0BNKK95YC

• 24mm Hole Saw (for panel cutouts)
  https://www.amazon.com/MOLLOM-BI-Metal-Cutting-Drywall-Plastic/dp/B0CGMBXJDL

• 3-Pin 3.81mm Panel-Mount Screw Terminal (LED output)
  https://www.amazon.com/3-Pin-3-81mm-Terminal-Shrouded-Flange/dp/B083932T2K

• Ultra-Slim Short Ethernet Cables (internal wiring)
  https://www.amazon.com/Ethernet-CableCreation-Network-Category-0-25m%EF%BC%880-82FT%EF%BC%89/dp/B076PV41W3

• USB-C Panel-Mount Adapter (power input)
  https://www.amazon.com/QIANRENON-Straight-Connector-Mounting-Extension/dp/B0CQ4VD2N2

• Anker USB-C Cable (internal power routing)
  https://www.amazon.com/Anker-Charging-Samsung-MacBook-Braided/dp/B0CRZ6JJ6D

I want to thank Ramon for helping with the track layout and for bringing his LED tunnel, which added a really cool effect to the track. We ran a mix of small races and two-pilot team relay races, rotating partners so everyone had a chance to fly.

Around 9:15 PM, I started breaking down the track to make sure we had enough time to clean up. With the help of Ramon and Mick, we got everything packed and the room reset by 9:50 PM.

It was a good first event, and I am looking forward to more meetups in the future. The space worked well for six pilots, a little tight but manageable. I hope we can find a bigger but still affordable space down the road.

Round1 Hayward management was amazing and very supportive. I really appreciate their help and hope we can continue hosting events there.

My Best Session So Far

Had a few clean runs today and finally hit a 13.99-second streak over three consecutive laps — my best so far!
Lap times from my best pack:

4.7
4.6
4.8
4.6
4.5
4.8

It’s always satisfying when you start linking turns smoothly and can feel the rhythm through each gate.

Gear and Setup

• Drone: Mobula 6 HDZero

• Battery: Lava 300 mAh 1S HV

• Timer App: TinyFPVTimer for Android / TinyFPVTimer for iOS

I use the TinyFPVTimer app to record my laps. It’s simple and works great for indoor practice sessions.

Small Crashes, Big Surprises

During the session, I managed to break two propellers, but honestly, I’m still impressed by how durable the Mobula 6 HDZero is. Even with a few hard hits, it kept flying smooth and stable after a quick prop swap.

Why I Love This Track

RaceGOW5 Track 1 is compact, has a great rhythm, and feels made for whoops.
The tighter sections teach throttle discipline, while the open sections let you stretch out clean lines. It’s also a perfect fit for small-space flying — no need for a big gym or warehouse.

I don’t submit my times to the RaceGOW event leaderboard — I just fly the tracks for fun and to keep improving. Each layout is a new challenge, and seeing progress over time is what keeps me hooked.

Next Goal:
Break under 13.5 seconds with three clean consecutive laps.

Until then, I’ll keep flying, swapping props, and chasing smoother lines.

Bonus — Track Run Practice with LED Gates

Here’s a short clip of my RaceGOW5 Track 1 practice run using my LED gates setup.
The track is tight but fun, and the lighting really adds to the atmosphere.

What you need

• Quad with ExpressLRS receiver

• Computer with Wi-Fi

• USB data cable

• Small desk fan

Steps

1. Safety first

   • USB power only (don’t plug in the flight battery for this step).

   • Aim a fan at the quad so it doesn’t overheat on the bench.

2. Connect by USB

   • Plug the quad into your computer.

     

3. Wait for Wi-Fi mode

   • You’ll see the receiver LED blink steadily at first.

   • After ~1 minute it changes to rapid blinking = Wi-Fi mode is active.

   • If you’re following the video, this portion is sped up.

4. Join the receiver’s Wi-Fi

   • On your computer, open Wi-Fi networks and select ExpressLRS RX.

     

   • Password: expresslrs (all lowercase).

     

5. Open the Web UI

   • In your browser, go to: 10.0.0.1

   • This opens the ExpressLRS Wi-Fi configuration page.

     

6. Set the Binding Phrase

   • Find Binding Phrase.

   • Enter the exact same phrase already set on your radio (example: levelupfpv).

   • Click Save. The quad will reboot.

     

7. Quick verify

   • Power on your radio.

   • Power the quad (USB is fine, or briefly with flight battery if you need full receiver power).

   • You should see the link establish automatically (no bind button needed).

Troubleshooting

• Don’t see “ExpressLRS RX”?

  • Wait the full minute; some receivers take a bit longer on first boot.

  • Toggle USB: unplug → wait 10 seconds → plug in again.

  • Make sure your computer is scanning 2.4 GHz networks.

  • If your radio is already powered and bound, the receiver may not enter Wi-Fi mode—turn the radio off and try again.

• Can’t open 10.0.0.1?

  • Confirm you’re connected to ExpressLRS RX Wi-Fi.

  • Try a different browser.

  • Forget the network, reconnect, and retry.

• No link after saving the phrase?

  • The radio and quad must have the exact same binding phrase (spelling and case).

  • Reboot both radio and quad.

  • If needed, temporarily disable Model Match on the radio for testing.

Next step: You’re ready to move on to arming checks and basic hover.
Missed part one? Start here: FPV Beginner Guide #1

🎥 Watch the Video Tutorial:

📹 Video & Camera Quality

The HDZero system keeps latency ultra-low, which is exactly what you want for racing.

• The video feed looks slightly lower resolution compared to the Mobula7 HDZero with the Nano V3 cam or Walksnail Lux.

• Still more than clear enough to track gates and fly confidently.

If you want absolute clarity, the Mobula7 HDZero edges it; for racing, the Mobula6 Race is tuned right.

✈️ Flight Performance

Flies great, but it has quirks.

• Ultra responsive, agile, and turns on a dime.

• Also feels squirrely until you adapt.

• I still prefer the Mobula7 HDZero when I want a planted feel and longer sessions.

🎮 Rates Setup

I’m flying with Oscar Liang’s Tiny Whoop rates (source):

Pitch/Roll

• Center Sensitivity: 230

• Max Rate: 1000

• Expo: 0.62

Yaw

• Center Sensitivity: 250

• Max Rate: 1300

• Expo: 0.68

Oscar explains it best:

“I personally run a slightly higher yaw rate, since I use a lot of yaw when flying tiny whoops indoors. The rapid sharp turns really benefit from that extra responsiveness.” — Oscar Liang

I agree. These rates feel fast at first, but once you adjust, the yaw authority makes tight indoor tracks smoother and more controlled.

📝 Rates CLI Snippet

For those who want to copy/paste directly into Betaflight:

# Oscar Liang Tiny Whoop Rates
rateprofile 0
set roll_rc_rate = 23
set pitch_rc_rate = 23
set yaw_rc_rate = 25
set roll_expo = 62
set pitch_expo = 62
set yaw_expo = 68
set roll_srate = 100
set pitch_srate = 100
set yaw_srate = 130
save

🔋 Battery & Flight Time

• With Lava 300mAh 1S, I’m getting around or under 3 minutes to 3.4V.

• The short flight time is the biggest con — right when you find your groove, the pack sags.

• The upside: 300mAh charges fast, so with multiple sets you can keep rotating.

For reference, Mobula7 HDZero + 550mAh 1S gives 4–5 minutes, which feels much more comfortable.

🛠️ Build & Durability

• Early stress mark under the right canopy screw.

• Battery protrudes; many fly toilet-tank style (sideways) to protect it.

• Tighten screws before flying. I lost a motor screw already — nylon screw kits aren’t cheap (~$30 at WeBleedFPV).

Durability is decent, but it’s clearly a race-tuned whoop, not a tank.

✅ Pros

• Extremely agile and responsive

• Ultra-low latency video

• Razor-sharp turns

• 300mAh packs recharge quickly

❌ Cons

• Short flight time (~3 min)

• Feels squirrely until you adapt

• Slightly lower cam resolution than Mobula7 HDZero

• Canopy stress early, hardware pricey

📊 Mobula6 HDZero Race vs Mobula7 HDZero

🔋 Battery Guide

• Mobula6 HDZero Race (65mm, 1S) → Lava 300mAh 1S HV. Get 2–3 sets (5 packs each).

• Mobula7 HDZero (75mm, 1S) → GB3 or Lava 550mAh 1S HV for longer endurance.

• Meteor75 Pro O4 (75mm, 1S) → Lava 550mAh 1S HV (solid choice for your setup).

• Mobula7 O4 (75mm, 2S) → GB3 530–550mAh 2S HV, or Tattu R-Line 650mAh 2S for outdoor runs.

Storage tip: keep packs at 3.8V/cell when not flying.

📂 Full Default Betaflight CLI Dump (Mobula6 HDZero)

defaults nosave


# version
# Betaflight / STM32F411 (S411) 4.4.2 Jun 25 2024 / 07:33:20 (23d066d08) MSP API: 1.45

# config: YES

# start the command batch
batch start

# reset configuration to default settings
defaults nosave

board_name CRAZYBEEF4SX1280
manufacturer_id HAMO
mcu_id 002100343533511137393932
signature 

# name: Mob6 HDZERO RACE

# resources
resource MOTOR 1 B08
resource MOTOR 2 B10
resource MOTOR 3 B06
resource MOTOR 4 B07

# feature
feature -RX_SERIAL
feature -SOFTSERIAL
feature -TELEMETRY
feature RX_SPI

# serial
serial 0 131073 115200 57600 0 115200

# beeper
beeper -ARMED

# beacon
beacon RX_LOST
beacon RX_SET

# map
map TAER1234

# aux
aux 0 0 0 1800 2100 0 0
aux 1 1 1 1200 1600 0 0
aux 2 2 1 1700 2100 0 0
aux 3 35 3 1550 2100 0 0

# vtxtable
vtxtable bands 6
vtxtable channels 8
vtxtable band 1 BOSCAM_A A CUSTOM     0    0    0    0    0    0    0    0
vtxtable band 2 BOSCAM_B B CUSTOM     0    0    0    0    0    0    0    0
vtxtable band 3 BOSCAM_E E CUSTOM  5705    0    0    0    0    0    0    0
vtxtable band 4 FATSHARK F CUSTOM  5740 5760    0 5800    0    0    0    0
vtxtable band 5 RACEBAND R CUSTOM  5658 5695 5732 5769 5806 5843 5880 5917
vtxtable band 6 LOWBAND  L CUSTOM     0    0    0    0    0    0    0    0
vtxtable powerlevels 3
vtxtable powervalues 14 23 0
vtxtable powerlabels 25 200 0

# master
set gyro_lpf1_static_hz = 0
set gyro_lpf2_type = PT2
set gyro_lpf2_static_hz = 0
set dyn_notch_q = 500
set dyn_notch_min_hz = 120
set dyn_notch_max_hz = 500
set acc_lpf_hz = 10
set acc_calibration = 101,196,48,1
set dshot_idle_value = 600
set dshot_burst = OFF
set dshot_bidir = ON
set dshot_bitbang = AUTO
set motor_pwm_protocol = DSHOT300
set motor_poles = 12
set motor_output_reordering = 0,3,2,1,4,5,6,7
set failsafe_delay = 4
set failsafe_recovery_delay = 20
set align_board_roll = 180
set align_board_yaw = 135
set vbat_max_cell_voltage = 440
set vbat_min_cell_voltage = 310
set vbat_warning_cell_voltage = 347
set yaw_motors_reversed = ON
set small_angle = 180
set deadband = 1
set yaw_deadband = 1
set pid_process_denom = 1
set osd_vbat_pos = 45
set osd_rssi_pos = 33
set osd_link_quality_pos = 3465
set osd_rssi_dbm_pos = 3498
set osd_tim_1_pos = 3114
set osd_tim_2_pos = 2433
set osd_flymode_pos = 3562
set osd_g_force_pos = 65
set osd_throttle_pos = 3529
set osd_vtx_channel_pos = 2081
set osd_current_pos = 2528
set osd_mah_drawn_pos = 2497
set osd_craft_name_pos = 2547
set osd_warnings_pos = 329
set osd_avg_cell_voltage_pos = 2465
set osd_disarmed_pos = 2517
set osd_esc_rpm_pos = 161
set osd_core_temp_pos = 14616
set osd_displayport_device = MSP
set osd_canvas_width = 50
set osd_canvas_height = 18
set debug_mode = RX_EXPRESSLRS_SPI
set vtx_band = 5
set vtx_channel = 8
set vtx_power = 1
set vtx_freq = 5917
set vcd_video_system = HD
set gyro_1_sensor_align = DEFAULT
set gyro_1_align_yaw = 0
set expresslrs_uid = 245,132,181,219,10,94
set expresslrs_rate_index = 1
set craft_name = Mob6 HDZERO RACE

profile 0

# profile 0
set p_pitch = 50
set i_pitch = 68
set d_pitch = 30
set f_pitch = 101
set p_roll = 53
set i_roll = 72
set d_roll = 31
set f_roll = 108
set p_yaw = 53
set i_yaw = 72
set f_yaw = 108
set d_min_roll = 31
set d_min_pitch = 30
set simplified_i_gain = 75
set simplified_d_gain = 105
set simplified_pi_gain = 120
set simplified_dmax_gain = 0
set simplified_feedforward_gain = 90
set simplified_pitch_d_gain = 85
set simplified_pitch_pi_gain = 90

profile 1

profile 2

profile 3

# restore original profile selection
profile 0

rateprofile 0

# rateprofile 0
set rates_type = BETAFLIGHT
set roll_rc_rate = 100
set pitch_rc_rate = 100
set yaw_rc_rate = 100
set roll_srate = 70
set pitch_srate = 70
set yaw_srate = 70

rateprofile 1

rateprofile 2

rateprofile 3

# restore original rateprofile selection
rateprofile 0

# save configuration

🎯 Final Thoughts

The Mobula6 HDZero Race is a pure race whoop: insanely nimble, perfect latency, effortless tight turns. The trade-off is endurance; ~3 minutes feels short for casual flying.

If you want more flight time and a planted feel, the Mobula7 HDZero is the better choice. If you want the most agile, gate-snapping 65mm racer, the Mobula6 Race is the one to grab.

☕ Support My Work

✨ Highlights (Quick Takeaways)

• 4–5 minutes of flight time on 450/550 mAh packs, even with beat-up batteries.

• Frame and canopy still intact after 10-ft crashes — frame durability is good.

• Lux camera fragile (IR filter fell off) but fixable with glue; ~$60 if replacement needed.

• Compact size + HDZero low latency = much easier gap hitting and quick adjustments.

• Antenna is built into the AIO — if it breaks, the whole board may need replacement.

• Still very fast, agile, and fun to fly — but requires more care than I expected.

🛡️ Frame & Canopy Durability

• Frame condition: No cracks in the arms, but I’ve already broken two propellers near the base. Recommend keeping plenty of extras on hand.

• Flexibility: Frame still bends a lot, which I think helps spread crash forces.

• Dampeners/gummies: Still holding solid, no slipping.

• Canopy condition: Starting to show stress marks and looks pretty beat up after repeated crashes. The front ducts are becoming misshapen, which could affect airflow slightly.

  

  

• Protection: The foam pad and lens lip continue to help, but the canopy overall doesn’t provide enough lens protection on its own (better with the extra canopy mod).

• Camera glue: Haven’t needed to remove the glue yet — unknown how serviceable it really is.

🔧 Wiring, Antenna & Mods

• Motor wire hack: Floss + twist fixes remain intact, adding strain relief and reducing risk of pulled pads.

• Power lead reroute: Rewiring to the back made battery installs easier. Stock works well, but expect a tough install if you reroute.

  

• Connector reliability: The A30 connector stays tight and reliable after heavy use.

• Antenna: The ELRS antenna is built into the AIO. If it breaks, the board likely needs replacing, though adding an external ELRS module might be possible for advanced pilots. I’d still reinforce it with E6000 for crash safety.

💥 Damage Report (After More Crashes)

• After several hard crashes, the Lux camera developed a red hue at the bottom of the video feed.

  

• On inspection, the IR filter inside the lens had come loose. I carefully removed it and glued it back with E6000.

  

• Since re-gluing, the red hue is gone and the video looks normal again.

• While it’s holding up so far, it still feels like a weak point in the camera design—if the filter comes loose again, replacing the Lux lens (~$60) may be necessary.

🏗️ Lens & Canopy Mods

• Ordered a replacement lens, but the threads don’t match the Lux housing well. The new lens also didn’t come with an IR filter. Running without the filter might be possible, but image colors will likely shift, especially outdoors.

• To protect the fragile camera, I added a Mobula7 canopy on top of the stock Lux canopy.

• The double-canopy setup adds noticeable protection: fewer lens hits, more confidence in crashes.

  

• Downsides: it adds a little extra weight and makes turtle mode more difficult, but the trade-off is worth it for durability.

🔋 Batteries & Flight Performance

• Still consistent 4–5-minute flights on 450 mAh and older 550 mAh packs.

• My well-used 550 mAh packs (6+ months) still deliver. I’ll test fresh packs soon.

• Battery voltage sag is noticeably lower versus my Meteor75 Pro O4—lighter weight = less strain.

• Flight feel is slightly snappier with 450 mAh, but the difference is subtle.

📡 Video & Goggles

• Focus chart remains extremely useful—dial in once, done.

• Feed quality: Minor breakup when objects block view, but not distracting.

• Low light: Still good indoors.

• Range vs. Interference: DJI holds the edge longer, but HDZero excels for quick indoor freestyle.

🕹️ Flight Feel & Progress

• Increasing stick time has made more throttle sense intuitive. Still surprised by how little throttle is needed compared to Meteor75 Pro O4.

• Gap hitting: The Mobula7’s compact size and lighter weight give me more margin of error compared to the Meteor75 Pro O4. Combined with HDZero’s low latency, it feels easier to slip through tight gaps and make quick adjustments mid-flight.

• Prop wash: No issues—stable flight from start.

• Prop types: Tri-blades feel smoother; bi-blades feel looser.

🔧 Maintenance, Parts & Expense (Beginner Friendly Thoughts)

• Parts still working: Everything's intact. Haven’t replaced anything yet.

• All-in-one caution: AIO replacements are expensive—beginners should know that soldering may be needed if things break.

• Beginners tips: This is a fun quad, but consider if you’re ready: tight builds mean solder replacements. Adjust throttle with caution.

Current Parts Pricing (from Pyrodrone and others at time of writing):

• Replacement canopy (Mobula7/Mobula6 fixed 25°): around $3–4

• Replacement motor (EX1002 20,000 KV): around $16 each

• Spare 75 mm V4 frame: around $7

• AIO flight controller (includes ELRS antenna): much more expensive (~$70–$80, if available)

• HDZero Lux camera: around $60

✅ Pros & Cons

Pros:

• Very agile and fast — low latency HDZero shines indoors.

• Frame is tough and flexible — absorbs crashes well.

• Consistent 4–5 minutes flight time on 450–550 mAh packs.

• Compact size helps with hitting smaller gaps.

• Focus chart makes dialing in the lens easy.

• Double-canopy mod adds strong protection.

Cons:

• Lux camera fragile, IR filter and lens issues after crashes, ~$60 to replace.

• Canopy provides limited camera protection unless you mod it.

• Extra canopy adds weight and makes turtle mode harder.

• ELRS antenna built into the AIO — break it, replace the whole board.

• Repairs (RX/TX resoldering, IR filter glue fixes, camera swaps) are challenging due to tiny pads.

• Less durable overall than first impressions suggested — requires more care.

🏁 Final Thoughts (Long-Term Verdict)

The Mobula7 HDZero is still one of the most fun whoops I’ve flown — fast, agile, and capable of tight gap flying thanks to its compact size and low latency video. But after damaging the camera, I’ve become a bit more careful with it. The durability isn’t quite as bulletproof as my first impressions suggested: the frame holds up well, but the Lux camera is fragile and costly to replace.

With the extra canopy mod and a glued IR filter, my build feels solid and confidence-inspiring again. It’s a blast to fly and has become my main indoor quad, but I now think of it as high-performance with some delicate parts, not indestructible.

🎮 Game Stats (For Fun)

A different way of looking at it, in “game terms”:

• Weight Class: Ultra-Light (1S Whoop)

• Durability: 6/10 → 8/10 with extra canopy (+2) — Frame strong, canopy decent, Lux camera fragile but much better protected with the double-canopy mod.

• Speed/Agility: 9/10 — Very fast, agile, quick throttle.

• Flight Time: 8/10 — 4–5 minutes on 450–550 mAh packs.

• Pilot Level: Medium-High — Fast and powerful, repairs may require soldering.

☕ Support My Work

Goal: Convert a BETAFPV Meteor75 Pro 1S PNP to HDZero using the Whoop Lite Bundle, reusing a canopy for mounting the HDZero Nano V3 camera.

Difficulty: This is an easy-to-advanced build. It’s easy because it’s solder-free, but repinning the JST harness can be challenging. Some builders may choose to remove motor plugs and solder motors directly, and the same goes for the VTX wiring.

Parts List (Pyrodrone)

Total (before tax/shipping): $276.96

Footnote:
*The Vision40 canopy is about ~$4 (RotorRiot), and the Mobula7 canopy is about ~$4 (WeBleedFPV link). Used together, they provide proper protection for the HDZero Nano V3 lens. STL files are online if you have a 3D printer.

Important: Do NOT use the Vision40 canopy — it leaves the camera lens exposed and unprotected. Ensure whatever canopy you choose provides proper lens protection, or use the Mobula7 canopy/mod.

Tools

• #000 Phillips screwdriver

• Tweezers/JST-SH pin tool

• Low-temp soldering iron (optional if hard-wiring)

• Smoke stopper (BT2.0 adapter — optional for whoops, but can be used with caution)

• Kapton/electrical tape

• Isopropyl alcohol + cotton swabs

• E6000 adhesive (for securing UFL and MIPI connections)

Wiring Map (Repinning)

Below is a fun interactive section — look at the diagram of the AIO and VTX with the harness, and guess which wire goes where.

Pick Your Wiring Answer:

A) 5V → 5V | GND → GND | TX → RX | RX → TX
B) 5V → GND | GND → 5V | TX → TX | RX → RX
C) 5V → TX | GND → RX | TX → GND | RX → 5V
D) 5V → 5V | GND → GND | TX → TX | RX → RX

(Correct answer at the bottom of the post!)

Build Steps

Note: The Meteor75 Pro PNP already has the motors, AIO, and frame assembled. These steps include notes for those building entirely from scratch.

1. Install Motors (Scratch Builds Only): Seat all four motors into the frame, ensuring wires face inward. When plugging motors into the AIO, inspect the JST connector pins—if they don’t align, a pin could be bent. Never pull on the wires when disconnecting; instead, gently pry from the sides of the JST housing.

2. Install AIO (Scratch Builds Only): Place the AIO in the frame, install the M2 damper for vibration isolation (Vision40 Hardware Kit if needed), connect motor plugs.

   

3. Prepare VTX: Assemble the Whoop Lite VTX, remove the metal shielding, add dampers. Install the MIPI cable by aligning it with the port on the VTX or camera, then gently pressing down until it clicks. Repeat for both ends.

   

   

   Gently lift the metal shielding, the tabs should slowly lift

4. Repin & Connect: Repin the JST harness to match the wiring map, connect the VTX to the AIO.

   

5. Quick Power-On Test: Props off, battery in — verify VTX powers on (R1 channel default) and video feed is active.

6. Assemble Components: Make sure the canopy actually protects the Nano V3 lens before final assembly. Feed antenna cable through top, install canopy over VTX, position VTX over AIO, and sandwich cables flat.

   

7. Secure Antenna: Connect UFL antenna to VTX and zip tie to canopy.

   

8. Inspect & Battery Test: Check connections, battery test.

9. Betaflight Configuration: With COM port drivers installed, connect to Betaflight and configure each tab to your preferences.

Pre-Flight Checklist

• Props & canopy secure

• Battery at 4.35V (LiHV)

• VTX power: 25mW indoor / 200mW outdoor

• OSD shows voltage + LQ

• Channel clear

• Hover test before full flight

Notes

• Matrix 3-in-1 FC is digital-only; perfect for HDZero.

• HDZero control/OSD via MSP, not SmartAudio.

• E6000 adds extra security to UFL and MIPI connectors.

• Canopy choice is critical: make sure it protects the Nano V3 lens.

BetaFlight

Optional set your rates

You can connect your radio and test Throttle, Yaw, Pitch, and Roll. Make sure Channel Map is AETR1234 (Mode 2)

Set your Modes

Ensure you note the direction of your propellors, this picture is showing props in.

Turn off Core temperature or you will keep seeing the warning. If Core temperature keeps warning your Low batter warning will not show.

#OSD CLI
set osd_warn_bitmask = 270207
set osd_rssi_dbm_alarm = -100
set osd_vbat_pos = 2563
set osd_rssi_pos = 192
set osd_link_quality_pos = 2531
set osd_rssi_dbm_pos = 2499
set osd_rsnr_pos = 160
set osd_tim_1_pos = 386
set osd_tim_2_pos = 3628
set osd_remaining_time_estimate_pos = 33
set osd_flymode_pos = 3597
set osd_throttle_pos = 3565
set osd_vtx_channel_pos = 33
set osd_crosshairs_pos = 313
set osd_current_pos = 2594
set osd_mah_drawn_pos = 2626
set osd_craft_name_pos = 535
set osd_home_dist_pos = 98
set osd_flight_dist_pos = 130
set osd_warnings_pos = 14837
set osd_avg_cell_voltage_pos = 44
set osd_pit_ang_pos = 97
set osd_rol_ang_pos = 65
set osd_disarmed_pos = 267
set osd_esc_tmp_pos = 129
set osd_esc_rpm_pos = 150
set osd_core_temp_pos = 225
save

Quick Review of the Build

This Meteor75 Pro HDZero conversion turned out clean and solid. The solder-free design made it beginner-friendly, but the JST repinning added just enough challenge to keep it interesting. Removing the VTX shielding was necessary for a snug fit, and the E6000 on the UFL and MIPI adds peace of mind for racing durability. Cable management between the AIO and VTX was key — keeping it flat and untwisted avoided MIPI stress. The canopy fit was tight but secure, and initial tests showed stable video and good weight balance. Overall, it’s a fun, compact HDZero build with great performance potential.

Lesson Learned: The Vision40 canopy left the Nano V3 lens exposed and it got nicked after a few light bumps.

That’s the beauty and the madness of FPV — every day in the hobby you learn something new. Troubleshooting can be frustrating, but it’s also part of the fun and makes each build more rewarding.

Updates:

• I ordered two replacement Nano V3 lenses directly from HDZero — total cost was $30.24 with shipping. I also learned that gently twisting the lens forward or back adjusts the focus.

• I ordered a few shorter replacement lenses that may fit better under the canopy, and I plan to test the Mobula6 HDZero Racing as well.

• Looking back, this build may have been better suited with the HDZero Eco Bundle to save cost. However, that camera lacks side screw holes, which could make canopy mounting tricky. I may still try the Eco Bundle on another 75mm or 80mm build.

• One advantage of the DJI O4 Lite and HDZero Whoop Lite paired with the Vision40 canopy is the flexibility — the VTX assembly can be moved between whoop frames.

For now, I fixed the lens protection issue by cutting up an extra Mobula7 canopy and using that piece as a guard. The Mobula7 canopy itself is only ~$4.

No lens protection

With lens protection

Flight Notes:

• The whoop feels very similar to my Meteor75 Pro O4 in flight.

• The HDZero Whoop Lite VTX is heavy (similar to O4 Lite, just slightly lighter), and is probably better suited for a 2S build like the Mobula7 O4.

• Despite the extra weight, it still flies well, and the Mobula7 canopy protection makes it field-ready.

• Turtle mode is harder with the heavier build, but durability is good — you mentioned that earlier in chat. That gives readers a real-world “tradeoff.”

Bonus – Walksnail Avatar HD Mini 1S Lite Kit Setup

If you want to swap the Meteor75 Pro into Walksnail instead of HDZero, you’ll need to solder the included JST 1.0 cable to the Walksnail VTX.

Steps

1. Prep the Cable:

   • Take the JST 1.0 cable included with the Walksnail VTX.

   • Tin the ends of each wire with a small amount of solder.

2. Reference Pinout:

   • Double-check the pinout on the Walksnail board against the diagram below (picture here).

   • Ensure you know which wire is 5V, GND, TX, RX before soldering.

3. Solder Carefully:

   • Solder each wire to the correct pad on the Walksnail VTX.

   • Be quick with heat to avoid lifting pads.

4. Secure the Wires:

   • Once soldered, add a bit of Kapton tape or E6000 to secure the JST cable and relieve stress.

5. Connect to AIO:

   • Plug the JST 1.0 connector into your Meteor75 Pro AIO.

   • Confirm the orientation and match pinout correctly (5V → 5V, GND → GND, TX → RX, RX → TX)

     

6. Power Test:

   • Props off, plug in a LiPo.

   • Confirm the Walksnail VTX powers up and video feed shows in goggles.

⚠️ Note: Unlike the HDZero Whoop Lite, the Walksnail Mini 1S Lite Kit requires soldering. Double-check your wiring against the provided pinout before powering on. A wrong connection can fry the VTX instantly.

✨ Pro Tip: If you wire your JST harness correctly, you can easily swap between a Walksnail VTX and an HDZero VTX on the same Meteor75 Pro frame without rewiring the flight controller.

Correct Wiring Answer

A) 5V → 5V | GND → GND | TX → RX | RX → TX ✅

🎥 See it in Action:

☕ Support My Work

All-in-one beginner kits are okay to get you flying fast, but they don’t really grow with you. A better path is to buy gear piece by piece that you can keep using as you progress. Here’s my recommended beginner setup:

🎮 Radio (Controller)

RadioMaster Pocket ELRS

• Compact, affordable, and ExpressLRS built-in.

• Works with any (ELRS) quad you buy in the future.

• Add two 18650 button-top batteries.

🔗 Amazon | Pyrodrone | GetFPV

🔋 Batteries:
Amazon | Pyrodrone | GetFPV

🔋 Batteries & Charger

For 1S whoops like the Air75, here are the best picks:

• 550mAh Lava (BT2.0) – great flight times, strong punch.
  🔗 Amazon | Pyrodrone

• 450mAh Tattu (BT2.0) – lighter, solid for indoors.
  🔗 Amazon

• ViFly WhoopStor V3 Charger – charges and storage-charges 1S packs.
  🔗 Amazon | Pyrodrone | GetFPV

👓 Goggles (FPV Video)

• Budget Option (Analog Only): Eachine EV800D
  Cheap, reliable, and comes with DVR recording.
  🔗 Amazon | Pyrodrone | GetFPV

• Upgrade Option: HDZero BoxPro Plus
  Future-proof goggles – runs analog, HDZero, and even Walksnail (with VRX).
  🔗 HDZero | Pyrodrone | GetFPV

🚁 First Quad

BetaFPV Air75 (Analog, 75mm)

• Perfect beginner whoop: durable, cheap, and fun indoors or outdoors.

• The 75mm size is more forgiving than 65mm (better flight times, more durable motors).

• Runs on 450–550mAh BT2.0 packs.

🔗 Amazon | Pyrodrone | GetFPV

💡 If you’re flying in a tiny indoor space, the Air65 fits better – but durability and flight times are weaker.

⚡ Battery Best Practices (Must Read!)

Flying FPV means you’ll go through batteries fast. To make them last:

• ✅ Charge before you fly – don’t leave packs sitting fully charged.

• ✅ Storage charge after flying – keep them around 3.8V/cell.

• ✅ Don’t drain too low – land at 3.2–3.3V/cell minimum.

• ✅ Charge at 1C – for example:

  • 300mAh → 0.3A

  • 450mAh → 0.45A

  • 550mAh → 0.55A

• 💡 My tip: I charge all my 1S packs at 0.4A. That way, I can plug in 300, 450, or 550mAh packs without changing settings.

⚠️ Treat LiPos with respect – good habits keep your batteries safe, last longer, and give you consistent flight performance.

🧰 Buy as You Need It

It’s easy to go overboard buying spares when you’re new. For example, I bought a ton of extra propellers at first thinking I’d break them constantly. On a whoop, the ducts protect them — unless you see major flight issues like vibration/jello, you don’t need to replace props often.

👉 A better approach: buy spares when you actually need them (batteries excluded — you’ll always want more of those).

🌬️ Bench Setup & Best Practices

When working on your whoop at the desk, a few habits will save you from burning hardware or losing hours of setup:

• 🌬️ Use a fan during setup – when your whoop is plugged into the computer (USB + battery), it can overheat quickly. Keep a cheap desk fan blowing on it.

• 💾 Back up your configuration – always save a diff all or take screenshots of each Betaflight tab.

• ⚠️ Only upgrade firmware if you need to – upgrading wipes your config, and copying settings between Betaflight versions doesn’t always work.

• 🔑 Use a binding phrase (ExpressLRS) – makes binding radios and receivers painless across all your quads.

👉 These little steps prevent a lot of frustration and keep your quads consistent as you grow.

👥 Join the Community

FPV is way more fun with others:

• Check out MultiGP → https://www.multigp.com/

• Look for local Facebook FPV groups.

Even if you don’t own a drone yet, meeting pilots in your area will help you learn faster, try different gear, and get into races or fun fly events.

🛒 Where to Buy FPV Gear

Here are my go-to stores for FPV parts, batteries, and quads:

• Pyrodrone – huge selection, fast shipping, often best prices.

• GetFPV – great for radios, goggles, and whoops.

• TinyWhoop – whoop-specific parts, props, and accessories.

• NewBeeDrone – premium whoop parts and batteries.

• WeBleedFPV – excellent BT2.0 batteries, props, and whoop race gear.

• Amazon – useful for fast returns on radios, chargers, and tools.

💡 Tip: Amazon is great for easy returns, but FPV-specialty shops usually have better stock, newer releases, and community support.

✅ Why This Kit?

• Radio first → practice in sims for free.

• Air75 quad → cheap, durable, and fun indoors or out.

• Charger & batteries → more stick time, less waiting.

• Future-proof goggles → start with analog, upgrade to HD later.

• Practical tips → don’t overspend, cool your quad, back up configs, and join the community.

This setup skips the “toy kit trap” and gives you gear you’ll keep using.

🏁 Final Tip

At the end of the day, the best gear is the one that gets you flying.
Start small, fly safe, and have fun. 🚁🔥

☕ Support My Work

🔑 Key Takeaways

• Super agile: Lighter than my Meteor75 Pro O4, with hover around 25–30% throttle.

• Gap killer: Low canopy design lets it slip into tiny spaces — I even flew it under my bed.

• Durable design: Foam pad + protective lip help protect the camera, canopy holds up in crashes.

• 1S power: With 550 mAh packs I’ve been getting ~5 min of hard flights, 450 mAh around 4 min.

This is my initial hands-on review of the Mobula7 HDZero after my first sessions flying it hard. I’ve focused on setup, flight feel, and early performance notes. I’ll follow up with a long-term review after more packs, races, and durability checks to see how it holds up over time.

First Impressions

The Mobula7 HDZero is lighter and more agile than my Meteor75 Pro O4.
Hover throttle sits at about 25–30% (compared to ~40% on the Meteor75 Pro O4), making altitude changes quick and easy.

450 mAh vs 550 mAh: I honestly didn’t notice much difference. I had 12 batteries in rotation (mix of 450 mAh and 550 mAh) and was randomly picking packs — flight feel stayed consistent.

The real surprise was how well it handles tiny gaps. I was able to dive under my bed, hit small openings, and thread spaces I never thought possible with a 75 mm whoop. Part of that confidence comes from the low-profile canopy design. Compared to the Meteor75 Pro’s bulky canopy, the Mobula7 feels slimmer and more compact in the air — which really shows when you’re gap-hunting.

Video Performance

HDZero won’t win a cinematic beauty contest against DJI O4, but for racing and freestyle, the latency and clarity are excellent.
I had no problem spotting gates, wires, or gaps even in indoor lighting.

• Pros: Ultra-low latency, very flyable in tight spaces.

• Cons: Colors and low-light performance can’t match O4.

Paired with HDZero Goggles 2, I had a comfortable fit — the wide elastic headband feels large and cushioned, making longer sessions easy.

Flight Feel

Out of the box, the Mobula7 HDZero feels smooth, responsive, and locked in.
No changes were needed — it just works.

Design, Canopy & Durability (Early Notes)

• Fixed camera angle: The stock camera mount isn’t adjustable. I’d love to see alternate-angle canopies (e.g., ~15°, ~25°, ~35°) or a simple wedge system so you can match indoor vs. outdoor speeds.

• Protection: The canopy could use more front/side coverage. A slightly thicker nose or small TPU bumper would help protect the camera lens and shell during tumbles.

• Foam pad design: Happymodel added a small foam pad right below the camera, sitting between the cam and AIO. This cushions impacts when the canopy flexes, and even though the canopy only mounts at three points, the foam helps spread the force. I was worried at first, but so far this design is working really well.

• Protective lip: The canopy also has a small lip at the end of the camera cutout. This acts like a mini bumper, helping shield the lens from direct hits — it’s been working great so far.

• Camera glue: It looks like Happymodel used some kind of glue to secure the camera in place. It hasn’t caused issues yet, but I’m not sure how easy it’ll be to remove if I need to replace the camera down the road.

• Crash performance (so far): I’ve had a lot of crashes already and the frame/canopy seem to be holding up. No major damage yet — just scuffs.

• Newbie-friendly wish: Happymodel should consider a solderless variant with camera and motor plugs to make repairs/swaps easier. I get they’re chasing low weight, but even an option would be great.

• Alt idea: A variant similar to the Mobula7 O4 on an 80 mm frame with motor plugs could balance ease-of-use and durability while keeping the HDZero stack light and tidy.

Build & Durability Notes

• Motor screws: I already had one back out. Worth reminding — check your motor screws regularly. For newbies: don’t over-tighten, as you can easily damage the motor windings.

• Motor wires: Stock routing could be cleaner. Ideally, the wires should be twisted and tied to the frame (floss or micro zip ties) to prevent stress on the pads. I plan to tidy mine up soon for better durability.

• Battery fit: The Lava packs feel a bit loose in the tray. A strip of electrical tape on the tray helps tighten the fit. Right now, the power lead holds it in place, but with lots of crashes, I could see the cable eventually being pulled or ripped from the AIO.

• Connector: The Mobula7 HDZero comes with an A30 connector. It works fine, but I really wish it shipped with a BT2.0 instead for better compatibility across whoops.

🔋 Battery Performance

Aggressive freestyle/race flights, usually landing at ~3.48 V/cell to baby my packs:

My Whoop Setup Opinions

• This Mobula7 HDZero has me wanting a Mobula6 HDZero to try a lighter 65 mm whoop for comparison.

• My Vision40 in a 75 mm frame feels heavy — I would not recommend DJI O4 or Walksnail on 75 mm whoops.
  The motors (1002) just can’t carry the VTX weight well:

  • Feels underpowered

  • Flight times degrade significantly (you’re looking at ~300 mAh packs for decent handling)

  • Yes, it flies, but not pleasantly

🧰 Pilot Tips

• Props off before USB connection.

• Consider a better antenna if flying outdoors.

• Store LiPos at 3.8 V/cell to extend lifespan.

• Match your goggle’s aspect ratio and latency mode to your flying style.

✅ Verdict

For me, this quad is pure fun — light, agile, and HDZero sharp.
Coming from heavier 75 mm whoops like my Meteor75 Pro O4, the Mobula7 feels like taking off a backpack.

📊 Comparison: Mobula7 HDZero vs Meteor75 Pro O4

📂 Full Default Betaflight CLI Dump (Mobula7 HDZero)

defaults nosave


# version
# Betaflight / STM32F411 (S411) 4.5.1 Aug  1 2024 / 13:38:51 (77d01ba3b) MSP API: 1.46
# config rev: ad0057e

# start the command batch
batch start

# reset configuration to default settings
defaults nosave

board_name CRAZYBEEF4SX1280
manufacturer_id HAMO
mcu_id 0026005f3431501420393556
signature 

# name: M7 Freestyle HD

# resources
resource MOTOR 1 B08
resource MOTOR 2 B10
resource MOTOR 3 B06
resource MOTOR 4 B07

# feature
feature OSD

# serial
serial 0 131073 115200 57600 0 115200

# beeper
beeper -ARMED

# beacon
beacon RX_LOST
beacon RX_SET

# map
map TAER1234

# aux
aux 0 0 0 1800 2100 0 0
aux 1 1 1 1150 1550 0 0
aux 2 2 1 1700 2100 0 0
aux 3 35 3 1550 2100 0 0

# vtxtable
vtxtable bands 6
vtxtable channels 8
vtxtable band 1 BOSCAM_A A CUSTOM     0    0    0    0    0    0    0    0
vtxtable band 2 BOSCAM_B B CUSTOM     0    0    0    0    0    0    0    0
vtxtable band 3 BOSCAM_E E CUSTOM  5705    0    0    0    0    0    0    0
vtxtable band 4 FATSHARK F CUSTOM  5740 5760    0 5800    0    0    0    0
vtxtable band 5 RACEBAND R CUSTOM  5658 5695 5732 5769 5806 5843 5880 5917
vtxtable band 6 LOWBAND  L CUSTOM     0    0    0    0    0    0    0    0
vtxtable powerlevels 3
vtxtable powervalues 14 23 0
vtxtable powerlabels 25 200 0

# master
set gyro_lpf1_static_hz = 0
set dyn_notch_count = 2
set dyn_notch_q = 600
set dyn_notch_max_hz = 650
set acc_calibration = 101,196,48,1
set dshot_burst = OFF
set dshot_bidir = ON
set dshot_bitbang = AUTO
set motor_poles = 12
set motor_output_reordering = 0,3,2,1,4,5,6,7
set failsafe_delay = 4
set failsafe_recovery_delay = 20
set align_board_roll = 180
set align_board_yaw = 45
set vbat_max_cell_voltage = 440
set vbat_min_cell_voltage = 310
set vbat_warning_cell_voltage = 320
set yaw_motors_reversed = ON
set small_angle = 180
set deadband = 1
set yaw_deadband = 1
set pid_process_denom = 2
set osd_warn_bitmask = 8191
set osd_vbat_pos = 45
set osd_rssi_pos = 33
set osd_link_quality_pos = 3466
set osd_link_tx_power_pos = 234
set osd_rssi_dbm_pos = 3498
set osd_rsnr_pos = 234
set osd_tim_1_pos = 3115
set osd_tim_2_pos = 2433
set osd_remaining_time_estimate_pos = 234
set osd_flymode_pos = 2554
set osd_anti_gravity_pos = 234
set osd_g_force_pos = 65
set osd_throttle_pos = 3530
set osd_vtx_channel_pos = 2081
set osd_crosshairs_pos = 205
set osd_ah_sbar_pos = 206
set osd_ah_pos = 78
set osd_current_pos = 2528
set osd_mah_drawn_pos = 2497
set osd_wh_drawn_pos = 234
set osd_motor_diag_pos = 234
set osd_craft_name_pos = 2547
set osd_pilot_name_pos = 234
set osd_gps_speed_pos = 234
set osd_gps_lon_pos = 234
set osd_gps_lat_pos = 234
set osd_gps_sats_pos = 234
set osd_home_dir_pos = 234
set osd_home_dist_pos = 234
set osd_flight_dist_pos = 234
set osd_compass_bar_pos = 234
set osd_altitude_pos = 234
set osd_pid_roll_pos = 234
set osd_pid_pitch_pos = 234
set osd_pid_yaw_pos = 234
set osd_debug_pos = 234
set osd_power_pos = 234
set osd_pidrate_profile_pos = 234
set osd_warnings_pos = 329
set osd_avg_cell_voltage_pos = 2465
set osd_pit_ang_pos = 234
set osd_rol_ang_pos = 234
set osd_battery_usage_pos = 234
set osd_disarmed_pos = 2518
set osd_nheading_pos = 234
set osd_up_down_reference_pos = 205
set osd_ready_mode_pos = 234
set osd_esc_tmp_pos = 234
set osd_esc_rpm_pos = 161
set osd_esc_rpm_freq_pos = 234
set osd_rtc_date_time_pos = 234
set osd_adjustment_range_pos = 234
set osd_flip_arrow_pos = 234
set osd_core_temp_pos = 1069
set osd_log_status_pos = 234
set osd_stick_overlay_left_pos = 234
set osd_stick_overlay_right_pos = 234
set osd_rate_profile_name_pos = 234
set osd_pid_profile_name_pos = 234
set osd_profile_name_pos = 234
set osd_rcchannels_pos = 234
set osd_camera_frame_pos = 35
set osd_efficiency_pos = 234
set osd_total_flights_pos = 234
set osd_aux_pos = 234
set osd_sys_goggle_voltage_pos = 234
set osd_sys_vtx_voltage_pos = 234
set osd_sys_bitrate_pos = 234
set osd_sys_delay_pos = 234
set osd_sys_distance_pos = 234
set osd_sys_lq_pos = 234
set osd_sys_goggle_dvr_pos = 234
set osd_sys_vtx_dvr_pos = 234
set osd_sys_warnings_pos = 234
set osd_sys_vtx_temp_pos = 234
set osd_sys_fan_speed_pos = 234
set osd_canvas_width = 50
set osd_canvas_height = 18
set debug_mode = RX_EXPRESSLRS_SPI
set vtx_band = 5
set vtx_channel = 1
set vtx_power = 2
set vtx_freq = 5658
set displayport_msp_fonts = 0,0,0,0
set gyro_1_sensor_align = DEFAULT
set gyro_1_align_yaw = 0
set gyro_2_bustype = SPI
set gyro_2_sensor_align = CW0
set expresslrs_uid = 0,0,224,214,254,20
set expresslrs_rate_index = 1
set rpm_filter_weights = 100,20,100
set rpm_filter_fade_range_hz = 100
set craft_name = M7 Freestyle HD

profile 0

# profile 0
set dterm_lpf1_dyn_expo = 7
set vbat_sag_compensation = 100
set iterm_relax_cutoff = 30
set iterm_limit = 500
set pidsum_limit_yaw = 1000
set p_pitch = 41
set i_pitch = 70
set d_pitch = 37
set f_pitch = 110
set p_roll = 41
set i_roll = 70
set d_roll = 37
set f_roll = 111
set p_yaw = 41
set i_yaw = 70
set f_yaw = 111
set d_min_roll = 37
set d_min_pitch = 37
set thrust_linear = 20
set simplified_master_multiplier = 155
set simplified_i_gain = 95
set simplified_d_gain = 80
set simplified_pi_gain = 60
set simplified_dmax_gain = 0
set simplified_feedforward_gain = 60
set simplified_pitch_d_gain = 90
set simplified_pitch_pi_gain = 95
set ez_landing_limit = 5

profile 1

profile 2

profile 3

# restore original profile selection
profile 0

rateprofile 0

# rateprofile 0
set rates_type = BETAFLIGHT
set roll_rc_rate = 100
set pitch_rc_rate = 100
set yaw_rc_rate = 100
set roll_srate = 70
set pitch_srate = 70
set yaw_srate = 70

rateprofile 1

rateprofile 2

rateprofile 3

# restore original rateprofile selection
rateprofile 0

# save configuration
save

Long-Term Review Coming
I plan to revisit this quad in a few weeks once I’ve logged more hours indoors and outdoors, tested different props, and compared it side-by-side with my Meteor75 Pro O4 and (hopefully) a Mobula6 HDZero. That’s when we’ll see how durable it is, how the VTX holds up, and whether my early excitement still holds.

☕ Support My Work

Welcome to the first post in my FPV From Zero to First Flight series!
This series will walk you from opening your FPV gear to your first safe flight — no prior experience needed.

In this first guide, we’ll cover how to set the ExpressLRS (ELRS) bind phrase on the RadioMaster Pocket so your quads can auto-bind without pressing any bind buttons.

Why Set a Bind Phrase?

When your radio and quad’s receiver share the same bind phrase, they connect automatically.
It’s faster, simpler, and avoids the hassle of pressing tiny bind buttons.

What You’ll Need

• RadioMaster Pocket with built-in ExpressLRS (2.4 GHz)

• A phone or laptop with Wi-Fi

• About 5 minutes

Step 1 – Enter Wi-Fi Mode on the Radio

1. Power on your radio.

   

2. Press and hold SYS to open the System Menu.

   

3. Go to Tools → select ExpressLRS.lua.

   

4. Scroll to Wi-Fi Connectivity → select Enable Wi-Fi.

   

5. Wait ~20 seconds. The module LED will blink differently and may display “Wi-Fi mode”.

Step 2 – Connect Your Device

1. On your phone or laptop, open Wi-Fi settings.

2. Connect to the network named ExpressLRS TX.

3. Enter the password: expresslrs

   

Step 3 – Open the ELRS WebUI

1. Open your web browser.

2. Type 10.0.0.1 into the address bar.

3. Press Enter — the ExpressLRS configuration page will load.

Step 4 – Set Your Bind Phrase

1. Find the Binding Phrase box.

2. Enter a short but unique phrase you’ll remember (e.g., levelupfpv).

   

3. Click Save & Reboot.

   

4. The module will restart with your new bind phrase set.

Done!

Your radio is now ready to automatically bind to any ExpressLRS receiver using the same phrase.

In the next post, we’ll set the same phrase on your quad so they link instantly.

🎥 Watch the Video Tutorial:

Note: This guide assumes you already know some basic FPV terms like Betaflight (drone configuration software), ExpressLRS (radio link system), VTX (video transmitter), and OSD (on-screen display).
If you’re brand new to FPV, I’ll be posting a full step-by-step beginner setup guide soon — covering everything from unboxing your gear to your first flight.

Golden Rules

• Props OFF for all bench work.

• Don’t update firmware yet (Betaflight or ELRS).

• Back up everything before you change anything.

• Use safe power-up practices for your quad type.

0) Before Touching Anything

Don’t update Betaflight or ExpressLRS yet. Fly it stock first so you know what “normal” feels like and so your backups are valid.

Why wait? Updating can introduce version mismatches and new defaults that break your current setup.
CLI backups don’t always forward-import: If you back up on an older Betaflight and import to a newer one, some CLI commands may fail or change names.
When to upgrade: Only if you need a feature/fix. Example: some Mobula7 AIOs ship with older Betaflight that doesn’t support OSD—you’ll want to update to a version that does so you can see OSD.

1) Backups (Do This First)

Radio (EdgeTX/OpenTX/Radiomaster):

1. Power on radio → connect USB → choose USB Storage.

2. Copy the entire SD card to your computer (keep this folder safe).

3. (Optional) Use Companion to back up radio models/settings.

Whoop (Betaflight):

Option 1 — CLI Method

1. Open Betaflight Configurator → connect USB (battery not plugged).

2. Go to CLI → type: diff all

3. Click Save to File. Name it like this: Mobula7-HDZero-Betaflight-4.4.3.txt

(Quad name – Video system – Betaflight version)

Option 2 — Presets Tab Method

1. Open Betaflight Configurator → connect USB.

2. Go to the Presets tab.

3. Click Save Backup in the top right.

4. Save with the same naming style above.

2) Install Drivers (Windows 11)

Fresh installs usually don’t have serial drivers.

• Install STM32 VCP (Virtual COM Port).

• Reconnect the quad and confirm Betaflight sees a COM port.

3) First Connection to Betaflight

1. Plug in USB only (no LiPo yet).

2. Click Connect; move your quad—attitude should move in the 3D model.

3. If sensors don’t show, some boards need LiPo just to initialize sensors (keep props off and stay safe).

4) Bind the Radio to the Drone (ExpressLRS) — Binding Phrase via Wi-Fi

Recommended method: Use a Binding Phrase so your gear automatically links.

ExpressLRS Web Interface Screenshots – ExpressLRS® is a trademark of its respective owners. Used for educational purposes only.

Step A — Set Binding Phrase on the Radio (Internal ELRS TX)

1. On your radio, press SYS → under Tools, select ExpressLRS.

2. Go to Wi-Fi Connectivity → Enable Wi-Fi.

3. On your computer, connect to the Wi-Fi network ExpressLRS TX.

4. Password: expresslrs (all lowercase)

5. Open a browser and go to http://10.0.0.1.

6. Under Binding Phrase, enter a phrase you’ll remember (e.g., MyFPVBind2025).

7. Click Save.

Step B — Set Binding Phrase on the Quad (ELRS RX)

1. Important: Keep a small fan blowing on your quad — powering it via USB or battery can cause the VTX to overheat if not cooled.

2. Connect the quad to your PC via USB-C.

3. Wait about 1 minute — the quad’s ELRS RX will start a Wi-Fi access point.

4. Connect to the Wi-Fi network ExpressLRS RX (or similar).

5. Password: expresslrs (all lowercase)

6. Open a browser and go to http://10.0.0.1.

7. Under Binding Phrase, enter the exact same phrase you set on your radio.

8. Click Save.

Step C — Link & Test

1. Power-cycle both the radio and the quad.

2. They should automatically link (check LQ in OSD or ELRS status LED).

3. If not linking, double-check both phrases match exactly.

5) Verify & Calibrate

A) Radio Mode & Channel Map

• Make sure your radio is Mode 2 (Throttle left stick).

• In Betaflight → Receiver tab:

• Channel map should match your radio (common: AETR1234).

• Move sticks—confirm:

• Roll = Right stick left/right

• Pitch = Right stick up/down

• Yaw = Left stick left/right

• Throttle = Left stick up/down

• Midpoints ≈ 1500, endpoints ≈ 1000/2000 (±5–10 is ok).

B) Accelerometer Calibration

• Put quad on a level surface → Setup tab → Calibrate Acc.

C) Switches & Modes

• Assign:

• ARM (2-position)

• BEEPER (optional but helpful)

• ANGLE (for bench tests only—fly Acro once in the air if that’s your plan)

• Verify switches respond in the Modes tab.

D) Motor Direction (Props Off)

• Motors tab → check each motor spins the expected direction.

• Reverse in Betaflight if needed.

6) First Power-Up

For larger quads:

1. Plug LiPo through a smoke stopper.

2. Confirm: no smoke, no hot components, VTX powers, OSD in goggles.

3. Set VTX band/channel and power level (stay low indoors).

For whoops:

• Smoke stoppers generally don’t work due to their low current limits.

• If you’ve soldered anything, use a multimeter to check for shorts first:

• Set to continuity mode.

• Touch one probe to battery positive, the other to battery negative.

• You should not hear a beep — a beep means a short and you should fix it before plugging in.

7) Maiden Flight Checklist

• Props on, clear indoor space or open field.

• Arm, gentle hover, check stick response, disarm.

• Hover → figure 8s → yaw turns → low passes.

• Keep line-of-sight; keep it close; set beeper hotkey.

8) When Should I Upgrade?

Only upgrade Betaflight/ELRS when:

• You need a specific feature/fix.

• You’re prepared to re-configure everything from notes (not just import CLI).

• You’ve made fresh backups first.

Heads-up: Restoring CLI from older to newer BF can fail on some commands. Use it as a reference, not a blind import.

9) Quick Troubleshooting

• No COM port: Install STM32 VCP + CP210x drivers; try a new cable/port.

• Won’t arm: Check Modes tab, arming disable flags, receiver activity, gyro calibration.

• Twitchy/oscillations: Props bent, motor screws too long, or bad tune—revert to factory first.

• No OSD: Check BF OSD page + VTX display protocol; some older firmware needs update.

10) Quick Betaflight Reference (Screenshots)

We’ll go over each tab in detail in a separate post, but here are screenshots of each tab with important items highlighted in red for quick reference.

1. Power & Battery Tab – Minimum/Maximum/Warning Cell Voltage.

2. Receiver Tab – Correct channel map and stick ranges.

3. Modes Tab – Arm, Angle, Beeper, Flip Over After Crash setup.

4. Motors Tab – Motor numbering and direction check.

5. OSD Tab – Recommended OSD elements for whoops.

6. Presets Tab – How to save a backup and view available tunes.

Betaflight Configurator Screenshots – Betaflight® is a trademark of its respective owners. Used for educational purposes only.

Pros of the RadioMaster Pocket:

• Extremely portable — great for traveling or “on the go” whooping

• Lightweight and comfortable for small hands or quick sessions

• Can be upgraded with Nano AG01 gimbals for smoother stick feel

  • Keep in mind: Nano AG01 gimbals have shorter stick travel compared to full-size AG01 gimbals. I had to add extra expo to compensate for the shorter throw.

If possible, skip the Pocket and go straight to the TX15 or Boxer Max.
I started with the Pocket, put 70+ hours in the sim, and wanted more precision. The TX16 was an option but felt big; the Boxer was “just right” with the perfect number of switches for FPV.

Why I chose the Boxer Max:

• Pre-installed AG01 CNC gimbals – smooth, precise, adjustable

• CNC aluminum faceplate – tough and great-looking

• Upgraded switches – longer life and better feel

• Folding antenna – more portable, less damage risk

Step 2: Get in the Simulator

Before buying a drone, get comfortable in a simulator.

My pick: VelociDrone with the Micro Drones add-on (for sub-250g drones).

Why VelociDrone?

• Realistic flight physics

• Tons of community-made tracks

• Deep customization options

Pro tip:
10–20 hours of sim time is enough for most people to be ready to fly their first whoop confidently.

Step 3: Goggles

If you buy only analog goggles now and go digital later, you’ll be buying twice. Start with something that covers all systems.

Options:

• HDZero Box Pro Plus – Affordable entry into HDZero with built-in analog support.

• HDZero Goggles 1 – Can sometimes be found used for $200–$300 with an analog module included.

• HDZero Goggles 2 – Latest model, built-in analog support.

Why HDZero goggles?

• Supports Analog, HDZero, and Walksnail (with the Walksnail VRX module)

• No extra gear needed for analog or HDZero

• Add the Walksnail VRX later for Walksnail

• One of the few goggles supporting Walksnail’s high frame rate mode

Step 4: Your First Whoop

⚠️ Backup first: Before you do anything, back up everything.

• Radio: Copy your SD card contents to your computer.

• Whoop: Connect to Betaflight and save your configuration.

📌 Also: Before you fly, check out my upcoming guide — “You Got All Your Gear — What to Do Next” — for step-by-step tips on safe setup in Betaflight, when not to upgrade, and how to avoid breaking features when restoring backups.

I personally like 75mm and 80mm whoops — a great balance between performance and flight time.
I’d only suggest 65mm HDZero whoops if you know you want to focus on racing only.

Good starter picks:

• BetaFPV Air75 (Analog) – Cheaper entry into FPV, great for learning if you’re okay starting with analog video.

• Mobula7 HDZero – Digital option with better image quality, but higher upfront cost.

Batteries: Lava 450mAh HV or Tattu 450mAh
Charger: VIFLY WhoopStor

Step 5: Start Flying (and Crashing)

Once you get your whoop:

• Fly 6 packs a day

• Start indoors; if outside, stick to an open field

• Keep flights close — whoops can disappear in grass fast

• Use a buzzer, but know wind can make them hard to hear

• Expect to break things — I killed my VTX on day two doing a flip over a slide

Step 6: Balanced Practice

In sims and real life, practice both left and right turns.
When I first flew in real life, my right turns were weak because most LiftOff Micro Drones tracks favored left turns.

Beginner FPV Cost Breakdown

📌 Note: You can absolutely find more budget-friendly options, but the items I’ve selected here are what I would personally get if I had to start all over again. The pricing is meant to give you a general idea of what to expect. This is also why I dedicated 60+ hours of sim time before buying anything else — I wanted to be sure I was committed before spending on quality gear.

💲 Pricing from: Pyrodrone, HDZero, NewBeeDrone, WeBleedFPV

⚠ Note: Tariffs increase prices on some items, and shipping is not included in the totals.

Budget Ranges

💲 Pricing from: Pyrodrone, HDZero, NewBeeDrone, WeBleedFPV
⚠ Note: Tariffs increase prices on some items, and shipping is not included in the totals.

Where to Buy

Trusted FPV stores:

• Pyrodrone

• GetFPV

• TinyWhoop

• NewBeeDrone

• WeBleedFPV

• Amazon (for chargers, LiPo bags, tools)

Final Tips

• More stick time = faster progress

• Skill matters more than gear — don’t rush upgrades

• Expect repairs, it’s part of FPV

• Start safe, then explore bigger builds

💡 Coming Soon Guides:

• You Got All Your Gear — What to Do Next

  • Covers first steps in Betaflight setup

  • Don’t update ExpressLRS or Betaflight right away — fly it stock first

  • Why backups matter and how to make them

  • Restoring backups between Betaflight versions may break some CLI commands

  • When to upgrade Betaflight (e.g., Mobula 7 AIO shipped with older BF version that didn’t support OSD)

• Installing USB serial drivers on Windows 11 so Betaflight can connect

• Getting started with Betaflight

• Charging guide for the VIFLY WhoopStor

• VelociDrone setup tips

• How to set up your first whoop

• Binding your radio to your drone

☕ Support My Work

%%[buymeacoffee]

I started FPV in early 2025 with a Meteor75 Pro O4 and jumped straight into DJI. I’d logged 60 hours in the Liftoff Micro sim before buying anything, so I felt ready… until real life reminded me that sims don’t bend canopies.

On Feb 28, 2025 I ordered my Meteor75 Pro O4. First day out? Pure joy—until pack #3 when I front-flipped over a playground slide and smacked a table. Bent the O4 board. Humbling. Helpful. Here’s what I wish I knew before that first park session.

1) Sim time helps—real life still hits harder

The sim gave me muscle memory and confidence, but depth perception, wind, and nerves are different outside.

What I do now

• Warm up low and slow for one pack (figure-eights, lines, gentle flips).

• Practice spotting and bailing: if a move feels wrong, disarm early.

• Treat “first pack of the day” like a cold start—no hero moves.

Pro tip: If you’re trying a new trick, give yourself altitude and space. Record DVR; it’s priceless for reviewing mistakes.

2) Budget for the hobby you actually want

I expected to buy a quad and some batteries. Reality: chargers, tools, spare parts, better props, more batteries, and a few fixes. Worth it—FPV is a tinkerer’s playground and absolutely scratched my “build/solve” brain from growing up with computers.

Starter charging gear I recommend

• 1S & 2S: A Vifly WhoopStor or Vifly Whoop Series charger — super easy, balance charges each pack individually, and keeps things safe for tiny whoops and micro quads.

• 3S–6S: A Hota D6 Pro — dual-channel, balance charger, AC/DC capable, and solid build quality.

• Portable field charging: Hota T6 — lightweight, DC-powered, perfect for topping up packs at the field from a larger LiPo or battery station. Also works as a battery tester — just plug in your main lead, and it will display the pack’s current voltage on screen.

Safety notes:

• Always charge in a LiPo safe bag or fireproof case.

• Charge at 1C unless you’re in a hurry and know your packs can handle it.

• Never leave batteries unattended while charging.

• I don’t recommend parallel charging for beginners — if it’s done wrong, it can be dangerous. Stick to chargers that balance each pack individually.

Pro tip: Buy two of anything that grounds you (like a canopy or camera mount). Waiting for a $5 part is the worst.

3) Flying with others: etiquette matters (and DJI can interfere)

My first group session was awesome—new friends, tons of learning. But with DJI in a whoop environment, I caused interference and sat out a lot to be respectful. We took turns and still had a great time, but I learned fast:

Group-flying basics

• Ask before you plug in. Confirm channel/power and race mode.

• If analog/HDZero pilots are present, let them lead channel planning.

• Keep output power low unless the group decides otherwise.

• Always bring a secondary whoop just in case something fails mid-event. At one of my first meets, a motor died halfway through — luckily, I had another whoop in my bag and was able to keep flying instead of sitting out the rest of the day.

4) Rates are personal—pick a baseline, then iterate

I started with Oscar Liang-style faster rates and stuck with them. They made my whoop feel snappy and precise, and forced my reactions to speed up. I swapped to those rates a few weeks in—once I could cruise the house—and never looked back.

How I tune rates now

• Lock a camera tilt and stick with it for a few sessions.

• Pick one change at a time (e.g., increase roll super rate slightly).

• Fly the same track/line for A/B comparison.

• Save profiles for “tight whoop” vs “open park.”

Pro tip: If your moves feel “twitchy,” reduce super rate first; if they feel sluggish, raise rc_rate a touch before messing with expo.

5) Confidence is good—humility keeps you flying

That first crash taught me to respect physics, momentum, and my own adrenaline. The rush is real—like riding a motorcycle—but the best flights come from calm inputs and solid habits.

My day-one checklist (whoop edition)

• Props off for bench tests

• Smoke stopper on first plug-in after any change

• OSD voltage and link quality confirmed

• VTX power/channel set, DVR recording

• Arming test (no yaw drift, correct motor direction)

• First pack: warmup lines and altitude discipline

Bonus Lessons Learned Over Time

These are things I picked up through experience and from reading posts on Reddit — small details that can save you money, time, and frustration.

1. Whoop motor shaft sizes matter
Whoop motors usually have either 1mm or 1.5mm shafts. Props won’t always slide on easily.

• If the prop hole is too tight, carefully drill it out before mounting.

• Forcing it can bend the shaft, make the shaft slip from the bell, or damage the prop.

2. XT30 charging tip
If you charge batteries with XT30 connectors, get a quality adapter.
I recommend: NewBeeDrone XT60 Female to XT30 Male adapter (2Pack) 16AWG 10CM — the extra length gives you space to connect without strain, and the 16AWG wire is flexible enough to position easily.

3. Keep balance plug protectors
Some batteries ship with a JST-XH AB Clip Buckle LiPo Balance Plug Protector. Don’t toss them! They help you unplug the balance lead without yanking the wires.

4. Buzzers save quads
Once, I clipped a tree branch and thought the quad was right there… it was 20 feet away. A self-powered buzzer could have saved me 20 minutes of searching.

5. Soldering discipline
Take your time, use flux, and check every connection with a multimeter.
One wrong pad can fry hardware — I’ve killed 3 flight controllers and 1 VTX by rushing. Each mistake hurts, but it’s part of the learning curve.

6. Respect people and property
If someone is nearby (like walking a dog), land until they pass. FPV is more fun when we share the space respectfully.

7. Buy as you go
It’s easy to stockpile parts you never use. Buy what you need when you need it. At minimum, keep one spare drone ready so you can keep flying if something breaks.

Why I’m hooked

FPV feels like flying—exploring like a bird with a toolkit in your backpack. It’s technical and creative at the same time. Meeting pilots in person, watching skilled flyers at a whoop race, and realizing how much there is to learn… that made me want to fly more and help the community grow.

What’s next on LevelUpFPV

• Beginner-proof whoop setup checklist (printable)

• My exact rates + why they work for me

• Bay Area micro-class flight spots (safe times and tips)

💬 Your turn: What do you wish you knew before your first pack? Drop it in the comments—I’m collecting tips for that printable checklist.

☕ Support My Work

How It All Started

Like many pilots, I stumbled into FPV after watching a few too many drone videos online.
The mix of speed, skill, and pure freedom was impossible to resist.

I started small, learned the basics, and (of course) spent a lot of time turtle-mode’ing out of grass or zip-tying arms back together.

My Current Fleet

Right now, I’m flying a mix of whoops, cinewhoops, and sub-3” freestyle quads.
Each one has its own personality and purpose:

Indoor Whoops

• Meteor75 Pro O4 – My go-to for tight indoor tracks and tiny whoop races.

• Mobula7 O4 – Light, nimble, and perfect for 2S fun.

Cinewhoop / Pusher

• Pavo20 Pro O4 – For smooth, cinematic footage and close-proximity flying.

Sub 3” Freestyle

• Ikon 2.5 Pro – My lightweight freestyle ripper for parks and tight gaps.

• Vision40 – A versatile little powerhouse I’ve tuned across multiple Betaflight versions.

The current squad ready for takeoff.

Why “LevelUpFPV”?

Because FPV is all about progression.
You don’t wake up one day doing perfect power loops or nailing split-S moves.
You start small, crash a lot, tweak your tune, swap props, and… slowly but surely, you level up.

This blog is about documenting that process — so you can learn from my wins (and my mistakes) without having to burn through quite as many props.

What You’ll Find Here

• Build Logs & Guides – Parts lists, wiring tips, and setup notes.

• Tuning Experiments – PIDs, rates, filters, and how they feel in the air.

• Flight Spot Reviews – Safe, fun places to fly (starting with the Bay Area).

• Event Recaps – Tiny Whoop races, meetups, and FPV gatherings.

• Gear Reviews – Honest takes on props, batteries, chargers, goggles, and radios.

• Lessons Learned – From pre-flight checklists to crash recovery hacks.

Let’s Fly Together

FPV is more fun when it’s shared.
I’ll be posting regularly, so drop a comment, share your own builds, or just say hi.

You can also catch future flight footage and build videos on my upcoming YouTube channel — same name, LevelUpFPV.

Here’s to smooth flights, soft landings, and always leveling up. 🚁

💬 Your turn:
Have you just started FPV too? Tell me about your first quad or your favorite flying spot in the comments — I’d love to hear your story.

☕ Support My Work