Blheli 32 Configurator Download

If you want the best performance out of your miniquad racer, we highly suggest you use BLHeli_S ESCs. This is because these ESCs have been developed solely with quadcopter performance in mind. They integrate with your flight controller software to provide some really neat functionality and, with the release of the BLHeli Configurator Chrome app, are exceptionally easy to flash and configure.

Blheli32 Download For Windows 10
Blhelisuite Download For Windows 10
Blheli_32 Configurator Download For Pc Windows 10 64-bit

This article provides step-by-step instructions on how to configure freshly-flashed BLHeli_S ESCs so that they all have the correct settings and so that your props are spinning in the correct direction. We’ve done this before on the archaic BLHeliSuite Windows program – this time we will walk you through using the fairly new BLHeli Configurator Chrome app. Like Betaflight Configurator, this is a beautiful, modern app which can be used on any operating system to flash and configure your ESCs. The new UI is far easier to use than the old BLHeliSuite that ran on Windows. Still, if you want to use that software – check out our old guide.

Preparation

Download the latest BLHeli32 Configurator here. Download the BLHeli32 User Manual here. 1x Lumenier Razor LED 55A 4in1 F3 BLHeli32 2-6s ESC; 1x 8pin micro JST-SH 7cm connector for 4in1 ESC to FC connection; 1x 2200uF 35V Capacitor4x M3 Anti-vibration gummies (extra) Note: Arm LEDs sold separately.
This is the first video of my BLHeli Suite playlist. I show you how to download and install it for the next upcoming videos. Download web page - https://blhe.

Before you jump into configuring your ESCs, you’ll want to get a few things in order. First of all, we recommend you remove the props from your quadcopter and plug it into your battery using a smokestopper. The reason is that the process of flashing and programming ESCs always risks a situation where the ESC gets into a corrupted state which can either cause your motor to spin up to full throttle or short out a motor winding and cause serious damage to your quad. Using a smokestopper prevents both of these things and removing your props is cheap insurance to protecting your fingers.

If you’ve just finished building your quad, we recommend you start out by flashing your flight controller with Betaflight. The steps in this guide will not work if your Flight Controller does not support the BLHeli passthrough provided by new versions of Betaflight and/or Cleanflight. This is outlined in the previous article in this series. Now lets get started!

There's no installer yet or auto-update features, so you'll have to retain archive contents for future use and download a new version when it comes out. Configurator is now built for all major platforms as a standalone app. Added a warning about missing BLHeli32 support.

Configuration

Configuration begins in the Betaflight Configurator Chrome app.
Connect to your quadcopter’s flight controller by picking the appropriate serial port and clicking connect. You can tell by unplugging and re-plugging your flight controller into your computer. The correct COM port will disappear and reappear.
Go to the “Motors” tab.
Click the checkbox in the bottom right that says “I understand the risks” (you did remove the props, right?).
Run up each motor using the slider in the bottom left of the Motors tab. Start with motor 1. Move the slider up to ~1100 and note the direction your motor is rotating. Notice the handy diagram in the middle of the motors tab. Is your motor 1 spinning the same direction as motor 1 in that diagram? If not, write down “Motor 1 Reversed” in a notepad.
Repeat step (5) for motors 2-4.
Close Betaflight Configurator. Two configurators cannot be connected to your quadcopter at the same time.
Plug your quadcopter’s flight controller into your computer using a micro USB cord.
Plug a flight battery into your quadcopter.
Launch BLHeli Configurator
Pick the correct serial port – it’s the same one you used in Betaflight Configurator.
Click “Connect”
Click “Read Setup”
The main configuration screen will load. This shows a nicely organized array of configuration options. The configuration options on the left are set for all 4 ESCs on your quadcopter. The options on the right are set for each individual ESC. The buttons at the bottom conveniently let you restore the default settings or flash all the ESCs:
The numbers in this diagram outline the configuration order shown below:
1. First up, we recommend you flash the latest version of BLHeli onto your ESCs. This is trivial in this new configurator. Simply click “Flash All” and select the latest version and “Flash”:
  You will be brought back to the main screen where each ESC will be updated, one at a time. If you found your own firmware, you can flash that using “Select File Manually”. We recommend most folks use the ESC Firmware provided directly from BLHeli configurator. Installation of the wrong ESC firmware can and will completely destroy your ESC. If you do flash your own firmware, only do it to a single ESC at a time!
2. Startup power configures how quickly your ESC responds to rapid throttle changes. It has been reported that lowering it can help fix motor problems on high-performance motors like the new EMax RS2206S series. We do not recommend you adjust this unless you have motor problems in flight, but if you do you should lower it to .25 or .125.
3. Motor timing adjusts how far advanced the ESC drives the magnetization of the field windings when compared to the magnetic fields of the permanent magnets. Again – we don’t recommend you change this on your first set-up unless you specifically know that it needs to be done. Almost all mini-quads run “medium” or “high” timing for maximum thrust.
4. If you are flying with a standard BLHeli ESC (e.g. not a BLHeli_S ESC), a final option will appear here to change “PWM Frequency/Damped”. This should always be set to “Damped Light” for multirotors. This option is automatically enabled in BLHeli_S ESCs and does not show up in the Configurator.
5. Here you will configure motor direction and PPM values for your 1st ESC.
  1. Motor Direction: In steps (1)-(6) above, you determined which motors, if any, were not spinning in the right direction. You can now fix this by changing the “Motor Direction” drop down from “Normal” to “Reversed” for those motors which were spinning the wrong way.
  2. PPM Values:If you are using DSHOT – and you absolutely should if you have BLHeli_S ESCs – ignore this field. If not, you should change the “PPM Min Throttle” to “1020” and “PPM Max Throttle” to “2000”. This will give your ESCs the maximum amount of resolution available for smooth flying.
6. Here you will configure motor direction and PPM values for your 2nd ESC. See (5) above for how to do this.
7. Here you will configure motor direction and PPM values for your 3rd ESC. See (5) above for how to do this.
8. Here you will configure motor direction and PPM values for your 4th ESC. See (5) above for how to do this.
9. Once all configurations are done (or when exiting the BLHeli Configurator program, e.g. for checking motor direction), click “Write Setup” to save your settings to all 4 ESCs.
Disconnect from BLHeli Configurator and repeats steps (1)-(6) to confirm that all your ESCs still work and your motors are now all spinning in the correct direction.

That’s it. Once you’ve completed these steps, your ESCs are configured and you are ready to configure your flight controller.

If you run into any problems or have questions, please drop us a comment below. We love getting feedback so that we can keep our content as relevant as possible.

If the ESC has this capability, it allows monitoring and logging of performance data that previously required additional sensors (like power modules and RPM sensors). The detailed data provided by every ESC allows real-time decisions and individual ESC or motor performance tuning and failure analysis.

Note

ArduPilot does not currently support bi-directional Dshot reporting of telemetry via the ESC signal wire, nor does it support the polling of the ESCs for telemetry data via throttle idle messages over the signal line in non DShot protocols.

Connect all ESC’s telemetry wires to a single serial port’s RX pin on the autopilot (above diagram uses Serial5 as an example). ESC telemetry is currently only supported with BLHeli_32 ESCs. A pin or wire for ESC telemetry is pre-soldered on most BLHeli_32 ESCs. If the wire isn’t pre-soldered you will need to solder it yourself. Pinouts for serial ports on The Cube can be found here.

Set the following parameters to enable BLHeli_32 telemetry feedback to a autopilot’s serial port:

SERVO_BLH_AUTO = 1 to enable automatic mapping of multirotor motors for BLHeli_32 pass-through and telemetry support. for most multirotor and quadplane users this will do the right thing. If using BLHeli_32 ESCs on non-multirotor motors with the respective SERVOn_FUNCTION set to 70 (=throttle), 73 (=throttle left) or 74 (=throttle right), you will need to further specify the used outputs as follows:

SERVO_BLH_MASK : a bitmap used to enable BLHeli_32 pass-through and telemetry support on non-multirotor motors and / or exactly specify which servo outputs you want to enable pass-through and telemetry on (if available in ESC).
SERVO_BLH_OTYPE : This needs to be set to the protocol being used for the DShot protocol being used on those additional outputs if not the same as the normal copter style motor outputs.

SERIAL5_PROTOCOL 16 (= ESC telemetry). This assumes serial port 5 is used. Adjust the serial port’s protocol parameter to 16 , for the serial port whose RX input is connected to the ESC(s) telemetry pad. The correlation between serial port numbering and UART physical ports for you autopilot should be documented in its description page linked here.
SERVO_BLH_TRATE defaults to 10. this enables telemetry at a 10hz update rate from the ESC.
SERVO_BLH_POLES defaults to 14 which applies to the majority of brushless motors. Adjust as required if you’re using motors with a pole count other than 14 to calculate true motor shaft RPM from ESC’s e-field RPM.

Logging and Reporting¶

Blheli32 Download For Windows 10

The autopilot requests status information from one ESC at a time, cycling between them. This information is logged to the onboard log’s ESCn messages and can be viewed in any ArduPilot compatible log viewer.

RPM
Voltage
Current
Temperature
Total Current

The RCOU messages are also written to the onboard logs which hold the requested output level sent to the ESCs expressed as a number from 1000 (meaning stopped) to 2000 (meaning full output).

This data can also be viewed in real-time using a ground station. If using the Mission Planner go to the Flight Data screen’s status tab and look for esc1_rpm.

Note

Sending BLHeli_32 telemetry data to the GCS requires the telemetry connection use MAVLink2. ArduPilot uses MAVLink2 by default on the USB port but if another port is used it may be necessary to set the SERIALx_PROTOCOL parameter to 2 (where “x” is the serial port number used for the telemetry connection).

Blhelisuite Download For Windows 10

In addition, some telemetry values can be displayed on the integrated on-board OSD, if your autopilot has one.