Before I assure you that you are not running Dshot, after connecting to Mission Planner and in the Messages screen what do you see for this message? Post a screen capture.
Move the motors to AUX outputs where DShot is supported.
AM32 Configurator only communicates when DShot protocol is active.
Connect via AM32 Configurator again.
Set the correct Motor KV value (very important).
Write settings & power-cycle the ESC.
After doing this:
Motor direction could be set in the configurator
Throttle response became smooth and linear
RPM increased normally across full throttle range
Conclusion
For AM32 ESCs, always use DShot-capable AUX outputs so the configurator can communicate properly.
And make sure to set the correct motor KV — otherwise the ESC will limit low-RPM power.
I have a question regarding motor poles configuration in AM32 ESC firmware.
My motor datasheet shows:
n = 18 (stator slots)
p = 24 (magnet poles)
I am currently configuring the ESC via AM32 Configurator.
By default, the Motor Poles value was not matching the motor datasheet.
Question:
Do I need to set the Motor Poles value in AM32 to 24 (based on p)?
Or should I leave the default value?
I recommend also shift to bdshot Arducopter firmware. It will helps you a lot on Harmonic Notch filter settings without additional hardware change, noise and vibrations reduction. Take note, Aux port 2 onwards on Cubepilot support bdshot.
If that was true at some point I don’t think it is any longer.
HWDEF: PE14 TIM1_CH4 TIM1 PWM(1) GPIO(50) BIDIR PE13 TIM1_CH3 TIM1 PWM(2) GPIO(51) # this will automatically be shared with TIM1_CH4 PE11 TIM1_CH2 TIM1 PWM(3) GPIO(52) BIDIR PE9 TIM1_CH1 TIM1 PWM(4) GPIO(53) # this will automatically be shared with TIM1_CH1 PD13 TIM4_CH2 TIM4 PWM(5) GPIO(54) BIDIR PD14 TIM4_CH3 TIM4 PWM(6) GPIO(55) BIDIR
I know it’s zero, that’s why I posted they are Dshot capable if configured properly. It was not configured properly. You have just re-stated the obvious.
