Basic Information:
[v] Printer Model: Voron2.4
[v] MCU / Printerboard: Mellow Super 8
[v] Host / SBC: intel 12100/5600g
[v
klippy (6).log (656.3 KB)
] klippy.log
Describe your issue:
After replacing the super8 MCU, I used X86 as the host, but it always prompts “timer too close” during homing. This issue also occurs when I try to run on 5600g or 12100 CPUs under Ubuntu 22 and Debian 11/12.
Hello @channinghe !
As a first step you may have look on this:
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.
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 …
system
Closed
January 17, 2025, 1:13pm
3
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.