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.

TMS320F280049C: InstaSPIN GUI with customer's board

Part Number: TMS320F280049C
Other Parts Discussed in Thread: LAUNCHXL-F280049C, BOOSTXL-DRV8320RS, DRV8320, C2000WARE

Hi Experts,

A customer would like to use "C2000 InstaSPIN Universal GUI" with their developed board.
Do we have any document which describes how and where the SW has to be modified or developed?

For example, the Labs for LAUNCHXL-F280049C + BOOSTXL-DRV8320RS are utilized as reference.
What source codes have to be modified and how?

Thank you very much for your kind explanation.
Best regards,
Hitoshi

  • Don't need to change any extra source code for GUI, even don't need to re-design the GUI if you don't change the object variables in the example projects. You might take a look at the below link about the GUI composer.

    https://dev.ti.com/gc/designer/help/GC_UserGuide_v2/overview.html

  • Hi Yanming,

    I do not change the GUI but I would like use it with the customer's board.
    The GUI "C2000 InstaSPIN Universal GUI" works with LAUNCHXL-F280049C + BOOSTXL-DRV8320RS.

    On the other hand, F280049C is utilized on thier board but motor drivers are different from DRV8320.
    Moreover, the PIN assignments are also different from the LAUNCHXL-F280049C + BOOTXL-DRV8320RS.

    Now, could you please let me know to work with Lab05 on their HW?

    Thank you very much for your kind help.
    Best regards,
    Hitoshi

  • Hitoshi Sugawara said:
    Now, could you please let me know to work with Lab05 on their HW?

    Works from update symbols (*.out) customers project dropped into run time GUI target folder. Good to disable drv8320rs init calls perhaps in user.h? 

  • HI Experts,

    Could you please teach me how I should modify the source codes from the Lab05 to work with the customers's board?

    Best regards,
    Hitoshi

  • lab 5 works with GUI using the symbols file (lab5.out) if customer keep variable names the same, no problems. I don't think anyone in the forum is going to show your customer how to program their hardware.  

    My recent point ST produced SDK for motor drive source with speed control PI and update cycles for FOC. TI approach is to analyze every aspect of motor torque and speed control and have customers with more questions than answers. It would seem customers should not use (lab5.c) to control the ePWM module in my opinion as it is very basic configuration. Seems to omit duty cycle updates outside of ROM calls to FAST and or pre-charge functions for HV 1/2 bridge gate drives. Note dead band (hal.c) is always enabled adding to switching losses in efficiency. The only life boat might come from fast current loop cycle scavenging (FCL) but I'm not sure the x49c even does that or what is required at this point. 

  • Hi GI,

    I appreciate your comment, but I would like to have the advice from the application engineers for TI C2000 team.

    If the GUI is available for the customer, it helps a lot for their development.

    Thank you and  best regards,
    Hitoshi

  • You might take a look at the InstaSPIN lab guide, and follow the operation instruction to run/debug/change the labs step by step, and then use the GUI according to the GUI guide. Both guides can be found in the folder of MCSDK as below.

    \ti\c2000\C2000Ware_MotorControl_SDK_2_01_00_00\solutions\common\sensorless_foc\docs

    You only need to change the user.h for different motors if you are using TI’s EVM kits.

    In most cases, you just need to change the hal.c, hal.h and user.h if you want to implement the example labs on your board.

    You can use the GUI directly if you don't change the "MOTOR_Vars_t"  struct definition. 

  • Hi Yanming,

    Now I am working with a customer to modify hal.h, hal.c and user.h in order to adjust their HW.
    If I find any questions, will ask you locally.

    Thank you very much for your kind guideline for the modification.

    Best regards,
    Hitoshi