Unfortunately, I did not find any logs (did I miss them?) so I cannot contribute much.
In any case:
I do not know if you modified it, or if it is Sovol default:
[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) error message, which would have allowed to diagnose such a lot easier.
post after reply to your question asking for logs contain the whole config dir (config.zip)
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
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…
Did not find a klippy.log in there. Configs are not needed most of the time. Always provide a full and unmodified klippy.log
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.
ah, stupid, uploaded config instead of log … log is only in the first post… and here is the whole logs dir
(larger than 8M, 13.8 so cannot upload to forum here)
bugs happen, now when I know what it is it is kinda easy but…
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…
… log is only in the first post… and here is the whole logs dir