prusaslicer gcode freezes printer
Hey guys. I recently switched from superslicer to prusaslicer, but now all my newly sliced gcodes somehow make the printer freeze for 3 minutes after starting a job.
The gcode flavor is set to Klipper. My ratos and Klipper are updated. I run a raspi 3b+ and an octopus 1.1.
Any idea what’s happening here? If i run an old gcode, the print starts immediately.
21 Replies
continuing-cyan•2y ago
I attached a "good" and a "bad" gcode. The only difference that I can see is that SS puts the preview icon at the end of the file while PS puts it at the beginning....
continuing-cyan•2y ago
@_sebastianm do you have object processing enabled?
continuing-cyan•2y ago
Have to look. Never heard of that feature
it's a moonraker setting to enable object cancelling
continuing-cyan•2y ago
Never changed anything in moonraker. So I am sure I have default values
actually I think I found the answer myself.
in PS, the gcode starts with M190, and while the bed is heating the printer seems frozen (no idea why the console doesnt show it, but the bed is heating in those 2-3 minutes).
In SS, the temperature is set via the startcode, and not explicitly with M190 at the beginning of the file
continuing-cyan•2y ago
this option looks a bit like it, right?
ratty-blush•2y ago
Did you setup the start gcode following the RatOS directions? It tells you to modify the start gcode to prevent this.
ratty-blush•2y ago
Slicer Configuration | RatOS
RatOS comes with STARTPRINT and ENDPRINT macros that you can call directly from your slicers. This way the printer knows how to start a print, and you can there easily switch between slicers without worrying if you changed anything in another slicer.
continuing-cyan•2y ago
yes, I copied that specific startcode into my slicer (otherwise my adaptive mesh wouldnt work)... but I dont think that the checkbox "start gcode options" is mentioned anywhere.
I used this startcode:
https://os.ratrig.com/docs/configuration/adaptive-meshing
ratty-blush•2y ago
I asked because I can still see an M190 S68 and an M109 S215 in the "bad" one which should not be there. I haven't looked at he adaptive mesh stuff yet.
continuing-cyan•2y ago
but yes, this is exactly what I mentioned above.. apparently PS outputted the temp gcodes twice
ratty-blush•2y ago
Double check the custom gcode in both the printer and filament sections. I'm betting you have something in there you don't want.
continuing-cyan•2y ago
Yeah, it’s the option I posted 15min ago. Issue is fixed since I unchecked it.
Superslicer didn’t have that, so I didn’t really notice it.
ratty-blush•2y ago
That must be new to the 2.6 beta you are using. It's not in 2.5 that I am using.
aah this is a new 2.6.0 beta thing
Good that they added this
continuing-cyan•2y ago
What’s the benefit?
Previously prusaslicer would look for heater gcode in your start gcode, if they were there it wouldn't emit it automatically. But that meant you'd always have to have heater gcodes in your custom gcode, which sucks when you're using klipper macros. Now you can use klipper macros without having to call heater commands before/after the macro.
continuing-cyan•2y ago
Thx for the explanation. But I just uncheck that box, right?
I assume so, i don't know which state stops it from emitting heater commands, but that's the state you want
continuing-cyan•2y ago
👍