Adaptive Bed Mesh crashes Klipper (Timer Too Close)

General Discussion
1

Basic Information:

Printer Model: Creality Ender 3 V3 SE
MCU / Printerboard: STM32f401 stock SE motherboard
Host / SBC : Generic amlogix s905x android TV STB using armbian 22 kernel 5.10
klippy.log

klippy(2).log (411.4 KB)

Describe your issue:

Hi, I just installed klipper a few days ago on my ender 3 v3 se and using an android TV set top box that I installed armbian onto. Things have been going great until I tried using klipper’s adaptive bed meshing where the printer would probe a few points then suddenly it would fail and shows this error :

MCU 'mcu' shutdown: Timer too close This often indicates the host computer is overloaded. Check for other processes consuming excessive CPU time, high swap usage, disk errors, overheating, unstable voltage, or similar system problems on the host computer. Once the underlying issue is corrected, use the "FIRMWARE_RESTART" command to reset the firmware, reload the config, and restart the host software. Printer is shutdown

I thought it could be a problem with the bed mesh process in general so I tried to calibrate it via the UI but nope, it finished without problems. I also tried KAMP plugin but the same problem occurred. Some forum posts have suggested that It’s host running out of resources but when I tried adaptive bed mesh calibrating nothing seems abnormal (normal cpu, ram, swap, disk usage)

Here’s a video showing klipper and host resource manager while running the adaptive bed mesh calibration : Watch Recording 2026-06-17 200252 | Streamable

2

It does not seem like a vanilla klipper with vanilla firmware, where version information is absent from the log.
So, it is hard to even guess something.

From my PoV, I guess, serial_bridge_send makes things happen too late.

-Timofey

3

ah yeah, forgot to include that. it is a non vanilla klipper, specifically this fork that adds support for the printer’s original display.

edit : here’s the software version

image
image519×468 6.71 KB

as for the logs, i’ve cut the earlier parts that i thought weren’t relevant, I will upload the full logs here
klippy (2).zip (1.7 MB)

update : seems like it was my cheapo USB cable that I used that caused this error. I tried replacing the cable with a longer one and it just worked, and replacing back to the original cable causes the same error.

4

version
version517×180 2.73 KB

The Moonraker version makes sense, but your Klipper version not at all (didn’t check the other versions). Right now it is 0.13.x. You are also tracking GitHub - jpcurti/ender3-v3-se-klipper-with-display: Modified klipper for ender3-v3 se with stock display support. https://jpcurti.github.io/ender3-v3-se-klipper-with-display/#/ · GitHub. A genuine Klipper tracks GitHub - Klipper3d/klipper: Klipper is a 3d-printer firmware · GitHub.

5

It’s 0.13.0 :wink: