Octoprint: New Problems with Pause / Resume GCODE Commands (Prusa i3)

[CoolNamesAllTaken]

I updated to the most recent version of Octoprint recently, and things have been working just fine, until I tried to pause a print today.

OctoPrint version : 1.3.6
OctoPi version    : 0.14.0

Printer / Octoprint Info

My printer is a Prusa i3 MK2S running the latest firmware, FW 3.1.0. The new Prusa firmware was installed in November and worked happily with the previous Octoprint version I had (1.3.5, I think), including numerous pause / resume cycles, but with the update to 1.3.6 the pause and resume commands seem to be having some issues.

The browser I am using is Google Chrome. This issue has been repeated from Mac OS and Windows 10.

GCODE Info

Here's what I have in my GCODE scripts:
After print job is paused:

M601 ; pause print

Before print job is resumed:

M602 ; Resume print
G4 P5000 ; Dwell

Bug Description

The issue occurs when I hit "pause" or "resume" during a print job. Expected events (what used to happen with the previous OctoPrint firmware) and actual events (what occurs with Octoprint 1.3.6) are detailed below.

Expected events on "pause":

Print head stops movements, turns off extruder heater, moves to heating position (in the air above home position) and awaits further instructions. Bed heater remains on.
"Resume" button appears on online Octoprint interface.

Actual events on "pause":

Print head freezes in current position on build plate, turns off extruder heater. Bed heater remains on.
"Resume" button appears on online Octoprint interface, but appears to have already been clicked.

Expected events on "resume":

Print head turns on extruder heater, remains in heating position. Print head reaches print temperature, moves to pause position and resumes printing.

Actual events on "resume":

Print head remains in incorrect paused position (not in heating position). Octoprint displays target extruder temperature as the correct printing temperature (240˚), but the actual temperature of the print head does not increase. The printer displays the message "Heating..." on its LCD, but the target extruder temperature on the printer says 0˚. Printer stays in this configuration for 10+
minutes (note: bed heater is still on).

Log file

octoprint.log
The log is rather messy and includes a full system reboot (raspi and printer), with the printer being rebooted multiple times (shows up as a printer reset detected).

Please let me know if I need to add anything else! I appreciate the help.

[GitIssueBot]

Hi @CoolNamesAllTaken,

It looks like there is some information missing from your bug report that will be needed in order to solve the problem. Read the Contribution Guidelines which will provide you with a template to fill out here so that your bug report is ready to be investigated (I promise I'll go away then too!).

If you did not intend to report a bug but wanted to request a feature or brain storm about some kind of development, please take special note of the title format to use as described in the Contribution Guidelines.

Please do not abuse the bug tracker as a support forum - if you have a question or otherwise need some kind of help or support refer to the Mailinglist or the G+ Community instead of here.

Also make sure you are at the right place - this is the bug tracker of the official version of OctoPrint, not the Raspberry Pi image OctoPi nor any unbundled third party OctoPrint plugins or unofficial versions. Make sure too that you have read through the Frequently Asked Questions and searched the existing tickets for your problem - try multiple search terms please.

I'm marking this one now as needing some more information. Please understand that if you do not provide that information within the next two weeks (until 2018-01-04 03:10 UTC) I'll close this ticket so it doesn't clutter the bug tracker. This is nothing personal, so please just be considerate and help the maintainers solve this problem quickly by following the guidelines linked above. Remember, the less time the devs have to spend running after information on tickets, the more time they have to actually solve problems and add awesome new features. Thank you!

Best regards,
~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being, so don't expect any replies from me :) Your ticket is read by humans too, I'm just not one of them.

[cnlson]

I was just coming here to report the same exact thing. so 2nd prusa mk3 with the same issue with 1.3.6

[cnlson]

@CoolNamesAllTaken no idea why but you are still sitting at incomplete ticket so your issue is not being reviewed

[CoolNamesAllTaken]

Hmmm...is there anything I’m missing that’s obvious?

It’s good to know that someone else has the same issue!

Sent from my iPhone

On Dec 22, 2017, at 10:59 PM, cnlson [e-mail] wrote:

@CoolNamesAllTaken no idea why but you are still sitting at incomplete ticket so your issue is not being reviewed

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[cnlson]

I think all of these have to be in the body:

1) - I have read the FAQ.
2) #### Link to contents of terminal tab or serial.log
3) #### Browser and Version of Browser, Operating System running Browser

might want to attach the gcode also

[CoolNamesAllTaken]

Those exact words, or that general content? I’ve included 2) and 3).

It could also be that the devs are on break for Christmas...

On Sat, Dec 23, 2017 at 11:15 PM cnlson [e-mail] wrote:

I think all of these have to be in the body:

1.
- I have read the FAQ.
2. Link to contents of terminal tab or serial.log
3. Browser and Version of Browser, Operating System running Browser

might want to attach the gcode also

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/foosel/OctoPrint/issues/2308#issuecomment-353769441,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIpModB_fwmtXLf1edxTvpce1DSFtDI3ks5tDfn9gaJpZM4RJS4g
.

[cnlson]

It's automatic, so for sure #1

On Dec 24, 2017 1:28 PM, "John McNelly - [email protected]"
wrote:

Those exact words, or that general content? I’ve included 2) and 3).

It could also be that the devs are on break for Christmas...

On Sat, Dec 23, 2017 at 11:15 PM cnlson [e-mail] wrote:

I think all of these have to be in the body:

1.
- I have read the FAQ.
2. Link to contents of terminal tab or serial.log
3. Browser and Version of Browser, Operating System running Browser

might want to attach the gcode also

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/foosel/OctoPrint/issues/2308#issuecomment-353769441
,
or mute the thread
fwmtXLf1edxTvpce1DSFtDI3ks5tDfn9gaJpZM4RJS4g>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/foosel/OctoPrint/issues/2308#issuecomment-353799869,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABYA6z5thM1eLUJQ9ZXz7T4TqPK2R15sks5tDqXEgaJpZM4RJS4g
.

[cnlson]

bingo - @GitIssueBot GitIssueBot added type:potential bug and removed type:incomplete ticket labels 4 hours ago

[CoolNamesAllTaken]

Boop! I'm hoping this is in the right place?

[cnlson]

I think this was fixed with a firmware update. I'm not running octoprint at all right now until the prusa firmware gets sorted.

[foosel]

Please always use the issue template and fill it out completely. Because then I don't have to run after stuff like a terminal output/serial.log all the time, which I now once again have to ;)

If this bit from octoprint.log however was triggered by you pausing your print:

2017-12-20 17:10:51,331 - octoprint.util.comm - INFO - Got a resend request from the printer: requested line = 689581, current line = 689582
| Last lines in terminal:
| Recv: ok
| Send: N689573 G1 X160.837 Y121.160 E0.01849*94
| Recv: ok
| Send: N689574 G1 X160.716 Y121.847 E0.02362*88
| Recv: ok
| Send: N689575 G1 X160.569 Y122.356 E0.01793*82
| Recv: ok
| Send: N689576 G1 X160.422 Y122.966 E0.02123*88
| Recv: ok
| Send: N689577 G1 X160.163 Y123.804 E0.02971*82
| Recv: ok
| Send: N689578 M105*26
| Recv: ok T:237.7 /240.0 B:90.0 /90.0 T0:237.7 /240.0 @:121 B@:75
| Send: N689579 G1 X159.930 Y124.718 E0.03192*89
| Recv: ok
| Send: N689580 G1 X159.868 Y125.161 E0.01515*83
| Recv: ok
| Send: N689581 G1 X159.838 Y125.567 E0.01377*87
| Recv: Error:Line Number is not Last Line Number+1, Last Line: 689580
| Recv: Resend: 689581

then your problem is caused by a bug in the Prusa Marlin fork as reported in prusa3d/Prusa-Firmware#331 and this ticket is actually a duplicate of #2285. Closing this since this most likely the case here, if not please provide your terminal output or better yet a serial.log (see the contribution guidelines on where to find and how to enable that) and request a reopen.

[Ixitxachitl]

So.. is there a solution?

[foosel]

See this FAQ entry.

[Ixitxachitl]

So no? Pause is just incompatible with the current firmware?

On Mon, Oct 22, 2018, 5:04 AM Gina Häußge [e-mail] wrote:

Please see this FAQ entry
https://discourse.octoprint.org/t/printer-specific-original-prusa/239.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/foosel/OctoPrint/issues/2308#issuecomment-431814954,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQKpgTidiMPY-K13wdd7vn77JU_WRXyLks5unbRQgaJpZM4RJS4g
.

[cnlson]

The current firmware does get have the issue

[cnlson]

This was for an old firmware, 3.11 Mk3 3.10 mk2

[Ixitxachitl]

3.4 MK3 definately has this issue.

On Mon, Oct 22, 2018 at 10:29 AM cnlson [e-mail] wrote:

This was for an old firmware, 3.11 Mk3 3.10 mk2

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/foosel/OctoPrint/issues/2308#issuecomment-431906214,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQKpgdCDXeRLroQ0z9H2bw1nhu0BJH_6ks5ungBqgaJpZM4RJS4g
.

[JohnOCFII]

3.4 MK3 definitely has this issue.

Not sure how current this list is, but it implies that M601/M602 for pause/resume on the Prusa firmware is only supported when printing from SD card, not over USB as from OctoPrint.

https://github.com/prusa3d/Prusa-Firmware/wiki/Supported-G-codes

[MStylesMS]

So, what about M76? I am trying to use that to pause a print being sent from OctoPi to an MK3-MMU2 but it did not pause.

[forestqc69]

So, what about M76? I am trying to use that to pause a print being sent from OctoPi to an MK3-MMU2 but it did not pause.

Same thing for me, but that code doesn't seem to be valid for the Prusa MK3..