# SV07plus, KlipperScreen & MCU 'mcu' shutdown: Rescheduled timer in the past **URL:** \ **Category:** General Discussion\ **Created:** [December 29, 2023, 1:59am UTC](https://klipper.discourse.group/t/sv07plus-klipperscreen-mcu-mcu-shutdown-rescheduled-timer-in-the-past/12661 "2023-12-29T01:59:33Z")\ **Posts on this page:** 5\ **Page:** 2
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [January 1, 2024, 8:30am UTC](https://klipper.discourse.group/t/sv07plus-klipperscreen-mcu-mcu-shutdown-rescheduled-timer-in-the-past/12661/21 "2024-01-01T08:30:47Z")
Unfortunately, I did not find any logs (did I miss them?) so I cannot contribute much. In any case: > [@arhi](#): > > now why the heck is my slicer wanting to extrude 60mm of plastic during 1mm of movement is weird. That looks like bug in orca slicer ☹ … I see that crash happens with E20 already I do not know if you modified it, or if it is Sovol default: ```auto [extruder] ... max_extrude_cross_section = 500 ``` This setting effectively disables sanity checks that would have exactly reacted upon aberrant extrusion amounts and would have produced a [Move exceeds maximum extrusion (AA mm^2 vs BB mm^2)](https://klipper.discourse.group/t/move-exceeds-maximum-extrusion-aa-mm-2-vs-bb-mm-2/6636) error message, which would have allowed to diagnose such a lot easier. In any case, you seem to be on the right way 👍 ---
**Author:** ![arhi](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/arhi/32/9011_2.png) [@arhi](https://klipper.discourse.group/u/arhi)\ **Post date:** [January 1, 2024, 4:43pm UTC](https://klipper.discourse.group/t/sv07plus-klipperscreen-mcu-mcu-shutdown-rescheduled-timer-in-the-past/12661/22 "2024-01-01T16:43:07Z")
> [@Sineos](#): > > Unfortunately, I did not find any logs (did I miss them?) so I cannot contribute much. first post has klippy.log.zip post after reply to your question asking for logs contain the whole config dir (config.zip) > [@Sineos](#): > > I do not know if you modified it, or if it is Sovol default: I have changed it now to 40, original 500 was there by default… that’s wow PRC manufacturers understand safety in config ☹ The issue I have now is that I hate how this works, if this move is ordered by slicer (def bug in slicer imho) I do not want printer to pee itself and sit in a corner … currently I see that ```auto max_extrude_cross_section = 500 ``` is actually better config than what I changed it to as with 500 this move will produce MCU shutdown and that will turn heaters off while 40 will produce error (move exceeds…) and both heaters will remain on but print will stop so in 99% cases I have nozzle touching bunch of plastic heating it through tip for hours… not a good scenario, mcu shutdown is better scenario, it will turn off heaters… proper scenario would be to either skip this move or slow it down … and display warning or something similar but if it is stopping print - turn the darn heaters off ☹ In any case I think max velocity for the extruder should exist and not only max velocity for “e only” moves… but I’m new so who knows what I’m missing here… for start this G-code was never supposed to exit slicer but… ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [January 1, 2024, 5:32pm UTC](https://klipper.discourse.group/t/sv07plus-klipperscreen-mcu-mcu-shutdown-rescheduled-timer-in-the-past/12661/23 "2024-01-01T17:32:07Z")
> [@arhi](#): > > post after reply to your question asking for logs contain the whole config dir (config.zip) Did not find a klippy.log in there. Configs are not needed most of the time. Always provide a full and unmodified klippy.log > [@arhi](#): > > is actually better config than what I changed it to as with 500 this move will produce MCU shutdown and that will turn heaters off while 40 will produce error (move exceeds…) Well, you can use a different slicer if it should be a slicer bug. In any case, turning off sanity checks is not a wise idea and a proper setting there would have made the diagnosis much easier. > [@arhi](#): > > not a good scenario, mcu shutdown is better scenario, it will turn off heaters See [on\_error\_gcode](https://www.klipper3d.org/Config_Reference.html#virtual_sdcard) ---
**Author:** ![arhi](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/arhi/32/9011_2.png) [@arhi](https://klipper.discourse.group/u/arhi)\ **Post date:** [January 1, 2024, 7:17pm UTC](https://klipper.discourse.group/t/sv07plus-klipperscreen-mcu-mcu-shutdown-rescheduled-timer-in-the-past/12661/24 "2024-01-01T19:17:39Z")
ah, stupid, uploaded config instead of log 😃 … log is only in the first post… and here is the whole logs dir > **[13.2 MB file on MEGA](https://mega.nz/file/NiQUFYaZ#VoHTjAX0mRxXntwALxjsf6PmlK_GFvYb6B2vdUaaKPE)** (larger than 8M, 13.8 so cannot upload to forum here) > [@Sineos](#): > > Well, you can use a different slicer if it should be a slicer bug. bugs happen, now when I know what it is it is kinda easy but… > [@Sineos](#): > > In any case, turning off sanity checks is not a wise idea and a proper setting there would have made the diagnosis much easier. I never turn off sanity checks but many PRC made pritners I seen do that, set the thermal runaway to crazy values, this is just one in a see of examples… one would assume defaults these printers come with are safe but… > [@Sineos](#): > > See on\_error\_gcode great thanks ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\ **Post date:** [March 1, 2024, 7:18pm UTC](https://klipper.discourse.group/t/sv07plus-klipperscreen-mcu-mcu-shutdown-rescheduled-timer-in-the-past/12661/25 "2024-03-01T19:18:25Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed. [Previous page](https://klipper.discourse.group/t/sv07plus-klipperscreen-mcu-mcu-shutdown-rescheduled-timer-in-the-past/12661.md?page=1)