MBL1660A Sensorless - Controller does not change motor power

I've managed to set up my MBL1660A in sensorless mode so that the motor starts turning smoothly, in both directions.

However, once it starts, I can't change the rotation speed. Changing the motor command does not change the applied motor power.

Sensorless calibration does not work - the result is much worse after than before.

Note: I noticed that the motor power used in the startup phase becomes the minimum motor power that will ever be applied ... is that on purpose ? Could it be changed ? I noticed that when I have a low max deceleration, stopping the motor is very smooth, which I guess means that the controller could apply lower power to the motor.

Hey, this stuff doesn't make any sense at all in regards to how our sensorless should function. Let me know which version of firmware you are on.

FID reports v1.8d MBL1XXXA 1/8/2018

Two screen captures with two different commands applied. Speed does not change, and neither does the Motor Power metric. I'm in open loop mode. If I switch to closed-loop speed, it basically behaves the same way but with a different "fixed" motor power, and therefore a higher speed (which is P * the command I apply)

The motor turns smoothly.

If I run instead in closed-loop speed mode, I get a baseline motor power of P * Start Up Power (here, P=4 and Start-Up Power=50)



If I set a command where P * Command > Start Up Power, the controller does apply that command and the motor does start to turn faster



Then, if I stop after having set a low-ish max deceleration, I get a "clean" deceleration:

Does this happen at higher motor commands?

In Open Loop, yes. It's stuck at the startup power. I can add that the reported "Hall RPM" (which I guess is taken from the back EMF) is good - I have an encoder coupled to the motor on a test bench, and it's fairly accurate.

In Close Loop Speed mode, the motor power starts to change when Command * P is greater than the startup power.