• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 29 subscribers
  • Views 810 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.

DRV8301 fault

Hiroyasu Matsubara
Expert 1405 points
Other Parts Discussed in Thread: DRV8301

There is a question about the design using DRV8301. The target board contains Hercules MCU and DRV8301. The SPI communication between Hercules and DRV8301 is well,and when PWM signal generated on Hercules and into DRV8301,DRV8301 "fault" occures.("OCTNw" didn't occure) And,I read the "Status Register 1" of DRV8301 when fault occured,only the "FAULT" bit was indicated. And the problem occures even when any motor is connected to the target board or not. DRV8301 Powergood pin is fine,and DRVEN is asserted. Could anyone tell how to solve this problem ? I would appriciate if anyone would reply to my question. Regards, Hiroyasu
  • 0
    TI__Guru 55655 points

    Matsubara-san,

    Is the target board one of our TI Evaluation Modules or is it your own board?  Please provide full part number if it is a TI board as there are several that we support.  If it is your own board design, please provide schematic and layout.

    Is the external FAULT pin also cycling low?  My initial assumption is that you are getting a "false" over-current trip since it is occurring with no motor connected.  Or it is possible there is a short on your board that the DRV8301 is responding to.  Unfortunately, the OC bits in the status register are not "sticky".  This means the bits are cleared after reporting.  This most likely explains why you are not seeing accurate reporting of which channel is tripping OC.

     

  • 0 in reply to Ryan Kehr
    Expert 1405 points
    Dear Ryan Kehr, Thanks for your kind reply. We found a mistake on our design,and the "DRV8301 fail" doesn't occure after correcting our design. Regards, Hiroyasu
  • 0 in reply to Ryan Kehr
    Intellectual 335 points

    Hi Ryan,

    I saw this post and thought I would add my problem in here because the initial post seems similar.

    I have a DRV that is faulting for overcurrent (latched OC mode) and I am reading the status to figure out which FET it is tripping on (I am aware the status register needs two reads). What I get back is the status indicating a fault but no overcurrent flag or which FET it may have been. 

    I noticed in your reply in this thread that the OC flags are not "sticky" - so what is their persistence and what are the requirements to reading them before they go away? 

    I should also say that I know a OC fault is occuring because I can see it on the external OCTW fault pin. It goes low when the drive disables.

    Thanks,

    Jon