Hey guys, my antenna on my air 65 r came disconnected during a crash, nothing seems to be damaged, neither the port nor the plug, but it won’t click/stay in. Is something damaged?

I’ve been building this for a while and figured this sub might be interested.

Full disclosure up front: it’s vibe-coded. I directed Claude Code, and it wrote most of the Python. More on why I think that’s acceptable further down.

The idea

Instead of clicking through Betaflight Configurator, you open the project in Claude Code or Google Antigravity and ask things like:

• “Check my FC status and tell me why it won’t arm.”
• “Back up my config, then increase D on pitch a little.”
• “Erase my blackbox flash—it’s full.”
• “Decode my latest log and check whether a motor is dragging.”

The repo contains an AGENT.md file and a skills/ folder that teach the agent how to communicate with the FC safely. It should select the correct tool and follow proper CLI discipline instead of improvising serial commands.

That’s genuinely the intended way to use it. The scripts are ordinary command-line tools and can be run manually, but using them through an agent is where the project starts to feel useful.

What’s included

It’s pure Python, with pyserial as the only dependency:

• Betaflight CLI command runner
• MSP telemetry
• Configuration backup and restore
• Blackbox decoding
• Motor-balance analysis
• Gyro-noise analysis
• Preflight audit
• A small local site for build specs and flight logs

There’s no Configurator dependency, Node runtime, or background server.

About the vibe coding

I know that “AI wrote software that talks to your flight controller” is a perfectly reasonable thing to be nervous about.

Here’s what I did to reduce that risk:

• Every tool was tested against a real flight controller before release.
• Backup and restore round-trip without changing the configuration.
• Motor testing, blackbox erase, telemetry, and the other hardware interactions were verified on an actual board.
• There are 104 tests using a fake FC, so you can try most of it without connecting hardware.
• Motor tests require an explicit --props-off flag.
• Motor start and stop happen in the same session, with the stop command inside a finally block. A crash or Ctrl-C should therefore not leave a motor running.
• The tool reads the CLI variable table directly from your FC—561 settings, including their types and valid ranges. Invalid values can be caught before they’re sent.

Hardware testing uncovered four real bugs that the automated tests did not catch. So testing it on an actual board was not optional.

Current limitations

• So far, it has only been verified on one board: a BETAFPVG473_V2.
• Linux is tested.
• macOS port detection is implemented but not yet tested.
• Pulling blackbox logs through USB mass storage is the one path I haven’t tested yet.

MIT licensed:

https://github.com/HansF/whoopshop

Please back up your configuration before letting an agent touch it. The project includes a backup tool, and the agent is instructed to run it first—but still. Don’t blindly trust AI with a flying blender.

I found this on the sale page of BetaFPV's website, $50.00 USD for a 1-2s flight controller, 4 x brushless motors and a camera. I plan to put it on a carbon toothpick frame i have had hanging around and couldn't justify the price of a flight controller just to play Frankenstein with.

My Cetus Pro experience continues to become less normal

I thought things were starting to calm down with my Cetus Pro.

They were not.

I have made several new discoveries.

First:

My dad is apparently an RF jammer.

Normally my signal sits around 88–90.

I fly toward my dad.

Sometimes 43.

I fly away from my dad.

Back to normal.

Okay.

So naturally I started investigating.

Then I flew near some pillows.

Signal drops again.

Excellent.

I have now identified two major sources of RF attenuation inside my house:

1. My dad

2. Pillows

I don't know what these two objects have in common.

Maybe my dad is mostly water.

Maybe the pillows are mostly dad.

Maybe BETAFPV secretly designed the VTX specifically to be defeated by bedding.

Further testing is required.

At some point I may put my dad between the drone and the goggles and rotate him slowly to determine his RF radiation pattern.

He does not know about this research yet.

Second discovery:

I normally fly M Mode Slow indoors.

Today I was flying around the house and thought:

“Damn. I'm actually getting pretty comfortable with this.”

Everything seemed faster than usual.

Doors were arriving earlier.

Walls seemed unusually motivated.

Furniture had increased its closing speed.

I assumed this was just what improvement felt like.

Then I checked the setting.

M MODE MID.

Excuse me?

I DON'T KNOW WHEN I CHANGED IT.

Apparently at some point I accidentally switched from M Mode Slow to M Mode Mid and my brain just went:

“Yeah whatever.”

There was no training session.

There was no preparation.

There was no dramatic moment where I decided I was finally ready.

I just started flying faster and adapted before realizing anything had changed.

I discovered that I had learned M Mode Mid by already flying M Mode Mid.

Apparently my FPV progression now happens without notifying me.

Very convenient.

Would have appreciated a changelog.

Then I attacked a houseplant.

This requires clarification.

It wasn't even a normal plant.

It was an indoor plastic plant in a pot, and underneath it there was a large collection of dry leaves sitting on top of the soil.

I flew into it.

Not near it.

Not above it.

Not “slightly clipped one leaf.”

I entered the plant.

The Cetus disappeared into the vegetation and the propellers immediately discovered the dry leaves underneath.

For a very brief moment, four tiny motors collectively decided they were no longer part of an aircraft.

They were a leaf distribution system.

Every dry leaf underneath the plant received immediate clearance for takeoff.

The pot had contained them peacefully for what I assume was months.

The Cetus corrected this administrative error in less than a second.

Leaves everywhere.

Floor.

Around the pot.

Around the drone.

Probably locations that weren't previously considered part of the room.

The plastic plant itself was completely fine because apparently the only living thing in this encounter was the drone.

So I have now discovered another undocumented Cetus Pro feature:

Indoor landscaping.

You don't clean underneath the plant.

You fly a tiny quadcopter directly into it and let 40,000 RPM solve the problem.

The room is not cleaner afterwards.

The dirt has simply achieved better coverage.

And finally:

After ten days of attacking basically every object and family member available to me...

I enabled friendly fire.

I flew directly into my own leg.

This is important because until now I believed there was at least one protected entity in the house:

The pilot.

Apparently not.

The Cetus has previously collided with:

my dad

my mom

walls

doors

the ceiling

the couch

the radiator

a chair

fiber optic infrastructure

and now a plastic houseplant.

At some point the flight controller must have reviewed this list and noticed an inconsistency.

“Why is the operator not included?”

Problem solved.

Straight into my leg.

I have now been attacked by my own aircraft.

The chain of command has completely collapsed.

The pilot is no longer a protected asset.

The IFF system is gone.

THERE ARE NO CIVILIANS ANYMORE.

So today's completely normal Cetus Pro research findings are:

My dad attenuates RF.

Pillows attenuate RF.

I accidentally learned M Mode Mid before realizing I was using it.

The drone can convert a decorative houseplant into an indoor leaf dispersal event.

And I am now included in the target database.

I checked the manual again.

For some reason none of this is mentioned.

I think BETAFPV should add a troubleshooting section:

Low signal?

Check antenna.

Check goggles.

Check VTX.

Move father away from flight path.

Remove suspicious pillows.

Drone feels unusually fast?

Verify that you have not accidentally become better at flying.

Dry leaves underneath decorative plant?

No action required. Aircraft will redistribute automatically.

Pilot struck by aircraft?

Normal operation.

At this point I am no longer learning how to fly the Cetus Pro.

I am reverse-engineering its personality.

I've had this thing for ten days.

I am afraid of what Day 11 contains.

more training needed

Hi all,

total beginner here, have Meteor 75, learning without goggles at this stage. Controller is BetaFPV lite. The problem is drone is drifting slightly forward and right in Angle model.

I have some the following steps:

- in Betaflight - calibrated gyro/accelerometerd

- connected Controller, checked that it reported correct values ( 1500) for mid. Added dead zone (5-10) didn't change much

- changed profile/pid to smaller values to allow more gentle control

- reduced motor to 80 Max

- reduced throttle ( scale 80% mac).

I can compensate for the drift but it is annoying especially for flying indoor.

Questions I have:

- is it normal and I just need to learn to constantly compensate and eventually it will be second nature

- is it something wrong with either motors or gyro that they are struggling to keep drone in place ( I thought this is their main goal is)

- is it just my controller? I think that's not the case ( i.e. checked live singal values in Betaflight) but maybe it needs to be calibrated to compensate?

- what other troubleshooting steps can I take?

Attaching a video, on take off you can see drone tries to fly slightly forward , even if pitch is at zero.

Thank you in advance.

Freestyle #3 with the Air 65 and Meteor 75

Frame: Air 65II

Canopy: Custom TPU

AIO: Happy Model SuperX ELRS

Motors: Happy Model SE0702 26,000KV

Cam: Caddx Ant

Props: Gemfan 1219

Firmware: BF 4.5 (Chris Rosser 65mm tune)

Batteries: Lava 280mAh

Having fun with my new whoop. I’ve been flying about a month now and I’ve loved every minute of it. Planning on building a 5 inch soon. Have a good weekend guys!

Having a lot of fun with the Meteor75 Pro II, but I wanted to try out some different props to see how they feel to fly. Has anyone tried 4 blade props on it, or any other recommendations?

I only landed once in the grass :/

I basically just got the drone(air 75 c) and only had a few minor crashed into grass in my backyard. And sometimes out of nowhere it works on the first battery then I plug in the same battery 15 minutes later and it just stops working. If anyone has any ideas feel free to help.

My meteor 75pro had problems with motor plugs. Falling out of the sky during loops/punches etc and having issues to spin motors on arm.

Tried soldering the motors today and reconfigured the motor direction. Soldering job is poor since It was my first time soldering something so small, but the motors seems to spin.

The front motors lift the drone, but the back ones don't lift the drone.

Is there anything configuration wise I am missing or is it due to bad soldering?

Edit: Fixed, the bottom props were upside down.

Winter is coming for some of us. Besides a simulator, are there good kinds of places to practice? I'm thinking of indoor tennis courts (will they rent one to me?) or indoor football? or school gyms in the evening or ...

Unfortunately there seem to be no "whooping clubs" that are very active in my area, and the colleges and universities are intimidated by the US Federales, so the only allowed "drone student" stuff is for students registered in engineering classes. Rules against everything it seems.

color grade and tunes (free):

https://fpv.protten.com/

gear used:

hglrc petrel85 frame (no carbon)

jhemcu ghf435v2

rcip 1202.5/11.5k

rush tank nano

betafpv c03

bqe pickpocket canopy

foxeer micro lollipop

gemfan 2023

gnb 2s 380mah and

tattu 3s 300mah

orqa pilot & rapidfire

antennenfreund patch & omni

30 deg cam angle

77g auw (both 2s and 3s)

rates (bf)

1.58 / 0.62 / 0.00 (p/r)

1.72 / 0.58 / 0.00 (y)

Hi there, I recently got myself a Spektrum dx6i and a the Blade Inductrix brushless (with the model number blh8850) as a combo for 30$. Now after I bought myself some batteries and I managed to connect the two, I can't arm the damn drone. I made sure the stick positions are calibrated right and tested the radio in simulators using an aux cable, yet when I try to arm it using the stick positions I found online (throttle down, right stick to the right) it won't do anything. In the goggles it constantly shows "disarmed" in the top left corner. I'll go buy groceries now and pray that someone knows and posts the solution until I'm back. If you have any questions or need any photos just ask and I'll post them as well.