Part Number:DRV10983

Hi,

Our customer wants to control 50V Brush Motor. Could you please provide a solution?

Thanks.

Kevin Xiong

Part Number:DRV10987

I need a motor controller to control a bldc pancake motor. This motor has 4 coils fed with 24vdc at 90 degrees apart. It has a perm mag. Your part is 3-phase and does not do this. Any way to solve this?

Part Number:DRV11873

DRV11873 can not start and spin up the BLDC in small chances, only removing and reconnect the power can fix this.

When this issue happens, RD, FG pin is pulled high, CPN pin is pulled low, U V W COM pins are in DC voltage.

RD pulled low should be indicating a lock protection? What causes this situation?

When motor is running as expected, FG output frequency is 150Hz.

Original link:e2echina.ti.com/.../158369

Part Number:DRV8320

I’m trying to design based on the leakage current of the DRV8320 but the leakage seems to change based on the resistors I use. So I’m thinking it’s some kind of resistance between the charge pump voltage and the SHX pins.

So… I basically need to better understand what is causing the leakage current for me to try to come up with a model.

1)      What is causing the leakage current exactly at SHX in the DRV8320S when in independent mode and all FETS off?

2)      Can I model this leakage as a resistor between SHX and VCP or VM?

Part Number:DRV8842

HI All,

Am having an issue with the HBRIDGE DRV8842 and the behavior is different in EVM and in my board.

The schematic is pretty much the same.

I have document my observation in the word document.

Can someone please help?

We are interfacing STM32F4 (MCU) with DRV8842PWPR

Motor:

AE200: 24VDC, Ampere Draw Max,

1.38Amps Average, Peak Starting Current 9A for 3.22ms

HBRIDGE Setting:

VREF: 1V

ISENSE: 0.1Ohms

ICHOPPING CURRENT: 2A(1/(5*0.1)

ICURRENT SETTING :(I4:I0)=11111

Sleep,Reset,IN1, IN2 ,I[4:0] controlled from MCU.

Power Supply:

The HBRIDGE is supplied by 24V Supply from board.

Schematic:

EVM Schematic:

Board Layout:

Bottom Layer:

Top Layer:

Issue:

The DRV8842 doesn’t drive the motor consistently and triggers the fault when OUT2 or OUT1 gives 24V at times.

The DRV8842 EVM works perfect with the motor and the one on my board doesn’t.

The schematics is pretty much similar with the EVM.

Normal Working when not driving motor:

Case 1(Fault Trigged):

But the above doesn’t happen in the EVM.

Is it because of the starting current of 9A for 3ms which is causing this?

Case2:

The HBRIDGE is not responding to the commands on IN1 & IN2 on OUT1 & OUT2.

Hint:

1. I powered the EVM with my board’s 24V and the board works fine thought the 24V dips to 16V when starting the motor for 12ms.
2. I have a bulk of 100uF 63V aluminum similar to EVm on board.
3. I have the same sense resistor value of EVM (0.1Ohms as per EVM BOM)
4.  
5.  

Can I send the HBRIDGE to TI for RMA and dechiping it for analyzing?

Questions:

1. What is the OCP response time and the Isense Response time (is ISENSE 3.7us?)
2. How to limit the inrush current of the Motor if HBRIDGE doesn’t do it?
3. Why the H Bridge allows to rise the current and doesn’t go to PWM mode when exceeding the chopping current?
4. Why the EVM behaves the correct way?
5.  

 (Please visit the site to view this file)

Part Number:DRV8412

Hi all

Would you mind if we ask DRV8412?
Please refer to the attachmentfile, and could you give us the reply?
(Please visit the site to view this file)

Kind regards,

Hirotaka Matsumoto

Part Number:DRV8871

We design full bridge with DRV8871 to drive brush motor; And we need INA199 to enlarge the voltage to get the current；

And question is how to handle the all connection of GND? Such as MCU(GND) and DRV8871(GND)and INA199(GND) 

Part Number:DRV10987

Hi,

I am working on BLDC motor application using DRV 10987. I wanted to know regarding GUI based programming options for DRV 10987. 

Is DRV109xx EVM Graphical User Interface based software for evaluation kits only OR can it be used for custom made boards ?

Part Number:DRV8703-Q1

I am having some troubles communicating with the drv8703-q1 eval baord through SPI.  

I am running at 500Khz baud rate, 16 bit data transfer & writing  to address 0x02 and data value (0x1A) to enable the PWM ( 00010000 00011010) .

I am able to write to the DRV eval board through the TI GUI.

MOSI (microcontroller) connected to SDI (DRV board)
MISO (microcontroller) connected to SD0 (DRV board) (3.3V signals)

We are unable to read or write SPI to the eval board. I have removed the 0 ohm resistor from R29 (nSCS) on the eval board.

Part Number:UC3717A

Hi

What is the maximum operating frequency for this H-Bridge?

Thanks

Tony

Part Number:DRV8830

DRV8830 is unable to enter sleep mode when IN1 and IN2 are set to low, the DRV8830 power consumption is still more than 400 uA.

Part Number:DRV10983-Q1

I am using DRV10983-Q1 for fuel pump application. When I used EVM module I could able to meet 14 LPH. but the same DRV10983-Q1 with customized PCB is not able to meet the same flow. 

BOM wise everything is same. 

Part Number:DRV8872

We use DRV8872-Q1 in Self-locking charging gun.The device can't load by Electronic load,but it is nomal by resistance and relay,the upper bridge is directly to low bridge once connect Electronic load.

Part Number:DRV8870

Good morning!

I would like to check to make sure that the signal I am delivering to both IN1 and IN2 are within tolerance and can be used without damaging the the driver. As you can see from the included scope shots, the waveform does dip below ground to about -200mV. The datasheet does claim an absolute max of -300mV but I would like to know if there would be any foreseeable issues with my use case. IN2 is the same waveform but simply phase shifted.

Respectfully,

Lucas Schulte

Part Number:DRV2700EVM

Hi

We have bought 4 pieces of DRV2700EVM recently, and tested them right after their arrival, finding that three of them worked well with correct amplification while the rest one only doubled the input voltage as output. After our first test, we went back to check whether the wrong amplification was induced from human error. Just after we connected and turned on the power supply of DRV2700EVM, a lot of smoke came out from the circuit board, and we turned off the power supply immediately. We then checked circuit and found one circuit line burning out.

        We want to make an exchange to our local supplier and they asked us to provide a complete test report to your engineers in order to check if any of the test step was wrong, leading to the failure of the circuit.

        Here are our test steps:

1. We set our jumpers as follows:

JP 2, 3, 4, 12, 13: Connected

JP 5, 6: Opened

JP7, 8, 9: PU

JP10, 11: VIN

1. Connect TP8 to ground and connect DC_IN to a voltage supply supporting continuous square wave signals ( the power of voltage supply is off). The square wave signals have peak to peak voltage of 2V along with a DC offset of 1V.
2. Connect J2’s + port to a 5V DC voltage power supply and – port to ground. ( The power supply is off.)
3. Connect the high voltage output to the Oscilloscope: Vin+ to Channel 1, Vin- to Channel 2, and GND to both channels’ ground. To assure Input and Output have a common ground, connect GND to TP8.
4. Turn on the voltage supply of J2 and turn on the power supply of DC_IN.
5. Check the result on the oscilloscope.

Since we didn’t record the output result of the wrong amplification signals before the circuit burned out, we can only provide the output signals of the rest well-functioning drivers and of the damaged drivers:

The yellow curve represents the signals of Ch1, while the blue curve represents the signals of Ch2.Both the signals show square wave with peak to peak voltage of 50V. The purple curve is the difference of signals in Ch1 and Ch2, revealing a square wave with peak to peak voltage of 100V (50X amplification rate).

        However, the damaged driver shows no amplification, even no output signal when measuring.

        Please leave any comment if find any incorrect setup or step in the test step description above. Thank you.

Part Number:DRV8662

Hello there,

I am facing a problem while realizing the DRV8662 circuit practically. 

I want to drive 1µF piezo stack with this driver. My piezo stack operates on 0 to 75V and I want to drive it on step response or DC voltage for around 1Sec. Is it possible with this driver?

I did simulation in TINA spice software below is the simulation result of my circuit. 

I got the simulation result for the above circuit as below.

I solder the DRV8662 driver on PCB board shown below and connect the same circuit as shown in TINA schematic. 

I gave the same input as shown in a simulation but in an actual circuit on a breadboard, I got the very different result. On the output pin, I got 3.2V as shown below. 

We can see from the simulation that, at the FB pin I should get the 1.3V signal instead I got 160mV.

At the capacitor C2 I should get 38.32V as per simulation instead I got 2.32V.

what should be the problem for the error?

Part Number:DRV2605L

Hi,

We’re trying to get a bit more clarity around using the IN/TRIG pin to input a PWM signal to vary the amplitude of ERM drive strength using the DRV2605L.

 I have a couple questions:

1) Is it possible to vary the amplitude of an ERM drive using PWM interface? 

2) Is the last sentence of the first paragraph in section 8.3.5.1 below correct?  Is this really applicable to standby mode?  Can this mode be used with an ERM or is specific to an LRA?

3) Are there additional details around the appropriate register settings for the PWM input mode of operation?

>>>>>>>>>>>

8.3.5.1 PWM Interface

When the DRV2605L device is in PWM interface mode, the device accepts PWM data at the IN/TRIG pin. The

DRV2605L device drives the actuator continuously in PWM interface mode until the user sets the device to

standby mode or to enter another interface mode. In standby mode, the strength of vibration is determined by the

duty cycle.

For the LRA, the DRV2605L device automatically tracks the resonance frequency unless the LRA_OPEN_LOOP

bit in register 0x1D is set. If the LRA_OPEN_LOOP bit is set, the LRA is driven according to the frequency of the

PWM input signal. Specifically, the driving frequency is the PWM frequency divided by 128.

 <<<<<<<<<<<<<<<<

Thanks,

Sal

Part Number:DRV2667

We have designed a 4-layer PC board with (5) DRV2667 devices on it.  We closely followed the recommended PCB layout from the datasheet, but overlooked one feature-- we did not ground or provide thermal vias on the thermal pad.  Pins 4-6 are grounded to a copper area.

In addition we inadvertently used a 50V rated capacitor on the BST output (which is programmed for 100V).

Several devices have failed when the boost converter is switched on even with no piezo connected.  After the failure the parts exhibit a low (10's of ohms) resistance from BST pin to GND and the part draws excessive current.

Is the GND connection on the pad mandatory for correct no-load operation of the part?  Or is it only required when driving a load to cool the device?  We do plan to revise the PCB layout but I would like to be confident this is causing the failure.  Obviously we will also replace the under-rated capacitor.

Any insight into the type of over-stresses which can cause a catastrophic failure of this part would be helpful.

Thanks!

Part Number:DRV10987

Hi,

I am using DRV10987 with my smart car application.,I have done what I can with Turning Guide.However,i can't spun my motor with under configurations.Here is my motor parameter and tested data:

void DRV_init(void)
{

		i2c_init(i2c0,100*1000);

		i2c_init(i2c1,100*1000);
 
		systick_delay_ms(1);				//Wait for set up 1ms

		do
		{
 
			i2c_write_reg(i2c0,DRV10987_Address,EECRTL,0x80,0x00);				//Setting EEPROM Access permission and DISABLE!!!!!!!! the motor

			i2c_write_reg(i2c0,DRV10987_Address,EEPROM1,0x00,0x00);				//clearer EEPROM Access code

			i2c_write_reg(i2c0,DRV10987_Address,EEPROM1,0xC0,0xDE);				//Setting EEPROM Access code

			gpio_init(G0,GPO,0);

//			systick_delay_ms(1);				//Wait for set up 1ms

		}while(i2c_read_reg(i2c0,DRV10987_Address,EEPROM2) != 0x0001);		//Setting EEPROM able to read

		gpio_init(G0,GPO,1);

		i2c_write_reg(i2c0,DRV10987_Address,CONFIG1,0
																								| p5_SpectrumControl_MASK
																								| FG_both_open_and_close
																								| FG_Only_Close
																								| FG_POLES(16),
																								0
																								| CLK_ADJ_SELECT(0)		  //0:FULL 1:HALF
																								| 0x5B );								//Setting to 3.5R


		i2c_write_reg(i2c0,DRV10987_Address,CONFIG2,0
																								| 0x0A,									//Page 24
																								0
																								| CommAdvMode(0)					
																								| 0x02  );									//Page 37
		
		
		i2c_write_reg(i2c0,DRV10987_Address,CONFIG3,0
																								| ISDThr_80ms
																								| BrkCurThrSel(0)
																								| BEMF_HYS(0) 
																								| ISDEn(0) 
																								| RvsDrEn(0)
																								|	RvsDrThr_6P3,								
																								0
																								|	OplCurr_0p4			
																								| OplCurrRt_6
																								| BrkDoneThr_0 );							

		
		i2c_write_reg(i2c0,DRV10987_Address,CONFIG4,0
																								| AccRangeSec(0)
																								| StAccel2(0)
																								| StAccel(1),								
																								0
																								|	Op2ClsThr(1,10)			
																								| AlignTime(6) );

		i2c_write_reg(i2c0,DRV10987_Address,CONFIG5,0
																								| OTWarmingLimit(0)
																								| CloseLoopStuckLock(0)
																								| OpenLoopStuckLook(0)
																								| NoMotorLock(0)
																								| AbnormalKtLock(0)
																								| AbnormalSpeedLook(0),								
																								0
																								|	SWiLimitThr(0)			
																								| HWiLinitThr(0) 
																								| IPDasHWlLimit(0)  );


		i2c_write_reg(i2c0,DRV10987_Address,CONFIG6,0
																								| SpdCtrlMd(1)
																								| PWMFreq(0)
																								| KtLckThr(0)
																								| AVSIndEn(0)
																								| AVSMMd(0)
																								| IPDRIsMd(0),								
																								0
																								|	CLoopDis(0)			
																								| CIsLpAccel(0) 
																								| DutyCycleLimit(0)  
																								| SlewRate(0)  );


		i2c_write_reg(i2c0,DRV10987_Address,CONFIG7,0
																								| IPDAdvcAg(0)
																								| IPDCurrThr(0)
																								| IPDClk(0),								
																								0
																								| CtrlCoef(4)  
																								| Deadtime(10)  );

		
		i2c_write_reg(i2c0,DRV10987_Address,EEPROM5,0x00,0x06);

		while(i2c_read_reg(i2c0,DRV10987_Address,EEPROM2) != 0x0001);

		i2c_write_reg(i2c0,DRV10987_Address,EEPROM5,0x00,0x02);

		while(i2c_read_reg(i2c0,DRV10987_Address,EEPROM2) != 0x0001);

		i2c_write_reg(i2c0,DRV10987_Address,EECRTL,0x00,0x00);

		systick_delay_ms(5);				//Wait for set up

/***********************************************************************************************************************************************/

		do
		{

			i2c_write_reg(i2c1,DRV10987_Address,EECRTL,0x80,0x00);				//Setting EEPROM Access permission and DISABLE!!!!!!!! the motor

			i2c_write_reg(i2c1,DRV10987_Address,EEPROM1,0x00,0x00);				//clearer EEPROM Access code

			i2c_write_reg(i2c1,DRV10987_Address,EEPROM1,0xC0,0xDE);				//Setting EEPROM Access code

			gpio_init(G0,GPO,0);
// 
//			systick_delay_ms(1);				//Wait for set up 1ms

		}while(i2c_read_reg(i2c1,DRV10987_Address,EEPROM2) != 0x0001);		//Setting EEPROM able to read

			gpio_init(G0,GPO,1);

		i2c_write_reg(i2c1,DRV10987_Address,CONFIG1,0
																								| p5_SpectrumControl_MASK
																								| FG_both_open_and_close
																								| FG_Only_Close
																								| FG_POLES(2),
																								0
																								| CLK_ADJ_SELECT(0)		  //0:FULL 1:HALF
																								| 0x5B );								//Setting to 3.5R


		i2c_write_reg(i2c1,DRV10987_Address,CONFIG2,0
																								| 0x0A,									//Page 24
																								0
																								| CommAdvMode(0)					
																								| 0x02 );									//Page 37
		
		
		i2c_write_reg(i2c1,DRV10987_Address,CONFIG3,0
																								| ISDThr_80ms
																								| BrkCurThrSel(0)
																								| BEMF_HYS(0) 
																								| ISDEn(0) 
																								| RvsDrEn(0)
																								|	RvsDrThr_6P3,								
																								0
																								|	OplCurr_0p4			
																								| OplCurrRt_6
																								| BrkDoneThr_0 );							

		
		i2c_write_reg(i2c1,DRV10987_Address,CONFIG4,0
																								| AccRangeSec(0)
																								| StAccel2(0)
																								| StAccel(1),								
																								0
																								|	Op2ClsThr(1,10)			
																								| AlignTime(6) );

		i2c_write_reg(i2c1,DRV10987_Address,CONFIG5,0
																								| OTWarmingLimit(0)
																								| CloseLoopStuckLock(0)
																								| OpenLoopStuckLook(0)
																								| NoMotorLock(0)
																								| AbnormalKtLock(1)
																								| AbnormalSpeedLook(1),								
																								0
																								|	SWiLimitThr(0)			
																								| HWiLinitThr(0) 
																								| IPDasHWlLimit(0)  );


		i2c_write_reg(i2c1,DRV10987_Address,CONFIG6,0
																								| SpdCtrlMd(1)
																								| PWMFreq(0)
																								| KtLckThr(0)
																								| AVSIndEn(0)
																								| AVSMMd(0)
																								| IPDRIsMd(0),								
																								0
																								|	CLoopDis(0)			
																								| CIsLpAccel(4) 
																								| DutyCycleLimit(0)  
																								| SlewRate(4)  );


		i2c_write_reg(i2c1,DRV10987_Address,CONFIG7,0
																								| IPDAdvcAg(0)
																								| IPDCurrThr(0)
																								| IPDClk(0),								
																								0
																								| CtrlCoef(4)  
																								| Deadtime(10)  );

		
		i2c_write_reg(i2c1,DRV10987_Address,EEPROM5,0x00,0x06);

		while(i2c_read_reg(i2c1,DRV10987_Address,EEPROM2) != 0x0001);

		i2c_write_reg(i2c1,DRV10987_Address,EEPROM5,0x00,0x02);

		while(i2c_read_reg(i2c1,DRV10987_Address,EEPROM2) != 0x0001);

		i2c_write_reg(i2c1,DRV10987_Address,EECRTL,0x00,0x00);

		systick_delay_ms(50);				//Wait for set up

			

Part Number:DRV8323

I design a 48V inverter with DRV8320. I would like to measure the phase currents with shunt resistor. I also like to isolate the current signal so I decided to use AMC1301 isolation amplifier. Based on the datasheet the VDD1 voltage should be generated by a zener diode from the floating power supply of the gate driver:

My question is, in the case of the DRV8320 can is use the VCP terminal (output of the charge pump circuitry) to generate the voltage using Zener diode for AMC1301?

Thank you in advanced