• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 97 subscribers
  • Views 742 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.

LP-AM263: Assistance Needed: Module Overcurrent Issue with AM263x & DRV8316

Shahar Cohen
Intellectual 331 points

Part Number: LP-AM263
Other Parts Discussed in Thread: DRV8316REVM, TIDM-02018

Tool/software:

Dear TI Team,

I'm trying to run the universal_motorcontrol_am263x_r5fss0-0_nortos_ti-arm-clang_3phGaN example on the TI LaunchPad Sitara AM263x LP-AM263 with the DRV8316REVM, configured for DRV8316T using hardware mode (no SPI module).

DRV8316REVM HARDWARE To T NO SPI Configuration:

  • R9/R12 - DNP
  • R40/R45 - Tied to AGND
  • R37/R42 - Hi-Z
  • R38/R43 - Hi-Z
  • R41/R46 - Hi-Z, Tied to AGND, Tied to AVDD
  • R39/R44 - Tied to AGND

Pin Configuration Following Custom Board Example:

Configuration DRV8316REVM:

  • DRVOFF - GND
  • MCUVREF - 3.3V
  • NFAULT - 3.3V
  • NSLEEP - 3.3V

After building and running the example, when I set motorVars_M1.flagEnableRunAndIdentify to 1, it immediately resets to 0, with the reported fault being moduleOverCurrent.

Could you please help me identify the cause and suggest a possible solution?

Thanks!

  • 0
    TI__Genius 9590 points

    Hello,

    Please take a look at the TIDM-02018 design guide. We developed this software using an incremental build approach. Start at level 1 and debug your way up to level 4, step by step.

    Best,
    Masoud.

  • 0 in reply to Masoud Farhadi
    Intellectual 331 points

    Hi,

    After configuring user_mtr1.h according to my project on the F280025C and running the Level1 Universal Motor Lab, I am encountering undervoltage and module overcurrent faults.

    My power supply is 24V, but when checking the variable VdcBus_V, it only reads ~15V.

    The error originates from the runMotor1Control function, specifically in the following section:



    Could you please advise on what might be causing this issue and how to resolve it?

    Thanks!




  • 0 in reply to Shahar Cohen
    TI__Genius 9590 points

    If you increase up the DC bus voltage to 48V, what does the ADC measurement show? If it reads 30V, that means we need to change the ADC current scale factor.

    Best,
    Masoud.

  • 0 in reply to Masoud Farhadi
    Intellectual 331 points

    Hi, 

    I change to 38.91891891891892 as you mention
    And now its ~ 24V , but still moduleOverCurrent & underVoltage

  • 0 in reply to Shahar Cohen
    TI__Genius 9590 points

    If you're seeing both of these errors, it means there's a short circuit in your test. This is causing a spike in current and dropping the supply voltage, which results in undervoltage fault. Basically, you should be starting your tests at level 1 with the motor not connected to circuit. Like I said earlier, make sure to read the design guide and stick to the instructions first!

  • 0 in reply to Masoud Farhadi
    Intellectual 331 points

    Hi,

    As I mentioned, this is level one, and the motor is not connected.

    I have configured the hardware according to the custom board guide for the AM263.

    Please review my post carefully—we have replaced the DRV8316REVM with the DRV8316T following the DRV8316REVM setup.

    In addition, I have adjusted the ADC factor as you mentioned earlier.

    But as you can see, now there is one fault moduleoverCurrent.



    In addition I add the pin mapping in the main message, and the predefine. 

    We would appreciate any help.

  • +1 in reply to Shahar Cohen
    Intellectual 331 points

    Hi,

    I tried a few things that didn’t work:

    1. Increased the max current from 6A to 12A.
    2. Changed the drive mode to PWM6, both with and without the current limit. (I believe there might be an issue in the datasheet, as the connection to AVDD seems to be without a current limit.)
    3. Used the same wiring setup with the F280025C LaunchPad, which worked without any errors.
    4. The fault origin come from HAL_getMtrTripFaults.

    I would be happy for any expert help.

    TY Shahar