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.

MSPM0G3507-Q1: request source file of FOC_Lib.lib

Part Number: MSPM0G3507-Q1
Other Parts Discussed in Thread: MSPM0G3507, DRV8329

Tool/software:

Hi Experts,

My customer are using MSPM0G3507 with example of motor_control_pmsm_sensorless_foc\sensorless-foc_DRV8329.(SDK Version : mspm0_sdk_2_03_00_07)
They want to have immediate motor control for motor condition abnormalities.
However, they cannot check the details because it is pre-compiled as the provided FOC_Lib.lib.
Could you please provide the FOC library files for this sdk version?
also, please let me know how to build including the FOC library files in the current workspace.

thanks 

B.R,

  • Hi Robin,

    We have a open source version FOC example in our SDK named motor_control_universal_foc (SDK v2.03.00.07), customer could use it for details check.

    And for FOC library file build, in our motor_control_pmsm_sensorless_foc examples, it is included in link path, and no other operation needed.

    Best Regards,

    Pengfei

  • Hi Pengfei,

    I am a customer of Robin.
    My question is whether the sensorless example can be released so that the source code can be changed like the universal example.

    The sensorless example is locked with FOC.LIB.

    We need to stop the motor immediately and report the problem through LIN communication when an abnormality occurs in the motor like in the picture.

    The abnormality we report is various other than the high voltage warning that can be implemented using the User register like in the picture.
    We need to be free from stopping the motor and starting it again.
    However, the sensorless example is locked with the FOC.LIB file for operating the motor.
    If the universal example had the same motor driving algorithm as the sensorless example, I would have used it instead of the sensorless example, but there are many differences, such as the impossibility of Auto_handoff.
    Using the universal example is not a good idea.
    I would like to ask whether you can release the FOC.LIB file of the sensorless example like the universal example.

    Best Regards,

    Donguk

  • Hi Donguk,

    Sorry it is not unrealistic to release the FOC.LIB source code.

    About he universal example in SDK, the difference between closed source and universal is Dynamic Handoff vs Static hand-off. 

    Have you test you application based on our universal? 

    Best Regards,

    Pengfei

  • Hi, Pengfei.

    I used both source codes.
    As a result, there were some parts in the waveform that were different.
    For example, you mentioned that Auto_handoff doesn't work,
    but both the universal and Sensorless codes matched all possible parts of Userctrl/Userinput, but they were different.

    Sensorless has a register called RVS_DRV_CONFIG while Universal doesn't, and since the reserved register bits are different between the two codes, these parts are inevitably different, but I think this difference is minor and not the main reason for the different results.

    For example, when both Sensorless and Universal set Speed ​​​​​​​​​​Kp/Ki to 0 and enter closeloop, Sensorless will rotate at 92Hz while Universal will rotate at 67Hz even though it entered the same Handoff of 80Hz.

    Of course, if you increase Speed ​​​​​​​​​​Kp/Ki, both will go up to the RPM specified in Speedinput, but there is no doubt that they rotate in different ways. I'm not sure right now since both sources don't spin at their target RPM, but I think there will be a big difference in high RPM spin results between the two sources.

    Please release FOC.LIB if possible.

    I want to be able to freely control the motor to stop and spin again.

    Best Regards,
    Donguk

  • Hi Donguk,

    I'm sorry to tell that we are limited in providing source code of Library as  it  has multiple disclosures from other team.

    I will try to ask our expert for help on your questions and concern.

    Best Regards,

    Pengfei