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.

DRV8243-Q1: over temperature fault report problem

Part Number: DRV8243-Q1

Hello experts,

Hope you are doing well.

Our customer encountered a problem when utilize DRV8243-Q1 in thermal management project:

When they utilize heat guns to detect over temperature fault, but the device didn't report the TSD fault, however, the actual action comply with SCG fault: 

OUT1; OUT2 are set to 0, and OLP_CMP keep L,L,L.

After temp decrease down, the device would get back to normal state from SCG.

Could you please help analyze the problem.

Thank you.

Best regards.

  • Add information: The picture below is the waveform of the temperature test.

  • Hey Daniel,

    Are you using the Hardware or SPI version of the device?  If SPI you could read the  TSD bit in the FAULT_SUMMARY register to confirm. 

    Per 8.3.4.2 Over Temperature Protection (TSD) above I would expect OUT1/OUT2 and IPROPI to be HI-Z when a TSD event occurs.

    This overtemperature event/testing is happening when the device is awake, correct?  The table you posted is for Off-State diagnostics, which TSD is not a detectable event in off-state. 

    Regards,

    Jacob

  • Hello Thompson,

    Customer are using SPI version, however there is no TSD bit report when over temperature occur, the actual action is: 

    OUT1; OUT2 are set to 0, and OLP_CMP keep L,L,L (the waveform are shown in the latest reply)

    Besides, they did the test under off state, which is shown in the waveform.

    Looking forward to your reply.

  • Add my opinion, is there any special internal actions when temp arise under heat gun before thermal shutdown happen, that's to say, there are some other fault before TSD when temperature arise.

    So what's your idea by professional perspective, can you help the process in detail?

  • Hey Daniel,

    It appears to me the device is performing as expected - it detects TSD, waits for device to cool down, then turns back on.  Can you clarify what the problem is?

    The device does not have any other fault or actions before TSD (no warning).  You can change TSD_RETRY to change whether fault reaction is latched or retry:

    You could set reaction to latched to make it easier to read TSD bit before it resets

    Regards,

    Jacob