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.

TMS320F28069M: The problem of hall connection in lab11

Part Number: TMS320F28069M
Other Parts Discussed in Thread: LAUNCHXL-F28069M

My development board is launchxl-f28069m + bostxl-drv8305. I found the engineering instruction about lab11e in the user's guide and set JH_ QEP_ 1, and set gpio20, 21, 23 as the input of hall a, B, C according to the requirements. I also connect the hall wire sequence of the motor according to the requirements. When I start the project and set the relevant signs, the motor vibrates violently, but does not rotate. I guarantee that the motor parameters used have been identified by lab2b and are effective. When I switch the hall wires of a, B, C motors arbitrarily The motor can rotate.
1. Is there any error about hall line sequence in user guide? What is the real linear sequence?
2. After I arbitrarily adjust the line sequence, the motor can run, but I don't guarantee that the line sequence is necessarily right, because when I use the load to block the motor and move the load away, the motor will be fixed there. It needs to be touched before it can continue to rotate?
3. After the Hall motor is connected, it seems to vibrate when it drives the motor in the opposite direction at low speed and locked rotor. This still exists when I close the forced angle. This situation is that the accuracy of hall is not high enough, so we need to use an encoder? Or is it just because of the hall order?

  • 1. The hall line sequence depends on the motor, so you have to tune it as you did.

    2. It should be correct if the motor can run well. If the sequence is not right, the motor will not run with an overcurrent fault.

    3. That's normal, the algorithm with the hall sensor in this project is just for improving the startup performance, it's not optimized for very low-speed running. You might have to implement an encoder if you need to get a good performance with speed/position close loop at low speed.  

  • For low speed operation, can I try to use lab21 for high frequency injection? But I try to use high frequency injection and import user parameters. The motor has only sound, not rotation. I disabled the user parameter, it will rotate, but still feel unstable. My ultimate demand is torque control. I can drive the motor with reverse load. The reason why I don't want to use the encoder is that it costs too much.

  • It's just for an IPM motor with a high saliency ratio, and need to tune the injection voltage and control parameters based on the motor and system.

    As mentioned above, using sensored-foc is a better choice if you need high performance at low speed, even you implement the torque control that needs the precise rotor position also.