https://e2e.ti.com/support/motor-drivers-group/motor-drivers/Products covered in this section are TI's DRV family of motor drivers. Learn more at www.ti.com/motorcontrol.en-USTelligent Community 13https://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1676569/ulc1001-drv2911evm-ulc1001-drv2911evm-output-becomes-dc-like-below-24khz/6500894Fri, 02 Oct 2026 22:36:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:78db7a53-89fa-46b1-b825-7ea73dee12cdHailong ChenBased on datasheet, AD modulation is specifically built to handle lower ultrasonic frequencies, supporting a range from <50 kHz down to 10 kHz . It completely bypasses the direct-drive tracking loop constraints, delivering stable duty-cycle control at 20 kHz. In the original silicon design and the early Rev B revision, HEDD mode's current/voltage tracking loops and internal sensor-less algorithms were optimized to stabilize down to 25 kHz. Operating HEDD at approximately 20 kHz can possibly lead to an unstable zero-crossing detection loop, causing phase errors or unexpected driver fault trips. This might not be fully fixed.https://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1685572/drv8323-drv8323srtar-heating-under-normal-operating-conditions/6500890Fri, 02 Oct 2026 22:32:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a9a9cb95-52ae-4b8f-b41a-64071f9e34dcJesus Rodriguez ToscanoHello, Vivien, The DRV8323 is a driver not intended for 48V applications due to the 65V abs max. During motor operation, it is highly possible that transients can exceed the abs max rating of the device and lead to damage and high heat generation. I would recommend switching to either DRV8353 or DRV8363 as these have abs max rating of 85-100V. It is best practice to select a driver with an abs max at least 1.5x to 2x the nominal supply bus to account for transients. Also, for your current nominal power consumption of 576mW considering a Junction-to-ambient thermal resistance of 32.1°C/W (Tested, datasheet), the expected temperature of the board would rise to 44.5°C, which matches your initial temp rise to 40°C. It is possible that your PCB’s Junction-to-ambient thermal resistance is different, leading to the initial rise to 40°C. As for the cause of why it reached 56°C over one hour, this would be due to the rise in the ambient temperature around the driver from its original 26°C, over time. As far as your current layout and schematic, I don’t see any problems that would lead to a very high Junction-to-ambient thermal resistance. Though it is possible that your problem is only visible within the lower layers, could you share your layout for the other 5 layers? However, I can recommend some action items to decrease the rise in temperature. These include: Effectuating the plan of an additional 0V polygon pour both under the driver and on the bottom layer Adding an additional 4 thermal vias to allow for more thermal dissipation: Positioning your 0V layer as the 2 nd layer in the PCB to allow for a lower thermal resistance and higher heat flow Additionally add as many 0V polygons in the other layers as it is sensible, especially in the bottom layer Sincerely, Jesushttps://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1683267/mcf8329hsevm-need-faster-deceleration/6500874Fri, 02 Oct 2026 22:06:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:1324db2e-1ba4-442b-9de8-9a084bcd3442Michael ZarlingThank you for your support Dhinesh.https://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1686453/drv8332-ht-preferred-replacement-for-drv8332dkdr-and-product-lifetime-information/6500747Fri, 02 Oct 2026 19:24:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ad9a1d47-285d-4e60-98b9-8d6f5eb1df6fJesus Rodriguez ToscanoHello, Bhairu, Both DRV8376H and DRV8316CT are new devices, so they will be available for the foreseeable future, so there aren't any concerns of future availability for either of these devices. As for which one is the top recommendation, that depends on your application and the specs for said application. So, if you can share that information, I can help give you an accurate recommendation. Sincerely, Jesushttps://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1685229/drv8161-drv8161-gate-slew-rate-reduction/6500738Fri, 02 Oct 2026 19:10:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b19f6251-a588-4db8-83b5-71a444473768Joseph FerriHello, 1. The recommendation would be to add external gate resistors. Since the idrive is already at its minimum. I suspect that the switching speed is already very low at minimum idrive + 100 ohm resistor. Thanks, Josephhttps://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1686090/mct8316a-q1-i2c-bus-recovery-from-stuck-condition/6500720Fri, 02 Oct 2026 18:43:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:22ab41b7-7159-4c8a-9d4a-b9384da78ab9HoriaHi Venkatadri, any updates?https://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1685595/drv8161-drv8161-with-booster-for-more-gate-current/6500680Fri, 02 Oct 2026 18:07:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:0d5b06ed-9b68-4fb1-8430-e7b559fc2b15Joseph FerriHi Diego, Understood, yes this load would be quite significant so I understand the desire for a higher drive current. Spikes/transients on the Gate signals. Driving this much current, I would suspect that the transient voltages would be higher and could potentially damage the device You might lose out on some protections as mentioned before, but I don't see anything other than possible damage that would prevent the device being actually used in this application. Thanks, Josephhttps://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1685255/mct8329a-motor-driver-configuration-and-control/6500479Fri, 02 Oct 2026 14:13:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c1f09e20-4009-45c1-a183-ef287fdadb5aArunn KaushalyaHi Dinesh, I have tried the config 1. When motor not loaded, it starts really slow with grinding noise, and then an ABNORMAL_SPEED is reported. 2. When the motor is loaded, it starts with the load and but I keep on getting Sync error.https://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1682550/drv8800-inrush-current-at-start-up-with-2-wire-bldc-fan/6500451Fri, 02 Oct 2026 13:37:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:7a6418f1-92b3-4fd8-9269-10e3e60628eeMurugavel4637Hi Inoue-san, Thank you for the update. [quote userid="119143" url="~/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1682550/drv8800-inrush-current-at-start-up-with-2-wire-bldc-fan/6500203"]By inserting a resistor, the inrush current drops to around 1A, and the voltage on the OUT- side—which previously spiked momentarily to about 20V—now remains stable with virtually no rise. Therefore, we are proceeding with the plan to connect a 20Ω resistor in series.[/quote] This is a very good outcome. I'm glad the series resistor help mitigate the issue. [quote userid="119143" url="~/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1682550/drv8800-inrush-current-at-start-up-with-2-wire-bldc-fan/6500203"]Regarding the reason for using the DRV8800: Although we have other circuits capable of operating via FETs, they are all already allocated to other functions. This was the only available port capable of handling the operation. Since changing the circuit would require a board revision, we are proceeding with the plan to use it as is.[/quote] Understood. Please close this thread with 'RESOLVED', thank you. Regards, Murugavelhttps://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1686788/mcf8329a-mcf8329rryevm-unexpected-csa-gain-feedback-during-mpetFri, 02 Oct 2026 13:11:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:25c5b1fd-baff-4629-9e6e-edb088e71f6aOle GrendalPart Number: MCF8329A Other Parts Discussed in Thread: MCF8329RRYEVM , Hi TI team, We are testing the MCF8329RRYEVM with a WM8060-24V blower at Elotec in Norway. The board is controlled over I2C by an Arduino GIGA R1. We have established communication and can reach MOTOR_IDLE with a zero reference, but we have not yet completed MPET or seen the motor turn. During our latest MPET attempt, our firmware stopped the test after about 1.02 seconds because the gain feedback did not match the configured current sense amplifier gain: Register 0xAC = 0x8000007B: CSA_GAIN code 3, decoded as 40 V/V. Register 0xAE = 0x800000CD: BASE_CURRENT approximately 7.5073 A. Register 0x450 = 0x0003: CSA_GAIN_FEEDBACK code 3, decoded as 5 V/V. These interpretations follow the MCF8329A-Q1 datasheet. At the time of the stop, the algorithm was in MOTOR_MPET_MOTOR_BRAKE. Both fault registers were zero, BUS_CURRENT was zero, and no I2C errors were recorded. The readings were not simultaneous: the configured gain was read 411 ms before the feedback register. Our write log shows only watchdog servicing between those reads, with no writes to the gain or BASE_CURRENT settings. The mismatch check is part of our own firmware. Could you help us clarify the following? Is this difference between configured gain and gain feedback expected during MPET braking? Which gain and scaling should we use for current monitoring, and how are the internal current limits affected? Should these gain values match throughout MPET, or should our check account for specific algorithm states? The test ended with DRVOFF HIGH and a verified zero reference. No EEPROM settings were changed. I can provide the full register dump and timestamped logs if helpful. Best regards, OleMCF8329AMCF8329RRYEVMbuilding automationMCF8329A-Q1https://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1681398/mcf8315d-using-a-constant-high-on-speed-pin-to-wake-from-sleep/6500237Fri, 02 Oct 2026 05:52:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:db87f801-53d8-4d78-a406-ccc283b7f6bfMax AbildgaardHi Venkatadri, thanks for your reply. This sorted it out nicely! Best Maxhttps://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1682550/drv8800-inrush-current-at-start-up-with-2-wire-bldc-fan/6500203Fri, 02 Oct 2026 04:28:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:96f57aea-71a3-4201-8a15-0016a9a91934Shinichi InoueHi Murugavel, I could obtain the comment from the customer. Could you please see below? By inserting a resistor, the inrush current drops to around 1A, and the voltage on the OUT- side—which previously spiked momentarily to about 20V—now remains stable with virtually no rise. Therefore, we are proceeding with the plan to connect a 20Ω resistor in series. Regarding the reason for using the DRV8800: Although we have other circuits capable of operating via FETs, they are all already allocated to other functions. This was the only available port capable of handling the operation. Since changing the circuit would require a board revision, we are proceeding with the plan to use it as is. I appreciate your great help and cooperation. Best regards, Shinichihttps://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1683267/mcf8329hsevm-need-faster-deceleration/6500199Fri, 02 Oct 2026 04:20:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:91cfff37-6084-4765-b361-c6fdb53222b0DhineshHi Michael, Thank you for the update. Your observation is correct. MCF8329HS is capable of driving the motor when the speed pin is set low, whereas the MCF8329A is not. Thanks, Dhineshhttps://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1683267/mcf8329hsevm-need-faster-deceleration/6500029Thu, 01 Oct 2026 22:05:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d082d3aa-e2b2-429d-a7f2-1d846287eaedMichael ZarlingHi Dhinesh, I have the MCF8329EVM working with my motor now. To control the speed via I2C in Motor Studio, it seems that the MCF8329HSEVM did not require the potentiometer to be in the fully counterclockwise position, but the MCF8329EVM does require this. It doesn't make sense why they are different. I found this support ticket where someone mentioned it. MCF8329EVM: Unable to spin motor with I2C control with Motor Studio - Motor drivers forum - Motor drivers - TI E2E support forums Regards, Michaelhttps://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1685280/drv3946-q1-drv3946-q1-thermal-shutdown-bit-reported-via-spi-but-outputs-remain-active-and-hardware-is-cool/6499986Thu, 01 Oct 2026 21:08:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d2fdda9b-7960-4010-a708-0a8c5158aa54David MedisHi Fabrizio, It's possible the behavior you're describing is consistent with the OT bit being a warning-level flag, not the overtemperature temperature shutdown. The over temperature warning (TSD_W) threshold is set lower than the thermal shutdown itself. This can be disabled by the OT_W_DIS bit. Best, Davidhttps://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1685795/drv3946-q1evm-design-evm-is-not-working-as-expected/6499950Thu, 01 Oct 2026 20:20:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:e1bab820-0fef-424b-9833-5dfbaa37ddf3David MedisHello, Thanks for your question. I'm not sure I understand what you mean by not turning off the output drives. Are you saying the EVM is connected to the GUI successfully and you are able to configure the registers without issues, but the output is not going low? Are you setting internal current regulation mode or forcing a duty cycle? Is the Enable button also enabled? Best, Davidhttps://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1686550/drv2901-drv2901-without-ulc1001-for-small-sonar-application/6499651Thu, 01 Oct 2026 14:41:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:621cc6d0-e74b-4cb0-8ded-b00cf3528b4fAri ZamanHi Marco, Yes, the input PWM_A and PWM_B pins drive two separate half-bridges and will need to be complimentary PWM signals as usual in H-bridge applications. Thanks, Arihttps://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1685681/drv3901-q1evm-outdated-users-manual/6499610Thu, 01 Oct 2026 14:09:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f5ac22ec-06f6-4ffe-a380-3426aab7f659Ibinu Alaudeen NadeeraHi Aaron, Thanks for highlighting this. Let me look at this and get this updated. Thanks, Ibinuhttps://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1679115/drv8462evm-guidance-required-for-standalone-operation-of-drv8462evm-without-pc-connection/6499600Thu, 01 Oct 2026 13:55:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:68ec4eb7-a013-4db5-9250-d8cccf642dc0Murugavel4637Hello Sayali, [quote userid="602604" url="~/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1679115/drv8462evm-guidance-required-for-standalone-operation-of-drv8462evm-without-pc-connection/6499456"]With SPI settings, the FAULT LED is not turning ON. This makes it difficult to understand what is causing the issue in Hardware Mode.[/quote][quote userid="602604" url="~/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1679115/drv8462evm-guidance-required-for-standalone-operation-of-drv8462evm-without-pc-connection/6499456"]Is there any document or application note that explains all SPI configuration options in detail, such as:[/quote][quote userid="602604" url="~/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1679115/drv8462evm-guidance-required-for-standalone-operation-of-drv8462evm-without-pc-connection/6499456"] Additionally, could you please share how the calculations are performed for these parameters and how to determine the appropriate values based on motor specifications and application requirements? Since the driver is operating correctly in SPI mode but indicates a fault in Hardware Mode, understanding these settings would help us identify if any parameter differences are causing the issue. [/quote] All necessary documentation, calculations to configure the available features in SPI mode is provided in the device data sheet. Additionally there are two application notes, one for Auto Torque feature and two for the Stall detection feature. In order to debug the issue I suggest do not focus on the features that are not available in HW Mode because these are complex features and not related to the HW mode operation of this driver IC. These features will be disabled and not contribute to a fault condition or nFAULT pin LOW notification while in HW mode. Torque DAC setting - leave this at default register setting 100 % for matching with HW mode Standstill power-saving mode - not enabled leave register default Current sense blanking time - do not change leave at default Stall detection parameters - do not enable this feature is disabled in HW mode Current regulation settings - leave at default value Decay mode settings - leave at default STRC ripple control Overcurrent and fault threshold settings - leave at default Since the suspicion for the fault notification was open load OL detection you may want to focus on this feature. By default OL is disabled in the SPI mode. This may be the reason why you did not see the fault happen in SPI mode. Click the "Configure" button in the GUI while in SPI mode. This will open up the Fault Configuration window. Enable OL with the following configuration to match with the HW mode behavior. Be sure to set the Step Mode to Full-step 100 % and matching current setting same as used for HW mode. This will allow you to see if the fault was caused by OL detection feature. [quote userid="4637" url="~/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1679115/drv8462evm-guidance-required-for-standalone-operation-of-drv8462evm-without-pc-connection/6498725"]If one of the coils' current goes < 190 mA an open load fault may be reported. What was the VREF voltage when this nFAULT was reported? What is the DCR DC resistance and inductance of the stepper motor? I suspect the motor current was < 190 mA and caused and OL fault. When OL was detected it is a report only fault, the motor will continue to run normally. [/quote] Please share the DCR DC resistance and inductance of the stepper motor coil or the motor part# and datasheet. Regards, Murugavelhttps://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1686089/drv8163-q1-kyungshin-configurable-cpol-cpha/6499593Thu, 01 Oct 2026 13:43:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4b3b9391-1604-4a2e-9870-22456eec9a49Joshua Horlander CruzHi Luke, I am not sure if we have any device that can configure when the digital core will sample SDI, push out data onto SDO, and allow for SCLK to be idle high, we at least do not have an internal FET driver for 48V that supports this. Can you let me know the reason for needing a configurable CPOL and CPHA? The MCU will control SDI, SCLK, and nSCS so it usually is easier to adjust the CPHA and CPOL from the MCU side. Regards, Joshua