MCU 'mcu' shutdown: Timer too close error ONLY when using OrcaSlicer

General Discussion
1

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 (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.

2

Hello @5jvm0u4 !

OrcaSlicer can produce some weird stuff in connection with the M106 command. Like this from the Bad file:

; 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

3

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!

1 Like
4

I’m not sure what the root cause is, but your host system is under heavy load.

systime
systime800×600 51.6 KB

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

-Kevin

5

After some test, I can confirm this is NOT the cause of this problem, I’m stuck again…

6

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 (1.3 MB)

7

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.

1 Like
8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.