Haptics drivers from TI - DRV2605

paul20 · April 1, 2020, 12:55pm

Hi All, I’m trying to use DRV2605 from TI without any luck. Used datasht circuit and chked with Adafruit and Sparkfun breakouts. Get no response from either Arduino Nano sketches! need some expert advice, programming is not my strong point

RobertCNelson · April 1, 2020, 1:24pm

Hi @paul20, which DRV2605 break-out board are you utilizing for your project?

Adafruit has a nice example here, showing how to test with the basic example:

Can you share your work in progress schematic, or even a picture of your wiring setup? That could help diagnose your issue.

Regards,

paul20 · April 1, 2020, 1:37pm

Hi Robert, I was unaware of the boards when I ordered DRV8601 and 2605 from YKWho. The Cct I’m using is same as both Sparkfun and Adafruit, power and i2c. Uploaded ada and spark sketches on Nano, but get no action. Ive prepped 2x DRV8601 and 4x DRV2605 on purpose made pcb for breadboard. Im now stuck
rgds, Paul

paul20 · April 1, 2020, 1:39pm

I don’t knot how to include drawings etc.

RobertCNelson · April 1, 2020, 1:49pm

@paul20, you can attache most *.pdf or images by clicking in:

Regards,

paul20 · April 1, 2020, 1:50pm

Thanks, will do!

paul20 · April 2, 2020, 8:07am

DRV2605 Cct.pdf (56.0 KB)
This is what I’m using

paul20 · April 2, 2020, 8:42am

All C’s 1uF, All R’s 10K
I want to use smd ATtiny85 in place of the Nano to drive the 2605, as the PCB must be no bigger than 12 mm X 20 mm. The (now disused) ERM (555) board is 12 mm X 11 mm. This is a medical project.

RobertCNelson · April 2, 2020, 1:10pm

@paul20, which AVR, do you have physically connected to the DVR2605 today?

The Arduino Nano usually is an ATmega328 (with a real dedicated i2c port). While the ATtiny85 has a fake i2c (thru the USI peripheral), the ATtiny family need external pull-up’s when using the i2c mode (the internal AVR i/o pull-up can not be used on this device family with USI/I2C mode…)…

If your design is using the ATtiny85 today, you need to look at ATTinyCore, (if your using Arduino)…

Here are some migration notes:

github.com

SpenceKonde/ATTinyCore/blob/master/Migration.md

### ATTinyCore Migration Guide
This document describes the considerations for users of the Arduino IDE when migrating to ATTinyCore from other hardware packages that support the ATtiny line or other 8-bit AVR devices, and from the ATtiny84 to the ATtiny841.

### To ATTinyCore from other cores
Migration to ATTinyCore from other ATtiny hardware packages is typically straightforward - no code modification is typically required, however there are a number of features that require code changes to take full advantage of.
* Two different pin mappings have been used for the ATtiny84 on different cores. Both are supported by ATtinyCore; be sure to select the correct mapping from the Tools -> Pin Mapping menu.
* In order to support the full range of ADC channels, you must use the A# constants, or the ADC channel number when calling analogRead(), not the digital pin number. You may read from differential ADC channels by specifying channel number specified in the datasheets. You may read from the on-board temperature sensor via analogRead(ADC_TEMPERATURE).
* When using digitalRead/digitalWrite/pinMode, you must use the digital pin number, the A# constant, or the PIN_xn constants (for example PIN_B3 for PB3).
* ATTinyCore features a builtin universal SPI and Wire library - with other cores, you need to use libraries like TinySPI, TinyWire, USIWire, etc, with any libraries for SPI or I2C devices modified to use these libraries. With ATTinyCore, you may simply include SPI.h or Wire.h, and use unmodified libraries (the ones that would be used on an ATMega device). For the '841/441/828, when using I2C, select from the tools menu whether you want to support master, slave, or both - selecting both will significantly increase flash usage when Wire.h is included.
* ATTinyCore features a builtin Software Serial implementation named Serial on all parts except the '841/441/828/1634/2313/4313 (these parts have proper hardware serial). This uses the AIN1 and AIN0 pins (see the part-specific documentation pages for details); while this is named Serial to make it easy to port code from ATmega-based devices, it is still a software implementation: It is half-duplex (attempting to send and receive at the same time will result in sending and/or receiving gibberish), and sending and receiving is blocking (ie, the processor can do nothing else). Unlike SoftwareSerial, this uses the ACO vector instead of PCINTs, allowing PCINTs to be used by the application or other libraries. SoftwareSerial library may be used instead if desired.
* When using a serial bootloader on any part except the ATtiny828, the EERDY vector may not be used by the application (this is not used by the EEPROM library, and is usually not an issue). Additionally, if the part is reset during the very start of a serial upload, the bootloader will be corrupted - if this happens, the sketch will not work and the bootloader cannot be entered. To resolve this, connect an ISP programmer and "Burn Bootloader" again. Neither of these caveats apply when the serial bootloader is not used.
* When using direct port manipulation on the ATtiny828/841/441/1634, pullups are controlled by the PUEx register (see datasheet for details)

### From ATTiny84 to ATTiny841 (and from ATtiny44 to ATtiny441)
The ATtiny841 is largely compatible with the ATtiny84, only with additional features. There are a few differences to be aware of:
* The ATtiny841 has an additional timer, Timer2, which behaves identically to Timer1 - it is a 16-bit timer with all the same functionality.
* The ATtiny841 PWM channels can be remapped to different pins. If this is done, analogWrite() will not work (you must directly manipulate the relevant registers).
* The ATtiny841 allows the SPI and UART pins to be remapped. If this is done, the SPI library will automatically adapt; no other measures are needed.
* The ATtiny841 has hardware SPI and I2C slave, but no USI or hardware I2C master. Instead of using special Tiny-specific SPI/Wire libraries, and libraries modified to use them, use SPI.h or Wire.h - the Universal Wire and SPI libraries included with this core will automatically use the correct implementation of SPI or Wire for the hardware, and work with unmodified libraries (ie, ones meant for ATmega devices with normal SPI/I2C hardware).
* When using direct port manipulation, pullups are controlled by the PUEx register, rather than by DDRx set to input and PORTx set high.

This file has been truncated. show original

Regards,

paul20 · April 2, 2020, 1:33pm

Thanks for that Robert and Spence. Right now I want to do the easiest path to getting theDRV to work - and that is why I chose the Nano route initially. So lets stay with the Nano, Guys. Later the conversion to ATtiny will actually be simpler.
Regards

paul20 · April 2, 2020, 2:23pm

Hi Robert, I made a mistake above! Apologies - afterall I am 81! Got some progress. Loaded the Adafruit sketch agn and the serial monitor shows the “DRV test” and the Nano stops there, I unplug the i2c wires and the program happily runs on the monitor. Reset starts it over. Seems the DRV is not accepting the info. I also did a scan of the i2c addresses on the system and intermittently comes up with 0x5A, which is correct. I used the scanner in IDE examples, but why intermittently?
At least some progress

RobertCNelson · April 2, 2020, 2:51pm

HI Paul, no worries! This smells like a bus lockup, do you have any equipment to watch the SDA line (to see if the Adruino is holding the SDA line low…)? But let’s also quickly verify the i2c lines didn’t get reversed. Switching out the 10K resistors for 4.7K resistors might be an option, but let’s save that as a last resort…

Regards,

paul20 · April 2, 2020, 2:55pm

It would seem the DRV is not (able or bothering to) send the ACK to the Nano to get out of STANDBY mode. Is the Library Wire.h up to date? Or is there another version to be used?

paul20 · April 2, 2020, 2:57pm

I have a scope. I noticed before that the SDA line stays low with +ve going data.

RobertCNelson · April 2, 2020, 2:58pm

The Adafruit library seems pretty up to date: https://github.com/adafruit/Adafruit_DRV2605_Library/commits/master

paul20 · April 2, 2020, 3:00pm

Ignore my last, I’ll check again

paul20 · April 2, 2020, 4:03pm

The bus lines are hi with the signalling going low. Ok abt the library.

RobertCNelson · April 4, 2020, 9:11pm

Hi @paul20, just a quick update on this, i was able to get some parts from work for comparsion.

Adafruit DRV2605L: https://www.digikey.com/product-detail/en/adafruit-industries-llc/2305/1528-1346-ND/5356831
Adafruit Vibration ERM MTR: https://www.digikey.com/product-detail/en/adafruit-industries-llc/1201/1528-1177-ND/5353637
Arduino Nano (mega328p): https://www.digikey.com/product-detail/en/arduino/A000005/1050-1001-ND/2638989

Using the Adafruit DRV2605 Library with the Basic example works fine.

drv2605_sensor

Regards,

paul20 · April 5, 2020, 9:37am

I rebuilt the circuit on a copperless “vero” board (for wire-wrap) soldering every wire-wrap joint. The unit does the same thing - on power-up or reset, the internal (pin13) LED flashes once (as it should), the TX LED gives one very half-hearted flash, the serial monitor prints “DRV test”, then nothing. Supply voltage 4.8 from Nano 5v pin, bypassed with 1uF at DRV2605 and 10uF at feed-point. Pullup R =10K on bus lines.

paul20 · April 5, 2020, 9:47am

It did not work either. Then I replaced the DRV chip, and connected an ERM in place of LRA. Uploaded pgm and the vibrator ran without stopping. Suddenly everything died, Nano and motor. Voltage measured 1.3. Cut away DRV and volts returned to 4.9. DRV chip has popped, but wasn’t hot! We need to alter program to drive an LRA !!!

Topic		Replies	Views
Need vibration of piezo haptic actuator "z63000z2910z1z39" Motors, Actuators, Solenoids and Drivers electromechanical , motors-actuators-solenoids-and-drivers , epcos-tdk-electronics	0	763	December 17, 2021
ABX00062 Specifications Inquiry Development Boards, Kits, Programmers embedded , design-tools-and-resources , development-boards-kits-programmers	3	674	September 12, 2022
RTC DS3231 issues on Arduino Nano Integrated Circuits (ICs) clock-timing , analog-devices-inc-maxim-integrated	5	1050	February 14, 2023
Sabertooth 2x25 Motors, Actuators, Solenoids and Drivers dfrobot , electromechanical , motors-actuators-solenoids-and-drivers	6	985	August 16, 2021
Can I test an MCT8315Z motor driver on a breakout board before it’s populated with external parts? Motors, Actuators, Solenoids and Drivers	4	39	October 24, 2024

Haptics drivers from TI - DRV2605

Related topics