• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 748 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320F28069F: Rr value from motor identification is too small

Hae Ryong Jung
Expert 2150 points

Part Number: TMS320F28069F
Other Parts Discussed in Thread: MOTORWARE

Dear TI members,

I have tried motor identification process with lab02a in motorware. (custom F28069F board, with ACIM motor for 3 phase 380V )

as you can see in following capture, Rr value is too small. other values seems to be OK.

Actual Rr value from manufacture is around 2.14 Ohm, I could run motor with it, however there was a haunting at motor startup, so I'd like to use more accurate parameter values.

when I have tried to run motor with these parameters, there was an error USER_ErrorCode_motor_Rr_Low, and could not run the motor.

Would you please let me know what could cause this kind of wrong identification ?

How can I get exact parameter with it ?

I'm looking forward your kind help.

Best Regards,

Hae Ryong

  • 0
    TI__Guru** 117240 points
    Could you please make sure that the rotor is fully locked during identify the Rr and Ls? And set USER_MOTOR_RATED_FLUX correctly based on motor's specification?
    And you might use lab01b and lab01c to verify the h/w board, ensure both current and voltage sensing are good for running the motor.
  • 0 in reply to Yanming Luo
    Expert 2150 points
    1. rotor is fully locked during Rr, Ls identification, I confirm.
    2. initial USER_MOTOR_RATED_FLUX value was calculated by 4.8.1.4 of InstaSpin-FOC user guide(spruhj1g), and it was re-measured during identification. FYI, initial value is (0.8165*380/60)
    3. lab01b, lab01c was done, and I could run motor with FOC control.

    As I mentioned in before, the reason why I tried motor identification was to resolve haunting in startup until it reached speed fast enough (around 20Hz)
    After startup, motor running OK in FOC
  • 0 in reply to Hae Ryong Jung
    Expert 2150 points
    would you point out anything to check about my identification process or anything to verify ?
  • 0 in reply to Hae Ryong Jung
    TI__Guru** 117240 points
    Please post your user,h, and some current waveform to show the identification process for this motor. We need to have a look at these waveforms to know why the Rs is not correct if you have followed the process in instaSPIN lab guide and the current/voltage signal sampling is goo as you mentioned.
  • 0 in reply to Yanming Luo
    Expert 2150 points

    Thanks for your response,

    My user.h  is attached.

    3414.user.h

    would you please let me know which waveform of identification step you'd like to look into ?

    Actually, motor identification is not possible at my office, due to lock rotor condition.

    I need to go to the lab of our factory located at the outside of the city.

    Fortunately, I have a schedule to visit our factory at next Tue. then I could retry motor identification and getting waveform you want.

    please let me know the list of waveform til Monday. (my time zone is UTC+9)

    until then please take a look into my user.h, if there are any wrong setting. and let me know your opinion

    Thank you in advance.

  • 0 in reply to Hae Ryong Jung
    Expert 2150 points
    Dear Yanming

    Have you looked my user.h ?

    Would you please let me know your idea about my user.h ?

    and let me know which step of waveform you want to see in motor identification.


    Thanks
  • 0 in reply to Hae Ryong Jung
    TI__Guru** 117240 points
    Hi Ryong,

    What rated voltage and frequency is the motor per its spec.? You might use the formula below to set the USER_MOTOR_RATED_FLUX.
    USER_MOTOR_RATED_FLUX = 0.8*0.8165*Rated_V/Rated_f

    Could you please post the current waveform during the motor is running and gMotorVars.EstState equals to EST_State_RatedFlux, EST_State_RatedFlux_OL or EST_State_IdRated?
  • 0 in reply to Yanming Luo
    Expert 2150 points

    Hi Yanming,

    Thank for your response.

    I have used following definition for USER_MOTOR_RATED_FLUX, according to 4.8.1.4 of InstaSPIN user guide.

    #define USER_MOTOR_RATED_FLUX           (0.8165*380.0/60.0)

    but you have additional  0.8 multiplication. Could it be the cause ?

    Regarding to waveform, I have no schedule to visit factory where I could test motor identification for a while.

    so I cannot provide you waveform soon. 

    I think I close this issue now, I would re-open the issue later