DRV3946-Q1: PVDD_OV gets asserted on adjacent valves when a valve is shut off.

September 3, 2024, 9:53 am

≫ Next: DRV8214EVM: Sensorless Position Measurement and IPROPI

≪ Previous: DRV8889-Q1EVM: how to burn software into EVM

$

0

0

Part Number: DRV3946-Q1

Tool/software:

Greetings,

I've run into an interesting issue with the DRV3946 driver.

We have an application that uses 4 of the drv3946's to drive 8 valves.  The valves are close to each other (about 3mm) and when the wire to control the valve is run between the valves, disabling a valve will induce a PVDD_OV response on the valves adjacent to the valve that has been deactivated.   We have rerouted the wires so that they are not running between valves and this has helped, a bit, but the error still occasionally occurs. I have tried to increase the PVDD_OV deglitch time to it's maximum value with no effect.

We have also installed a shortly. diode on the output to ground to try and control this spike, so far with no success.

Also, PVDD_OV warning always asserts due to our power supply supplying 24 volts for the valves and the threshold for lvdd_ov warning appears to be 20 volts.

Is there something I can do to mitigate this?  I know I can disable the warning and the error with the control registers, but that seems like it would not be the best idea.

Any insight you can offer would be of help.

Thanks

Rick

---

DRV8214EVM: Sensorless Position Measurement and IPROPI

September 3, 2024, 1:20 pm

≫ Next: DRV8873-Q1: Possible change between "old" parts and "newer" parts.

≪ Previous: DRV3946-Q1: PVDD_OV gets asserted on adjacent valves when a valve is shut off.

$

0

0

Part Number: DRV8214EVM

Tool/software:

Hi All, 

I am evaluating the above IC for sensorless position control of a small (8mmx16mm size coreless) brushed motor, which is coupled to a planetary gearbox.

I am strugling to get reliable position control, with the reported number of counts changing dramatically based on load. 

I am also seeing a lot of noise on IPROPI. 

The EVM is in its factory state, with no modifications. VM is 3V, motor current is below 100mA

IPROPI and RC_OUT waveforms, EC enabled:

 

As above, but with EC disabled:

Any advice would be greatly appreciated.

DRV8873-Q1: Possible change between "old" parts and "newer" parts.

September 3, 2024, 2:49 pm

≫ Next: DRV8412: DRV84121 to support TEC funtion

≪ Previous: DRV8214EVM: Sensorless Position Measurement and IPROPI

$

0

0

Part Number: DRV8873-Q1

Tool/software:

Hello, 

I'm raising this question to eliminate the possibility of a dye change or a functionality modification on this part, since we've compared an old sample where the part has a visible "TI" logo and different markings, we are looking at an instance where the chip has its power removed and the SPI bus would collapse, this behavior was not seen on the "old" batch of parts, but for some reason, the "newer" parts seem to be more prone to have this failure happening on them, also, attached you will find the comparison of the "old" vs "new" part (IMG_01) for chip comparison or batch identification (please note that the "old" parts are still working with no problems, when the chip has it's power removed as opposed to the new parts that collapse the whole SPI bus.

As well as photos of a new part that was purchased through DigiKey (IMG_02), seems to have some residual contamination on the bottom pad, that can be cleaned with alcohol, is this residue considered "normal" and doesn't impact the functionality of this part, or should it be expected to have the bottom pad cleaned like on picture IMG_03?. Final pictured is the front side of the tape of parts ordered through DigiKey (IMG_04).

Thank you and hopefully we can get to a resolution on this topic.

 

DRV8412: DRV84121 to support TEC funtion

September 3, 2024, 8:17 pm

≫ Next: DRV8889-Q1: SPI Ready timing verification during testing

≪ Previous: DRV8873-Q1: Possible change between "old" parts and "newer" parts.

$

0

0

Part Number: DRV8412

Tool/software:

Hi team, 

I see we recommend to use DRV8412 to support TEC control. can you help to see if we have better choice here to meet below application request?

A TEC driver chip is required, and the specific selection requirements are as follows
1. Support 3.3V power supply voltage;
2. Support differential ±2.1 V TEC drive voltage output;
3. Output current capability > 1.1A (application scenario: at 25°C, the TEC internal resistance is 1.229Ω~1.502Ω);
4. It is best to support NTC detection function.

DRV8889-Q1: SPI Ready timing verification during testing

September 3, 2024, 10:00 pm

≫ Next: DRV8305-Q1: fault condition

≪ Previous: DRV8412: DRV84121 to support TEC funtion

$

0

0

Part Number: DRV8889-Q1

Tool/software:

Hi,

I'm currently verifying the SPI timing parameters mentioned in the datasheet, However there is no reference waveform available in the datasheet which could help me to understand on How i can measure the SPI ready time of 1ms during testing.

could you please suggest the ways in which i can ensure this parameter during testing ?

Thanks & Regards,

Vineet Anurag

DRV8305-Q1: fault condition

September 4, 2024, 12:25 am

≫ Next: MCT8316A: MCT8316A & MCT8315A

≪ Previous: DRV8889-Q1: SPI Ready timing verification during testing

$

0

0

Part Number: DRV8305-Q1

Tool/software:

Hello Experts,

My customer has question as follows. Would you answer them, please?
1. Recover from latched fault condition.
The latched fault condition will be indicated to the nFAULT-pin. To recover latched fault condition, customer need to write the CLR_FLTs bit asserted in register 0x9, bit D1. At this time, nFAULT-pin and gate driver are recovered to normal condition if latched fault condition is removed?

2. Power up sequence
When PVDD voltage is less than UVLO2, SPI communication is disabled, correct? Or If PVDD voltage is UVLO1<PVDD<UVLO2, SPI communication is still enabled?

3. PVDD_UVLO2
When device detect PVDD_UVLO2, Register 0x1(fault bit) and Register 0x3(bit 10) will be asserted, correct?

Best Regards,
Fujiwara

MCT8316A: MCT8316A & MCT8315A

September 4, 2024, 1:09 am

≫ Next: DRV8300: Firmware support_Trapezoidal sensorless control algorithm

≪ Previous: DRV8305-Q1: fault condition

$

0

0

Part Number: MCT8316A
Other Parts Discussed in Thread: MCT8315A

Tool/software:

Hi there,

We intend to use MCT8316A and MCT8315A in the design.

We don't need to use the SW_BK (internal Step-Down Back regulator) option.

My question is, can I remove the external peripherals- L_BK & C_BK from the design?

BR

Shachar   

DRV8300: Firmware support_Trapezoidal sensorless control algorithm

September 4, 2024, 2:11 am

≫ Next: DRV8308: Motor Driver Parts Recommendation Inquiry

≪ Previous: MCT8316A: MCT8316A & MCT8315A

$

0

0

Part Number: DRV8300

Tool/software:

Hi,

I have started working on Electronic speed controller, I need firmware support for my ESC which supports sensor less trapezoidal control algorithm.

Thanks

---

DRV8308: Motor Driver Parts Recommendation Inquiry

September 4, 2024, 2:18 am

≫ Next: DRV8825: The actual current peak does not match the set current value after stopping STEP signal

≪ Previous: DRV8300: Firmware support_Trapezoidal sensorless control algorithm

$

0

0

Part Number: DRV8308

Tool/software:

Hi, TI expert

The customer used to use DRV8308(TI) part on the board applied to ATMs(Automated Teller Machines), but due to delivery issues at the time, they changed it to MC33035(ONSEMI) part and are currently using it.

e2e.ti.com/.../MC33035_2D00_D_5F002800_ONSEMI_2900_.PDF

The customer would like to receive a recommendation for TI's Motor Driver, which is better than MC33035(ONSEMI) and has not been released for long.

The SPEC used by the customer is as follows.
- BLDC Motor Driver
- 200W class
- Vin: 24Vdc
- 5V used for IC

Can you recommend a suitable part?

Please check. Thanks.

DRV8825: The actual current peak does not match the set current value after stopping STEP signal

September 4, 2024, 3:38 am

≫ Next: DRV3901-Q1: Problems reading the trigger status from STATUS0 register

≪ Previous: DRV8308: Motor Driver Parts Recommendation Inquiry

$

0

0

Part Number: DRV8825

Tool/software:

hi,

After the motor is spinning normally, the customer stops the motor by stopping a pulse signal to the step pin. The current through the motor 2 phases are tested and the current through one of the phase  is much larger than the set maximum of 300 mA. Is this normal?

Test condition: After the motor is spinning normally, the customer stops the motor by stopping a pulse signal to the step pin.

Decay mode: Mixed decay; Microstep:  1/32; Without load with motor

the waveforms of phase current following out AOUT/BOUT are listed in attached.

e2e.ti.com/.../The-actual-current-peak-does-not-match-the-set-current-value-after-stopping-STEP-signal.pptx

DRV3901-Q1: Problems reading the trigger status from STATUS0 register

September 4, 2024, 5:26 am

≫ Next: MCF8316C-Q1: the range of maximum phase current

≪ Previous: DRV8825: The actual current peak does not match the set current value after stopping STEP signal

$

0

0

Part Number: DRV3901-Q1
Other Parts Discussed in Thread: AM2632-Q1,

Tool/software:

I am attempting to implement a fault diagnostic between the MCU and the DRV3901-Q1.  I am repeating the following two SPI transactions.  1. Write to CMD1 to CLR_FAULT, 2. Read  STATUS0.  I am alternating between asserting trigger 1 and trigger 2.  I can always read the status of the trigger 1 being asserted.  I can never read trigger 2 being asserted.  I am testing this using the DRV3901-Q1 EVM attached to our MCU (AM2632-Q1).  I have removed the shunts so that the DRV3901-Q1 can be controlled by the MCU instead of the on board MSP430.

MCF8316C-Q1: the range of maximum phase current

September 4, 2024, 5:40 am

≫ Next: MCF8315C: Motor driver for different types of BEMF

≪ Previous: DRV3901-Q1: Problems reading the trigger status from STATUS0 register

$

0

0

Part Number: MCF8316C-Q1
Other Parts Discussed in Thread: MCF8316AEVM

Tool/software:

Hi team,

We use MCF8316AEVM for debugging. When the maximum phase current of the motor is about 6A, the hardware fault HW_LOCK_LIMIT is reported;

The verification method is as follows: use the Align positioning method, the positioning current is 5.5A, the openl_oop_cunrrent_limit is limited to 6 A, after the positioning is completed, the hardware overcurrent is set to 8A, and the HW_LOCK_LIMIT is reported in the open loop stage;

The current loop parameters use KP: 0; Ki: 0 and KP: 2; Ki: 8200; two sets of parameters, and the performance is consistent. Hardware overcurrent occurs only when the phase maximum is about 6A. At present, only the current at the moment of open-loop positioning verifies that there is overcurrent, and whether the trigger current value is smaller after the closed loop.

Need help:
1. Since the maximum phase current of our company's products is about 7A, please help evaluate whether the chip is applicable. If it is not applicable, please provide suggested current range?
2. If this phenomenon is a debugging problem, can you point out the solutions

Fault picture:

Phase current waveform at the time of fault: the peak maximum value is only 6A.

Best regards!

Ethan

MCF8315C: Motor driver for different types of BEMF

September 4, 2024, 9:59 am

≫ Next: DRV8889-Q1: About the problem of DRV8889 stepper motor chip

≪ Previous: MCF8316C-Q1: the range of maximum phase current

$

0

0

Part Number: MCF8315C

Tool/software:

Hello! Im designing a motor driver for a BLDC that has a sinusoidal Back EMF

The driver that I need must be sensorless as there are no encoders or sensors in the motor that im driving.

I would like to know if the motor driver that I need must have sinusoidal control topology or driver with trapezoidal or FOC control can work

Thank you!

DRV8889-Q1: About the problem of DRV8889 stepper motor chip

September 4, 2024, 10:02 am

≫ Next: DRV8871: QUERY REGARDING ACTUAL DIMENSION OF THE EXPOSED THERMAL PAD

≪ Previous: MCF8315C: Motor driver for different types of BEMF

$

0

0

Part Number: DRV8889-Q1

Tool/software:

Hello expert,

I am using the motor chip DRV8889. The application scenario is the stepper motor of the car light. I have a few questions to confirm:

1. How to arrange the wiring harness when the chip is connected to the motor is beneficial to EMC. Do AOUT1 and AOUT2 wiring harnesses need to be twisted in pairs? Is it helpful to EMC if twisted in pairs.

2. What is the accuracy of the current obtained by The TRQ_DAC register set by the chip and the actual tested current? For example, the motor needs to have a holding current when it is not operating, there is a 10% error in my actual test current. Is this normal.

3. Is there any DRV8889 test program, we need some sample code to realize the acceleration and deceleration of the motor.

Thanks

DRV8871: QUERY REGARDING ACTUAL DIMENSION OF THE EXPOSED THERMAL PAD

September 4, 2024, 9:14 pm

≫ Next: ULC1001-DRV290XEVM: OUTPUT

≪ Previous: DRV8889-Q1: About the problem of DRV8889 stepper motor chip

$

0

0

Part Number: DRV8871

Tool/software:

 Please confirm and provide the actual dimension of the exposed thermal pad, since there are two actual dimensions are available in the latest datasheet.

---

ULC1001-DRV290XEVM: OUTPUT

September 4, 2024, 9:56 pm

≫ Next: DRV8214EVM: VM voltage remains at 0.0V

≪ Previous: DRV8871: QUERY REGARDING ACTUAL DIMENSION OF THE EXPOSED THERMAL PAD

$

0

0

Part Number: ULC1001-DRV290XEVM
Other Parts Discussed in Thread: ULC1001

Tool/software:

Hello.

Is the PWM output of ULC100 set to output randomly between Freq_Start and Freq_Stop? I am curious about how the PWM output settings of ULC1001 are set.

The figure below shows the output waveform of ULC1001.

DRV8214EVM: VM voltage remains at 0.0V

September 5, 2024, 1:31 am

≫ Next: DRV8214EVM: Number of Ripples too high for the GUI.

≪ Previous: ULC1001-DRV290XEVM: OUTPUT

$

0

0

Part Number: DRV8214EVM

Tool/software:

Hello,

I have just received my DRV8214EVM evaluation board and in the GUI the VM voltage always stays on 0V. So I looked at the diagram, an R12/R35 divider bridge provided to the processor this information. But on my board there is no R12. Is this an error or another reason?

Cordially.

DRV8214EVM: Number of Ripples too high for the GUI.

September 5, 2024, 2:16 am

≫ Next: DRV8243-Q1: Using SPI to control the driver

≪ Previous: DRV8214EVM: VM voltage remains at 0.0V

$

0

0

Part Number: DRV8214EVM

Tool/software:

Good morning,
I use a small 6v motor size 370 (RC car). I capture the IPROPI output with the oscilloscope for calibration, but I obtain 25 peaks in 1000us, which makes 250 peaks in 10ms. I cannot fill in the GUI these values.

Am I missing something?

Kind regards.

DRV8243-Q1: Using SPI to control the driver

September 5, 2024, 5:11 am

≫ Next: DRV8889-Q1: Fault Pin Voltage being at 1.3V before going HIGH (3.3V).

≪ Previous: DRV8214EVM: Number of Ripples too high for the GUI.

$

0

0

Part Number: DRV8243-Q1

Tool/software:

Hi, 

I want to confirm my understanding of the DRV8243P (SPI (P) = variant). I am using two DRV8243P's each configured as a single full bridge to control two seperate DC brushed motors. To reduce the amount of pins used I want to control them over SPI in a daisy chain configuration. 

As far as I can see, the drivers can be fully controlled over the SPI registers (SPI_IN Register) without needing external HW control signals. Is there any way to control the speed via the SPI registers or would it just toggle between 0 and 100% duty cycle whenever activating the driver? 

If no speed is settable trough the SPI registers, could one use a PWM signal on the EN/IN1 pin in the PH/EN mode and then use the SPI registers to write to and activate the driver? So in essence combining the two control modes? Or are these mutually exclusive, so using SPI to control the driver would disable the EN/IN1 and PH/IN2 inputs?

Alternatively, if I am to control only with SPI, would DRV_OFF be tied HIGH, EN/IN1 and PH/IN2 tied to GND or left floating? 

Br, 

Mathias 

DRV8889-Q1: Fault Pin Voltage being at 1.3V before going HIGH (3.3V).

September 5, 2024, 7:15 am

≫ Next: MCF8316A: some issue of the use of FOC

≪ Previous: DRV8243-Q1: Using SPI to control the driver

$

0

0

Part Number: DRV8889-Q1

Tool/software:

Hi,

I'm currently performing testing on the Motor Driver DRV8889-Q1, while testing i observed the Fault pin is intially at 1.3V before it goes HIGH (3.3V). 

As per the datasheet, Fault Pin is an Open drain which in our circuit is pulled-up to 3.3V via a 10K resistor.

It would really mean a lot if you can please help me understand the reason behind the 1.3V we are seeing before the Fault signal is asserted HIGH (3.3V). Attaching the waveform for reference.

Channel 1: Current through AOUT1 Pin

Channel 2: Fault Output Signal

Thanks & Regards,

Vineet Anurag