• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 117 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.

DRV8353F: nFault triggering issue

David Capdevila
Prodigy 250 points
Part Number: DRV8353F

Tool/software:

Hello,

We are currently usign the driver DRV8353FHRTAR controlled with a microcvontroller. We are using the hardaware version. We have found the follwing issues while using the driver.

- When enabling the driver, we have captured a dip in the nfault pin that triggers our error detection in the micronctroller, we would like to know why is triggering the nfault pin when enabling the driver during 2us.

- What is the reaction trime of the nFault pin from the point at which the errors arises until the pin is dirven low.

- Regarding the Hardware version, the OCP_MODE is configured by default to 01b? Is there any way to reconfigured it? If the mode 01b is used, the nfault pin should be driven low during 8ms? If not, where can we see this effect of the 8ms retry time?

Regards,

David

  • 0
    TI__Expert 4735 points

    Hi David,

    Apologies for the delay. I will look into this.

    Thank you,

    Joseph

  • 0 in reply to Joseph Ferri
    TI__Expert 4735 points

    Hi David,

    1. If you are able to provide waveforms at start up, that would be helpful in why you are seeing a fault. Would you be able to capture start up motor current as well as a picture of the waveform you see on nFault? Maybe there is a high inrush current on motor start up which is triggering your fault nFault.

    2. This is the deglitch time which for hardware version is set to 4us. 

    3. Yes, the OCP_MODE is 01b by default on the hardware version. In this version, it can be 8ms retry or it can be disabled. Do you see the nFault pin being lifted after the 8ms retry?

    Thank you,

    Joseph