Create devcontainer.json

[WontonSam]

[Racemade]

+1 Would be a good idea!! Having this problem a while. Thanks!

[sammy123k]

I've just discovered this behavior on my first print with inserted magnets in my Prusa XL, and it was quite surprising to me. I had oozing on the bed while it was paused, and the X carriage itself was positioned in a way where I didn't have full access to the print either!

It seems like a no brainer that on reaching a M601 pause in the GCODE, the printer should park the current tool as part of the pause, and pick the tool again up on resume. There are manual workarounds for this, but it feels like what is being asked of here is a much safer default behavior than the current behavior.

[rubillos]

Try setting your pause print gcode to this: (the G4 P100 commands are important, won't work properly without them)

G1 F{min(350.0, travel_speed)*60} ; set fast travel speed
P0 S1 ; park current tool
G4 P100
M601 ; perform printer pause
G4 P100
T{current_extruder} S1 L0 D0 ; pick current tool
G4 P100

[hickengr]

I also have the same problem with filament oozing and causing problems after resuming the print. rubillos' workaround is ok, but the XL has the ability to easily park the tool on the dock. Please implement this feature.

[pipcorona]

Try setting your pause print gcode to this: (the G4 P100 commands are important, won't work properly without them)

G1 F{min(350.0, travel_speed)*60} ; set fast travel speed
P0 S1 ; park current tool
G4 P100
M601 ; perform printer pause
G4 P100
T{current_extruder} S1 L0 D0 ; pick current tool
G4 P100

Super delayed reply to say thank you and this works great. Although I just had a print where it didn't park, so I need to investigate. It definitely had the custom G-Code so I'm not sure why it reverted to the old pause style. I do still think it would be nice to have this be the default behavior on a pause.

[Cloud-Tickler]

Try setting your pause print gcode to this: (the G4 P100 commands are important, won't work properly without them)

G1 F{min(350.0, travel_speed)*60} ; set fast travel speed
P0 S1 ; park current tool
G4 P100
M601 ; perform printer pause
G4 P100
T{current_extruder} S1 L0 D0 ; pick current tool
G4 P100

Thank you for the code example rubillos. Which slicer version have you been using? I tried this, and it doesn't work for me. The placeholder 'current_extruder' is not getting replaced when slicing. So the printer parks the tool, but then continues without picking the tool again. It also doesn't work when I try to send the command in Octoprint via terminal

Send: T[current_extruder] S1 L0 D0 Recv: echo:Unknown command: "T[current_extruder] S1 L0 D0" Recv: ok

Has there been a change on that command?

[CZDanol]

Afaik no

[Paliur]

Try setting your pause print gcode to this: (the G4 P100 commands are important, won't work properly without them)

G1 F{min(350.0, travel_speed)*60} ; set fast travel speed
P0 S1 ; park current tool
G4 P100
M601 ; perform printer pause
G4 P100
T{current_extruder} S1 L0 D0 ; pick current tool
G4 P100

Thank you for the code example rubillos. Which slicer version have you been using? I tried this, and it doesn't work for me. The placeholder 'current_extruder' is not getting replaced when slicing. So the printer parks the tool, but then continues without picking the tool again. It also doesn't work when I try to send the command in Octoprint via terminal

Send: T[current_extruder] S1 L0 D0 Recv: echo:Unknown command: "T[current_extruder] S1 L0 D0" Recv: ok

Has there been a change on that command?

In Prusa Slicer, this works without a hitch. However, you mustn't add custom code to a certain layer. You need to modify the pause parameter directly in “Printers -> Custom G-Code - > Print pause G-Code”.

Then, when you slice your model, you need to add a standard pause to the layer you're interested in. The code will then be interpreted correctly.

Sorry for my English ! Hope you understand what I mean !

[github-actions[bot]]

Thank you for your contribution to our project. This issue has not received any updates for 60 days and may be considered "stale." If this issue is still important to you, please add an update within the next 7 days to keep it open. Administrators can manually reopen the issue if necessary.

[github-actions[bot]]

This issue has been closed due to lack of recent activity. Please consider opening a new one if needed.