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.

TMS320F28069: The Pos_mrev variable is updated too slowly

Part Number: TMS320F28069


I am going to do the motor deceleration measures, but I find that the variable at this position st_obj [Motor2] .vel.conv.Pos_mrev is a bit slow to update, at least greater than 500ms, and I will use this variable to calculate the current position. I use It is an incremental encoder. Our product is used to pull the motor with a rope. When the load is large enough, I let go. The recovery force of the motor will be greater than the set load torque, and I want to The torque of the motor is given a value of 0 to make him brake, but my test found that because the st_obj [Motor2] .vel.conv.Pos_mrev variable is updated too slowly and the test result is catastrophic, is there any good way to solve this problem?

  • Please check what CPU bandwidth is taking by ISR. You should need to know what lab, PWM and ISR frequency are you using. You might take a look at the of the lab12b and lab13b of InstaSPIN lab guide and user's guide, and try to tune the below variables.

    gMotorVars.MaxAccel_krpmps
    gMotorVars.MaxDecel_krpmps

  • My chip model is f28069, and the routine uses a lab12c dual motor. I have not seen anything in this routine to change the values of gMotorVars.MaxAccel_krpmps and gMotorVars.MaxDecel_krpmps, except for gMotorVars.MaxAccel_krpmps when it is initialized Is assigned the value iq (0
    2) Doesn't the variable gMotorVars.MaxDecel_krpmps exist in lab12c?

  • Please follow the lab guide to make sure that you can identify and run the motor with lab12a and lab12b first. The lab12c is just a starting point to show the ability of the device, you must use a lower PWM frequency limit to the CPU bandwidth.