• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 84 subscribers
  • Views 293 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.

Original question:

TMS320F280025C: HAL SENSOR SEQUENCE AUTOMATIC IDENTIFICATION DURING COMMISSIONING

TMS320F280025C: How to reduce Motor Paramter Identification Time in FAST mode

Anil Sudhakaran
Expert 1125 points

Part Number: TMS320F280025C
Other Parts Discussed in Thread: DRV8353RS-EVM

Tool/software:

Hi,

In my production  code, I would like   to have less  time for motor parameter identification .

As of now it takes around 2 minutes to calculate  Rs_Ohm, Ls_d_H , Ls_q_H, flux_VpHz.

Please suggest  where to make changes  to get less time and also  how much I can decrease so that parameter accuracy will be mainitained.

Thanks & Regards,

Anil

  • 0
    Expert 1125 points
    Using DRV8353RS-EVM + LaunchXL- F280025C.
     
    More details are in "original question", 2 levels up of this discussion thread. 
    Thanks,
    Anil
  • 0 in reply to Anil Sudhakaran
    TI__Expert 6230 points

    Hi Anil,

    Thanks for providing more information. The time spend on the motor ID depends on the execution of the algorithm. Thus, it cannot be shortened. But would the latency be acceptable as you only need to run it for a new motor once at the beginning?

    Thanks,

    Jiaxin

  • 0 in reply to Jiaxin Teng
    Expert 1125 points

    Hi Jiaxin,

    Yes. it is used only once during commissioning.

    If there is an option I would like to briung down the time.

    Regards,

    Anil

  • 0 in reply to Anil Sudhakaran
    TI__Expert 6230 points

    Hi Anil,

    Just like what I said, the execution time depends on the algorithm itself, you may get shorter execution time with a MCU with faster CPU clock frequency.

    Thanks,

    Jiaxin

  • 0 in reply to Anil Sudhakaran
    Guru 56418 points

    Hi Arill,

    Seemingly it would be prudent to not include such ID process in a production application. Each motor may have varied parameters depending on manufacture process and other factors such as ambient temperature. Perhaps wise to certify, tagging each motor with specific parameter values to a certified MCU process of certain peripherals being calibrated. You could add other more prudent drive certification measures too. Such as each custom PCB MCU be fathered with a specific tagged motor to mitigate fallouts on final assembly line. Often minor details that can come back to haunt a company.