Pause/Resume print

;TYPE:CUSTOM
;added code by post processing
;script: PauseAtHeight.py
;current layer: 2
M83 ; switch to relative E values for any needed retraction
G1 F300 Z1.6 ; move up a millimeter to get out of the way
G1 F9000 X50 Y50
G1 F300 Z15 ; too close to bed--move to at least 15mm
M104 S0 ; standby temperature
M226 ; Do the actual pause
M17 E0
M109 S215 ; resume temperature
G1 F300 Z1.6
G1 F9000 X138.263 Y119.525
G1 F300 Z0.6 ; move back down to resume height
G1 F1800 ; restore extrusion feedrate
M82 ; switch back to absolute E values
G92 E0.06168

fcwilt

@Touchthebitum

Thanks.

Can you edit that code?

Since the firmware is trying to handle the pause/resume operations on it's own using the pause/resume files it would seem that the slicer generated code should not include any code that duplicates what those two files do.

So if the firmware pause/resume files do EVERYTHING that is needed then the slicer code should only be M226 or M600 for pause and nothing for resume.

Frederick

Touchthebitum

@fcwilt
Yes I can edit it.
Ok, thanks, I'll check that

Touchthebitum

nothing to do
I only placed M600 on the gcode. The pause is perfect but when I press on "resume" it goes on the print point and turns back on the pause location ...

fcwilt

@Touchthebitum said in Pause/Resume print:

when I press on "resume" it goes on the print point and turns back on the pause location ...

I don't understand what you mean by "goes on the print point" or "turns back on the pause location".

Can you phrase that another way?

Frederick

Touchthebitum

@fcwilt
the carriage turns back on the last printed position BUT doesn't print, then it turns back on the "pause" location

fcwilt

@Touchthebitum

Still not clear.

Are you saying the carriage moves to the correct location for resuming BUT the printer returns to the paused state?

Frederick

Touchthebitum

@fcwilt
exactly

fcwilt

@Touchthebitum said in Pause/Resume print:

@fcwilt
exact

Great.

And if you pause then resume using the Pause and Resume buttons on the DWC it all works correctly?

Frederick

Touchthebitum

@fcwilt
yes

fcwilt

@Touchthebitum said in Pause/Resume print:

@fcwilt
yes

Great - now I fully understand what you are doing and seeing.

What I don't understand is why pausing from the slicer isn't working. I have an idea but I need to try to verify it.

Perhaps we will get lucky and @dc42 will jump in here.

Frederick

Touchthebitum

@fcwilt
Pausing is working but resuming not ...

DIY-O-Sphere

@Touchthebitum said in Pause/Resume print:

if state.currentTool != -1

Can you try to remove that from the resume.g?

Touchthebitum

@DIY-O-Sphere
Tried but nothing changed

fcwilt

@Touchthebitum said in Pause/Resume print:

@fcwilt
Pausing is working but resuming not ...

Sorry - I meant that pausing from the slicer is not resuming correctly as opposed to pausing from the DWC which does resume correctly.

That suggests to me that the way the firmware handles a M226 or M600 pause is different from how it handles the pause initiated by the DWC.

Here is something to try - just a long shot.

Replace the M226 or M600 in the slicer with M400 followed by M25.

Frederick