Tool/software: Code Composer Studio
Hi
I have two questions about the HVPM_Sensorless control project.
1. in SMOPOS_CONST.C file,
volt1.MfuncV2 = svgen1.Tb;
volt1.MfuncV3 = svgen1.Tc;
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software: Code Composer Studio
Hi
I have two questions about the HVPM_Sensorless control project.
1. in SMOPOS_CONST.C file,
1. Because the adc read is done in per unit, it becomes necessary. Vb is the full scale dc bus voltage as sensed by the ADC.
2. True, the intent is to fit the sine values within the COMP range used in the EPWM peripheral. This effectively adds a 50% dutycycle as common mode voltage for all three phases, but they cancel out in line and do not produce any currents through the motor.
Thanks.
1. I got it.
2. What I'm confused with is that the output of PHASEVOLT_MACRO is the input of ESMO module, and the valpha and vbeta uses twice the real value.
If the valpha and vbeta is doube, does it affect the Sliding Mode Current Observer ?
As far as I'm concerned, to the formula below
v->EstIalpha = _IQmpy(v->Fsmopos,v->EstIalpha) + _IQmpy(v->Gsmopos,(v->Valpha-v->Ealpha-v->Zalpha));
Ealpha is almost equal to Zalpha, that is (Ealpha+Zalpha) is almost double the real back EMF, so the Valpha should be twice the real value.
Am I right?
Regards
Arrow
Sorry, then I don't understand why uses the doube value of the real valpha/vbeta for the ESMO module?
CAN I use the real duty rate (0~1)for the PHASEVOLT_MACRO, rather than (-1,1)?
Arrow
No, you should use Valpha and Vbeta only. The duty cycle is modulated based on this.
Duty cycle is based on PWM_MACRO(1,2,3,pwm1) function.
like (*ePWM[ch1]).CMPA.half.CMPA = _IQmpy(m.HalfPerMax,-m.MfuncC1)+ m.HalfPerMax;
PHASEVOLT_MACRO is just for ESMO' valpha and vbeta input.
The simulation of this macro using SVGEN1.Tx or Dx(x = A,B,C) is in the attached file.(Dx = -0.5 *Tx + 0.5)
I just found the SVGEN1.Tx is not the real phase voltage,and can't understand the following explanation.
2. True, the intent is to fit the sine values within the COMP range used in the EPWM peripheral. This effectively adds a 50% dutycycle as common mode voltage for all three phases, but they cancel out in line and do not produce any currents through the motor.
Keep in mind that the dutycycle loaded into comp is in pu.That is the missing link between the implementation and your understanding if I am correct...