[FEATURE] Include motor inductance in voltage control.

[dzid26]

I want to just lay out the foundation for a possible improvement, and also get feedback to verify the idea.

Issue

Lemma 1
Current is proportional to forward torque but only when its vector is at a 90-degree electrical angle.
Lemma 2
The current always lags the rotating voltage vector.

In the present Voltage control scheme, a 90-degree electrical angle is not maintained when speed increases.
Currently, this is the control scheme

Arduino-FOC/src/StepperMotor.cpp

Lines 297 to 299 in 45219c4

	else voltage.q = target*phase_resistance + voltage_bemf;
	voltage.q = _constrain(voltage.q, -voltage_limit, voltage_limit);
	voltage.d = 0;

:
Vd=0
Vq=BEMF+ I_target R

(Source)

Proposal

The voltage vector must be phase-shifted to compensate for the current vector lag. Since Park transform is already implemented, the phase lead angle can happen naturally by manipulating Vd. (White vector below)
The control should look like this:

Setting Vd=-I_target * ω*R_L will shift the effective current target vector to the desired 90deg. Only then will this current be proportional to torque.
ω is the electrical angular speed in rad/s. I.e. shaft speed * poles_pairs.
If the combined motor inductance R_L is unknown, it can be set to 0.
From what I know, coil inductance can be an approximation of motor inductance, but I don't know how good. On the other hand, R_Lcan be found experimentally presumably by optimizing the value for maximum motor power.

References:

https://docs.simplefoc.com/voltage_torque_mode#voltage-control-with-current-estimation-and-back-emf-compensation
https://endless-sphere.com/sphere/threads/tsdz2-mid-drive-with-860c-850c-or-sw102-displays-only-flexible-opensource-firmware-casainho-code-only.93818/post-1376865
https://github.com/EGG-electric-unicycle/documentation/blob/master/Shane_Colton/3phduo.pdf - page 27.

[runger1101001]

Thank you for this report! It makes sense to me, but I would like to think what @askuric thinks as well.

It could be easily implemented, I think as a subclass of BLDCMotor, and if it works well eventually rolled into the main implementation.

As you point out, the main problem for users will be obtaining the value of the motor inductance if it is not given in the datasheet...

[askuric]

Very interesting @dzid26,
I like the idea very much.
And it goes hand-in-hand with the field weakening also. We could definitely implement this in the motor classes.
For the sensorless control we will need the inductance value as well and this enhancement could be an easy addition trough which we could start extending our API to allow users to set it.

I'm going to test this in code and report back, if the results are as expected we could make it a part of our next release.

[askuric]

Hey guys,
So I've had some time today and I've tested your proposal. It works like a charm, the voltage control (depending on the inductance value set) can reach much higher velocities than it could without it.
In my setup:

• gbm4108H
• 500cpr encoder
• simplefocshield
• stm32g474 nucleo
• 20 V power supply - 12V voltage limit
  motor with the voltage control max velocity reached is:
• L = 0 - 110rad/s
• L = 0.01 - 130 rad/s

What's even more interesting is that using this simple approach the max velocity reached is higher than for the pure foc_current approach, which reaches the max velocity of around 120rad/s. foc_current approach has a longer loop time and that might be the issue. However foc_current approach reaches the 120rad/s velocity with much lower current than the any of the voltage control modes, which is natural as well.

So all in all, I am very happy with this addition and it sets a nice base for the future features. Thatnks a lot for your proposition and if you have the time to test the code that would be awesome as well.

For my motor the

// pole_pairs   : 11
// resitance     : 10 Ohm
// KV rating    : 110 
// inductance : 0.01 H
BLDCMotor motor = BLDCMotor(11, 10, 110, 0.01);

The phase inductance can be also set using

motor.phase_inductance = 0.001;

of in the Commander using the command I.
For example if you motor's command is M, then you can change the phase inductance

$ MI     
L phase: 0.01
$ MI0.001
L phase: 0.001

This is just an initial implementation though, and it might change till the next release, however I am fairly certain it will be a part of the simplefoc v2.3

[dzid26]

Amazing.
Maybe what is happening is that the motor starts to "experience" the field weakening and thus reaching higher speed.
I was thinking this could happen and that's why I was thinking the best way to find optimal L value is by maximizing peak power, that is under load.

I would love to try it. Funny thing is that I haven't run SimpleFOC on anything yet. So far I was just admiring simplicity and the good documentation :)

[runger1101001]

This is very cool.

[greymfm]

Just trying to understand this brilliant idea - this is related to both stepper and BLDC motors, correct? :-)

[greymfm]

I have added the changes to my code, and tested it - it works beautifully :-)

[askuric]

Awesome!
Yeah the steppers have the same issue. However they do have one transformation less when we calculate the Park and Clarke, as they have only two phases.

In the release v2.3 we did include this change to the stepper code as well, so please do let us know if it works for you as well. 😄

[Candas1]

Hi,

I used this feature with voltage mode and it works great.
I saw that the lag compensation code is commented out for foc_current mode, I assume that's what the PI control of D current does.

Now I think something is missing here, and that would also help with field weakening, I think it's called the circle limitation.
As you compensate the lag by increasing Vd, you should limit Vq.
This is how it is described in the STM32 FOC bible (chapter 4.12.1)

[Candas1]

I think the way it works now is that the waveform is saturated by the voltage limit of the driver resulting with overmodulation ?