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.

DRV8705-Q1: Fault function through SPI/HW

Part Number: DRV8705-Q1

Hi team,

I have some questions about the FAULT function.

  • For SPI variant, all fault information can be read by SPI, right? If yes, I can leave the Fault pin NC?
  • For HW variant, there’s no SPI channel, I can't get the fault information by HW, right? If yes, I must use nFault pin to read the fault indicator?
  • If there have two solutions for fault detected(just for common detection: overload, openload, overtemp), so the solution 2:use fault pin may have higher response time and reliability, right? And is our recommended solution?
    1. Use the current sense value to fault indicator
    2. Use the fault pin to indicate

Thanks!

Best Regard,

Ethan Wen

  • Hi Ethan,

    For SPI variant, all fault information can be read by SPI, right? If yes, I can leave the Fault pin NC?

    That is correct.

    For HW variant, there’s no SPI channel, I can't get the fault information by HW, right? If yes, I must use nFault pin to read the fault indicator?

    That is correct. in this case nFAULT should be pulled up to external supply.

    use fault pin may have higher response time and reliability, right? And is our recommended solution?

    For both solutions, monitoring faults through SPI or nFAULT pin, there will a small delay from when the fault actually occurs and when the fault can be read through the nFAULT pin or by reading the status registers. Typically this delay is very fast so there is no major difference between the response time between the two solutions. It is all up to the designer to determine which solution works best for their application.