Part Number: DRV8908-Q1EVM Other Parts Discussed in Thread: DRV8908-Q1 , MSP430G2553 Tool/software: Code Composer Studio Hi, I was hoping to use GUI Composer to build a custom eval program eventually running through a control sequence with a single button…
Part Number: DRV8908-Q1EVM Hello,
I've set up experimental hardware with the DRV8908 EVM and a PIC processor (18F2580). The PIC SPI port is provided by a production board where the SPI port is brought out to a stick header.
I'm trying to send and…
Part Number: DRV8906-Q1 Other Parts Discussed in Thread: DRV8908-Q1EVM The chip is DRV8906, and the evaluation board in my hand is DRV8908-Q1EVM. The current problem is that whenever I brake, a short circuit fault will be reported. I have to clear the…
Ahh okay!
In that case I would recommend 2x DRV8908-Q1 . Each output is rated for 1A. It is a fully SPI controlled device so it doesn't need too many GPIO inputs.
You can grab an EVM to try it out: DRV8908-Q1EVM Evaluation board | TI.com
Best, …
Hi Chris,
Thank you for your question.
Please use DRV8908-Q1 EVM document. DRV8908-Q1 and DRV8912-Q1 are same EVM.
https://www.ti.com/tool/DRV8908-Q1EVM
For USB cable, please refer outside of TI site like Digikey. We can find by searching "P/N…
Marcos,
The MCU support team doesn't check the motor driver forum. DRV8908-Q1EVM uses a MSP430 device as a microcontroller. You can get the detail hardware and firmware code design from the DRV8908-Q1EVM folder.
If you want to get a directly support…
Hi,
Thank you for your question. Please refer DRV8708-Q1/EVM product page on ti.com. DRV89xx are register/software compatible, just number of output channels are different. Please refer DRV8912-Q1EVMFirmware for DRV8906-Q1.
www.ti.com/.../DRV8908…
Hey Shoji-san,
Yuya Shoji said: Can the dead time be disabled?
No, the dead time is critical to prevent the MOSFETs shorting VM to GND (shoot-through). See 8.3.1.2.2 Cross Conduction (Dead Time) . And application report Delay and Dead Time in Integrated…
Hello,
The datasheet specifies there should be 2.5us between successive write gaps in 7.6 Timing Requirements . You might find unexpected behavior if you don't have this gap between the two 16-bit writes. Without that gap sure, two 16-bit writes back…
