• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 29 subscribers
  • Views 217 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

DRV8353RS-EVM: For DRV8353RS-EVM, what causes an automatic stoppage of the motor?

Robert Uehara
Prodigy 30 points
Part Number: DRV8353RS-EVM

Tool/software:

An issue my team is having is we hit 1000RPM and anything greater kills the motor. The motor is using 2.8A or so at that RPM level with the GUI. We want much higher RPMs and are curious how we can circumvent our motor getting killed with the GUI. The "Fault Status 1" bits read 0x7FF & "VGS Status 2" read 0x7F0.

After many retries followed by cuts of the motor, the GUI no longer is able to get past the motor ID learning phase. As a result of that VGS Status 2 now has a GDUV flag and Fault Status 1 has a gate fault error (bit 8) as before.

  • 0
    Prodigy 30 points

    It seems the motor completely disengages from the GUI and gets cut, but the feedback of the motor stopping does not get received by the InstaSPIN GUI. Is there any advice to get past this?

  • 0 in reply to Robert Uehara
    TI__Genius 12231 points

    Hi Robert,  

    Thank you for using our forum. 

    Is the evm no longer able to get past motor ID after a full device reset and reverted any changes made? If so, that may imply with the faults flagged of potential damage to the device. 

    For this application,  what is the IDRIVE setting set to on the EVM? A setting that is too high may cause the large transients during motor operation that could cause issues and potential failure if operating at larger voltage/currents.

    Can we check the two above questions?

    Best Regards, 

    -Joshua

  • 0 in reply to Joshua Maize
    Prodigy 30 points

    HI Joshua,

    Our IDRIVE settings have been set to defaults from the start, which is IDRIVEP_HS set to 150mA and IDRIVEN_HS set to 300mA. IDRIVEP_LS is set to 150mA & IDRIVEN_LS is set to 300mA.

  • 0 in reply to Robert Uehara
    TI__Genius 12231 points

    Hi Robert, 

    Thank you for the follow-up, can we reevaluate the motor system behavior when the IDRIVE settings are reduced to their lowest settings? (IDRIVE set to 50mA/100mA) and observe the system behaviour when running identification?

    Can we also collect waveforms for VCP. VGLS, CPH/CPL, and nFAULT when in the motor in the ID phase before a fault is triggered and the sequence is terminated? This should better help us understand the root issue and whether potential transients may cause the device to flag an issue during operation. 

    Best Regards,

    -Joshua