# Host & EBB | MCU Shutdown timer too close **URL:** \ **Category:** General Discussion\ **Created:** [January 16, 2025, 5:40pm UTC](https://klipper.discourse.group/t/host-ebb-mcu-shutdown-timer-too-close/21428 "2025-01-16T17:40:07Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![synerone](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/synerone/32/17171_2.png) [@synerone](https://klipper.discourse.group/u/synerone)\ **Post date:** [January 16, 2025, 5:40pm UTC](https://klipper.discourse.group/t/host-ebb-mcu-shutdown-timer-too-close/21428/1 "2025-01-16T17:40:07Z")
### Basic Information: Printer Model: SV08 MCU / Printerboard: stock SV08 board + EBB36 over U2C Host / SBC klippy.log Hello, since end of December, I’m getting a Timer too close error in almost all my prints. Even if I print the same file, it fails randomly, usually after 1+ hour of printing. In Every fail I get the timer too close message but 8/10 times is the host MCU, the rest of times is the EBBCan MCU. The first time that this issue happened I had Timelapse ON, and it was an 8 hour print that failed at the 10% mark, then again at the 21% mark, i did some changes and it failed for a third time at around 80% mark. Since then I’m trying to isolate the issue but I’m out of ideas. What I did: - Increased cooling: Added a fan to the toolhead board and the EBB MCU usually runs below 70 degrees | Added thermal glue, new heatsinks and more cooling to the mainboard, now runs almost 20 degrees cooler (usually was around 70-75 degrees, now runs @ 50-55). Just in case the heat were creating throttling. - Rewired and stiffened the can cable and connectors. Is a 20 awg shielded cable, I stiffened as much I could both ends to avoid play. - reflashed the ebb36 - uninstalled plugins to avoid bloat: Telegram bot, Obico, Octoeverywhere. - Re routed all the wires and verified connections & voltages. - Updated all librararies, plugins, packages, etc. I’m currently doing some no filament prints to check if its a slicer config or a klipper config. - Printing with timelapse ON | OFF - Printing with the camera disconnected - Printing after changing configs in the slicer All of the above using the same test model and they all fall at different points but everytime after 1-2 hours. I tried different things suggested here and in Reddit but nothing works. Maybe I’m missing something, but after checking the logs i wasn’t able to find something. When the error happens with the EBB MCU i found a spike in load and the clock was misaligned. But when the error appears in the Host MCU (which is most of the time) I see no spikes or anything strange (in my opinion) someone suggested me to try klippain vibrations profile macro to accelerate the troubleshooting progress due being a stress test and that i can trigger the error faster and he was right, whenever i use the macro, after some time the errors appear. This is all the info that I have, I appreciate if you can help me troubleshoot/fix the problem. Attaching screenshots and logs ![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/3X/e/c/ec8f75e64ac49a079fdc7dcc650fdfc537e87a1b.png) [Klippylogs.zip](https://klipper.discourse.group/uploads/short-url/AwvIVtT9MZWepXv5VgWiOLb6Skl.zip) (2.4 MB) [printer.cfg](https://klipper.discourse.group/uploads/short-url/sGIWsBEtqDjkfgNrqwZkVTZfrsP.cfg) (5.3 KB) ---
**Author:** ![Percival42](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/percival42/32/18091_2.png) [@Percival42](https://klipper.discourse.group/u/Percival42)\ **Post date:** [March 16, 2025, 3:57am UTC](https://klipper.discourse.group/t/host-ebb-mcu-shutdown-timer-too-close/21428/2 "2025-03-16T03:57:36Z")
Please say you got it fixed. Exact same issue here ---
**Author:** ![synerone](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/synerone/32/17171_2.png) [@synerone](https://klipper.discourse.group/u/synerone)\ **Post date:** [March 16, 2025, 5:21am UTC](https://klipper.discourse.group/t/host-ebb-mcu-shutdown-timer-too-close/21428/4 "2025-03-16T05:21:23Z")
Yes it got fixed. The problem was the Klippain Shake&Tune. Not a single TTC after uninstalling it completely ---
**Author:** ![Percival42](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/percival42/32/18091_2.png) [@Percival42](https://klipper.discourse.group/u/Percival42)\ **Post date:** [March 16, 2025, 12:50pm UTC](https://klipper.discourse.group/t/host-ebb-mcu-shutdown-timer-too-close/21428/5 "2025-03-16T12:50:18Z")
Thanks for letting me know, will have to fix that today ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\ **Post date:** [May 15, 2025, 12:50pm UTC](https://klipper.discourse.group/t/host-ebb-mcu-shutdown-timer-too-close/21428/6 "2025-05-15T12:50:52Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.