[Bug] Remote printing w/ Octoprint - filament change not working

[Isaac12x]

Further to issue #360 during remote printing when the printer reaches the M600 command in GCODE extruder pulls out the filament and waits for user input (a.k.a. continue when the new filament is loaded).

So, while doing that, when the new filament is loaded and I press continue, the printer comes back to the remote printing screen without loading the filament. Funny thing is it doesn't come back to print either.

Prusa mini FW version 4.0.5, Prusa slicer 2.2.0

[d-sko]

Same here, also with FW 4.0.5 and PrusaSlicer 2.2.0. Seemingly there is no way to resume the print after the filament is unloaded.

[Isaac12x]

I've dug a bit more in the issue trying to execute the G-code sequence manually. However, the receiver seems to be stuck in some sort of loop.

I guess it's expecting user input (press continue button when the new filament is loaded) but not registering the button press.

Message is: "Recv: echo:busy: paused for user"

[derpicknicker1]

Same problem here...

[davetyra]

This may be related, M601 M602 as inserted in the preview screen of PrusaSlicer 2.2.0 has similar behavior, printer pauses, but will not resume when button is pushed, this is printing from USB, not remote. FW 4.0.5 and PrusaSlicer 2.2.0

[Iqwertz]

I have the same Problem!

[JohnnyDeer]

Hi, in new FW version 4.1.0-RC1 is M600 repaired for printing via OctoPrint. Please try it out. I´m closing this issue as solved.

[dwineman]

Just tried it — the problem has not been fixed. Filament unloads, printer returns to the Octoprint screen. Never prompts to load new filament. "Change Filament" in the Tune menu does nothing. It is impossible to resume the print.

[ifekali]

Same here, not fixed yet.

[Crowlord]

Confirm not fixed. Multi coloured prints have to be done from USB stick.

[deltwalrus]

Confirmed here as well, not fixed.

[JohnnyDeer]

I can confirm too. Sorry to all, lesson for me... test everything by myself.

[JohnnyDeer]

Finally this issue should be fix in 4.1.0 final. Please try it and confirm that it is fixed :)

[olsw]

Can confirm this is definitely working now. Thanks!

[danielo515]

Finally this issue should be fix in 4.1.0 final. Please try it and confirm that it is fixed :)

4.1.0 of which software? Prusa-slicer? Octorpint? Something else?

[danielo515]

Whatever it was, it's working for me now, haha

[s-taylor]

So I’m on the latest firmware 4.3.3 and this did not work for me. I have since done a factory reset and now it works for me, hope this helps someone else.

[twobit0]

Still Not addressed on 4.3.4

[github-actions[bot]]

This issue has been flagged as stale because it has been open for 60 days with no activity. The issue will be closed in 7 days unless someone removes the "stale" label or adds a comment.

[danielo515]

Stale doesn't mean fixed

[danopernis]

Stale indeed doesn't mean fixed, but it does mean that the issue did not receive any updates in a long time.

@danielo515 can you test if the issue is still present in the newest version of the firmware? There have been several improvements and bugfixes since 4.0.5

[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.