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.

BOOSTXL-DRV8301: Question about inductance identification

Genius 3095 points
Part Number: BOOSTXL-DRV8301
Other Parts Discussed in Thread: LAUNCHXL-F28069M,

Dear team:

One of my clients designed a PCB based on the LAUNCHXL-F28069M and BOOSTXL-DRV8301 kit. Only MOSFET is different, and other hardware is the same.

Now in the motor parameter identification, the inductance value is much smaller than that measured by the official kit, and other values are the same.

Both lab01b and lab01c can control the normal operation of the motor. In the experiment with lab02a, the other parameters obtained in the recognition of self-made board and demo board are very close, except the inductance value. 

What would be the problem?

Best Regards

  • Both lab01b and lab01c can't fully verify the voltage signals sampling quality. You have to check the voltage sensing circuit the if the identification inductace has a much bigger difference between your own board and TI EVM.

    You may try to tune the identification variables also in the file of the user.h according to the motor.

    #define USER_MOTOR_RES_EST_CURRENT     (1.0)                               // A - 10-30% of rated current of the motor

    #define USER_MOTOR_IND_EST_CURRENT     (-1.0)                             // A - 10-30% of rated current of the motor, just enough to enable rotation

    #define USER_MOTOR_MAX_CURRENT           (5.0)                               // A - 30~150% of rated current of the motor

    #define USER_MOTOR_FLUX_EST_FREQ_Hz     (20.0)                           // Hz - 10~30% rated frequency of the motor

  • Dear Yanming:

    The sampling waveform of the voltage induction circuit of the circuit board is not different from that of the Ti development board. The quality of the sampling signal should not be a big problem. If you consider it comprehensively, do you have other reasons to cause the same problem?

    The parameters of user.h you mentioned have been modified and debugged, but the output results have not changed at all

    Best Regards

  • I don't think there are more other reasons if you follow the instructions in the lab guide to tuning the identification parameters I mentioned above. You have to check the hardware board and make sure that the ADC, WPM, and GPIO configurations are correct.