Tool/software:
Do you have the typical value and minimum value of the chip height? At present, on the figure of the specification, our measured values are as red letters.
Tool/software:
Hi TI Community,
We are using UCC28180DR to control and drive a boost PFC with 400V dc output voltage and 1 kW rating. IC peripherals are highlighted in the image shared below.
We are facing hardware damage issue where in the shunt current sense resistors and MOSFET gets damaged. As per the datasheet, IC provides soft overcurrent feature and peak overcurrent limit (PCL). Using design guide provided by TI, the calculated value for PCL is 29.2 Amps. At the same time selected MOSFET, IPP60R120P7 has a pulsed current rating of 78A.
Regarding this,
Is there any delay in PCL or SOC implementation logic?
Shouldn't PCL protection turn OFF the gate pulses to MOSFET?
Your insights are welcomed and it will be helpful if you can suggest a solution for the same.
Thank you for your help
Tool/software:
Hi team,
In D/S, it is said that user should delay 1ms before applying PWM when nSLEEP is switching low to high.
If this interval is shorter than 1ms, what type of trouble does occur?
Best regards,
Goto
Tool/software:
Hi Team,
I noticed in our roadmap which shows DRV8320 with charge pump architecture and DRV8328 with bootstrap architecture, could you possible help to share the advantage and disadvantage between this two different architecture? Thanks a lot for your support.
Best regards
Jie
Tool/software:
Team,
My customer wants to calculate the impact to gate driver FET at 150C.
Would you please provide the register value at Ta=150C to TDS(ON)_PU_HS, RDS(ON)_PD_HS, RDS(ON)_PU_LS, RDS(ON)_PD_LS?
The following data is at Ta=25C. we need the same data at Ta=150C.
Regards,
Shinji Nishio
Tool/software:
Hi Team,
The link https://www.ti.com/drr/opn/DRV3256-Q1-DESIGN is not accessible. Any workaround?
Regards,
Josel
Tool/software:
Hi,
My customer is reviewing DRV8242SQRHLRQ1 to EWP.
The existing Half bridge driver (DRV8904QPWPRQ1) controlled the speed by varying the frequency and duty with PWM control.
DRV8242SQRHLRQ1 review does not confirm the Duty setting part.
Please guide me on how to control the speed of the SPI version.
Tool/software:
Hello,
I am trying to use Motor Studio and a MCF8316AEVM to spin up a 3-phase BLDC motor. Running into issues in Motor Studio "Quick Spin".
There is a drop down menu to select a JSON file type to load default parameters to the eval board. I found a JSON file for the MCF8316C in one thread on the E2E forums. I downloaded and tried loading into the GUI but get an invalid file pop-up. Can you please supply a JSON file for the MCF8316A?
Tool/software:
Hi
My customer Magna is looking to evaluate the DRV8899-Q1 EVM. Their IT ran our software through some tool (https://www.virustotal.com/) and it came back with some flags that is making them hesitant to download. Is there a safe version of the EVM Software?
The other option is to use the TI Cloud Agent but they are also hesitant. Does the cloud tool upload any data to the TI cloud or other service or is it okay to use?
Regards
Kevin
Tool/software:
What the the SPI frequency range for the DRV3901-Q1?
Also, would it be possible to get the schematics for the eval board?
Thanks
Tool/software:
Hi, I'm considering a BLDC motor driver choice for a project and these two drivers seem roughly equivalent. The only guidance I've found is the related question linked from this post. Sleep current, optional buck, and the additional protection features on the DRV8334 are not important for me. Are there any other things to consider such as potential EOL for the DRV8323 since it's an older part? Or errata for the DRV8334 since it's a new release?
Thanks
Tool/software:
Does the nFAULT/NAD pull-up resistance have to go to VDD (5V) for correct SPI address setting?
I am interfacing the device with a 3.3V microcontroller, so need to know whether I will need to level shift this signal or if it is OK to have the pull-up go to 3.3V.
Tool/software:
we are observing in Hardware PWM mode, fault pin is going low for every 20s. What could be the reasons? We have connected the load also.
Tool/software:
Hi team,
My customer did SPx and SNx short to GND test, and found nearly every time our device's related SPx and SNx resistance to GND is very small after this test. What's the reason for this?
Above scope is the SPx and SNx waveform
BR,
Bengi
Tool/software:
I am reaching out to request technical assistance with some issues I've encountered while using the DRV8302 circuit. Initially, I faced a problem with the integrated buck converter failing to output 5 volts, which led me to disable it by connecting the EN_BUCK PIN to GND and using an external power source instead.
During the first trial, the motor only vibrated without turning, and shortly afterward, pins 29 and 30 burned out, showing nFAULT and nOCTW errors. In the second trial, I avoided connecting any components to the buck converter and connected pin 55 to ground. Unfortunately, after powering up the system, the card burned out, and pin 55 was also damaged.
I seek your support to understand whether the IC is still operational and undamaged, and to know the required signal to be input into the circuit. I am using a Six Step Commutation algorithm with an STM32F105 to generate the signal. Is this issue related to hardware or software? I have checked all internal power pins, and their values were within the acceptable range.
You can access the project files from here:
https://drive.google.com/drive/folders/1kg5lvlmvnN4wENb28xE1LVQ3SBfBA0m2?usp=sharing
Here is some of the control code used in my experiment:
/****************************** STATE 1 *********************************/
if (HALL_A==1 && HALL_B==0 && HALL_C==1 )
{
//B->A
set_PWM_duty_cycle(&htim1, TIM_CHANNEL_1, 0.0); //AH
set_PWM_duty_cycle(&htim1, TIM_CHANNEL_2, Duty);//BH
set_PWM_duty_cycle(&htim1, TIM_CHANNEL_3, 0.0); //CH
HAL_GPIO_WritePin(INL_A_GPIO_Port, INL_A_Pin, 1 );//AL
HAL_GPIO_WritePin(INL_B_GPIO_Port, INL_B_Pin, 0 );//BL
HAL_GPIO_WritePin(INL_C_GPIO_Port, INL_C_Pin, 0 );//CL
}
/****************************** STATE 2 *********************************/
else if (HALL_A==1 && HALL_B==0 && HALL_C==0 )
{
//C->A
set_PWM_duty_cycle(&htim1, TIM_CHANNEL_1, 0.0); //AH
set_PWM_duty_cycle(&htim1, TIM_CHANNEL_2, 0.0); //BH
set_PWM_duty_cycle(&htim1, TIM_CHANNEL_3, Duty); //CH
HAL_GPIO_WritePin(INL_A_GPIO_Port, INL_A_Pin, 1);//AL
HAL_GPIO_WritePin(INL_B_GPIO_Port, INL_B_Pin, 0);//BL
HAL_GPIO_WritePin(INL_C_GPIO_Port, INL_C_Pin, 0);//CL
}
/****************************** STATE 3 *********************************/
else if (HALL_A==1 && HALL_B==1 && HALL_C==0 )
{
//C->B
set_PWM_duty_cycle(&htim1, TIM_CHANNEL_1, 0.0); //AH
set_PWM_duty_cycle(&htim1, TIM_CHANNEL_2, 0.0); //BH
set_PWM_duty_cycle(&htim1, TIM_CHANNEL_3, Duty); //CH
HAL_GPIO_WritePin(INL_A_GPIO_Port, INL_A_Pin,0 );//AL
HAL_GPIO_WritePin(INL_B_GPIO_Port, INL_B_Pin, 1);//BL
HAL_GPIO_WritePin(INL_C_GPIO_Port, INL_C_Pin, 0);//CL
}
/****************************** STATE 4 *********************************/
else if (HALL_A==0 && HALL_B==1 && HALL_C==0 )
{
//A->B
set_PWM_duty_cycle(&htim1, TIM_CHANNEL_1, Duty); //AH
set_PWM_duty_cycle(&htim1, TIM_CHANNEL_2, 0.0); //BH
set_PWM_duty_cycle(&htim1, TIM_CHANNEL_3, 0.0); //CH
HAL_GPIO_WritePin(INL_A_GPIO_Port, INL_A_Pin, 0);//AL
HAL_GPIO_WritePin(INL_B_GPIO_Port, INL_B_Pin, 1);//BL
HAL_GPIO_WritePin(INL_C_GPIO_Port, INL_C_Pin, 0);//CL
}
/****************************** STATE 5 *********************************/
else if (HALL_A==0 && HALL_B==1 && HALL_C==1 )
{
//A->C
set_PWM_duty_cycle(&htim1, TIM_CHANNEL_1, Duty); //AH
set_PWM_duty_cycle(&htim1, TIM_CHANNEL_2, 0.0); //BH
set_PWM_duty_cycle(&htim1, TIM_CHANNEL_3, 0.0); //CH
HAL_GPIO_WritePin(INL_A_GPIO_Port, INL_A_Pin, 0);//AL
HAL_GPIO_WritePin(INL_B_GPIO_Port, INL_B_Pin, 0);//BL
HAL_GPIO_WritePin(INL_C_GPIO_Port, INL_C_Pin, 1);//CL
}
/****************************** STATE 6 *********************************/
else if (HALL_A==0 && HALL_B==0 && HALL_C==1 )
{
//B->C
set_PWM_duty_cycle(&htim1, TIM_CHANNEL_1, 0.0); //AH
set_PWM_duty_cycle(&htim1, TIM_CHANNEL_2, Duty); //BH
set_PWM_duty_cycle(&htim1, TIM_CHANNEL_3, 0.0); //CH
HAL_GPIO_WritePin(INL_A_GPIO_Port, INL_A_Pin,0 );//AL
HAL_GPIO_WritePin(INL_B_GPIO_Port, INL_B_Pin,0 );//BL
HAL_GPIO_WritePin(INL_C_GPIO_Port, INL_C_Pin,1 );//CL
}
/***********************************************************************/I hope you can assist me in resolving these issues as soon as possible. Thank you for your attention and assistance.
Best regards,
Tool/software:
Hi team,
I know DRV8910 has NMOS internally, do you know if we have PNP internally at your product line?
BR
Amber
Tool/software:
Hi team,
what is the CPOL and CPHA of our device? I see from datasheet about SPI Transaction, does this mean CPOL = CPHA=0?
BR,
Bengi
Tool/software:
Dear TI-Team,
I am currently evaluating the driver in my own design, but unfortunately, I have encountered a problem and need your assistance.
Every time I start my board, the status register reports a Buck Converter overcurrent fault. When I clear the fault using Clear Fault, the issue doesn't reappear.
The Buck Converter circuit can be seen here:
I am reading the following registers:
On the oscilloscope, I measure the following signals:
Is this behavior characteristic of the driver?
Best regards,
Juliana
Tool/software:
Hello,
Nisshinbo Micro Devices Inc NJW4302 (THREE-PHASE DC BRUSHLESS MOTOR CONTROL IC, datasheet is attached) would be EOLed and my customer is looking for replacement devices. Does TI have any recommendations?
e2e.ti.com/.../NJW4302.pdf
Best regards,
K.Hirano
Tool/software:
Hi team,
For below download software for DRV8889-Q1EVM, how can we burn this software into EVM? Which software should we use to load the code? What‘s the version of the software?
BR,
Bengi