You bought a stack with BLHeli_S ESCs because the price was right, then discovered Betaflight RPM filtering requires bidirectional DShot — and your ESCs don’t support it. The solution isn’t a new 4-in-1. Bluejay firmware unlocks bidirectional DShot, 48kHz variable PWM, and fully configurable startup power on BLHeli_S hardware you already own. The flash takes 5 minutes and the performance improvement is immediate.
Before You Flash: Confirm Compatibility
Not every BLHeli_S ESC can run Bluejay. Check these requirements before you connect:
Required hardware:
– BLHeli_S ESC (any bitbang target: A-H-20, G-H-30, L-H-20, etc.)
– EFM8BB21 bus type (99% of BLHeli_S ESCs use this — if yours is EFM8BB10, it’s too old and won’t work)
– A flight controller with Betaflight 4.2 or newer for the passthrough
Verify your current firmware in the BLHeliSuite32 or BLHeli Configurator. Note the ESC layout (which motor is which) and the current settings — you’ll need to restore PWM frequency and motor direction after flashing.
Step 1: Install ESC Configurator (Web Tool)
Bluejay uses the web-based ESC Configurator. Chrome or Edge required — Web Serial API isn’t available in Firefox or Safari. Open the site on a laptop, connect your flight controller via USB, plug in a LiPo, then click Connect.
If the Configurator doesn’t detect your ESCs, check:
– LiPo is plugged in (ESCs need battery power for the bootloader)
– Betaflight Configurator is closed (two apps can’t share the COM port)
– USB cable carries data, not just power
Step 2: Select Bluejay Firmware and Flash
Once connected, the Configurator reads each ESC’s layout and current BLHeli_S version. Click Flash All. Select:
– Firmware: Bluejay (latest stable, currently 0.21.x)
– PWM Frequency: 48kHz for most builds. 24kHz if you’re running 6S on 2207+ motors with aggressive props (lower switching frequency reduces FET heat). 96kHz is available but at the cost of ESC resolution — only use it on tiny whoops where silence matters more than precision.
– Minimum Startup Power: 1025 default. Raise to 1050-1075 if you hear startup screeching on high-KV motors. Lower to 1000 for 3-inch lightweight builds.
Click Flash. The process takes about 30 seconds per ESC. Do not unplug power mid-flash — you’ll brick the ESC and need a C2 programmer to recover it.
Step 3: Configure Bluejay Settings After Flash
Bluejay exposes parameters BLHeli_S hid from you:
- Startup Beep Volume: 80 (louder than the BLHeli_S default). Useful for locating a crashed quad in tall grass, but annoying at the bench. Set to 40 if you frequently power-cycle indoors.
- Brake On Stop: Enabled. This immediately stops the prop when you disarm, preventing the “windmilling” that snaps props on landing. Disable if you use turtle mode (brake fights the reverse rotation).
- Damped Light: Always on. No reason to disable it in 2026 — it’s what gives you the crisp throttle response.
- Motor Timing: Auto (default). Manual timing is useful only when chasing a specific desync at extreme KV ranges, and Bluejay’s auto-timing is better than BLHeli_S’s was.
Step 4: Enable Bidirectional DShot in Betaflight
With Bluejay flashed, bidirectional DShot is now available. Open Betaflight Configurator:
1. Configuration tab → ESC/Motor Features → set ESC/Motor Protocol to DSHOT300 or DSHOT600
2. Enable Bidirectional DShot (the toggle below the protocol dropdown)
3. Save and Reboot
Go to the Motors tab. With the LiPo plugged in, spin up motor 1 manually. In the main Betaflight window you should see RPM, error percentage, and temperature (if your ESC has a temperature sensor — most BLHeli_S don’t).
If you see “Error 100%” on all motors, bidirectional DShot isn’t getting through. Check: (a) Bluejay is actually flashed (open ESC Configurator, read settings — it should say Bluejay), (b) DShot protocol is selected (not Multishot or Proshot), (c) the flight controller supports bidirectional DShot on the MCU’s timer pins (F4 and F7 do; F3 and F411 sometimes don’t on all motor outputs — check your board’s timer map).
Bluejay Parameter Comparison Table
| Parameter | BLHeli_S Default | Bluejay Range | Recommended | Effect of Wrong Setting |
|---|---|---|---|---|
| PWM Frequency | 24kHz fixed | 24/48/96 kHz | 48kHz | 24kHz = louder, hotter; 96kHz = motor stutter on high load |
| Startup Power | 0.50 (fixed) | 1000-1100 | 1025 | Too low: motor won’t start, clogs firmware. Too high: screech, possible ESC damage |
| Motor Timing | Medium (fixed) | Auto, 1-31° | Auto | Manual timing mismatch causes desync at high RPM |
| Brake On Stop | Off | On/Off | On (off for turtle mode) | On + turtle mode = prop won’t reverse |
| Beep Volume | 0-255 (varies) | 0-255 | 80 | 255 = deafening; 0 = can’t find quad in grass |
Common Mistakes & How to Avoid Them
Mistake 1: Flashing without LiPo power. The ESC bootloader is powered from the battery rail, not USB 5V. If you connect the Configurator and see zero ESCs, plug in the LiPo. If you still see nothing, your ESC is likely EFM8BB10 (too old) or the signal ground between FC and ESC is broken.
Mistake 2: Leaving bidirectional DShot enabled with BLHeli_S firmware. Some BLHeli_S builds (16.7 and later) technically include a bidirectional DShot option, but it’s buggy — RPM data is noisy, error rates spike to 50%+, and Betaflight’s RPM filter will react to garbage data, making the quad fly worse. If you’re not on Bluejay, leave bidirectional DShot OFF.
Mistake 3: Running 48kHz with aggressive 6S setups. 48kHz switching is more efficient at partial throttle (quieter, cooler) but generates more FET heat at sustained full throttle because the higher switching frequency increases switching losses. On a 6S 2207 1900KV build with 5.1-inch props running full-throttle passes, drop to 24kHz. The motor won’t be quieter, but the ESC won’t thermal-shutdown mid-pass.
Mistake 4: Forgetting to recalibrate RPM filters after flashing. The RPM filter center frequencies shift slightly with Bluejay because the commutation timing changes. If you transferred your previous Betaflight tune, the dynamic notch will adapt — but the static RPM filter notches from your old BLHeli_S setup will be slightly off. Run a full-throttle punch with blackbox logging, check the FFT, and adjust if the motor noise peak moved by more than 50Hz.
Mistake 5: Flashing Bluejay without noting the motor layout and direction. The ESC Configurator flash erases the layout ordering on some targets. After flashing, verify motor positions and direction in Betaflight’s Motors tab. Reorder in the Configurator or remap resources if motors 1-4 don’t match the diagram.
⚠️ Regulatory Notice: The flight recommendations in this article should be followed in accordance with the latest 2026 drone regulations in your country or region. Always verify local laws regarding flight altitude, no-fly zones, remote ID requirements, and registration before flying. Regulations vary significantly between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities.
RPM filtering is the reason you’re flashing Bluejay in the first place — without it, Betaflight’s dynamic notch has to guess where your motor noise lives, and it’s usually wrong by enough to cause mid-throttle oscillations. The bidirectional DShot data gives Betaflight exact RPM for every motor on every loop iteration, which the dynamic notch then uses to place filter notches precisely on the motor frequency. As we covered in our Betaflight RPM filtering setup guide, enabling RPM filtering after flashing Bluejay reduces the gyro noise floor by 40-60% on most builds.
Bluejay’s 48kHz PWM mode changes how your motors behave at the low end of the throttle range. This has knock-on effects for your PID tune — the smoother low-RPM response means less I-term windup at idle, which changes how Anti-Gravity and I-Term Relax interact with your tune. We addressed this interaction in our Anti-Gravity and I-Term Relax guide.
If your BLHeli_S ESCs are on an older AIO board that’s seen better days, the Happymodel X12 5-in-1 AIO ships with Bluejay pre-flashed and handles 2S-4S on 12A per channel — enough for any 3-inch build and most lightweight 4-inch setups.