BLHeli - 32 Manual ARM Rev32.x
BLHeli - 32 Manual ARM Rev32.x
BLHeli - 32 Manual ARM Rev32.x
The code supports features to prevent sync loss. There are tuneable
parameters that can make the code run well even in the most
demanding situations, although default settings will work excellently
in normal operating environments.
The code also supports a beacon functionality, where the ESC will
start beeping after a given time of zero throttle. This can be very
useful for finding lost crafts.
Rampup Power:
Rampup power can be set to relative values from 3% to 150%. This is the maximum power
that is allowed when ramping up at low rpms and during startup. For low rpms, the maximum
power to the motor is limited, in order to facilitate detection of low BEMF voltages.
Rampup power also affects bidirectional operation, as the parameter is used to limit the power
applied during direction reversal.
During startup, the actual applied power depends on throttle input, and can be lower than the
maximum level set by the rampup power parameter, but the minimum level is a quarter of the
maximum level.
Motor Timing:
Motor timing can be set between approximately 10 and approximately 310 in approximately 10
increments (actual accurate values here are 15/16ths of a degree).
Typically a medium setting will work fine, but if the motor stutters it can be beneficial to
increase timing. Some motors with high inductance can have a very long commutation
demagnetization time. This can result in motor stop or stutter upon quick throttle increase,
particularly when running at a low rpm. Setting timing higher will allow more time for
demagnetization, and often helps.
This parameter can also be set to auto. I this case the code monitors demagnetization time,
and keeps timing as low as possible without having issues with demag. On well behaved
motors, timing can be low in the entire power range, and thereby max power can be reduced.
On not so well behaved motors, timing is increased as needed, and thereby improves margins
against sync loss.
PWM frequency:
Motor PWM frequency can be programmed in a range that is preconfigured by the ESC
manufacturer.
Code revisions from Rev32.9 and on support variable pwm frequency where the pwm
frequency is controlled by motor RPM. This mode is called “By RPM”.
This mode can be invoked by setting pwm high frequency to maximum.
By letting pwm frequency be controlled by RPM instead of throttle, some artifacts that can
arise from throttle control can be alleviated.
Demag compensation is an alternative way of combating the issue. First of all, it detects when
a demag situation occurs.
- In this situation, there is no info on motor timing, and commutation proceeds blindly
with a predicted timing.
- In addition to this, motor power is cut off some time before the next commutation.
A metric is calculated that indicates how severe the demag situation is. The more severe the
situation, the more power is cut off.
When demag compensation is set to off, power is never cut.
When setting it to low or high, power is cut. For a high setting, power is cut more
aggressively.
Code revisions from Rev32.9 and on also support a setting called “Very High”, for which
power is cut even more aggressively.
It is a pretty subtle effect. Power is modulated with a sine shape, following the top of a sine
wave through the commutation cycle so that the power when commutating shall be ideal for a
motor with sine shaped BEMF. Power is varied between sin(60deg)=87% when commutating
to sin(90deg)=100% in the middle of a commutation cycle, and then down again to
sin(120deg)= 87% at the end of the commutation cycle.
Maximum power is the same for sine mode as for regular mode, as when approaching full
power the ESC will transition smoothly into regular mode.
Varying power can only be done by varying pwm, so a high pwm frequency is preferable for
accurate sine mode operation. Still, even with 48kHz pwm frequency, a reasonable accuracy
of the sine modulation can only be achieved up to some 100k erpm. At higher erpms, the
motor still runs fine, but the quality of the sine modulation is degraded.
Due to the increased MCU processing for sine mode, max erpms is lower for sine mode than
for regular mode. Still it will generally be more than 300k erpm even for sine mode.
Note that if sine mode is chosen, then variable pwm frequency is disabled.
When setting to e.g. 10%/ms, it means that the power applied to the motor is not allowed to
increase by more than 10% per millisecond.
Motor Direction:
Motor direction can be set to fwd, rev, bidirectional 3D, bidirectional 3D rev, bidirectional
soft and bidirectional soft rev. In bidirectional mode, center throttle is zero and above is fwd
rotation and below is reverse rotation. When bidirectional operation is selected, throttle
calibration is disabled.
There are two bidirectional modes from Rev32.6, bidirectional 3D and bidirectional soft.
The 3D mode applies more power when reversing direction, and also limits minimum throttle
to 6%. The soft mode applies less power when reversing, and does not limit minimum
throttle.
Beacon/Signal Volume:
Sets the volume of beeps when beeping beacon beeps. The ESC will start beeping beacon
beeps if the throttle signal has been zero for a given time. Note that setting a high volume can
cause hot motors or ESCs!
Also sets the volume used for Dshot/Proshot initiated signal tones.
Beacon Delay:
Beacon delay sets the delay before beacon beeping starts.
The ESC measures temperature within the MCU and limits motor power if the temperature is
too high. Motor power is limited over a range:
- If the temperature is above the threshold, motor power begins to be limited.
- If the temperature is above the threshold plus approximately 150C, motor power is limited
to 25%. Motor power is not limited below 25%.
Current Protection:
Current protection can be enabled to limit current. If enabled, then current will be limited to
maximum the programmed value. The reaction time of the current limiting is quite fast, so
current will also be limited during accelerations.
The value given for current protection, is per ESC. So if setting limit to e.g. 40A for each of
the ESCs in a quad (using BLHeliSuite32 or the BLHeli_32 Android app), then the total
current limit for the four ESCs will be 160A.
Brake On Stop:
Brake on stop can be set between 1% and 100%, or disabled. When not disabled, the given
brake force will be applied when throttle is zero. For nonzero throttle, this setting has no
effect. This feature is primarily intended for fixed wing crafts with folding props.
On some ESCs this setting is not linearly programmable, it will just be enabled (at 100%
force for any setting 1%-100%) or disabled (this applies to ESCs that have “EN/PWM” style
fet drivers).
LED Control:
LEDs can be controlled on ESCs that support it. Up to 4 LEDs can be turned on or off.
Stall protection:
From revision 32.7, stall protection can be programmed to normal or relaxed. Relaxed stall
protection increases the risk of damage to ESC or motor but can recover faster when props hit
obstacles. For revision 32.6 and earlier, stall protection is relaxed.
Code revisions from Rev32.9 and on have a tweak to the relaxed stall protection mode, where
there is no boost on startup for this mode. So if you are flying with really low throttle and the
motors stop e.g. due to reverse flow, then they will just gently start up again on the low
throttle.
From code revision 32.4 and onwards, it is possible to select nondamped operation (for most
ESCs). This will degrade performance in multirotor applications but can be desirable for fixed
wing environments.
S.BUS:
From code revision 32.8 and onwards, S.BUS as input signal is supported. The S.BUS
channel is selected with BLHeliSuite32 or the BLHeli_32 Android app. If a valid S.BUS
channel (0 to 16) is selected, then the input signal will be interpreted as S.BUS.
S.PORT:
From code revision 32.8 and onwards, FrSky compatible S.PORT telemetry is supported. The
S.PORT physical ID is selected with BLHeliSuite32 or the BLHeli_32 Android app. If a valid
S.PORT physical ID (1 to 28) is selected, then the telemetry format will be S.PORT. Note that
only ESCs that use USART1 (port PB6) for telemetry support S.PORT. If the "S.PORT
Physical ID" programming parameter shows up in BLHeliSuite32, then your ESC supports it.
0% Time
When throttle signal is detected, it beeps one low tone beep. This signals that input signal is
detected. Then, when or if throttle is zero, it beeps one high tone beep. This signals the end of the
arming sequence, and the ESC is ready to run.
Also, if more than 50% throttle is detected at arm start, the ESC starts throttle calibration.
If the esc is armed and sees zero throttle for a given time, it beeps beacon beeps, which are
approximately one beep per three seconds.
Input signal:
Available throttle calibration range is from 1000us to 2000us, and the difference between minimum
and maximum throttle must be more than 140us (70us in bidirectional mode). If a calibration is
done where the difference is less than 140us (70us), the maximum will be shifted so that the
difference is 140us (70us).
Oneshot125 mode works just the same as regular 1-2ms mode, the only difference is that all timing
is divided by 8. And the same for Oneshot42, where all timing is further divided by 3. Multishot
also works similarly, except the input signal range is 5-25us.
Dshot is supported at any rate, up to at least Dshot1200 and Proshot at least up to Proshot1000.
When the input signal is Dshot or Proshot, throttle calibration is disabled, and the throttle
calibration values are ignored.
Input signal rates up to at least 32kHz are supported. But please note that higher input signal rates
put a heavier load on the MCU, and will reduce the maximum erpm that the ESC can handle.
For a 48MHz clock MCU, the minimum input signal rates are about 40Hz for 1-2ms PWM, about
1000Hz for Dshot and Proshot and about 300Hz for all other input signal types. For faster MCUs,
these frequencies will scale up proportionally to MCU clock frequency.
Note that codes from Rev32.8 and onwards no longer support Proshot.
Note that good frames count is limited to 32bit (4294967295 maximum), and that activation of
beacon will generate bad frames.
Telemetry:
From code revision 32.1 and onwards, telemetry is supported. Telemetry is designed to be
compatible with the specifications from KISS 24A, and delivers the following data:
- Temperature [0C]
- Voltage [V]
- Current [A]
- Temperature [Ah]
- Rotation speed [electrical rpm]
Temperatures below 00C are not supported, they will be shown as 00C.
For conversion from electrical rpm to mechanical rpm, divide by (motor poles)/2.
Note that rotation speed measurements are erroneous below 1000 electrical rpm for revision 32.6
and earlier.
For a 72MHz GigaDevice MCU, these speeds are approximately doubled (increased clock speed
and no flash memory wait states).
A 14 pole 2300kv motor on 4S will theoretically run up to (14/2)*2300*4*4.2 erpm = 270k erpm
Power up:
Once
Once
Once
Power up:
Once
Once
While measuring
Once
This beep sequence indicates that max throttle has been stored
While measuring
Once
This beep sequence indicates that min throttle has been stored
At this point throttle calibration values are stored. You may remove power from the ESC, or just
continue running your ESC.
Please note that for some ESCs, throttle calibration beeps are different from the above. If you are in
doubt, consult the manual of your specific ESC.
In this case the ESC will only accept 1-2ms pwm input signal.
Airbot_Wraith32_Plus_ST PB6
Airbot_Wraith32_ST PB6
Airbot_Wraith32_Mini_ST PB6
X_Racer_35A PB6
X_Racer_25A PB6
Betaflight_ESC_BL32_35A PB6
Mantis_ST PA14
BLARM_HK_6530 PA14
Siskin_ST PA14
FVT_Littlebee_Summer_30A PB6
FVT_Littlebee_Summer_35A PA14
Emax_Formula_45A PA14
Aikon_AK32_35A PB6
KS_BLHeli_32_30A PB6
Spedix_GS30A_V1_1 PB6
Spedix_GS35A_V1_1 PB6
Hobbywing_XRotor_BLHeli32 PB6
iFlight_Force32 PA14 (PB6 for Rev32.1)
DYS_Aria_32 PB6
Siskin_ST_32_Plus PB6
Siskin_GD_32_Plus PB6
FVT_Littlebee_Summer_25A PB6
T_Motor_F30A_BLHeli32_V1_1 PB6
T_Motor_F35A_BLHeli32_V1_1 PB6
Typhoon32 PA14
Ori32 PB6
Spedix_GS35A_4IN1_4S_V1_1 PB6
Spedix_GS35A_4IN1_6S_V1_1 PB6
Flycolor_X_Cross_BL_32 PA14
Spedix_GS20A_4IN1_4S_V1_1 PB6
Gemfan_Maverick PB6
AGF_BLHeli_32 PB6
TYPHEERX PB6
FVT_CloudPhoenix_12AX4 PB6
Aikon_AK32_4S_V1_0 PB6
NOX_ESC PB6
DALRC_ENGINE_40A PB6
FVT_CloudPhoenix_35A PB6
MARS32_35A PB6
HGLRC_T-REX_60A_ST PB6
HGLRC_DinoShot_40A_ST PB6
Flycolor_X_Cross_BL_32_35A PA14
Exuav_FishDrone PB6
Aikon_AK32_4IN1_35A_6S_V1_0 PB6
YGRC_32 PB6
RobotDOG_ST PB6
MARS32_40A PB6
HAKRC_30A PB6
HAKRC_35A PB6
KS_BLHeli_32_40A PB6
Airbot_Wraith32_Metal_ST PB6
RF1.h PA14
JHE_Aria_32 PB6
Siskin_Lite PB6
Tmotor_32Bit PA14
FrESC_80A PB6
KS_40A_4IN1_4S PB6
BLARM_HK_6530
Gemfan_Maverick
- Rev32.1:
Setting temperature protection to off causes maximum power to be very limited.
Direction reversals in bidirectional mode are not reliable.
Stalled motor protection does not work as intended, starting is attempted indefinitely, even if motor
is stalled.
- Rev32.2:
Withdrawn as in some cases it could beep very loud when disconnecting after a flash to this
revision.
- Rev32.3:
Dshot/Proshot save settings command (command no 12) does not always work.
The telemetry reported erpm can have some percent error.
- Rev32.4:
Telemetry data has a high CRC error rate.
Motor can twitch when stopping in bidirectional mode.
Proshot sometimes does not detect input signal, particularly at high input signal frequencies.
- Rev32.5:
Withdrawn due to random failures during flashing and setting changes.
- Rev32.6:
LEDs do not work on GetFPV and Furling32 codes.
- Rev32.8:
Noise spikes in bidirectional Dshot erpm data.
Bidirectional mode does not work for SBUS input signal