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.

DRV2667: How to diagnose?

Part Number: DRV2667
Other Parts Discussed in Thread: DRV2605LHello. Sorry being novice again. Now I am trying DRV2667 with Samsung piezo actuator. But, I tried the simple example found in below, but nothing happens with the actuator. >8.3.2 Typical Usage Examples >8.3.2.1 Single Click or Alert Example THe DRV667 chip is visible onm I2C bus and no error writing to its registers. BUt however after setting GO bit to 1, I can see no movement on the actutator. Then I tried with another unit of DRV2667 breakout board, another unit of Piezo actuator, but the resulr is the same. The queastion may sound vague but where I should look into, or which is the step-by-step procedure to diagnose the problem? I think I may be measuring the voltage on motor output pins from DRV2667. That should give me some hint? I am connecting this DRV2667 breakout board to Arduino compatible chip.
  • Update:

    I have checked (reading over I2C) that the data I have written on page 0 (control) and page 1 (header/waveform).
    So, at least the chip is functioning so that read/write over I2C is as expected.
    The issue is that actuator does not produce any sound/vibration.
  • Hi,

    What type of DRV2667 breakout board are you using? Can you share the schematic.
    Next would be to verify the device is being pulled out of standby mode. Can your readback the registers to make sure the writes are working correctly?
    Then verfiy if the boost voltage is correct based on your setting and resistors.
  • Thank you for your comment.
    I think I will check the actual voltage after getting my oscilator tool.

    The breakout board (Piezo Haptic Flex Module) is the one from Fiber labs.

    >would be to verify the device is being pulled out of standby mode.

    How can I check if the chip is out of standby mode?

    Is it enough that register 0x02 bit 6 (STANDBY) is cleared by writing 0 there?
    (But I do not see it being 1 at the first place.)

    >Can your readback the registers to make sure the writes are working correctly?

    Yes, I can read the same data as I have written to page 0 and 1 registers.
  • The device will turn on in standby mode (register 0x02 = 0x04). When you write this register to 0x00, it will be taken out of stndby mode and there should be a noticable increase in current supplied to the chip (10uA goes to ~130uA).
  • Hello.
    I tried some and now it is working with one of my configurations.

    I am driving this with Adafruit Pro Trinket (5V), and it seems I have problem when I connect this breakout module alone.
    If I have other I2C devices (together on my protocype board), I can see the Samsung actuator is making sound (i.e. "zzzzzz!").

    I also can see quick waveform of voltatge on my oscilator.

    I suspect my problem came from I2C instablity or pull-up register values, but I have not investigated it further yet.
    I think I will revisit this anyway after I became more familiar with I2C debugging with other measurement tools.
  • For a record.
    I further looked into thos, and I think instability I observed was caused by narrow power/gnd connection.

    I was still experiencing the issue (DRV2667 registers are OK, but no vibration on actuator).
    I was tryng this on bread-board, the I2C 5V power and BND connections were on bread-board jumpers (a few jumpers between MCU 5V/GND and DRV2667 VCC/GND).
    Check with multi-meter, I did not see voltage current on actuator.

    But if I added direct (one segment) jumpers between MCU 5V/GND and DRV2667 VCC/GND pins, I could see voltage current on atuator and actuator vibrated.

    If I try the same with DRV2605L, I did not see it, so DRV2667 is more sensitive to the power/GND connection response?
  • Hello,

    The DRV2667 will pull much higher peak currents than the DRV2605L. For this reason, the power may be more sensitive.