Remove props before ESC programming!
ESC programming generally requires battery power to be provided to the ESCs, and for unusual signals to be sent down the control line to the ESC. Motors can accidentally begin spinning. Ensure that ALL PROPS are removed from the vehicle prior to ESC programming and that wires and fingertips will not become entangled in motors if they begin to spin.
dRonin now supports programming ESCs using 4WIF-style passthrough. The “MSP” module emulates the MultiWii/Cleanflight/Betaflight configuration interface. BLHeli, BLHeli_S , BLHeli32, and SimonK ESCs can be reprogrammed.
First, it’s important to configure the USB virtual com port (USB VCP) to speak the MSP protocol. On the hardware configuration page, select that port as “MSP” and turn off any other MSP ports (e.g. those used for on-screen displays). Restart the flight controller.
Battery power and ESC programming
Battery power must be provided for ESC programming. On some ESCs, it is necessary to apply the battery power after connecting BLHeliConfigurator/BLHeliSuite.
Next, you may configure and program the ESCs. Remove any props, connect the flight controller with USB, and apply battery power.
With BLHeliConfigurator (recommended)
BLHeliConfigurator is a Chrome application that can be found here.
BLHeliConfigurator only works with MSP-style passthrough, so setup is easy. In BLHeliConfigurator, all that is necessary is to select the correct serial port at the upper right of the screen, click “Connect”, and then “Read ESCs” at the bottom of the screen.
- Download and run BLHeliSuite,
- on BLHeliSuite only (not 32): click the menu “Select Atmel/SiLabs Interface” and select “SILABS BLHeli Bootloader (CleanFlight)”,
- choose the proper serial port connected to the flight controller at the bottom of the window, and then click “Connect”,
- click “Read Setup”,
- configure the ESCs normally.
BLHeliSuite works under WINE on Linux systems.
- Configure MSP on the USB VCP in dRonin GCS (“Hardware” tab), reboot the controller,
- note down the tty device corresponding to your VCP (see the devices combobox in the bottom right corner if GCS if unsure),
ls -l ~/.wine/dosdevicesto find which COM device your VCP tty is mapped to in WINE (older versions of WINE don’t map devices automatically, in that case you will need to seek help from Google),
- launch BLHeliSuite(32).exe, should be able to double click it in Nautilus on a recent GNOME DE
- choose the correct COM port, and click “read setup”
- proceed to configure ESCs
Restore MSP configuration
After completing programming, the port configuration can be restored to save resources (and to re-enable MSP peripherals like OSDs).