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.

motor not running

Other Parts Discussed in Thread: DRV8301

I'm new in motor .. I have c2000 launcpad.. I found the drv8301 booster schematics from internet..And I made pcb..

Also I made all connection..

I used lab5b.out... But in my circuit , shunt resistor is changed by me..This resistors was 0.01 ohm 3W..But I didnt find this value..So I used 0.2 ohm 2 w resistor..

The other elements are the same as original schematic.. I connected the blcd motor.. I have a values like in the picture.. The short circuit current is very high.. Why it is so high? Also what is the reasons of not runnign of motor ? Thank you for helping..

Also my motor is bg40x50..
 
Also I cant see any signal output of drv8301  (SH_A ,B and C pins) .. Is the Drv8301 broken ? But I can see 3.3v on the Fault pin .. 

  • if you made a change to the voltage or current sensing you need to at a minimum update the user.h for the new USER_ADC_ values, and probably the FILTER_POLE as well. Did you follow the requirements in chapter 5 of SPRUHJ1 when making your changes?

    That's step 1.

    There could be any number of HW issues with your board also...always challenging to debug a full system like that. If you have a current probe it's worth seeing how the phases look and make sure the DC values and AC frequencies you expect to be generated during the Motor ID process are being created correctly.

    If you have a high speed motor make sure you use proj_lab02c for ID and not just proj_lab05b or 02a.
  • I didnt any changes.. I didnt use user.h it can seen in the picture.. Also today , I noticed the drv8301 is broken , so ı changed it.. I will try tomorrow..
  • if you changed the HW you need to have changed them correctly within specification, and change the SW.

    the bg40x50 motor looks to be 24V/2.1A so I'm not sure why you changed your HW before trying the solution. It would have worked perfectly reasonable.