# M114 to include manual stepper?

**URL:** <https://klipper.discourse.group/t/m114-to-include-manual-stepper/25459>\
**Category:** General Discussion\
**Created:** [January 3, 2026, 3:44am UTC](https://klipper.discourse.group/t/m114-to-include-manual-stepper/25459 "2026-01-03T03:44:02Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![koconnor](https://avatars.discourse-cdn.com/v4/letter/k/aca169/32.png) [@koconnor](https://klipper.discourse.group/u/koconnor)\
**Post date:** [January 4, 2026, 4:30pm UTC](https://klipper.discourse.group/t/m114-to-include-manual-stepper/25459/13 "2026-01-04T16:30:41Z")

</div>

> [@shai](#):
>
> we seem to be getting somewhere now but it’s not showing any numbers

Take a look through the documents I linked above. It should be possible to figure out where the error is. (It’s not easy to debug these things remotely, without the actual hardware.)

Also, make sure you’ve enabled the given manual\_stepper objects via the GCODE\_AXIS mechanism - the M114 code above definitely wont work if the motor isn’t mapped to its corresponding axis.

> [@shai](#):
>
> But when doing moves with stop on endstop, it gets over-compressed.

I answered this as best as I could at [How to create multiple probes for multiple manual\_steppers? - #24 by koconnor](https://klipper.discourse.group/t/how-to-create-multiple-probes-for-multiple-manual-steppers/24722/24) . You seem to be asking the question, “why does the Klipper software delay its response to the driver’s stall signal?” and the answer is, “it doesn’t”. The question I think you should be asking is, “why is the tmc driver only producing a stall signal after a delay?”. I’d say best would be to investigate different tmc driver configuration settings; it may also be possible that the tmc driver isn’t suitable for detecting stalls in that situation.

Maybe that helps a little,  
-Kevin

---

_[View the full topic](https://klipper.discourse.group/t/m114-to-include-manual-stepper/25459)._