Skip to content
View in the app

A better way to browse. Learn more.

The Drone Talk Hub - The Ultimate Drone Community Hub

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
  • Entries

    2
  • Comments

    0
  • Views

    342

About this blog

Personal drone flying experiences, equipment reviews, aerial photography projects, safety notes, and drone-related adventures.

Entries in this blog

If you've ever stared at the Betaflight PID tab and felt your eyes glaze over, this is for you. I'm not a tuning wizard. I just fly a lot, I crash a lot, and I've learned which knobs matter and which ones are mostly placebo.

Before you touch a single slider

This is the part everybody skips, and it's the reason most "bad tunes" aren't actually tune problems. Before I open the PID tab, I check the hardware:

  • Props: Look at every blade under a bright light. Tiny nicks and bent tips cause vibration that no slider will fix. I swap props way earlier than I used to.
  • Motor bells: Spin each motor by hand. Gritty or notchy means a bent shaft or dirt inside. A bent bell will haunt your gyro data.
  • Frame: Cracked arms or a loose stack cause weird oscillations that look like PID problems.
  • Soft mounting: If your flight controller is rubber-mounted, make sure the grommets aren't squashed or missing. Check that XT60 leads and motor wires aren't tugging on the board.
  • Battery strap: A loose pack shifts mid-flight and makes the quad feel unpredictable.

I once spent an entire evening tweaking D gain on a quad that turned out to have one slightly bent prop. Replaced the prop, and it flew great on the stock-ish tune. I try not to think about that evening.

Start with a blackbox log

I used to tune purely by feel. Now I always record a blackbox log first, even if it's just a short pack of hovering, a few punch-outs, and some snap rolls. If your flight controller has onboard flash, you're set. If it only has an SD card slot, make sure the card is formatted and fast enough.

Two things I check in the log viewer:

  • Motor outputs: If one motor is consistently working harder than the others, something is off mechanically or the center of gravity is weird.
  • Gyro noise: A clean gyro trace means your filters can stay light. A noisy one means you're going to be fighting hot motors and sluggish response.

I don't try to read every graph. I just look for obvious problems. If the noise is huge before I've touched anything, I go back to hardware before I do anything else.

Filters first, then PIDs

It took me embarrassingly long to understand this. Your PIDs can only be as good as the signal feeding them. If the gyro data is full of motor noise, the D term amplifies it and your motors heat up. So the order I follow is:

  1. Fix mechanical noise.
  2. Check that RPM filtering is enabled (if you have bidirectional DShot and a compatible ESC firmware, this is a game changer).
  3. Adjust filter sliders only if needed.
  4. Then tune PIDs.

If you're running bidirectional DShot with RPM filtering, you can usually run much lighter filtering than the old days. My builds feel noticeably more locked-in since I got that set up properly. If you haven't done it yet, it's worth the hour it takes to flash your ESCs and verify motor pole counts in the config.

The slider approach that actually works for me

Betaflight's tuning sliders get a lot of eye-rolling from folks who like manual numbers, but honestly they're a great starting point. Here's my routine:

Step one: Master slider. I start at default and fly a pack. Does it feel soft? Bump the master multiplier up a little. Do I see bounce-back after flips or hot motors? Bring it down. Small changes only, maybe 0.1 at a time.

Step two: Gyro filter slider. If motors are warm after a pack, I nudge it toward more filtering. If the quad feels laggy and mushy, I go the other way. After adding RPM filtering, I usually move this slider up a good amount.

Step three: D gain. This is the one that controls damping. Too low and you get propwash wobble and bounce-back after quick stops. Too high and the motors get hot and the quad feels twitchy. I raise it slowly and always do a motor temperature check after landing. If I can't comfortably hold a motor for a few seconds, I've gone too far.

Step four: P to I balance. If the quad drifts in long sweeping turns or feels like it doesn't hold its angle, I raise I. If it feels stiff or oscillates a bit on stops, I back off.

What bad tuning actually feels like

When I was new, I couldn't tell the difference between symptoms. Here's the cheat sheet I wish I'd had:

  • Bounce-back after flips: Not enough D, or too much P. Try more damping first.
  • Propwash wobble on descents: Usually D and filtering. Also check props, because worn ones make this much worse.
  • Hot motors, clean landing: Too much D or too little filtering. Back it off.
  • Slow, mushy feel: Over-filtered, or P too low.
  • High-frequency buzzing sound: Almost always D is too high or there's mechanical noise.
  • Slow wobble while hovering: Often an I or P issue, or a loose component.

Change one thing at a time

This sounds obvious, but when you're at the field and the light is fading, it's tempting to change three things and hope. Don't. I keep a small note on my phone with the date, the quad name, what I changed, and how it felt. When something improves, I know why. When it gets worse, I can undo it.

I also save a Betaflight diff before every tuning session. If I mess something up, I can paste the old version back in and pretend nothing happened.

Test flights that give useful info

Random freestyle is fun but it's not great for tuning. I fly a short, repeatable set of moves:

  • A slow hover for 10 seconds to check for wobble.
  • A few punch-outs straight up and forward.
  • Hard stops from speed.
  • A couple of flips and rolls.
  • One low, fast descent to check for propwash.

Then I land, feel the motors, and look at the log. It takes maybe three minutes per pack, and it's way more useful than a vague "that felt okay."

Don't chase perfection

My biggest lesson is that a tune that's 90 percent there and flies consistently beats a razor-sharp tune you never finish. Plenty of pilots spend months tweaking and never actually fly. I'd rather have a reliable quad that makes me smile for a full battery than one that's theoretically perfect.

If you're just starting out, try this: fix the hardware, enable RPM filtering if you can, use the default sliders, and fly a few packs. If something feels clearly off, change one setting and test again. That alone will get you most of the way there.

Next time I'll walk through how I check motor temps and set up a proper post-flight routine so you catch problems before they cost you a crash. In the meantime, if you've got a tuning trick that saved you hours, drop it in the comments. I'm always looking for ways to waste fewer evenings.

But a few weeks ago my buddy let me borrow his DJI Air 3 for a weekend while he was out of town. He just needed someone to make sure it didn't die sitting in a closet, basically. I said sure, figured I'd mess around with it a little. What ended up happening is I spent most of Saturday just flying it around my neighborhood and then drove out to a trail I know on Sunday and put it through some actual paces. And yeah. I get it now. I finally get what people are talking about.

Coming From FPV, This Felt Almost Weird

First thing I noticed is how calm the whole experience is. Like, I'm used to the drone doing exactly what I tell it to do, instantly, no hesitation, no second-guessing. If I nose it into a tree that's on me. The Air 3 though, it's almost like it has opinions. You push it toward something and it just... slows down. Stops. Holds there. The first time it happened I genuinely thought something was wrong with the signal.

The obstacle avoidance on that thing uses APAS 5.0, which is DJI's omnidirectional sensing system. There are sensors on the front, back, sides, top, and bottom. It's using a mix of wide-angle vision sensors and infrared for the bottom. The system is constantly building a map of what's around it and adjusting flight paths in real time. When I flew it through a section of trail with overhanging branches, it threaded through stuff I honestly wasn't confident about. Not perfectly, it did stop once and just hover rather than commit to a path, but still. For a drone that's not being piloted by someone with years of stick time, that's genuinely impressive.

The Transmission Side of Things Is Wild Too

I also spent some time thinking about the O3+ transmission system while I had it. My FPV quads run either analog video or DJI's older digital FPV system, so I have some frame of reference here. The range and signal stability on the Air 3 compared to what I'm used to is on another level. O3+ is doing a ton of work behind the scenes - it's constantly switching between frequencies, adjusting transmission power, basically doing everything it can to maintain a clean link even in congested RF environments.

I flew it about a mile out over an open field just to see what would happen with signal quality. The feed stayed completely clean the entire time. No breakup, no latency spikes. For FPV I'm usually getting some kind of interference or noise by that range depending on where I am. Different use cases obviously, but it made me appreciate how much engineering goes into consumer drones that we kind of just take for granted.

The Battery Situation Is Actually Reasonable Now

One thing I've always kind of rolled my eyes at with consumer drones is the battery specs feeling inflated. Like when a manufacturer says 40 minutes flight time and you get 22 in real world conditions. The Air 3 was getting me pretty consistent 28 to 32 minute flights with active flying, not just hovering. The Intelligent Flight Battery system is smart about discharge and it gives you actual time remaining estimates that feel trustworthy rather than wildly optimistic.

Compare that to my 5-inch freestyle build which runs 4S 1500mAh packs and gets me maybe 4 to 5 minutes of aggressive flying. Totally different world. I understand why consumer drones optimize for efficiency over performance at this point. The battery tech on the higher end consumer stuff has genuinely caught up to where the marketing claims are at least somewhat believable now.

The AI Subject Tracking Stuff Genuinely Surprised Me

I saved this for its own section because it deserves it. I had my dog with me at the trail on Sunday and on a whim I used the subject tracking to lock onto him while he was running around off leash. The drone followed him through some pretty chaotic movement, kept him in frame, adjusted altitude when he went up a small embankment, and didn't lose the lock for a solid three minutes of continuous tracking. I was just standing there holding the controller doing nothing.

The way these tracking algorithms work now is they're not just doing color blob tracking like the early days. The system is doing real-time subject recognition, estimating where the subject is likely to move based on trajectory, and combining that with the obstacle avoidance so it's not flying itself into stuff while following. It's a lot of processing happening on the drone itself, not just offloaded to the controller or an app. The onboard chips have gotten fast enough to handle it.

I'll be honest, as someone who flies FPV it made me feel a little bit like, okay what am I even contributing here. But then I took it back home and strapped on my goggles and flew my quad through a gap the size of a lunch box and felt better about myself. Different tools, different purpose.

Where I Think This Is All Going

This is the part where I'm just kind of thinking out loud because I genuinely don't know. But it seems obvious that the AI and automation side of drone tech is moving faster than the hardware side at this point. The motors and props and frame materials are pretty mature. But the software, the sensors, the onboard processing - that stuff is changing fast.

I've been reading about stuff like neural-network-based depth estimation replacing traditional stereo vision sensors, which could mean better obstacle avoidance in low light or in situations where texture-based sensing falls apart. And there's a lot of work being done on swarm coordination for commercial applications, which is interesting even if it's not relevant to what I do.

For FPV racing specifically I'm curious whether any of this trickles down. There are already some racing drones experimenting with GPS-based return-to-home as a safety net and some are messing with auto-arm sequences. Nothing like what the consumer drones are doing, but the technology exists and it's getting cheaper.

Anyway. This was a longer post than I planned. If you're an FPV pilot who's never touched a consumer drone I'd say borrow one for a weekend if you get the chance. It's a genuinely different experience and it gave me a lot to think about in terms of where the technology is heading. I'll probably write something more specific about FPV transmission systems next since that's more in my wheelhouse. Thanks for reading if you made it this far.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.