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.

C2000WARE-MOTORCONTROL-SDK: Universal Motor Control Lab Motor Id Not Working

Part Number: C2000WARE-MOTORCONTROL-SDK
Other Parts Discussed in Thread: BOOSTXL-DRV8323RH

Tool/software:

Hello,

I am working with the the Universal Motor Control Lab on the 280025C LaunchPad + BoostXL-DRV8323RH, with the Anaheim_BLY172S_24V (a motor with settings already in user_mtr1.h).  I imported the project from Motor Control SDK 5.02.00.00.

If I run the motor using the settings in user_mtr1.h (flag_bypassMotorId = true), the motor runs well and as expected.

I am testing out the Motor parameter ID function (DMC_BUILDLEVEL  DMC_LEVEL_4).  The only changes made after importing the project are setting the build configuration to Flash_lib_DRV3232RH_3SC, and changing the DMC_BUILDLEVEL.

When I try the Motor ID function (userParams_M1.flag_bypassMotorId = false), the Motor parameter ID process runs to completion.  The results however are not close to the settings in user_mtr1.h.  When I try to run the motor with the parameters selected by the Motor ID function, the motor rotates at very low speed.  As a guess, 15 RPM = 1Hz, despite speedRef = 40Hz, and increasing speedRef to 100Hz does not noticeably change the motor rotation.   

For Rs_Ohm, user_mtr1.h has ~0.4, and the motor parameter ID returned 0.001.

For Ls_d/Ls_q, user_mtr1.h has 0.0006 and the value returned by the Motor ID procedure is 0.000001

For Rated Flux VpHz, user_mtr1.h has 0.034 and the value returned by the Motor ID procedure is 0.036...so this seems to be close.

My expectation is that the Motor Parameter identification would return values close to what is in user_mtr1.h, and the motor would run well with the returned values.

Any suggestions on what the issue may be, or how to troubleshoot?

Thanks!

  • Mark,

    You stated that the only changes made were those- did you change the value of USER_MOTOR1 in user_mtr1.h to Anaheim_BLY172S_24V ?

    Regards,
    Jason Osborn

  • Yes, I that was the other change I made that I forgot to mention.  I had changed the motor in user_mtr1.h to the Anaheim model I am using.

  • Mark,

    When I've seen behavior like that before, it's generally been due to incomplete HW setup, which can be identified by running builds 1, 2, and 3 to verify the HW is valid, or in a couple of cases, due to poor connection somewhere between the motor, DRV booster pack, and C2000 LaunchPad. That said, normally in those situations, normal running of the motor is also non-functional, so that's a bit confusing.

    I suggest verifying that any necessary HW changes or configurations in the F280025C LP and the BOOSTXL-DRV8323RH described in the UMCL User's Guide, then running or re-running build 1, 2, and 3 of the lab to verify the HW is good.

    Regards,
    Jason Osborn