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.

CCS: Speed ​​does not change despite the increase of the transverse current Iq

Other Parts Discussed in Thread: MOTORWARE

Tool/software: Code Composer Studio

Hello ladies and gentlemen,

I am an electrical engineering student from Austria and my team and i have a problem and hope you can help us. We have been trying to steer our synchronous motor with the motor kit DRV8301 for a long time.
This is what we succeeded, however, we have a problem.
The stator resistance Rs and the stator inductance Ls were measured manually.
Then they were integrated into the user.h library quite normal.
However, our problem is that the rpm of the motor does not change from a certain speed (200 rpm), although the transverse current Iq is massiv increased.
Its only increasing until 4 Ampere, then there is nothing happening anymore.

What could be the reason?

With friendly greetings

Marco
  • drag and drop your user.h file into the reply

    please try to ID the motor using proj_lab02c to see if the values agree with your hand measurements.
  • Hello Chris,

    First thanks to your reply!

    The stator resistance Rs and the stator inductance Ls which where measured by hand nearly agree with the  ID and the motor data sheet so thats not the problem.

    Here is a picture of our user.h files, we use the example programm proj_lab04.


    It is simply unusual that the speed does not increase although we increase the cross current Iq massively. Is there maybe something with the frequency?

    With friednly greetings

    Marco

  • I don't understand the *8 you have used in the flux. I'm actually surprised that compiles correctly.

    also (200.0) is too high for the EST_FREQ

    You should use between 20-60 Hz for most motors

    can you please run proj_lab02c and provide the results of motor iD?
    make sure the motor starts spinning during RampUp state and keeps spinning for the duration of the ID process.
    if it stops spinning increase RES_EST_CURRENT until it spins throughout.


    after we have verified the motor parameters please use proj_lab10 to run the motor. this lab lets you view gMotorVars.Vs and Is which will tell you how much of the bus voltage and USER_MOTOR_MAX_CURRENT are being used, which will be important in debug.
  • Hello Chris,

    I am sorry for my ignorance its the first time we are trying to drive a motor with Code Composer. The *8 was because we have tried with which Flux the engine runs the best or the fastest.

    Yeah we change the EST_FREQ because we thougt maybe thats the solution for our problem usually we use 20.0.

    Ok we will do it like you said, because there where always problems when we tried to ID the Motor with pro_lab04. Then the motor datas are far away from the ones in the data sheets and our hand measurements and also the engine doesnt work at all.

    Only once out of 100 times, we did it as always, suddenly comes the right values ​​out. We have saved these at the same time and these also correspond with those from the data sheet. When we tried it a few minutes later again to identify the engine then the wrong values ​​with which the engine is not running came back.

    Its very strange...

    I want to thank you for your help!

    Marco
  • Hello!


    The proj_lab02c also does not work. In the "Ramp up" identification process, the motor does not start to rotate. After several attempts we always received different values. We also tried the proj_lab10. Even with this project we had no success.

    With friendly greetings

    Marco

  • proj_lab02c will ID any 3-ph synchronous motor, assuming you are using appropriate HW and power supply for your motor. Refer to the GUI User's Guide for some tips on how to set the user.h values to ID.

    starting on page 25

    C:\ti\motorware\motorware_1_01_00_17\docs\guis\universal