Does not resume correctly

[energiebrand]

When sending M600 on my Sidewinder x1 via Octoprint the Z-axis moves up 8-10cm (did not measure it exactly). When pressing RESUME in Octoprint the Z-axis does not move down but starts printing at that hight. I expect, that the Z-axis will move down the same way before continue printing.

[wgcv]

I was checking and yes was an error I think that is solved with the commit: 595753c

[energiebrand]

Hi wgcv, thanks a lot for checking this issue! Any idea about a date for a corrected version? :-) I am not a SW developer, so implementing your fix directly in the code is not an option for me,...I think...

[wgcv]

Update the plugin

[PLA7IN]

Hello @wgcv. I had some strange issues with the 1.0.0 version like @energiebrand and some extra issues too. So I updated to the new 1.0.1 version in hope this fix everything. Now it currently just kinda pause my Sidewinder so it stops in the process and doesn't move away from the print, so someone can change the material. I can resume printing over octoprint, but that's not a difference to just pause the print.

[Haacker]

I just had the same issue on my SideWinder X1. The printer just stops and leaves the printhead on the print job, rather than moving it up 80mm as specified in the settings for the plugin.

[wgcv]

Sorry was a bug solved in f866a0f

I tested the last version and work well, please if you have any issue or problem report!

[PLA7IN]

Now the head moves perfectly (if it is supposed that he does some print movements in the air over the object and then goes down on the object). But now I have the problems I had before with 1.0.0: the extruder doesn't extrude/move anymore.

[wgcv]

Sorry, what do you mean doesn't extrude? Did you press resume in Octoprint?

The normal process is:

1. Printing
2. Stop
3. Get up 8cm and move to home
4. Wait until the user changes the filament ( you can use the display menu to change the filament or a plugin for octoprint)
5. From Octorpint press resume
6. Resume the print and print until finish or other M600.

[PLA7IN]

Sorry that I wasn't excatly about this. Yeah, after sending a m600 over terminal it does all your discribed steps but in your point 6 (after resume press in octoprint) the printer did following:
He goes from his +80mm z Position over the started printing object in ca +80mm (so he just moves x and y) an started moving the head like he resume printing with this distance but without extracting material (this wouldnt be a problem. It just looked maybe unsupposed). After some head movements in the air, he stops, goes down on the object and moves the head like he want to resume printing but he doesn't extruder material.

With the Version 1.0.0 some das ago I printed an other object where retraction was active and the printer didn't extrude, but retract the material back and forth.

I hope I have explained it clearly enough :) thanks

If not, I can make a video for you later

[wgcv]

That sounds very weird @PLA7IN
What Octoprint version you have? Do you have Python 3 or Python 2?
What is your slicer? You are using any plugin with the slicer?
You can share the G-code (Few lines before and after the M600)

[PLA7IN]

Octoprint: 1.4.0
Python: 2.7.12
Slicer: PrusaSlicer-2.2.0
The slicer doesn't have any additional Plugins.
I was sending m600 over the terminal the last time, but i sliced an object too that always acted similar:

Here is a bit code from this file:

M204 S1250
G1 F1200
G1 X154.019 Y146.706 E0.31732
M204 S1000
; stop printing object Shape-Cylinder id:0 copy 0

G1 F6240.000
G1 X150.206 Y143.507 E-0.90931
G1 E-0.09069 F1200.00000
G1 Z9.440 F7800.000
M600
; printing object Shape-Cylinder id:0 copy 0
G1 X150.752 Y143.516
G1 Z9.240
G1 E1.00000 F900.00000
M204 S800
G1 F1200
G1 X151.421 Y143.842 E0.03863
G1 X151.939 Y144.160 E0.03158
G1 X152.428 Y144.522 E0.03158

[Questman01]

Hi i got the same issue like PLA7IN

When an M600 occours the Z is going up. X and Y are going to Park. After changing the Filament and klicking Resume in Octoprint an bigger Retract occours and the Head starts "Printing in the Air". After a few Movements Z is going down to the right position and starts to print (It Looks like it starts at the right XY and Z position). But in case of the big Retract before it took a while until Material is back in the Nozzel the the first few Movements are without printing anything.

The end result looks like the photo i have attached. Hope you can recognize it there.

Greetings Kai-Uwe

[DanHudson15]

I am still experiencing the print head staying at the same Z height. The head returns to the correct X and Y, but need to be manually set to the correct Z. Here is the code from before and after the pause:

Send: N12621 G1 F1500 E866.309151
Recv: ok
Send: N12622 G1 F300 Z1.3624
Recv: ok
Send: N12623 G0 F9000 X127.797 Y122.21 Z1.3628
Recv: ok
Changing monitoring state from "Printing" to "Pausing"
Send: N12624 M40036
[...]
Recv: ok
Send: N12625 M117 Filament Change48
Recv: ok
Send: N12626 G9116
Recv: ok
Send: N12627 M8324
Recv: ok
Send: N12628 G1 Z+80 E-0.8 F4500119
Recv: ok
Send: N12629 M8223
Recv: ok
Send: N12630 G9022
Recv: ok
Send: N12631 G1 X0 Y046
Recv: ok
Send: N12632 M11435
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
Recv: X:0.00 Y:0.00 Z:81.36 E:865.51 Count X:0 Y:0 Z:32526
Recv: ok
Changing monitoring state from "Pausing" to "Paused"
[...]
Recv: ok
Recv: ok
Recv: ok
[...]
Changing monitoring state from "Paused" to "Resuming"
Changing monitoring state from "Resuming" to "Printing"
Send: N12633 G0 X127.797 Y122.21 Z1.52112
Recv: ok
Send: N12634 G1 F300 Z1.3227
Recv: ok
Send: N12635 G1 F1500 E868.809151
Recv: ok
Send: N12636 G1 X127.954 Y122.394 E868.81558102

and here is the Gcode:
;TIME_ELAPSED:8140.599125
M600 E30.00 L300.00 X0.00 Y0.00 ; Generated by FilamentChange plugin
;LAYER:7
;MESH: logo(5).stl
G0 X127.797 Y122.21 Z1.52
;TYPE:WALL-INNER
G1 F300 Z1.32

[PLA7IN]

Here is the video I made with version 1.0.2 so that you maybe better understand what was I meaning. Sorry that I recorded it upright and with bad quality. I recorded it with my old Phone to show that I send m600 with my phone: https://youtu.be/dFMHTNsRmWE
I will now test 1.0.5 and give you a report if I know more.

[DanHudson15]

I may be working, I seem to have a clogged nozzle right after the color change.

…

________________________________ From: Konstantin Wacker <notifications@github.com> Sent: Thursday, July 9, 2020 1:47 PM To: wgcv/RewriteM600 <RewriteM600@noreply.github.com> Cc: HUDSON, DANIEL J. <DHUDSON@hanover.com>; Comment <comment@noreply.github.com> Subject: Re: [wgcv/RewriteM600] Does not resume correctly (#4) Here is the video I made with version 1.0.2. Sorry that I recorded it upright and with bad quality. I recorded it with my old Phone to show that I send m600 with my phone: https://youtu.be/dFMHTNsRmWE<url> — You are receiving this because you commented. Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_wgcv_RewriteM600_issues_4-23issuecomment-2D656263589&d=DwMCaQ&c=mJmNeTh4e8c7gpF9DFchHA&r=XqFGqFk0FhXFgIr_XM7S0wKRx6UfuwogwqxP9QPqobU&m=FXgxaEzk_Q8Gm8fwxkrn7KDSw8tOZdFpYipZtP2FLC0&s=iHvhc6W5OQR8eZ9LtYN8HJmIIZDJvqBTnvUDxKB1KXk&e=>, or unsubscribe<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_APOZIZOSPGFAM7UBYACEXFTR2X7BZANCNFSM4OLCXAWA&d=DwMCaQ&c=mJmNeTh4e8c7gpF9DFchHA&r=XqFGqFk0FhXFgIr_XM7S0wKRx6UfuwogwqxP9QPqobU&m=FXgxaEzk_Q8Gm8fwxkrn7KDSw8tOZdFpYipZtP2FLC0&s=FXsFXUTN8KSn2JikCkb3h6Inc4pRSNDdTuGBk5cHmkk&e=>.