There are settings you can play with in BLHeli_32 configurator to achieve better flight performance of your mini quad. In this article I will share the BLHeli_32 configurations that I use which give me the best results.
If you don’t want to read the long article, here is the summary:
- PWM Frequency: 48KHz for freestyle; Default (or higher) for racing
- Motor Timing: 22 or Auto for freestyle; 25 (or higher) for racing
- ESC Protocol: DShot600 for 8K/8K, or DShot300 for RPM filter (Betaflight 4.1 Recommendation)
I will go into a bit more detail what each setting means.
The “PWM Frequency” setting in BLHeli_32 changes how often the microcontroller (MCU) in the ESC sends updates to the MOSFET. This basically means how often the ESC drives the motor. This PWM setting is entirely unrelated to ESC protocol, FC looptime or the PWM frequency setting in Betaflight.
The default value for PWM Frequency in BLHeli_32 is 24KHz. By raising it to 48KHz you should notice an improvement in the smoothness of your flight performance right away.
When you increase the PWM frequency, the motors should run smoother and tend to generate less noise. It solves “mid throttle oscillations” for a lot of people, some even claim their motors come down cooler as well as getting longer flight time thanks to the improved efficiency.
Don’t go below 24kHz, you should always choose between 24 and 48KHz.
Why does higher PWM Frequency help reduce vibrations?
At lower PWM frequencies, there can be some aliasing/conflicts between the commutation rate and the PWM update rate.
Commutation rate is the time it takes to detect a zero crossing and switch through one feedback cycle, there are 6 commutations per one eRPM, so it is tied directly to RPM
This can result in some odd vibrations or roughness at certain throttle positions. Raising the PWM frequency to the FETs can move the harmonics where this happens outside the range of the commutation rate.
Downsides of Higher PWM Frequency
So why is the default not 48KHz then? Well, because there is no free lunch!
Higher PWM frequency gives you smoother flying experience at the expense of a little power loss (just a few percent). Because of this, higher PWM can reduce peak current draw slightly too, which isn’t necessarily a bad thing for the longevity of the ESC.
At higher PWM Frequency, the torque at low RPM can also be reduced slightly and so your low end throttle might feel softer.
For racers who want to have all the power available, might actually prefer lower PWM frequency, or just stick with the default value.
If you are a perfectionist, you can try 48KHz first, then slowly back it down to find the perfect middle ground between power and smoothness. Every setup is different.
The default Motor Timing in BLHeli_32 is “16 Deg”, which seems to work just fine for the majority of builds. However I always increase it when I am configuring my ESC.
Generally speaking, a higher motor timing is less likely to have “desync” issues. Increasing motor timing also increases the power of your motor at the expense of efficiency.
If you’re after raw power, you can try setting motor timing to around 25, or maybe even slightly higher. I don’t recommend using max settings just in case of unexpected problems. When the timing is set too high for a motor, it will tend to run hotter, this increases the likelihood of burning out a motor in a crash, or when something stops your motors from spinning freely.
For a good balance between power and efficiency, 22 seems to be a good value to get started. For a mini quad, it’s unnecessary to set motor timing lower than the default, unless you are driving a huge motor and propeller (e.g. 10″).
The optimal motor timing value can actually change with motor RPM, so if you are unsure you can just use the “Auto” option, which lets the ESC decide what motor timing to use on the fly. Generally, the auto option provides a good middle ground between efficiency and power through the whole throttle range.
Personally I haven’t seen a big difference when swapping motor timing settings between Auto and 22, but give it a try and let me know in the comment which setting works best for your setup.
Regardless of the differences in performance, DShot is indeed more CPU intensive. This has been the reason for some to opt for Multishot, to allow more processing power to run the “ultimate” 32K/32K Gyro sampling and looptime.
Anyway, give both protocols a try if you want to experiment. Personally I feel very minimal difference in performance between the 2 protocols, but when using DShot:
- I don’t have to worry about ESC calibration
- I use ESC beacon which relies on DShot command
- You need DShot in order to use ESC Telemetry
- Betaflight 4.1 recommends DShot300 for RPM Filter, or DShot600 for 8K/8K
This setting can help reduce “desync”. Just leave the setting at default unless you have desync issues, otherwise change it to high. (what is ESC desync)
High power builds (e.g. 6S or hexacopters) that suffer from electrical noise may benefit from setting demag to High, but in most cases Medium is fine.
Rampup Power is a setting designed to reduce current spikes due to the sudden increases in throttle by limiting the change of power.
If the motors are pushing close to the limit of your ESC’s, current spikes from punch-outs could inflict damage, reducing Rampup Power can lessen this risk.
Leave it at default if you are unsure, as setting it too low can lead to slow motor response.
Current protection limits the amperage passing through the ESC. The purpose is similar to Rampup Power, but the Current Protection setting is more specific on current limit.
I recommend leaving this setting to off (default), unless you know what you are doing.
Potentially this can be used to protect your ESC from “burning” due to current spikes, crashing and desyncs. But as long as the current rating of your ESC meets the requirement, you shouldn’t need to worry about it.
How about the Rest of the Settings?
For mini quad? Just leave them to default :) A lot of these settings are for fixed wings and planes.
- Jun 2018 – Article created
- Nov 2018 – Added Demag Compensation
- Feb 2019 – Updated Rampup Power and Current Protection
- Jan 2020 – Revised