<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://ez.analog.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Q&amp;amp;A - Recent Threads</title><link>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><lastBuildDate>Fri, 10 Jul 2026 14:36:38 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://ez.analog.com/motor-control-hardware-platforms2/f/q-a" /><item><title>TMCL-IDE PID tuning</title><link>https://ez.analog.com/thread/605179?ContentTypeID=0</link><pubDate>Fri, 10 Jul 2026 14:36:38 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:c8dcce9f-d2be-40bb-bc0b-6c95a6d56cc9</guid><dc:creator>Miodrag</dc:creator><slash:comments>0</slash:comments><comments>https://ez.analog.com/thread/605179?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/605179/tmcl-ide-pid-tuning/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hello everyone,&lt;/p&gt;
&lt;p&gt;I&amp;#39;m trying to set up motor control in TMCL-IDE with TMC4671 and TMC6100 evaluation kit (TMC6100-EVAL-KIT). I&amp;#39;ve managed to configure the device using configuration wizard, I set up open-loop, configured ADCs, and tried torque mode as well. Now I&amp;#39;m trying to tune the regulators, and I started with tuning torque coefficients as instructed in the documentation and tutorials&amp;nbsp;&lt;a href="https://youtu.be/rfZAs-QdYlQ?si=duI-YhgEIO6cPEuI"&gt;https://youtu.be/rfZAs-QdYlQ?si=duI-YhgEIO6cPEuI&lt;/a&gt; but I hit a problem I cannot resolve. I started PI tuning option, chose Torque/Flux mode, and then when I try to change Target value in Step settings I get Value out of range message. I&amp;#39;ve updated flux/torque limit register (PID_TORQUE_FLUX_LIMITS 0x5E), but I always get the same result. I&amp;#39;ve uploaded TMCL-IDE screenshot of the situation. If someone has some idea it would be much appreciated.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:172px;max-width:2560px;" alt=" " src="https://ez.analog.com/resized-image/__size/5120x344/__key/communityserver-discussions-components-files/314/Screenshot-2026_2D00_07_2D00_10-161917.png" /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>TMCL IDE PI Tuning</title><link>https://ez.analog.com/thread/604969?ContentTypeID=0</link><pubDate>Thu, 25 Jun 2026 18:40:46 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:21d147e6-adfa-4bf4-92e3-994e28c95219</guid><dc:creator>azincolorado</dc:creator><slash:comments>0</slash:comments><comments>https://ez.analog.com/thread/604969?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/604969/tmcl-ide-pi-tuning/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Background details: Using tmc4671 eval board with the 10A70V-EV-KIT +&amp;nbsp;&lt;span&gt;mpr80 BLDC motor from Parker&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Is there any way to expand the x axis at all? Additionally, when tuning the velocity loop, my velocity P value will go to the max for the autotuning and manually it does not go high enough to be able to properly control the motor in closed loop control. Is there a way to get this value to go higher at all or is there something else I could be missing when tuning this control loop?&lt;/p&gt;
&lt;p&gt;I also have had many times when I tune the control loop and save all the settings into a script in the tmcl ide and the next day it will just stop working completely. I have checked that my encoders are not drifting and they are outputting the right data.&lt;/p&gt;
&lt;p&gt;I have also been confused on commands in the scripting because it seems MVP commands do not work in closed loop control and I have been opting to use&amp;nbsp;WMC position target commands instead. The documentation for the IDE is outdated and doesn&amp;#39;t include much for PI control tuning testing scripts.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If someone could point me in the direction of documentation that is more updated or if you have any info on these problems please reach out. The code for the script is pasted below.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;// Select module&lt;br /&gt;#module 1 COM11/USB/id1/LandungsbrueckeV3&lt;/p&gt;
&lt;p&gt;// Use TMC4671 register addresses&lt;br /&gt;#include TMC4671_register_addresses.tpc&lt;br /&gt;// (C:/Users/alex.ziegler/AppData/Roaming/TRINAMIC Motion Control GmbH &amp;amp; Co. KG/TMCL-IDE/TMCL-Script/TMC4671_register_addresses.tpc)&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;//&lt;br /&gt;WMC PWM_MAXCNT , 0, $00000F9F, 1 //0x18: PWM maximum (count-1), PWM frequency is fPWM[Hz] = 100MHz/(PWM_MAXCNT+1)&lt;br /&gt;WMC PWM_BBM_H_BBM_L , 0, $00001919, 1 //0x19: Break Before Make time tBBM_L[10ns] for low side MOS-FET gate control&lt;br /&gt;WMC PWM_SV_CHOP , 0, $00000007, 1 //0x1A: PWM chopper mode, defining how to chopper&lt;/p&gt;
&lt;p&gt;//&lt;br /&gt;WMC ADC_I_SELECT , 0, $24000100, 1 //0x0A: Select input for raw current ADC_I0_RAW.&lt;br /&gt;WMC dsADC_MCFG_B_MCFG_A, 0, $00100010, 1 //0x04: &lt;br /&gt;WMC dsADC_MCLK_A , 0, $20000000, 1 //0x05: fMCLK_A = 2^31 / (fCLK * (dsADC_MCLK_A+1)), dsADC_MCLK_A = (2^31 / (fMCLK * fCLK)) - 1&lt;br /&gt;WMC dsADC_MCLK_B , 0, $20000000, 1 //0x06: fMCLK_B = 2^31 / (fCLK * (dsADC_MCLK_B+1)), dsADC_MCLK_B = (2^31 / (fMCLK * fCLK)) - 1&lt;br /&gt;WMC dsADC_MDEC_B_MDEC_A, 0, $014E014E, 1 //0x07: 0: PWM synchron, others according to register content&lt;/p&gt;
&lt;p&gt;//&lt;br /&gt;WMC ADC_I0_SCALE_OFFSET, 0, $01008144, 1 //0x09: Offset for current ADC channel 0.&lt;br /&gt;WMC ADC_I1_SCALE_OFFSET, 0, $01008167, 1 //0x08: Offset for current ADC channel 1.&lt;br /&gt;WMC ADC_I_SELECT , 0, $18000100, 1 //0x0A: Select input for raw current ADC_I0_RAW.&lt;br /&gt;WMC UQ_UD_EXT , 0, $00000FA0, 1 //0x24: External writable parameter for open loop voltage control mode, usefull during system setup, U_D component.&lt;br /&gt;WMC dsADC_MDEC_B_MDEC_A, 0, $014E014E, 1 //0x07: 0: PWM synchron, others according to register content&lt;/p&gt;
&lt;p&gt;//&lt;br /&gt;WMC ABN_DECODER_MODE , 0, $00000000, 1 //0x25: Polarity of A pulse.&lt;br /&gt;WMC ABN_DECODER_PPR , 0, $00039D00, 1 //0x26: Decoder pulses per mechanical revolution.&lt;br /&gt;WMC ABN_DECODER_COUNT , 0, $0000D5CA, 1 //0x27: Raw decoder count; the digital decoder engine counts modulo (decoder_ppr).&lt;br /&gt;WMC ABN_DECODER_COUNT_N , 0, $0001B606, 1 //0x28: Decoder count latched on N pulse, when N pulse clears decoder_count also decoder_count_n is 0.&lt;br /&gt;WMC ABN_DECODER_PHI_E_PHI_M_OFFSET, 0, $00000000, 1 //0x29: ABN_DECODER_PHI_M_OFFSET to shift (rotate) angle DECODER_PHI_M.&lt;br /&gt;WMC ABN_DECODER_PHI_E_PHI_M , 0, $B1093B03, 1 //0x2A: ABN_DECODER_PHI_M = ABN_DECODER_COUNT * 2^16 / ABN_DECODER_PPR + ABN_DECODER_PHI_M_OFFSET;&lt;br /&gt;WMC PID_POSITION_ACTUAL , 0, $FFAD9FC7, 1 //0x6B: Actual multi turn position for positioning. WRITE on PID_POSITION_ACTUAL writes same value into PID_POSITION_TARGET to avoid unwanted move.&lt;br /&gt;WMC MOTOR_TYPE_N_POLE_PAIRS , 0, $00030003, 1 //0x1B: Number n of pole pairs of the motor for calcualtion phi_e = phi_m / N_POLE_PAIRS.&lt;/p&gt;
&lt;p&gt;// --- Limiter setup (set before entering velocity/position mode) ---&lt;br /&gt;WMC PIDOUT_UQ_UD_LIMITS , 0, $00007FFF, 1 //max PWM/voltage output = 32767 (full)&lt;br /&gt;WMC PID_TORQUE_FLUX_LIMITS , 0, $000007D0, 1 //current limit = 2000 (see units note)&lt;br /&gt;WMC PID_VELOCITY_LIMIT , 0, $0001E848, 1 //velocity clamp = 125000 (set high to start)&lt;br /&gt;WMC PID_POSITION_LIMIT_LOW , 0, $800146C0, 1 //-2,147,400,000&lt;br /&gt;WMC PID_POSITION_LIMIT_HIGH, 0, $7FFEB940, 1 //+2,147,400,000&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;WMC MODE_RAMP_MODE_MOTION, 0, $00000003, 1 //0x1F: position mode&lt;br /&gt;WMC PHI_E_SELECTION, 0, $00000003, 1 //0x52: &lt;br /&gt;WMC VELOCITY_SELECTION, 0, $00000009, 1 //0x50: phi_m_abn (mechanical angle from ABN)&lt;br /&gt;WMC POSITION_SELECTION, 0, $00000009, 1 //0x51: phi_m_abn&lt;/p&gt;
&lt;p&gt;// PI control parameters (P in [31:16], I in [15:0])&lt;br /&gt;WMC PID_FLUX_P_FLUX_I , 0, $2EE01B58, 1 //0x54: PID_FLUX_P = 12000, PID_FLUX_I = 7000&lt;br /&gt;WMC PID_TORQUE_P_TORQUE_I , 0, $2EE01B58, 1 //0x56: PID_TORQUE_P = 12000, PID_TORQUE_I = 7000&lt;br /&gt;WMC PID_VELOCITY_P_VELOCITY_I,0, $7FFF0FA0, 1 //0x58: PID_VELOCITY_P = 32767, PID_VELOCITY_I = 4000&lt;br /&gt;WMC PID_POSITION_P_POSITION_I,0, $008C0000, 1 //0x5A: PID_POSITION_P = 140, PID_POSITION_I = 0&lt;br /&gt;WMC PID_POSITION_ACTUAL, 0, $00000000, 1 //set position to 0&lt;/p&gt;
&lt;p&gt;WAIT TICKS, 0, 5000&lt;/p&gt;
&lt;p&gt;Loop:&lt;/p&gt;
&lt;p&gt;WMC PID_POSITION_TARGET, 0, 5000, 1 // quarter turn, direct&lt;/p&gt;
&lt;p&gt;WAIT TICKS, 0, 2000&lt;/p&gt;
&lt;p&gt;WMC PID_POSITION_TARGET, 0, 15000, 1 &lt;br /&gt;WAIT TICKS, 0, 2000&lt;/p&gt;
&lt;p&gt;WMC PID_POSITION_TARGET, 0, 0, 1 &lt;br /&gt;WAIT TICKS, 0, 2000&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;JA Loop&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Limit switch</title><link>https://ez.analog.com/thread/604938?ContentTypeID=0</link><pubDate>Wed, 24 Jun 2026 08:46:12 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:824e112e-0bdd-463d-8857-0e6e1caccc17</guid><dc:creator>MarkusIOM</dc:creator><slash:comments>0</slash:comments><comments>https://ez.analog.com/thread/604938?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/604938/limit-switch/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p class="isSelectedEnd"&gt;&lt;span&gt;Dear Sir or Madam,&lt;/span&gt;&lt;/p&gt;
&lt;p class="isSelectedEnd"&gt;&lt;span&gt;I am trying to control a linear stage with a stepper motor using a TRINAMIC TMCM-102-IF motion controller, TMCL-IDE 4.11.0 software, and a USB connection in Direct Mode. Controlling the motion itself is no problem. However, I am experiencing an issue when using the limit switches.&lt;/span&gt;&lt;/p&gt;
&lt;p class="isSelectedEnd"&gt;&lt;span&gt;When a limit switch is activated, the stage pulls the corresponding signal line from +5 V to 0 V (active low). The controller correctly detects the switch state, and I can read the status in the TRINAMIC software.&lt;/span&gt;&lt;/p&gt;
&lt;p class="isSelectedEnd"&gt;&lt;span&gt;By default, the limit switches are ignored (Parameters 12 and 13, &amp;quot;Stop switch disable&amp;quot;, set to 1). After manually setting Parameters 12 and 13 to 0, the limit switches worked correctly the first time they were activated. When a switch was triggered, the stage stopped and the controller correctly blocked further movement toward that switch.&lt;/span&gt;&lt;/p&gt;
&lt;p class="isSelectedEnd"&gt;&lt;span&gt;However, after moving the stage back toward the center, motion in that direction remained blocked, even though the switch was no longer activated.&lt;/span&gt;&lt;/p&gt;
&lt;p class="isSelectedEnd"&gt;&lt;span&gt;I repeated the test with the opposite limit switch and observed the same behavior. After triggering limit switch 2, movement toward limit switch 2 was permanently blocked as well. As a result, both directions are now blocked.&lt;/span&gt;&lt;/p&gt;
&lt;p class="isSelectedEnd"&gt;&lt;span&gt;I have verified the following:&lt;/span&gt;&lt;/p&gt;
&lt;ul data-spread="false"&gt;
&lt;li&gt;&lt;span&gt;The wiring is correct.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;When the limit switches are ignored (Parameters 12 and 13 set to 1), the stage operates normally.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;When limit switch monitoring is enabled, the stage does not move (since both directions are blocked)&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;ul data-spread="false"&gt;
&lt;li&gt;&lt;span&gt;If only one limit switch is ignored, movement in the corresponding direction is possible.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;The stage provides the correct signals at both switches: +5 V when inactive and 0 V when active (verified with a voltmeter).&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;The controller correctly reports the state of both switches in the TRINAMIC software.&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p class="isSelectedEnd"&gt;&lt;span&gt;It appears that activating a limit switch sets an internal status or parameter that prevents further motion in that direction. However, when the switch is released, this status does not seem to be cleared automatically.&lt;/span&gt;&lt;/p&gt;
&lt;p class="isSelectedEnd"&gt;&lt;span&gt;I have already tried the following:&lt;/span&gt;&lt;/p&gt;
&lt;ul data-spread="false"&gt;
&lt;li&gt;&lt;span&gt;Rebooting the controller&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Clearing the error flags (Parameter 36)&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Restoring the factory settings (Parameter 137)&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p class="isSelectedEnd"&gt;&lt;span&gt;Unfortunately, none of these actions resolved the issue. Motion in both directions remains blocked.&lt;/span&gt;&lt;/p&gt;
&lt;p class="isSelectedEnd"&gt;&lt;span&gt;Has anyone experienced a similar problem or knows how to reset the limit-switch status so that motion is re-enabled after the switch is released?&lt;/span&gt;&lt;/p&gt;
&lt;p class="isSelectedEnd"&gt;&lt;span&gt;Thank you in advance for your help,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Markus&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>TMC2130-EVAL-KIT and   Landungsbrücke Eval System: Problem with getting the motor to stop with stallguard2</title><link>https://ez.analog.com/thread/604833?ContentTypeID=0</link><pubDate>Wed, 17 Jun 2026 12:25:14 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:cbecdd6c-b20a-477a-8b03-1b707fafe54d</guid><dc:creator>Enokkio</dc:creator><slash:comments>0</slash:comments><comments>https://ez.analog.com/thread/604833?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/604833/tmc2130-eval-kit-and-landungsbrucke-eval-system-problem-with-getting-the-motor-to-stop-with-stallguard2/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hello, first time poster so a bit unsure of the etiquette but i hope I&amp;#39;ve understood things correctly.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I am currently using the TMC2130-EVAL-KIT and Landungsbr&amp;uuml;cke Eval System together with the TMCL-IDE (v4.110). The stepper motor is from Haydonkerk, E21H4N.&amp;nbsp; I have been unable to make the motor stop for when the SG_RESULT value hits 0, i tuned the SGT-threshold for the motor.&lt;/p&gt;
&lt;p&gt;If i put smartEnergy Velocity to anything below my target/current speed it instantly kills the motor speed (independent of acceleration speed), and it seems to register as a stall as i need to click reset stall to make it start again. I followed this video (&lt;a href="https://www.youtube.com/watch?v=l6r63Q7Yr58&amp;amp;t"&gt;https://www.youtube.com/watch?v=l6r63Q7Yr58&amp;amp;t&lt;/a&gt;&amp;nbsp;&lt;span&gt;coolstep is irrelevant&amp;nbsp;&lt;/span&gt;) aswell both with my configs changes and without&amp;nbsp;but i didn&amp;#39;t get the same result, granted it is different evaluation board and motor.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Currently I&amp;#39;ve set:&lt;/p&gt;
&lt;p&gt;TCOOLTHRS to its max value 0x00FFFFF&amp;nbsp;&lt;/p&gt;
&lt;p&gt;THIGH to 0&lt;span&gt;x0000001&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Target velocity to 52100pps which corresponds to 1rps (hopefully this makes the back EMF-significant enough)&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;acceleration to 2k pps^2&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Maximum current: 168mA&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Minimum current: 72mA&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The reason for the register values to my understanding is to make sure that the speed of the stepper motor TSTEP is between TCOOLTHRS and THIGH for stallguard to trigger.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I have also disabled stealthChop both in chopper settings and in the conf register by disabling en_pwm_mode. I&amp;#39;ve also made sure to activate diag0_stall and diag1_stall (Though unsure if that did anything).&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any input would be helpful! Thanks!&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>motor is noisy  by standstill current reduction......</title><link>https://ez.analog.com/thread/604633?ContentTypeID=0</link><pubDate>Fri, 05 Jun 2026 12:10:28 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:4be1c730-0f06-4714-99c9-f20a2c0a7e65</guid><dc:creator>SaadNaeem</dc:creator><slash:comments>0</slash:comments><comments>https://ez.analog.com/thread/604633?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/604633/motor-is-noisy-by-standstill-current-reduction/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;I am using stepper motor which require around 110mA current per coil.........!&lt;br /&gt;originally i am using sense resistor of 750mA which is corressponds to 400mA and stand still current reduction of 34% is 136mA.&lt;br /&gt;so motor get hot&amp;nbsp; if i enable stand still current reduction by floating enable pin.....!&lt;br /&gt;so my requirement is to use 2R2 resistor to get running current of 110mA or more and current reduction of 37mA.&lt;br /&gt;Is this ok to use 2R2 resistor?&lt;br /&gt;&lt;br /&gt;Also even using 750mA and floating enable pin &amp;quot;CFG6_ENN &amp;quot; there is a sound coming from motor......!&lt;br /&gt;not too much noisy.......&lt;br /&gt;Is it a problem as motor precise enough no component motor or driver is getting hot???&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Charge Pump failure, although recommended fixes were applied</title><link>https://ez.analog.com/thread/604557?ContentTypeID=0</link><pubDate>Mon, 01 Jun 2026 16:49:02 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:59dba63c-718f-46e2-9c35-d01f30665b91</guid><dc:creator>egoeppert</dc:creator><slash:comments>0</slash:comments><comments>https://ez.analog.com/thread/604557?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/604557/charge-pump-failure-although-recommended-fixes-were-applied/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi there,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;We are using a TMC2160 Stepper Motor Driver.&lt;/p&gt;
&lt;p&gt;We design the PCB according to the recommendation ( well my HW colleague missed the Filter recommandations for the charging pump but designed part of the circuit according to the datasheet)&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;The driver has been used&amp;nbsp; several days without problems with 24V voltage input ( Lab DC power supply )&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The initial design is in the picture here.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://ez.analog.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/314/pastedimage1780330675872v1.png" /&gt;&lt;/p&gt;
&lt;p&gt;While trying to increase the voltage of the Power supply to 48V ( which is our voltage target) we experienced troubles as the driver became hot, drew more current even disabled state, and the motor could not longer be controlled.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We tried the recommended changes&amp;nbsp; (Datasheet Section 3.1, p14) which is an RC Filter on the charge pump input.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://ez.analog.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/314/TMC2160A_5F00_ChargePump_5F00_Design.png" /&gt;&lt;/p&gt;
&lt;p&gt;With power supply of 24V, the signal on CPO and CPI were 2 Square signals, Amplitude ~12V , F= 750KHz and an offset of +24V on CPI. The square signal was also visible on both sided of the signal once the failure occurred , but the 24V&amp;nbsp; offset was missing.&lt;/p&gt;
&lt;p&gt;I had no time to make an scope screenshot, as soon after , the same failure appeared on the driver ( not sure if I might have made a short with my probe or if it was the same problem, but I didn&amp;#39;t even had the time to try the motor this time)&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We have 3 x 220uF Caps on the 48V , as near as possible to the power bridges.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Did anyone come across a similar&amp;nbsp; problem ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Is there any additional recommendation concerning what that issue, that we could try before burning any more chips ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;[Edit]&amp;nbsp;&lt;/p&gt;
&lt;p&gt;After checking our PCB, the 3 x 220uF Caps for 24V/48V buffering/decoupling capacitors seems be connected to PGND and not GND.&lt;/p&gt;
&lt;p&gt;PGND is used to measure the motor current / calculate power ( PGND and GND are connected through a 20mOhms Shunt)&lt;/p&gt;
&lt;p&gt;The driver however is connected to GND and 24V//48V&lt;/p&gt;
&lt;p&gt;Not sure if that could be one of the cause of the Charge Pump failure in the Driver.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://ez.analog.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/314/pastedimage1780393401318v1.png" /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Voltage Differential Required to Trigger TMC2590 Short‑Circuit Protection</title><link>https://ez.analog.com/thread/604550?ContentTypeID=0</link><pubDate>Mon, 01 Jun 2026 10:18:04 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:51dcfd96-a830-49c4-ad57-3c06e5917220</guid><dc:creator>Ydouami</dc:creator><slash:comments>0</slash:comments><comments>https://ez.analog.com/thread/604550?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/604550/voltage-differential-required-to-trigger-tmc2590-short-circuit-protection/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hello,&lt;br /&gt;&lt;br /&gt;I am using a TMC2590 to drive a 50 V stepper motor, and the MOSFETs are being switched off due to short‑circuit detection. I have observed that the motor outputs show a voltage difference relative to VS.&lt;br /&gt;Could you please tell me what voltage differential between VS and the motor outputs is required to trigger the short‑circuit detection ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Unable to communicate via SPI with TMC5160</title><link>https://ez.analog.com/thread/604149?ContentTypeID=0</link><pubDate>Tue, 28 Apr 2026 16:48:08 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:f3f1967e-d909-49e7-8653-4403ae9376d3</guid><dc:creator>SaadNaeem</dc:creator><slash:comments>2</slash:comments><comments>https://ez.analog.com/thread/604149?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/604149/unable-to-communicate-via-spi-with-tmc5160/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;I am migrating from TMC2660 to TMC5160 using psoc CY8C4248AZI-L485.&lt;br /&gt;&lt;br /&gt;while reading a register e.g. ioin= 0x04 or irrun= 0x10 i get alway&amp;nbsp; first byte as 0x39 and then on first try i get all 0xffffffff&lt;br /&gt;if i try to read again i get 0x00....&lt;br /&gt;can some body guide why it is so?&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Maximum PWM frequency of MAX22208</title><link>https://ez.analog.com/thread/604112?ContentTypeID=0</link><pubDate>Sun, 26 Apr 2026 15:43:45 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:ab0d0aa2-45fb-4623-9142-495087aff6fc</guid><dc:creator>MohanMukka</dc:creator><slash:comments>1</slash:comments><comments>https://ez.analog.com/thread/604112?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/604112/maximum-pwm-frequency-of-max22208/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hello,&lt;br /&gt;&lt;br /&gt;we are planning to use MAX22208 for one of our application, which is best suited for our requirements, while i was looking datasheet for&amp;nbsp;&lt;span&gt;maximum PWM switching frequency that can be applied im unable to find it. C&lt;/span&gt;an you please provide what is the maximum PWM switching frequency of MAX22208 supported.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>XACTUAL only increments</title><link>https://ez.analog.com/thread/604053?ContentTypeID=0</link><pubDate>Wed, 22 Apr 2026 12:46:00 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:5aa8453f-8ab4-4d3d-b068-301a265b1fae</guid><dc:creator>gjm27n</dc:creator><slash:comments>8</slash:comments><comments>https://ez.analog.com/thread/604053?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/604053/xactual-only-increments/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;I am using a TMC4361A for a new design and after resetting XACTUAL to a predetermined amount, I need to read via SPI to know location. I&amp;#39;ve noticed XACTUAL increments in both directions. Is it possible (or is there another register) that increments in one direction and decrements in the other?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Suspected torque-off mode</title><link>https://ez.analog.com/thread/603795?ContentTypeID=0</link><pubDate>Tue, 07 Apr 2026 18:22:43 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:f5b2dbb8-d173-4285-9855-1f8ff1718c57</guid><dc:creator>dkarnes</dc:creator><slash:comments>0</slash:comments><comments>https://ez.analog.com/thread/603795?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/603795/suspected-torque-off-mode/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;We are operating in CANopen mode, running motors in position mode.&amp;nbsp; Both STO pins are tied together, so they should not ever be in different states.&amp;nbsp; However, intermittently the symptoms we are seeing seem consistent with the torque off mode.&amp;nbsp; When in this state, motor move commands generate a slightly audible &amp;quot;click,&amp;quot; seeming to indicate the command was issued, but the motors do not move.&amp;nbsp; When in this state, all motors exhibit the same symptom.&amp;nbsp; The only thing that clears the condition is a power cycle of the TMCM 6214.&amp;nbsp; Resetting our host system does not resolve the state.&amp;nbsp; Also, the DS402 status words do not reflect any fault conditions.&amp;nbsp; My questions are twofold.&amp;nbsp; (1) Does anyone know what is causing this state? (2) Is there any way to query its status?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Stall Guard result is not varying enough to use cool step</title><link>https://ez.analog.com/thread/603770?ContentTypeID=0</link><pubDate>Mon, 06 Apr 2026 17:43:17 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:3b0160bc-500f-49f8-8951-f74c26d8caa1</guid><dc:creator>maxd777</dc:creator><slash:comments>2</slash:comments><comments>https://ez.analog.com/thread/603770?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/603770/stall-guard-result-is-not-varying-enough-to-use-cool-step/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;I am using a small stepper motor (&lt;span&gt;SY20STH30-0604&lt;/span&gt;&lt;span&gt;A) to spin a worm drive, and it worked great. But now I am trying to use the cool step functionality because I am having heat issues. I have the TMC5240 eval kit, and I am looking at the SG result value, which drives cool step, and I see that the SG result does not vary much if I apply a heavier load and only drops around 10 units until the load gets too heavy and it stalls. I was wondering if there is any way to blow up the resolution of the SG result? Like instead of varying 10 units I could make it vary 100?&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>TMC2240 100uF capacitor</title><link>https://ez.analog.com/thread/603698?ContentTypeID=0</link><pubDate>Tue, 31 Mar 2026 17:26:05 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:bb8e65e0-e474-4406-8f9f-9fddf4bf0acf</guid><dc:creator>AranelJNJ</dc:creator><slash:comments>1</slash:comments><comments>https://ez.analog.com/thread/603698?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/603698/tmc2240-100uf-capacitor/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&amp;nbsp;For the TMC2240 the datasheet lists, &amp;quot;A minimum capacity of 100&amp;micro;F at VS is recommended for best performance.&amp;quot; on page&amp;nbsp;124. The schematic devkit for the product show a 47uF DNP capacitor for Vs.&amp;nbsp;TMC2240-BOB_V10. How much is performance impacted by using a 47uF versus 100 uF.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;The TMC2240-eval also doesn&amp;#39;t show a large capacitor for Vs.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>TMC5160A-WA hardware configuration for control through only SPI</title><link>https://ez.analog.com/thread/603643?ContentTypeID=0</link><pubDate>Fri, 27 Mar 2026 12:19:03 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:49220694-b4f5-4e77-ad2c-d33c18d95bde</guid><dc:creator>savi</dc:creator><slash:comments>17</slash:comments><comments>https://ez.analog.com/thread/603643?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/603643/tmc5160a-wa-hardware-configuration-for-control-through-only-spi/rss?ContentTypeId=0</wfw:commentRss><description>&lt;div&gt;Hi ,&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&lt;div&gt;We are using the part :&amp;nbsp;TMC5160A-WA for driving 2 phase stepper motor with 5A current. this stepper motor is placed inside a peristaltic pump which will be used in a medical device.&lt;/div&gt;
&lt;div&gt;schematics is attached in file.&lt;/div&gt;
&lt;div&gt;Basically i want to control the motor using this driver IC&amp;nbsp;TMC5160A-WA by controlling SPI communication from MCU. No other inputs from MCU is provided. pls go through schematics for our configuration. my doubt is under which mode the ic have to configure to do the control purely by SPI communication?&lt;/div&gt;
&lt;div&gt;we are not planning to connect encode signal from motor back to driver ic encoder input?does it causes issue in basic working of&amp;nbsp;TMC5160A-WA.&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&lt;div&gt;expecting reply soon....&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://ez.analog.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/314/analog.jpg" /&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>What is new in the TMC5262 and why is it a Game Changer for Stepper motors?</title><link>https://ez.analog.com/thread/603576?ContentTypeID=0</link><pubDate>Tue, 24 Mar 2026 09:44:01 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:5fb1e313-4932-4f9a-8331-fe1581645dc4</guid><dc:creator>BernhardDwersteg</dc:creator><slash:comments>1</slash:comments><comments>https://ez.analog.com/thread/603576?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/603576/what-is-new-in-the-tmc5262-and-why-is-it-a-game-changer-for-stepper-motors/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;TRINAMIC brought SpreadCycle with the TMC262 in 2012 and StealthChop in 2015 with the TMC5130. What is the Special about StealthChop+?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Interface TMC8100 with TMC4671's SPI debug interface to periodically update PHI_E_EXT with the encoder's position</title><link>https://ez.analog.com/thread/603512?ContentTypeID=0</link><pubDate>Fri, 20 Mar 2026 04:33:51 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:59c785b3-4515-42e6-8c80-6821f2d0fa3d</guid><dc:creator>krassi</dc:creator><slash:comments>0</slash:comments><comments>https://ez.analog.com/thread/603512?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/603512/interface-tmc8100-with-tmc4671-s-spi-debug-interface-to-periodically-update-phi_e_ext-with-the-encoder-s-position/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;My goal is to use the &lt;strong data-start="451" data-end="525"&gt;TMC8100 to periodically update the &lt;code data-start="488" data-end="499"&gt;PHI_E_EXT&lt;/code&gt; register of the TMC4671&lt;/strong&gt; via its SPI debug interface ...&lt;/p&gt;
&lt;p&gt;Has anyone implemented this type of interface between &lt;strong data-start="905" data-end="926"&gt;TMC8100 &amp;rarr; TMC4671&lt;/strong&gt;?&lt;/p&gt;
&lt;p&gt;Is it feasible for the TMC8100 to directly drive the &lt;strong data-start="984" data-end="1007"&gt;SPI debug interface&lt;/strong&gt; of the TMC4671, or is an MCU required as an intermediary?&lt;/p&gt;
&lt;p&gt;Are there any recommended synchronization strategies?&lt;br /&gt;&lt;br /&gt;Any example code, application notes, or reference designs demonstrating this architecture?&lt;br /&gt;&lt;br /&gt;note:&amp;nbsp;I understand that, in order to use this encoder as the position source for FOC, the &lt;code data-start="402" data-end="413"&gt;PHI_E_EXT&lt;/code&gt; register needs to be periodically updated with the encoder position, after applying the required offset and conversion based on the motor pole-pair count.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>How to update firmware to TMC8100  via  UART of MCU ?</title><link>https://ez.analog.com/thread/603507?ContentTypeID=0</link><pubDate>Fri, 20 Mar 2026 02:10:57 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:8f00c142-8b33-49bc-b7b1-999e11626267</guid><dc:creator>double6318531</dc:creator><slash:comments>1</slash:comments><comments>https://ez.analog.com/thread/603507?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/603507/how-to-update-firmware-to-tmc8100-via-uart-of-mcu/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;TCM4671 + TMC8100 + STM32,&amp;nbsp; &amp;nbsp;How can i&amp;nbsp; update fimware to tmc8100 via uart of MCU?&amp;nbsp; Do you have some example demo or doccument to guide user ?&amp;nbsp; &amp;nbsp;&lt;em&gt;&lt;span class="skip"&gt;Looking forward to your reply&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Synchronizing multiple TMC5240's</title><link>https://ez.analog.com/thread/603493?ContentTypeID=0</link><pubDate>Thu, 19 Mar 2026 12:26:13 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:4bc21ccb-76f5-4c36-a060-8f329c9335e8</guid><dc:creator>HKeni</dc:creator><slash:comments>3</slash:comments><comments>https://ez.analog.com/thread/603493?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/603493/synchronizing-multiple-tmc5240-s/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;I have come to experience, very painfully, that no matter what I try I cannot get two or more steppers running the TMC5240 to be driven in sync. I have tried SPI broadcast (separate CS pins fired simultaneously), providing a common clock source, etc. Has anyone figured out an effective way to trigger the motion synchronously?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>TMC2160 SPI Interface example error in Datasheet rev 1.10</title><link>https://ez.analog.com/thread/603319?ContentTypeID=0</link><pubDate>Wed, 11 Mar 2026 07:44:37 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:46f6d368-db63-47bc-9a97-b3c32b0b7242</guid><dc:creator>Nicolai</dc:creator><slash:comments>1</slash:comments><comments>https://ez.analog.com/thread/603319?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/603319/tmc2160-spi-interface-example-error-in-datasheet-rev-1-10/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I assume that the example SPI write access on page 21 of the TMC2160 datasheet (rev 1.10 / 2023-Mar-01) is so obviously wrong that no one bothers asking about it or fixing it?&lt;/p&gt;
&lt;p&gt;&lt;span style="font-family:impact, chicago;"&gt;action&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;data sent to TMC2160&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;data received from TMC2160&lt;/span&gt;&lt;br /&gt;read TSTEP&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 0x1200000000&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 0xSS &amp;amp; unused data&lt;br /&gt;read TSTEP&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 0x1200000000&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 0xSS &amp;amp; TSTEP&lt;br /&gt;write IHOLD_IRUN:= 0x00011F10&amp;nbsp; &amp;nbsp; &amp;nbsp;0x9000&lt;span style="font-family:impact, chicago;font-size:inherit;"&gt;ABCDEF&lt;/span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 0xSS &amp;amp; TSTEP&lt;br /&gt;write IHOLD_IRUN:= 0x00021807&amp;nbsp; &amp;nbsp; &amp;nbsp;0x9000&lt;span style="font-family:impact, chicago;"&gt;123456&lt;/span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 0xSS00011F10&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>TMC2209 homing accuracy with mechanical end stops only (not stall detection)</title><link>https://ez.analog.com/thread/603155?ContentTypeID=0</link><pubDate>Wed, 04 Mar 2026 10:15:59 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:a081c3f8-c840-4453-a955-c8a0bc93045e</guid><dc:creator>DGLyon</dc:creator><slash:comments>6</slash:comments><comments>https://ez.analog.com/thread/603155?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/603155/tmc2209-homing-accuracy-with-mechanical-end-stops-only-not-stall-detection/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I am developping a product using two stepper motors. I have implemented TMC2209 and it work well to rotate the motor.&lt;/p&gt;
&lt;p&gt;However I can&amp;#39;t make homing using stall detection repeatable on the pre-serie samples. For that reason I changed to more basic homing using mechanical end stop and bumping into it multiple time to ensure position is home position.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I inplemented&amp;nbsp; full step mode and pattern detection to ensure the position is repeatable : coil supplied and B coil is not supplied (reading back from the TMC2209).&lt;/p&gt;
&lt;p&gt;This works ok but when switching back to 1/64 step mode, I notice a shift that is not repeatable when power is cycled. This creates inaccuracy to the homing.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Is that an expected behavior ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Is this strategy relevant to do such a homing using TMC2209 ?&lt;/p&gt;
&lt;p&gt;In term of mechanical design this is very basic : the shaft of the motor is firmly attached to a bracket bumping in a rigid mechanical part for homing.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks for your help.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>When connecting to TMC4671-TMC6100-BOB the Landungsbruecke error LED lights up</title><link>https://ez.analog.com/thread/603079?ContentTypeID=0</link><pubDate>Sun, 01 Mar 2026 14:15:23 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:6ce7ea8b-23be-45f3-ae06-0b745e40e05d</guid><dc:creator>PhiMo</dc:creator><slash:comments>3</slash:comments><comments>https://ez.analog.com/thread/603079?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/603079/when-connecting-to-tmc4671-tmc6100-bob-the-landungsbruecke-error-led-lights-up/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;I have a&amp;nbsp;Landungsbruecke Module v3.1. The firmware is &amp;quot;LandungsbrueckeV3_v3.09.6_BL_TMC4671_TMC6100_BOB&amp;quot;. &lt;br /&gt;The wiring is as specified in the &amp;ldquo;&lt;a href="https://www.analog.com/media/en/evaluation-documentation/evaluation-design-files/tmc4671-tmc6100-bob-firmware-guide.zip"&gt;tmc4671-tmc6100-bob-firmware-guide&lt;/a&gt;&amp;rdquo; manual.&lt;br /&gt;As soon as I select the motion controller board or the driver board, the error LED on the landing bridge lights up.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:768px;max-width:978px;" alt=" " src="https://ez.analog.com/resized-image/__size/1956x1536/__key/communityserver-discussions-components-files/314/1.jpg" /&gt;&lt;/p&gt;
&lt;p&gt;The registers of the TMC6100 are all set to 0 and cannot be changed.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:768px;max-width:978px;" alt=" " src="https://ez.analog.com/resized-image/__size/1956x1536/__key/communityserver-discussions-components-files/314/2.jpg" /&gt;&lt;/p&gt;
&lt;p&gt;The motor also does not rotate in &amp;ldquo;open loop&amp;rdquo; mode.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;Is there a solution to this problem, or am I doing something wrong?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>dcStep Wizard not showing on TMCL IDE (4.3.0) connected to TMC5130 Eval Board (v1.5) through Landungsbrucke (v3.0)</title><link>https://ez.analog.com/thread/603028?ContentTypeID=0</link><pubDate>Thu, 26 Feb 2026 16:25:38 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:fa8028df-1f5c-4cd3-9367-3130af02efb2</guid><dc:creator>AMLatLightcast</dc:creator><slash:comments>3</slash:comments><comments>https://ez.analog.com/thread/603028?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/603028/dcstep-wizard-not-showing-on-tmcl-ide-4-3-0-connected-to-tmc5130-eval-board-v1-5-through-landungsbrucke-v3-0/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;I have TMCL IDE 4.3.0 on my laptop connected via USB to the ADI Trinamics Landungsbrucke v3.0 which is connected to the TMC5130-EVAL v1.5.&lt;/p&gt;
&lt;p&gt;The TMC5130 clearly states that the dcStep mode is available for the TMC5130 and I can see the dcStep registers in the register browser. There are also videos available from Trinamics showing how to use the dcStep Wizard with the TMC5130 EVAL so it&amp;#39;s quite clear that the Wizard should be available for the board I&amp;#39;m using (&lt;span&gt;TMC5130-EVAL v1.5.&lt;/span&gt;).&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;However, the TMCL-IDE doesn&amp;#39;t show the dcStep. It shows stallGuard and coolStep... but not dcStep event though it clearly detects the board:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://ez.analog.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/314/pastedimage1772122632045v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;I can see that the dcStep Wizard is not listed in the plugins list:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://ez.analog.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/314/pastedimage1772122977567v2.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;but I can&amp;#39;t find an option to add it / download it or enabled it.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any idea what I&amp;#39;m missing to make the TMCL-IDE load the dcStep Wizard?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thank you for your support, much appreciated!&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>TMC4671: Normal operation without SPI</title><link>https://ez.analog.com/thread/602979?ContentTypeID=0</link><pubDate>Wed, 25 Feb 2026 10:25:20 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:e2260f20-0c5f-4ec8-8033-acca48d5ff2c</guid><dc:creator>Coolstep</dc:creator><slash:comments>0</slash:comments><comments>https://ez.analog.com/thread/602979?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/602979/tmc4671-normal-operation-without-spi/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;We want to move from Maxon control system to a dedicated chip on the board. I got&amp;nbsp;the&amp;nbsp;TMC4671-10A70V-EV-KIT and try to get it running with our product.&lt;/p&gt;
&lt;p&gt;Short summory: steering application, 100 W BLDC motor, 2 pole pairs, 24/48 V,&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;With our device we have the following interface:&lt;/p&gt;
&lt;p&gt;1. PWM - frequency to set the velocity&lt;/p&gt;
&lt;p&gt;2. DIR - digital pin to set the direction&lt;/p&gt;
&lt;p&gt;3. EN - digital pin to turn off the motor, but still have the low side mosfets engaged.&lt;/p&gt;
&lt;p&gt;I could not find, how to realize such an interface. Programming parameters on startup is not a problem, but i would like to keep the current interface without putting an intermediate MCU between our current control chip and the&amp;nbsp;TMC4671.&lt;/p&gt;
&lt;p&gt;Is there a way to realize this functionality?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>TMC9660 Shootthrough &amp; Bootstrap Undervoltage</title><link>https://ez.analog.com/thread/602956?ContentTypeID=0</link><pubDate>Tue, 24 Feb 2026 10:55:42 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:68df3130-9640-4a36-81f0-329d719a4ce4</guid><dc:creator>luigic</dc:creator><slash:comments>1</slash:comments><comments>https://ez.analog.com/thread/602956?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/602956/tmc9660-shootthrough-bootstrap-undervoltage/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Currently have 3 TMC9660 boards, all exhibiting the same behavior. I set them up in UBLTools and TMCL-IDE using the default parameters specified in the datasheet for a 3-phase BLDC motor. I used the Wizard to test the TMC9660 configuration process before writing application code. Up to this point, there were no problems. However, once it was time to start the system, all phases had their bootstrap undervoltage flags go up, even Y2, which is unused. Clearing these bits was pretty easy (except for Y2, for which the protection flag needed to be disabled again, even though it was already disabled, to clear the flag). This seems to happen every time I first switch to open-loop mode. Once in open-loop mode, power was immediately being consumed, despite being at 0 duty cycle. The amount of power lost through shoot-through did not change with the duty cycle; it scaled with voltage. Upon checking with an oscilloscope, shoot-through occurs on every phase.&lt;/p&gt;
&lt;p&gt;I tried every combination of adaptive drive time on/off, the break before make time, gate drive current, etc., and nothing affected how much shootthrough was occurring. All three units have the same exact problem.&lt;/p&gt;
&lt;p&gt;The only setting that affected shoot-through was setting the switching&lt;span&gt;&amp;nbsp;&lt;/span&gt;scheme&lt;span&gt;&amp;nbsp;&lt;/span&gt;to flat bottom, which reduced it by 20%.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;This power loss is present in all modes available to me: open-loop current, voltage, and Hall-effect. In system off, but with the Low-side or High-side fets set to high, there is no power loss.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;To summarize, I&amp;#39;m facing these problems:&lt;/p&gt;
&lt;p&gt;- Unknown undervoltage bootstrap warning on startup and first initiation of the gate drive unit.&lt;/p&gt;
&lt;p&gt;- Shootthrough that is not affected by any parameter setting except switching&lt;span&gt;&amp;nbsp;&lt;/span&gt;scheme&lt;span&gt;&amp;nbsp;&lt;/span&gt;type, and is present in all modes.&lt;/p&gt;
&lt;p&gt;Attached is an image of the schematic.&lt;img style="max-height:1200px;max-width:2000px;" alt=" " src="https://ez.analog.com/resized-image/__size/4000x2400/__key/communityserver-discussions-components-files/314/Screenshot-2026_2D00_02_2D00_24-184252.png" data-cke-saved-src="https://ez.analog.com/resized-image/__size/4000x2400/__key/communityserver-discussions-components-files/314/Screenshot-2026_2D00_02_2D00_24-184252.png" /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I&amp;#39;d appreciate any help. Thank you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Controller stops working over time</title><link>https://ez.analog.com/thread/602854?ContentTypeID=0</link><pubDate>Thu, 19 Feb 2026 10:40:46 GMT</pubDate><guid isPermaLink="false">a884d118-f55f-49de-87eb-b9dbaf99b3e3:8f55baa7-d732-46cd-94f2-36115e186788</guid><dc:creator>nirdvash</dc:creator><slash:comments>6</slash:comments><comments>https://ez.analog.com/thread/602854?ContentTypeID=0</comments><wfw:commentRss>https://ez.analog.com/motor-control-hardware-platforms2/f/q-a/602854/controller-stops-working-over-time/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;We are using the TMCM-6110 to drive an X,Y stepper motors that move a small stage. The TMCM is mounted as a piggyback on our hosting board. Most of the time, everything works great but we encounter cases where the stepper motors will act very strange - for example turn the wrong way, make a &amp;#39;hiss&amp;#39; noise when in idle, sometimes it will make loud noises. Some of these cases are solved simply by turning our system off and on again but sometimes the problem stays and when we open up our unit we see that channel 0 which runs the X motor has been stressed by over current because there are signs of burns on both side of the PCB and on its connector - please see images&amp;nbsp;below.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Some more figures/parameters/facts on our system:&lt;/p&gt;
&lt;p&gt;1. Supply voltage - 24VDC, 5A.&amp;nbsp; This is regulated down from an external 36V/4.5 power supply (model PW-150A-1Y360H). Please see below schematics of the power supply. The 24V is fed to both power inputs of the TMCM. Our ON/OFF switch is switching the 36V to the regulator.&lt;/p&gt;
&lt;p&gt;2. The&amp;nbsp;MaxCurrent parameter (on both motors) is set to 184.&lt;/p&gt;
&lt;p&gt;3. The&amp;nbsp;StandbyCurrent parameter (on both motors) is set to 140.&lt;/p&gt;
&lt;p&gt;4. The system stays on 24/7 but does not move most of the time.&lt;/p&gt;
&lt;p&gt;5. We have grounded the TMCM to all other connectors.&lt;/p&gt;
&lt;p&gt;6. The cables we are using are 2 meters long. They are&amp;nbsp;LI12Y(LC,PUR) SERVO (4&amp;times;0.25 + 4&amp;times;0.14 + 1&amp;times;2&amp;times;0.14)&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;If there is anyone here from the ADI team or the members of this forum that has had such a problem and can direct us to understanding it and solving it - we would be very thankful.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank you,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Nir.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://ez.analog.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/314/PCB-TOP.jpeg" alt=" " /&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://ez.analog.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/314/PCB-BOTTOM.jpeg" alt=" " /&gt;&lt;a href="https://ez.analog.com/cfs-file/__key/communityserver-discussions-components-files/314/Power.pdf"&gt;ez.analog.com/.../Power.pdf&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>