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.

  • TI Thinks Resolved

CCS/TIDM-1003: How to start running the motor? Custom board, code is uploaded to MCU

Intellectual 260 points

Replies: 3

Views: 87

Part Number: TIDM-1003

Tool/software: Code Composer Studio

Hello! I have made a PCB with the same schematic as the TIDM-1003 design. I have uploaded the code that belongs with TIDM-1003 but I am unsure of how to make it start :) I try to follow the steps below: 

On step 4. I get a message when I click the "clock" symbol. I simply click "Yes" but am not sure if anything is wrong here:

In step 5. I cannot find the variables "Flag_enableSys" and "Flag_Run_Identify". Look at the figure below, am I looking in the correct place?

Would be grateful for any help :) BR Niclas

  • The subject matter expert is on limited availability, he will respond when he is ale to. Thanks for the patience.

  • Now I am getting somewhere, but I have problems. I am setting "gMotorVars.Flag_Run_Identify" and "gMotorVars.Flag_enableSys" to 1, and then immediately the inverter starts. But I get huge currents. Even when I have no load connected, the inverter will reach very high currents. I have the DC bus connected to a power supply, and have set a current limit on it.

    When no load is connected there probably shouldn't be any current going?!
  • In step 4, you need to include "proj_TIDM_1003.js file" by clicking "View->Scripting Console->Open File". You can also add some variables into the "Expressions" window by typing the variables.

    Before motor running with close loop, we strongly recommend to verify integrity of your own board’s signal chain first by using open loop test. MotorWare has two labs Lab_1b, Lab_1c for this purpose. For more details, please find the Labs User’s Guide in the MotorWare.

    Of course, the HAL file(hal.c) and User file(user.h) should be replaced with the one TIDM_1003 provides for building open loop test projects. Also, #include search path in the project properties should be updated if you’ve changed the hal file path.

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.