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.

DRV8353RS-EVM: proj_lab02b does not identifies motor.

Part Number: DRV8353RS-EVM
Other Parts Discussed in Thread: MOTORWARE, , DRV8353

Hi,


 I'm working with Motorware projects using the F28027F and a DRV8353RS-EVM.

As a first step, I used the DRV8353Rx 1.0.1 GUI for identifying and running my motor and everything worked fine. Then I installed motorware in my ubuntu laptop and started the InstaSpin labs. 
I get the DRV8353 firmware from this post and followed the suggested steps.

The problem I am facing now is that when I run the proj_lab02b from CCS, and set gMotorVars.Flag_enableSys and gMotorVars.Flag_Run_Identify to 1 nothing happens. In my understanding from the instaspin_labs pdf, it should start motor ID.
I don't have any feedback from the debugger, or at least I don't know where to have it.

 
When gMotorVars.Flag_enableSys and gMotorVars.Flag_Run_Identify are set to 1 I get this values:

  •     gMotorVars.UserErrorCode = USER_ErrorCode_NoError
  •     gMotorVars.CtrlState = CTRL_State_OffLine
  •     gMotorVars.EstState = EST_State_Idle

What may I'm doing wrong? Is there some flag that I'm not setting?

Thanks.

  • Hey Tiago,

    Thank you for your question. We will aim to provide a response shortly.

    Best,
    Akshay

  • Can you try to run in lab01b/c to check if the PWM outputs are right or current/voltage sensing signals are right?

    Can you check if the sensing dc bus voltage is correct within CCS?

  • Hi Yanming

    This is the behaviour of my EVM running lab01b:

    It starts with the expressions set as shown below.



    When Flag_enableSys and Flag_Run_Identify are enabled, CtrlState changes from CTRL_State_Idle to CTRL_State_OffLine at a first moment. And this can be seen in each one of MOTA/B/C.

      

    Then, I think less than two seconds before Flag_enableSys and Flag_Run_Identify are enabled, both CtrlState and EstState changes to CTRL_State_OnLine and EST_State_OnLine respectively. At this moment the motor tries to spin but this don't last more than two seconds.
    If I try to repeat the lab (I mean, desabling and enabling Flag_enableSys and Flag_Run_Identify), the motor doesn't spin at all. I have to stop the debug session and start it again.

    The sensed dc voltage seems to be good.



    Thanks in advance

  • [FAQ] BOOSTXL-DRV8323RS and BOOSTXL-DRV8323RH InstaSPIN and MotorWare support

    [FAQ] DRV8353RS-EVM with InstaSPIN and MotorWare support

    Try to tune the following parameters for running the lab01b according to your motor.

    #define USER_MOTOR_FREQ_LOW                                (10.0)                        // Hz - suggested to set to 10% of rated motor frequency

    #define USER_MOTOR_FREQ_HIGH                                      (100.0)                        // Hz - suggested to set to 100% of rated motor frequency

    #define USER_MOTOR_FREQ_MAX                                (120.0)                        // Hz - suggested to set to 120% of rated motor frequency

    #define USER_MOTOR_VOLT_MIN                                (3.0)                        // Volt - suggested to set to 15% of rated motor voltage

    #define USER_MOTOR_VOLT_MAX                                (18.0)                        // Volt - suggested to set to 100% of rated motor voltage

    For running the lan02b, please try to tune the identification variables in the file of the user header file according to the motor.  And don't add any load on the motor when run this lab for motor parameters identification, to ensure that the motor spins smoothly during Flux measurement and Ls identification states.

    #define USER_MOTOR1_RES_EST_CURRENT      (1.5f)                               // A -  10-30% of rated current of the motor

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

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

    #define USER_MOTOR1_FLUX_EST_FREQ_Hz     (40.0f)                            // Hz - 10~30% rated frequency of the motor

  • [FAQ] DRV8353RS-EVM with InstaSPIN and MotorWare support

    From here is where I get the code to test my EVM. I mentioned this in my first post. 


    Try to tune the following parameters for running the lab01b according to your motor.

    I've already tuned this parameters. Still having the same issue.

  • I've already tuned this parameters. Still having the same issue.

    Keep tuning the v/f profile as mentioned above according to your motor. Don't add any load to the motor in lab01b and lab01c, this lab is just used to verify the board.

    You may check if the current and voltage sensing without connecting the motor first in lab01b, and then connecting the motor to check these sensing signals.

    Since you are using the TI EVM, you may try to run the lab02b, but tuning the identification variables as mentioned above after run the lab01b and lab01c successfully. 

  • I've tunned the v/f profile as you said. Now I can run lab01b and c. Lab01b with some motor noises that I understand are normal and lab01c at low rpm but extremely quiet.
    However, I'm still having the same issue at lab02b that I mentioned here:

    When gMotorVars.Flag_enableSys and gMotorVars.Flag_Run_Identify are set to 1 I get this values:

    •     gMotorVars.UserErrorCode = USER_ErrorCode_NoError
    •     gMotorVars.CtrlState = CTRL_State_OffLine
    •     gMotorVars.EstState = EST_State_Idle
  • Can you check the angle and speed from the FAST estimator in lab01c? The values of these two variables should be close to the values from the open-loop control in lab01c.

  • OK. Please make sure that the connection is correct and the current/voltage sensing signals are right before you try to run the lab02a/b/c. Let's know if you have any further question.