DRV8353R: I would like to know the cause of the DRV8353RS motor driver damage.

youngtak han

Part Number: DRV8353R

I am using the DRV8353RS and have checked via SPI communication and only the GDUV error signal is active.
The rest of the signals are consistent with the datasheet. However, I have a picture like the one in the datasheet and looking through it, it looks like the activation is correct. I would be grateful if you could confirm this.

I checked that the PWM signal applied to the DRV8353RS through the DSP is normal, and the PWM output is normal when the motor is not connected, but when the motor is driven, the motor driver or mosfet is damaged.

So far, only phase A is being corrupted and I was wondering if you have any data on this phenomenon. Do I need to change the IDRIVE settings in this case?

over 1 year ago

0 youngtak han over 1 year ago

Prodigy 100 points

I'm attaching the schematic as a PDF file just in case. Do you see anything wrong with it?

These are the DRV8353RS peripheral circuit and mosfet schematics, respectively.

1030.DRV8353RS.pdf

MOSFET.pdf

0 Sarah Anthraper over 1 year ago in reply to youngtak han

TI__Prodigy 420 points

Hi Youngtak,

Thanks for the question. I will aim to provide feedback by the end of next week.

Best,

Sarah

0 youngtak han over 1 year ago in reply to Sarah Anthraper

Prodigy 100 points

Is it correct that GDUV is not enabled?
Or is it correct that it is activated when power is applied?
IDRIVE is set so that damage no longer occurs while the motor is running, but GDUV is always enabled.
I just want to make sure that the intermittent nFAULT signal is caused by GDUV.
I look forward to your reply, thank you.

0 Joshua Maize over 1 year ago in reply to youngtak han

TI__Genius 12231 points

Hi Youngtak,

I will be helping take ownership of this thread now, and would like to ask:

Can the GDUV fault on power up be reset and permanently cleared? It indeed may be the case of the fault triggering on power up and the bit being latched in the register although the fault-condition has already cleared
For this Phase A damage or odd behavior, can you help explain further what is happening (or provide waveforms comparing phase A to B and C)?

Thank you and Best Regards,

-Joshua

0 youngtak han over 1 year ago in reply to Joshua Maize

Prodigy 100 points

The problem that consistently occurred in phase A no longer occurs after adjusting IDRIVE. It seems that the motor driver and phase A MOSFET were damaged by not adjusting IDRIVE.
When applying 48V power to the motor driver and checking the SPI communication, GDUV is enabled.
The rest of the signals match the datasheet.

0 Joshua Maize over 1 year ago in reply to youngtak han

TI__Genius 12231 points

Hi Youngtak,

I understand and am glad to see there was a resolution for that.

Is this GDUV issue still occurring?

Best Regards,

-Joshua

0 youngtak han over 1 year ago in reply to Joshua Maize

Prodigy 100 points

Yes, we are still experiencing that issue.
An error signal (GDUV) is occurring when the motor driver is activated after power is applied.

How can I reset GDUV errors?

0 Joshua Maize over 1 year ago in reply to youngtak han

TI__Genius 12231 points

Hi Youngtak,

I understand, and to reset the fault you must apply a reset-pulse sequence to ENABLE, as detailed in the datasheet here: Please let me know if this fault still occurs after reset.

Best Regards,

-Joshua

Motor drivers

Motor drivers forum

DRV8353R: I would like to know the cause of the DRV8353RS motor driver damage.