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.

DRV8308: DRV8308 - dosen't behave as expected.

Part Number: DRV8308

I set the driver.

First I config the registers

//1.Use basic sine mode - default
reg_val = 0;
DRV8308_WriteRegister(DRV8308_REG03, reg_val);
      
//2.Set the FG select to use the TACH input signal + Clock PWM mode
reg_val = (0x01<<4) | (0x03<<2);
DRV8308_WriteRegister(DRV8308_REG00, reg_val);

Then I set halls according to the table - state 3

if (dir == 0)
{
     HALLU_HI;
     HALLV_LO;
     HALLW_HI;
}
else if (dir == 1)
{
     HALLU_LO;
     HALLV_HI;
     HALLW_LO;
}

Then I set pins
DIR = 0
ENABLE = 1

And finaly I apply PWM (16khz) to CLKIN and FGINN/TACH pins.

According to the table I should see
UHSG = PWM
ULSG = 0
VHSG = 0
VLSG = 1
WHSG = 0
WLSG = 0

But I see all 0 and only VHSG I see weird signal - amplitude 1 volt, pulse width 5ns,
period between pulses 5ms.

What should I do to fix the problem?

  • Hi Evgeny7,

    We will investigate and reply by tomorrow.

    While waiting can you provide a little additional information?
    Have you monitored the FAULTn pin to determine if there are any faults? If there are faults what does register 0x2A report?
    What are the markings of line 2 and 3 on the top of the package? If you cannot determine the characters, feel free to attach a photo of the top of the package.

    Thank you.
  • I'll read and report the value of 0x2A.
    The lines on the package

    DRV8308

    TI 7BIC
    CJ7E G4

    The value of the 2A register is inconsistent. 

    Sometimes it's 0x00 - no errors.

    Sometimes it's 0x01 - OCP.

    Sometimes it's 0x10 - CPFAIL.

    I'll attach the schematics.drv_power.pdf

  • Hi Evgeny,

    Sorry for the delay.

    PWM should not be connected to FGINN. It should either be connected to a logic level signal indicating the speed of the motor or set up as shown in Figure 27.

    Also where are the local VM filter capacitors (0.1uF at the VM pin of the DRV8308, and typically another 0.1uF from VBUS to GND at each phase. Please refer to the DRV8308EVM as an example.

    If you are reading 0x01 (OCP) or 0x10 (CPFAIL), these should be understood before trying to run the motor.

    One method to try to determine the cause is to disconnect the motor load but leave the hall sensors connected. If possible, turn the motor by hand to confirm the outputs are correct and there are no faults. Once this is confirmed, the next step is to re-connect the motor and run.
  • Hi Rick,
    I'm trying to run DC motor in H-Bridge topology.
    As we discussed here
    e2e.ti.com/.../642030
    I understand I should connect FGINN pin to let the driver think the motor is running - so it could set the appropriate signals on the gates.

    And I get OCP without connecting the motor. First I want to see correct signals on the gates.

    Did I miss something?

  • Hi Evgeny7,

    Thank you for reminding me of the prior discussion. The PWM connection is needed.

    Let us start with the OCP.

    How much current are you running through the FETs?
    Where are the local ceramic VM capacitors for the DRV8308 and FETs?
    Are the OCP settings correct? Do you have enough deglitch?
    Have you captured the VDS voltages just prior to the fault?
  • Hi Rick,
    I didn't connect the motor so no current should run. In my schematics (attached above) I placed the capacitors as in the evaluation board.

    The problem I don't see the right signals on the gates - say in state 3 - U high side should be PWM and V low side should be high.

    I'm not sure the registers settings are correct. What is preferable values?

  • Hi Evgeny,

    Is VREG active (~5V) when you are trying to observe the gate signals?
  • Yes. I see also HALLU = 5v, HALLV = 0v, HALLW = 5v as it should be in state 3 (according to the table).
  • Hi Evgeny7,

    Would you please click the resolved button. We will continue to work the issue via private communications.

    Thank you.