New build, Pause not triggering from gcode
Hi all, wasn't sure where to put this, as I've only seen a few reddit posts regarding this behavior, and they were all older, with no clear solutions.
I'll provide all the context I can, I figure most of it will be irrelevant, but you never know.
New kit built Mk4S with MMU3, flashed to the new firmware on both. Slicing being done with Prusa 2.9.4, files transferred via USB.
Prints are looking good, and I've got full connectivity on both android and via slicer over my network.
I've been re-building some purchased .3mf (because it seems like whatever the originator built them in didn't play nice, I guess Bambu is a closed ecosystem for a reason)
When I try to insert a pause marker, it shows in the interface, as well as I can find the M601 line in the gcode summery (using the slider down the bottom). However, it doesn't trigger at all during the printing.
Is there a system setting on the printer I may have missed? The firmware flash turned it back on the high flow mode, so it's possible there is a default I'm not seeing.
My other machine is an ender3 3v 3se, running from an older version of creality slicer, so I'm a bit used to attribute chasing, and I like that Prusa makes that easy, but I'm also not super clear on what defaults live in the printer itself and override the gcode.
Thanks folks.
If the M601 command has an S parameter it doesn't pause.
Cheerio,
RE: New build, Pause not triggering from gcode
Thanks for the input, not quite sure what to do with that, but this is what I'm seeing in the steps around that zone. If I wanted to manually change something in this BGCODE file, what direction should I head?
171781 ;AFTER_LAYER_CHANGE
171782 ;4.2
171783 ;M74 W51.0714
171784 ;PAUSE_PRINT
171785 M117 Place magnets in slots and resume printing
171786 M601
171787 M486 S-1
Historically there was a problem with Octoprint filtering out pause commands - I presume you are not using Octoprint?
And for a while there was a mismatch on some printers 'though not, I think, the Mk4, when running outdated firmware.
https://help.prusa3d.com/article/prusa-firmware-specific-g-code-commands_112173
Chheerio ,
RE: New build, Pause not triggering from gcode
Nope, not running Octo, and since a lot of folks seem to have run the new firmware, I'd have thought it would be a problem that others would have run into in the last few months.
Since it seems like the code is generating in the slicer, is there a chance it's a firmware problem, even if others are not encountering the same occurrence? I don't want to go play firmware whack-a-mole between the printer and MMU if I can help it. And it seemed like I had a clean upgrade. Once the current print is done, I'll make up a test print to see if I can get some differing behavior.
RE: New build, Pause not triggering from gcode
Okay, update, I manually triggered a pause on the current print to insert parts, one layer early. Then it triggered the Gcode pause on the layer it was supposed to. Same file as before that failed to pause. I'll keep trying some things and see if I can find a consistent pattern, so if others run into this, there might be somewhere to start from.
RE: New build, Pause not triggering from gcode
Okay, so now it's working. If I do find a way to get it to fail pauses again, I'll post it here. It's possible that I was somehow able to trigger an export of the preview before it got re-sliced.