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.

DRV8825: NFAULT pulled down and fail to run

Part Number: DRV8825

Hi  team,

My customer is using DRV8825 for step motor driving. Days ago they discovered 5 failure parts out of 1000. The failure is that the NFAULT node is pulled down after there comes STEP signal, and no output current, as shown in below Fig.1 and Fig.2.

Fig.1

Fig.2

 

They have conducted cross experiments: put a failure part into a new board, still failure; put a new part into the original board, failure disappears, which indicates that the failure goes with the device.

Below are the schematic, the data sheet of the motor they are using and the normal part test results.

Fig.3 schematic

Fig.4 motor spec

Fig.5 normal part

Fig.6 normal part

I wonder do this part have such problem before? Or what may be the cause for this problem?

Looking forward to your reply! Thanks!

George Zhao

  • Hi George,

    What are the voltages on VCP and V3P3OUT when nFAULT is asserted?
    What is the sequence from VM rising to the first STEP being issue?
    How much time is between each step in the sequence?
    What action is required to remove the nFAULT?
    toggle nRESET
    power cycle
    toggle nSLEEP
    If the motor is disconnected, do the outputs operate?

    If toggling nRESET, nSLEEP, or power cycle removes the fault, please ask the customer provide the following scope captures.

    Zoom in (10us/div) triggering @ nFAULT falling.
    Add nSLEEP, AOUT1 voltage, and AOUT2 voltage in one scope capture.
    Replace AOUT1 and AOUT2 with BOUT1 and BOUT2 in a second scope capture.

    Also, please provide the markings on the top of the package.
  • Hi Rick,

    Thanks for support.

    The VCP and V3P3OUT voltage as shown in below picture:

    Also, toggle nRESET, nSLEEP or power cycle did not remove the nFAULT. When disconnect the motor, the output is constant high. 

    Thanks!

    George

  • Hi George,

    If toggling nRESET, nSLEEP, or power cycle does not remove the nFAULT, it appears there is a short in the system. OCP is occurring and the device does not recover. Removing the load corrects the problem.

    A quick check to determine if the AOUT1/2 or BOUT1/2 is causing the fault is to disconnect BOUT1/2 and try to run the motor.
    If the nFAULT no longer asserts, BOUT1/2 appears to be the problem side.
    If nFAULT still asserts, disconnect AOUT1/2 and connect BOUT1/2.
    If nFAULT still asserts, the problem could be with both sides.
    Please add the requested scope captures zoomed in.
  • Hi George,

    Do you have any updates?
  • Hi George,

    We have not heard from you in some time, and are assuming your issue has been resolved. If you still have questions, please reply to the post or if the post is locked, please select "+ Ask a related question" at the top of the post.
  • Hi Rick,

    Sorry for late reply because of the Chinese new year holiday.
    I have requested the customer to do the test to see if short happened.
    Also is there any chance that the short may happened inside the device?
    CQE has done the IV test for this part and the result is good. Further analysis is ongoing too.
    Thanks!

    George