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.

TMS320F280049C: Enabling features

Part Number: TMS320F280049C
Other Parts Discussed in Thread: C2000WARE

Hi,

I'm using lab is13.

questions:

1. What is the correct way to enable motor ID, if I already set "flagEnableSys" and run the motor once? I tried setting userParams.flag_bypassMotorId = 0 and calling EST_setParams(estHandle, &userParams); again in the while loop, but the estimator gets stuck at ROVERL. Strangely, the "flagMotorIdentified" is 1.

2. What is the correct way of enabling RsRecalc, after enabling "flagEnableSys", so next time the motor runs it will start with RsRecalc? I get the same behavior as with the motor ID above - the Estimator is stuck at the RS state:

3. I noticed a big difference between is05 and is13 - In is05 the CTRL concept is being used, while in is13 it is not. The mainISR between these two labs is very different. Can you please explain this? Seems like a big change between these two labs.

4. What happens is a estWaitTime is 0 ? e.g. pUserParams->estWaitTime[EST_STATE_LS] = 0;

thank you!

  • I'm using lab is13.

    Could you kindly elaborate what SDK this refers to so that the thread can be assigned to the appropriate expert.

    Thanks.

  • Motorcontrol SDK. Instaspin on 284009C.

  • It has been assigned to the expert. Please expect a response soon.

    Thanks.

  • Please refer to the lab guide to run the example labs, the guide at the folder below.

    \ti\c2000\C2000Ware_MotorControl_SDK_<version>\solutions\common\sensorless_foc\docs\labs

    I'm using lab is13.

    You have to use the is05 if you want to run motor ID.

    2. What is the correct way of enabling RsRecalc, after enabling "flagEnableSys", so next time the motor runs it will start with RsRecalc? I get the same behavior as with the motor ID above - the Estimator is stuck at the RS state:

    Please refer to is10 example lab,

    3. I noticed a big difference between is05 and is13 - In is05 the CTRL concept is being used, while in is13 it is not. The mainISR between these two labs is very different. Can you please explain this? Seems like a big change between these two labs.

    Motor ID needs CTRL object and the related functions.

    4. What happens is a estWaitTime is 0 ? e.g. pUserParams->estWaitTime[EST_STATE_LS] = 0;

    Recommend to use the default settings for the wat time, otherwise, the Motor ID will not work well to identify the correct parameters.