Part Number: HVBLDCMTR
Tool/software: Code Composer Studio
My understanding: HALL3_NEXT_STATE_MACRO in the routine determines the value of the HallMapPointer based on the currently acquired Hall state signal after the HallMap is created. Then the main interrupt program should set the drive PWM state(pwm1.CmtnPointer), according to the value of HallMapPointer. As the following program:
However, the PWM state(pwm1.CmtnPointer) in the routine seems to have nothing to do with HallMapPointer, and pwm1.CmtnPointer still assigns the corresponding value according to the state of hall1.HallGpioAccepted. As shown below:
I want to ask: What is the role of HallMap creation in the operation of the rear motor? Shouldn't HallMap be used to determine the value of pwm1.CmtnPointer?