ESC configurator for BLHeli_S, Bluejay and AM32

Features

• Passthrough

  Uses the flight controller's 4-way interface, so no separate USB linker is needed.

• All ESCs at once

  Settings shared by every ESC are edited together, or pick one ESC to change only that one.

• Motor direction

  See which way each motor will spin and reverse it, with no wires swapped.

• Firmware flashing

  Flash a BLHeli_S, Bluejay or AM32 .hex to every ESC it was built for.

• Startup melodies

  Write Bluejay and AM32 startup tunes from RTTTL text, a tap-to-add keyboard or a piano roll with preview.

• Demo ESCs

  Simulated BLHeli_S, Bluejay and AM32 ESCs to read and tweak with nothing connected.

How ESC passthrough works

Your flight controller already has a wire to each ESC's signal pad. Betaflight and INAV can switch those pins into a serial passthrough, the 4-way interface, so a configurator can read and write the ESC settings. FlySpark does this for you when you open the ESC configurator, and lists each ESC with its firmware and version.

This is the same approach used by BLHeli Suite, BLHeliSuite32 and the esc-configurator.com web app. FlySpark adds it to the same tool you use for the flight controller, on a phone as well as in a browser.

Supported ESC firmware

BLHeli_S, Bluejay and AM32 can be read, changed and flashed. Bluejay adds bidirectional DShot for RPM filtering in Betaflight, which is why many pilots flash it onto BLHeli_S hardware.

BLHeli_32 is detected but not configured. Its settings and flashing protocol were never published, so FlySpark tells you what it found and points you to the right tool instead of guessing.

Safety first

Always take the propellers off. The ESCs need battery power to answer, so plug in a pack after connecting USB. If the ESCs do not respond, check that the flight controller is disarmed and that the battery is really connected. After changing direction, confirm it with the motor test on the Betaflight configurator page before flying.

How to configure ESCs through the flight controller

1. Remove propellers. Take every propeller off the drone.
2. Connect the flight controller. Open the ESC configurator in Chrome, Edge or the FlySpark app and connect the flight controller over USB or Bluetooth.
3. Plug in the battery. Power the ESCs with the flight battery so they can answer.
4. Read, edit and write. FlySpark enters passthrough and reads every ESC. Change the settings and write them back.

Frequently asked questions

Can I configure BLHeli_S ESCs from Android?

Yes. The FlySpark Android app reaches BLHeli_S, Bluejay and AM32 ESCs through the flight controller over USB OTG, Bluetooth or a Wi-Fi MSP bridge.

Does it support BLHeli_32?

No. BLHeli_32 ESCs are detected, but their protocol was never published, so they cannot be changed here.

Can I flash Bluejay?

Yes. Load a Bluejay .hex built for your ESC and FlySpark flashes it to every matching ESC through passthrough.

Why do my ESCs not show up?

The battery must be connected, the drone must be disarmed, and the flight controller must run Betaflight or INAV with passthrough support.

Do I need a separate USB linker?

No. The flight controller acts as the linker.

Related tools

• Betaflight Configurator in your browser and on your phone

  Set up Betaflight in your browser or on Android: ports, PIDs, rates, OSD, modes, presets and CLI over USB or Bluetooth. Free, with a no-hardware demo.

• INAV Configurator for the browser and your phone

  Configure INAV planes, wings and multirotors in your browser or on Android: mixer, navigation, waypoint missions, programming and OSD. Free demo inside.

• Blackbox explorer for Betaflight and INAV logs

  Open Betaflight and INAV blackbox logs (.BBL, .BFL, .TXT) in your browser: gyro and PID graphs, noise spectrum, GPS track, video sync, CSV and GPX export.

• Firmware flasher for Betaflight, INAV, ArduPilot and PX4

  Flash Betaflight, INAV, ArduPilot and PX4 firmware from your Android phone over USB OTG. DFU and bootloader support, with a settings backup first.

See every FlySpark tool