supermerill / SuperSlicer

G-code generator for 3D printers (Prusa, Voron, Creality, etc.)
4.04k stars 515 forks source link

with superslicer sliced gcode crashes klipper - klippy shutdown #4206

Open DaStivi opened 3 months ago

DaStivi commented 3 months ago

What happened?

for some, yet unknown reason to me, every print i sliced with superslicer crashes my voron 350 with klipper... not sure if i changed some version, as you can see in the screenshot it worked with some 2.5.59.8 version... what i also did was updating my Klipper, but also not totaly sure if this was in-between this time...

Orcaslicer gcode worked in-between too... image

my last print that went without klippy shutdown (01.04.2024 10:52) is almost the same as the print before that had the error too! the only thing i did with this gcode, is to remove the superslicers config setting on the bottom of the gcode file and i added some M117 Debug notes... but didn't changed anything else! so basically removing the config section helped! image

one thing i just noticed right now, after pasting the pictures... there is ahnother M117 Time Left 0s after the PRINT_END... maybe this is causing the issue, i will test this after the ongooing print!

Project file & How to reproduce

nothing fancy, just sliced normal STLs tested with different models also resettet the Print(er) settings Flamecraft_Coins.zip

Version

2.5.59.8 (Discrete legend Edition Pre-release) & 2.5.59.9 (some nightly build that compiled without errors)

Operating system

tested with Windows 11 and Fedora 40

Printer model

Voron 2.4 350 with Afterburner

jbeima commented 3 months ago

By chance have you tried turning "object_labels" off?

anonymousaga commented 1 month ago

Please send your klippy.log

As far as I can guess without the log, the command that is failing is G1 F16800;_WIPE at line 122822

supermerill commented 1 month ago

Please send your klippy.log

As far as I can guess without the log, the command that is failing is G1 F16800;_WIPE at line 122822

why do you think it's failing because of that? what's wrong with this line?

anonymousaga commented 1 month ago

Please send your klippy.log As far as I can guess without the log, the command that is failing is G1 F16800;_WIPE at line 122822

why do you think it's failing because of that? what's wrong with this line?

again, its just a guess without the log, but I assumed that G1 commands cannot run without an X Y Z or E parameter.

@DaStivi please send your klippy.log