• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 30 subscribers
  • Views 2354 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.

Questions on Drv2605

Ravindra Babu
Prodigy 50 points
Other Parts Discussed in Thread: DRV2605L, DRV2605, DRV2605LEVM-MD, DRV2700

Hi,

We are working on a project to enable haptic feedback to the end user based on audio from the games. I had few questions regarding DRV2605 haptic chips.

1)      How many actuators\motors can be driven with one DRV2605 chip?

2)      Can you explain more about the broadcast mode when we are planning to put more than one drv2605 chip?

3)      Can we have the chips programmed with audio-vibe as default mode?

We need to freeze our design in 2-3 days. It would be great to get answers and any reference implementations.

Thanks,

Ravindra

  • 0
    TI__Intellectual 1940 points

    Hi Ravindra,

    Thank you for your interest in our Haptic devices!

    1) If you have the circuitry to properly select between motors/actuators, the limit should be as many as you would like. The DRV2605L EVM drives an ERM or an LRA, depending on which mode was selected. Please refer to page 26 in the DRV2605L EVM. In this EVM, an analog switch and a HI/LO signal from the MSP430 are used to select between actuators/motors.

    2) I will look into this for you. Could you please share more details on how you envision using broadcast mode?

    3) I do not think the chips can have audio-to-vibe as the default mode. I will look into this more to confirm and provide you with more details as to how to best accomplish this. Will you have an on board controller/processor?

    Please let me know if you have any more questions!

  • 0 in reply to Luis Cordova
    Prodigy 50 points

    Hi Luis,


    1) If you have the circuitry to properly select between motors/actuators, the limit should be as many as you would like. The DRV2605L EVM drives an ERM or an LRA, depending on which mode was selected. Please refer to page 26 in the DRV2605L EVM. In this EVM, an analog switch and a HI/LO signal from the MSP430 are used to select between actuators/motors.

    -  We want to drive multiple motors at the same time. In the EV kit today we have to choose one of the motor and actuator. Can this be done?

    2) I will look into this for you. Could you please share more details on how you envision using broadcast mode?

    - We want to drive at least 4 motors based on the game content on various parts of the body. If only one motor can be driven at a time by a drv2605, then we need to give a one drv2605 for every motor. 

    3) I do not think the chips can have audio-to-vibe as the default mode. I will look into this more to confirm and provide you with more details as to how to best accomplish this. Will you have an on board controller/processor?

    - Yes we do have a complete x86 processor with windows running on it. We can have a driver and send I2c commands but we just want to color code the boards and provide to the end user and provide a simple swapable mechanism for the end user.

  • 0 in reply to Ravindra Babu
    TI__Expert 8940 points
    Hi, Ravindra:

    we have an EVM called DRV2605LEVM-MD for multiple actuator applications.
    here you can find more information about this board : www.ti.com/.../drv2605levm-md

    the chip cannot be audio-to-vibe in default. it need to be configured by I2C commands to be that mode.
  • 0 in reply to Ravindra Babu
    TI__Intellectual 1940 points

    Hi Ravindra,

    Driving multiple motors/actuators with one driver typically results in poor performance or no performance at all. Poor performance could mean jumpy vibration from the ERMs, or inconsistent vibration strengths from each LRAs.

    It is important to note that our device uses a closed-loop control system to optimally drive the actuators and derives calibration and driving information from the back EMF of the actuator itself. Multiple actuators will look like one actuator or load, where there is the inherent manufacturing variation among the same set of actuators from the same company. The closed-loop system will derive inconsistent and incorrect information about the actuator(s) during operation and calibration. Using one driver per actuator ensures optimum performance as the device only sees one actuator with one constant set of specs and one load to deliver current to.

    What type of actuators are you considering?

    Have you considered using Piezo? Our DRV2700 device could drive multiple piezo actuators.

    One driver per actuator is still the best option.

    Luis Cordova

  • 0 in reply to Luis Cordova
    Prodigy 50 points

    Hi,

    Does TI provide windows I2C driver for this chip? We are trying to interface multiple boards to an X86 processor running  windows: 

    https://learn.adafruit.com/adafruit-drv2605-haptic-controller-breakout/overview

    Thanks,

    Ravindra

  • 0 in reply to Ravindra Babu
    TI__Expert 8940 points

    Hi, Ravindra:

    we don't have windows I2C driver for DRV2605L.

  • 0 in reply to Peter Li79
    Prodigy 50 points

    Hi Peter,

    We are daisy chaining various small haptics board as part of wearables. There would be only one I2C master on the system running windows which would be driving the various small boards daisy chained from one board to another. 

    We have a design ready with our team. Can you exactly point me to the right FAE who will help us review our design? IF you are the correct FAE, can you provide your email ID or can we get on a call for us to review?

    Thanks,

    Ravindra

  • 0 in reply to Ravindra Babu
    TI__Expert 8940 points

    Hi, Ravindra:

    which country are you in?

    we have a team in Dallas, you can contact Prakash, Arjun <a-prakash@ti.com>.

    Thanks.