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.
Hi,
I am evaluating the HFI library and have my system functioning with some issues. One is the transition to/from HFI and eSMO angle estimates. I am basing the code off of the HVPM_Enhanced_Sensorless project.
transition1.spd = rc1.SetpointValue;
transition1.angleHFI = hfi1.thetaEst;
transition1.angleSMO = esmo1.Theta;
ANGLE_TRANSIT(&transition1);
speed2.EstimatedTheta = transition1.angle;
Usually the system goes from HFI to eSMO without issue, but when transitioning back the HFI algorithm goes unstable. I am observing the encoder angle (YELLOW), eSMO angle (GREEN), HFI angle (MAGENTA), and transition1.angle (CYAN) thru the DAC outputs. Seen below while under HFI control.
Once I switch to eSMO control, I noticed the HFI angle becomes unstable and is lost, per below. Perhaps this is the reason why the transition isn't working.
I have also tried to operate the system under encoder feedback and look at the HFI estimated angle and the same situation occurs, the HFI angle is all over the place. The only time the HFI solution converges is when it is actually used as commutation.
Questions:
1) Is this expected behavior?
2) Is there a way to execute the HFI in parallel while under encoder control?
Help is appreciated. Thanks!
1. This is not expected. The example code released in controlsuite is tested to function properly changing the speed from positive to negative and viceversa transitioning through zero speed.
2. Sure, you can build a custom build level using the encoder while keeping the HFI active but keeping it off from feeding into PARK/IPARK / speed fbk calc routines.
Hope it helps.