# Sensorless Homing with the TMC 2240 drivers

**URL:** <https://klipper.discourse.group/t/sensorless-homing-with-the-tmc-2240-drivers/11438>\
**Category:** General Discussion\
**Created:** [November 7, 2023, 6:58pm UTC](https://klipper.discourse.group/t/sensorless-homing-with-the-tmc-2240-drivers/11438 "2023-11-07T18:58:51Z")\
**Posts on this page:** 8\
**Page:** 3

<div class="post-metadata">

**Author:** ![DrumClock](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/drumclock/32/177_2.png) [@DrumClock](https://klipper.discourse.group/u/DrumClock)\
**Post date:** [November 13, 2023, 6:11pm UTC](https://klipper.discourse.group/t/sensorless-homing-with-the-tmc-2240-drivers/11438/41 "2023-11-13T18:11:52Z")

</div>

the 600 mm/s is only a rapid movement of the toolhead, not printing, it will run around 200 mm/s

---

<div class="post-metadata">

**Author:** ![mykepredko](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/mykepredko/32/2085_2.png) [@mykepredko](https://klipper.discourse.group/u/mykepredko)\
**Post date:** [November 13, 2023, 6:16pm UTC](https://klipper.discourse.group/t/sensorless-homing-with-the-tmc-2240-drivers/11438/42 "2023-11-13T18:16:15Z")

</div>

I think the simple solution (after all you’ve been through) is to not move the toolhead that fast.

---

<div class="post-metadata">

**Author:** ![LifeOfBrian](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/lifeofbrian/32/2380_2.png) [@LifeOfBrian](https://klipper.discourse.group/u/LifeOfBrian)\
**Post date:** [November 13, 2023, 7:13pm UTC](https://klipper.discourse.group/t/sensorless-homing-with-the-tmc-2240-drivers/11438/43 "2023-11-13T19:13:33Z")

</div>

So to sum this up: you just did not try the right SGT value before or was there anything I missed here?

---

<div class="post-metadata">

**Author:** ![hcet14](https://avatars.discourse-cdn.com/v4/letter/h/ecd19e/32.png) [@hcet14](https://klipper.discourse.group/u/hcet14)\
**Post date:** [November 13, 2023, 7:25pm UTC](https://klipper.discourse.group/t/sensorless-homing-with-the-tmc-2240-drivers/11438/44 "2023-11-13T19:25:14Z")

</div>

> [@DrumClock](#):
>
> I don’t know why @hcet14 keeps referring to TMC 2130

Sorry about that, just called my old parents. That always confuses me.

> [@hcet14](#):
>
> Can you do me a favor and try something around 0. Maybe 2?

The second important thing is using DIAG0. Also see [GitHub - andrewmcgr/klipper\_tmc\_autotune: TMC stepper driver autotuning Klipper python extra](https://github.com/andrewmcgr/klipper_tmc_autotune)

---

<div class="post-metadata">

**Author:** ![mykepredko](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/mykepredko/32/2085_2.png) [@mykepredko](https://klipper.discourse.group/u/mykepredko)\
**Post date:** [November 13, 2023, 8:25pm UTC](https://klipper.discourse.group/t/sensorless-homing-with-the-tmc-2240-drivers/11438/45 "2023-11-13T20:25:28Z")

</div>

@DrumClock

Just looking at your table:

 ![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/9/9dbb24d75ff445fdeaf6f71309ab98de2c114d7a.png)

and I was thinking you might want to expand your variables a bit - try 0.6A for your run\_current and 25 for your homing\_speed.

These are the values that I am using and I’m getting a better range of values where StallGuard works instead of the single value that you’re getting.

---

<div class="post-metadata">

**Author:** ![DrumClock](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/drumclock/32/177_2.png) [@DrumClock](https://klipper.discourse.group/u/DrumClock)\
**Post date:** [November 14, 2023, 6:30pm UTC](https://klipper.discourse.group/t/sensorless-homing-with-the-tmc-2240-drivers/11438/46 "2023-11-14T18:30:05Z")

</div>

HI @mykepredko ¨  
so I did more tests and it’s the same, just too sensitive.  
the best combination is marked “green”

-Petr

 ![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/3/3c1507a090e5614597a10385bdb4b05c2f37beae.png)

---

<div class="post-metadata">

**Author:** ![mykepredko](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/mykepredko/32/2085_2.png) [@mykepredko](https://klipper.discourse.group/u/mykepredko)\
**Post date:** [November 14, 2023, 6:32pm UTC](https://klipper.discourse.group/t/sensorless-homing-with-the-tmc-2240-drivers/11438/47 "2023-11-14T18:32:44Z")

</div>

Interesting that the chip is that sensitive to only have one working value for sensorless homing.

I don’t know what else to say other than I’m happy things are working for you.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\
**Post date:** [December 15, 2023, 4:33am UTC](https://klipper.discourse.group/t/sensorless-homing-with-the-tmc-2240-drivers/11438/48 "2023-12-15T04:33:19Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

[Previous page](https://klipper.discourse.group/t/sensorless-homing-with-the-tmc-2240-drivers/11438.md?page=2)
