Pause print G-code ignored during print on Prusa MINI?
 

Pause print G-code ignored during print on Prusa MINI?  

Page 1 / 2
  RSS
Marc Liyanage
(@marc-liyanage)
Active Member

I generated a gcode file in PrusaSlicer that has a pause in the middle so I can insert a nut. The instruction seems to be in the G-code, see below.

When I watched the printer at the point where it was supposed to pause, I saw my message flash on the display very briefly, but the printer did not stop and move the head out of the way at all, it immediately moved on to the next layer which covered the cavity for the nut.

Is there a known bug in the firmware?

 

G1 Z6.000 F9000.000
;AFTER_LAYER_CHANGE
;6
M117 place nuts in slots and resume
M601
G1 E-3.20000 F4200.00000
G1 Z6.200 F9000.000

Best Answer by Gordon W:

It's a known issue, and still present in the current release candidate for the next firmware release. See https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/283 . There is a workaround of using colour change  suggested as an alternative in that bug report.

Posted : 01/07/2020 6:19 am
JoanTabb
(@joantabb)
Moderator

Have a look at this video, about 11 mins 50...    

this works on Mk3, so probably works on Mini... 

Regards Joan

I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK...
Posted : 01/07/2020 11:46 am
towlerg
(@towlerg)
Honorable Member

FWIW in PS if you set the height you want to pause ans right click on the plus sign, you have the option to add pause print (M601). I have no idea what a Mini does when it encounters M601.

This post was modified 5 months ago by towlerg
Posted : 01/07/2020 12:45 pm
ahcben
(@ahcben)
New Member

Yep, I have the same problem right now.

I'm using PrusaSlicer v2.2.0 and Mini firmware v4.0.5.

 

@joantabb, sadly this workaround doesn't seem to work on the Mini.

I have added the following GCode from this video:

G1 X10.000 Y200.000 EO; parking position
M1; pause
M105; return to current t°

it does move the plate and pause the Mini, but I couldn't resume the print.

I've tried to Pause / Unpause via the LCD, but it was stuck with the "Pausing..." message.

Then Stop via the LCD was not working; I had to reboot the unit..

Regards,

Benjamin.

This post was modified 5 months ago by ahcben
Posted : 01/07/2020 2:11 pm
Felix De Montis
(@felix-de-montis)
New Member

I just tried using the pause code on my Mini and like @liyanage my Mini didn't stop. As with their gcode, mine also includes M117 for the message and M601 for the pause.

So it seams like the Mini doesn't support the M601 code.

Posted : 01/07/2020 2:22 pm
HeneryH
(@heneryh)
Trusted Member

I was having trouble with the info message (ie "insert red" or "insert black") that I was trying to insert into my filament change commands because the desired message would get displayed then a x ms later was overwritten with a new message.  I wonder if this pause after my message would give me enough time to notice and read the change message.

Posted : 01/07/2020 2:23 pm
HeneryH
(@heneryh)
Trusted Member

Hmmm, the user stop (m1) command would be interesting if it didn't clear the LCD.  That is the trouble with getting the filament change message to the LCD. You need to display it then prevent something else from overwriting it for a period of time.  If the M1 instructs the user to hit the button then that would have overwritten my message.

Maybe with the M1 it would at least end up in the console output where I can read it.

This post was modified 5 months ago by HeneryH
Posted : 01/07/2020 2:40 pm
Gordon W
(@gordon-w)
Reputable Member

It's a known issue, and still present in the current release candidate for the next firmware release. See https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/283 . There is a workaround of using colour change  suggested as an alternative in that bug report.

Posted : 01/07/2020 2:42 pm
Marc Liyanage
(@marc-liyanage)
Active Member
Posted by: @joantabb

Have a look at this video, about 11 mins 50...    

this works on Mk3, so probably works on Mini... 

Regards Joan

Thank you for the tip Joan, unfortunately from reading the GitHub issue posted below it seems that it does not work on the Mini:

M1 seems to do nothing but make it stuck in the printing UI, unable to pause or stop, or exit, without hitting reset.

 

Posted : 01/07/2020 3:10 pm
ahcben
(@ahcben)
New Member

@gordon-w

Thanks for the info 👍 

Posted : 01/07/2020 3:11 pm
Marc Liyanage
(@marc-liyanage)
Active Member
Posted by: @gordon-w

It's a known issue, and still present in the current release candidate for the next firmware release. See https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/283 . There is a workaround of using colour change  suggested as an alternative in that bug report.

Thanks a lot Gordon, I will follow along that GitHub issue. I also just tried the 4.10 RC firmware before reading that and can confirm that it still doesn't work.

Posted : 01/07/2020 3:11 pm
JoanTabb
(@joantabb)
Moderator

Sorry guys, I don't have a Mini to try. 

did you guys try the code or just veto it in favour of the git hub issue?

I tried several options on the Mk3, before I found one that worked. 

Regards Joan

I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK...
Posted : 01/07/2020 4:03 pm
ahcben
(@ahcben)
New Member

@joantabb

cf https://forum.prusaprinters.org/forum/general-discussion-announcements-and-releases/pause-print-g-code-ignored-during-print-on-prusa-mini/#post-226070

the following GCode from this video ... does move the plate and pause the Mini, but I couldn't resume the print.

Posted : 01/07/2020 4:08 pm
JoanTabb
(@joantabb)
Moderator

Oh dear, 

lets hope they sort the issue soon

 

regards Joan

I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK...
Posted : 01/07/2020 4:12 pm
Marc Liyanage
(@marc-liyanage)
Active Member
Posted by: @gordon-w

It's a known issue, and still present in the current release candidate for the next firmware release. See https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/283 . There is a workaround of using colour change  suggested as an alternative in that bug report.

I tried the color change option instead as a workaround and that is indeed a temporary solution. It's a bit of a hassle because I have to reinsert the same filament and clean up the nozzle, but I was able to insert the nuts and continue the print.

 

Posted : 02/07/2020 3:37 am
Gordon W
(@gordon-w)
Reputable Member

According to a comment by a Prusa employee on Github ( https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/362#issuecomment-655328782 ) the problem has been fixed in the 4.1.0 release. Unfortunately I don't have my mini yet, so can't confirm one way or the other!

Posted : 08/07/2020 12:15 pm
Felix De Montis
(@felix-de-montis)
New Member

Altough there is a comment saying that it works now, I just tried printing this gcode which has the M601 code, and it still didn't work. So the issue is still available.

G1 Z0.800 F9000.000
;AFTER_LAYER_CHANGE
;0.8
M117 place fabric and resume printing
M601
G1 E-3.20000 F2400.00000
Posted : 08/07/2020 1:30 pm
Gordon W
(@gordon-w)
Reputable Member

@dervondenbergen

If you are running the final version of 4.1.0 and the problem is still there, could you add a comment to the github issue so that the developers are aware?

Thanks in advance.

Posted : 08/07/2020 1:33 pm
Felix De Montis
(@felix-de-montis)
New Member

@gordon-w

Yes, just downloaded and installed it from https://www.prusa3d.com/drivers/

I think the GitHub Issue you linked is not the one about M601. That one is still open: https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/283

This post was modified 5 months ago by Felix De Montis
Posted : 08/07/2020 1:37 pm
Marc Liyanage
(@marc-liyanage)
Active Member

@gordon-w I agree with @dervondenbergen that the GitHub issue you referenced is for a different issue.

However it's good to know that that one (which I wasn't aware of) is fixed now, because the filament change instruction could be used as a workaround for the pause G-code not being handled properly yet.

Posted : 08/07/2020 5:19 pm
Page 1 / 2
Share:

Please Login or Register