# Random erratic extruder movements at the beginning of the print

**URL:** <https://klipper.discourse.group/t/random-erratic-extruder-movements-at-the-beginning-of-the-print/7120>\
**Category:** General Discussion\
**Created:** [March 9, 2023, 12:45am UTC](https://klipper.discourse.group/t/random-erratic-extruder-movements-at-the-beginning-of-the-print/7120 "2023-03-09T00:45:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [March 9, 2023, 4:04am UTC](https://klipper.discourse.group/t/random-erratic-extruder-movements-at-the-beginning-of-the-print/7120/2 "2023-03-09T04:04:06Z")

</div>

Hello @PKav !

You may have a look here:

> [@Timer too close](https://klipper.discourse.group/t/timer-too-close/6634):
>
> Timer too close Background A “Timer too close” error occurs when the MCU is asked to schedule an action at a time that is already in the past. This typically results from delayed communication between the host and the MCU - for instance, if the host was busy or the message was blocked en route. warning Important: Klipper can identify what command was too late, but cannot determine why the delay occurred. The root cause is often external - such as USB congestion from a webcam or high system …

---

_[View the full topic](https://klipper.discourse.group/t/random-erratic-extruder-movements-at-the-beginning-of-the-print/7120)._