# MCU 'mcu' shutdown: Timer too close error ONLY when using OrcaSlicer **URL:** \ **Category:** General Discussion\ **Created:** [October 22, 2024, 1:56pm UTC](https://klipper.discourse.group/t/mcu-mcu-shutdown-timer-too-close-error-only-when-using-orcaslicer/19568 "2024-10-22T13:56:36Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![5jvm0u4](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/5jvm0u4/32/15118_2.png) [@5jvm0u4](https://klipper.discourse.group/u/5jvm0u4)\ **Post date:** [October 22, 2024, 1:56pm UTC](https://klipper.discourse.group/t/mcu-mcu-shutdown-timer-too-close-error-only-when-using-orcaslicer/19568/1 "2024-10-22T13:56:36Z")
### Basic Information: Printer Model: Voron 2.4 MCU / Printerboard: Spider V2.3 Host / SBC: RPI 4B 2GB, EBB36 V1.2 (both via USB) [bug.zip](https://klipper.discourse.group/uploads/short-url/45mNLMuA9WjOjAJClFlnKywnLtn.zip) (2.1 MB) ### Describe your issue: I’m consistently getting this error every single print since yesterday, over 600hr of print time and suddenly every print fails at layer between 5~10. I’ve tried reinstall everything, wipe out whole SD card and start over, but nothing changed untill I try switching to PrusaSlicer and suddently everything works and no error whatsoever. I then try different presets in OrcaSlicer, even different printer presets but that error still pops out at layer 8. I havn’t change anything in OrcaSlicer before this incident beside some built in calibration tests, so I’m not so sure if this is a slicer problem or a klipper problem. I’ve include both (good) and (bad) gcode that are from Prusa and Orca respectively, and the log file. ---
**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:** [October 22, 2024, 2:53pm UTC](https://klipper.discourse.group/t/mcu-mcu-shutdown-timer-too-close-error-only-when-using-orcaslicer/19568/2 "2024-10-22T14:53:57Z")
Hello @5jvm0u4 ! OrcaSlicer can produce some weird stuff in connection with the `M106` command. Like this from the Bad file: ```auto ; stop printing object Voron_Design_Cube_v7 id:0 copy 0 M106 S76 M106 S76 M106 S76 M106 S76 M106 S76 M106 S76 M106 S76 M106 S76 ;LAYER_CHANGE ``` You may update Klipper. [https://www.klipper3d.org/Config\_Changes.html](https://www.klipper3d.org/Config_Changes.html) ---
**Author:** ![5jvm0u4](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/5jvm0u4/32/15118_2.png) [@5jvm0u4](https://klipper.discourse.group/u/5jvm0u4)\ **Post date:** [October 22, 2024, 3:39pm UTC](https://klipper.discourse.group/t/mcu-mcu-shutdown-timer-too-close-error-only-when-using-orcaslicer/19568/3 "2024-10-22T15:39:24Z")
My klipper version is Version: v0.12.0-321-g8e1cdb199 I believe it’s the lastest version since I just re-install everything today and flashed everything up-to-date. I’ll try deleting those duplicated M106 and run the modified gcode to see if it helps, I’ll also submit a issue in OrcaSlicer’s GitHub page. Hope this is the solution, it’s dirving me crazy… Great appreciation! ---
**Author:** ![koconnor](https://avatars.discourse-cdn.com/v4/letter/k/aca169/32.png) [@koconnor](https://klipper.discourse.group/u/koconnor)\ **Post date:** [October 22, 2024, 8:30pm UTC](https://klipper.discourse.group/t/mcu-mcu-shutdown-timer-too-close-error-only-when-using-orcaslicer/19568/4 "2024-10-22T20:30:40Z")
I’m not sure what the root cause is, but your host system is under heavy load. ![systime](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/3/3456c2864db0b7d8062756cb35374f4360f29378.png) It could be a large number of redundant commands from the slicer. Or it could be traditional host issues (like failing sdcard, overheating, background processes, etc.): [Timer too close](https://klipper.discourse.group/t/timer-too-close/6634/1) -Kevin ---
**Author:** ![5jvm0u4](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/5jvm0u4/32/15118_2.png) [@5jvm0u4](https://klipper.discourse.group/u/5jvm0u4)\ **Post date:** [October 23, 2024, 8:13am UTC](https://klipper.discourse.group/t/mcu-mcu-shutdown-timer-too-close-error-only-when-using-orcaslicer/19568/5 "2024-10-23T08:13:53Z")
After some test, I can confirm this is NOT the cause of this problem, I’m stuck again… ---
**Author:** ![5jvm0u4](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/5jvm0u4/32/15118_2.png) [@5jvm0u4](https://klipper.discourse.group/u/5jvm0u4)\ **Post date:** [October 23, 2024, 8:50am UTC](https://klipper.discourse.group/t/mcu-mcu-shutdown-timer-too-close-error-only-when-using-orcaslicer/19568/6 "2024-10-23T08:50:31Z")
I tune down slicing resolution from 0.005 to 0.05, and now instead timer too close, it emit “Heater extruder not heating at expected rate”, but when I look into log file, it shows that it’s the same problem: Receive: 99 89994.387698 89994.387310 12: seq: 1c, shutdown clock=3419833690 static\_string\_id=Timer too close … Heater extruder not heating at expected rate Transition to shutdown state: Heater extruder not heating at expected rate [bug2.zip](https://klipper.discourse.group/uploads/short-url/eSsV0EjFdgxG5JougxphSUrdqvT.zip) (1.3 MB) ---
**Author:** ![5jvm0u4](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/5jvm0u4/32/15118_2.png) [@5jvm0u4](https://klipper.discourse.group/u/5jvm0u4)\ **Post date:** [November 12, 2024, 2:24pm UTC](https://klipper.discourse.group/t/mcu-mcu-shutdown-timer-too-close-error-only-when-using-orcaslicer/19568/7 "2024-11-12T14:24:36Z")
It’s G2/G3 that’s causing this problem, OrcaSlicer will still generate, specifically, G3 even when arc fitting is disable, while in PrusaSlicer, it’s actually off when set to off. That’s why I couldn’t find out why. I simply change[gcode\_arcs]resolution from 0.001 to 0.01 and solve everything. ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\ **Post date:** [December 13, 2024, 12:24am UTC](https://klipper.discourse.group/t/mcu-mcu-shutdown-timer-too-close-error-only-when-using-orcaslicer/19568/8 "2024-12-13T00:24:56Z")
Closed on December 13, 2024, 12:24am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.