Pause/Resume print

[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

[Touchthebitum]

@fcwilt
same result

[fcwilt]

@Touchthebitum said in Pause/Resume print:

@fcwilt
same result

Not really surprised at that.

Have you tried pressing the DWC Resume button a second time?

Frederick

[Touchthebitum]

@fcwilt
yes , three, four times

[fcwilt]

@Touchthebitum said in Pause/Resume print:

@fcwilt
yes , three, four times

And each time it returns to the paused state?

Frederick

[Touchthebitum]

@fcwilt
yes

[fcwilt]

Can you open the gcode file generated by the slicer and find the place where it issues the M226/M600?

I would like to see, say, 10 lines of the gcode before and after that place.

Frederick

[Touchthebitum]

@fcwilt
I copied the last requested modifications (M400/M25):

G0 F7200 X119.901 Y137.202
G0 X123.484 Y131.281
G0 X124.451 Y129.87
G0 X125.512 Y128.529
G0 X126.639 Y127.282
G0 X127.866 Y126.092
G0 X129.172 Y124.987
G0 X130.548 Y123.972
G0 X131.989 Y123.051
G0 X133.489 Y122.23
G0 X138.746 Y120.054
G0 X139.123 Y119.677
G1 F1500 X139.672 Y119.552 E0.02789
G1 X142.19 Y119.156 E0.12626
G1 X144.892 Y118.999 E0.13406
G1 X146.137 Y119.026 E0.06168
G0 F7200 X145.873 Y119.084
G1 F1800 E-1
;MESH:NONMESH
;TYPE:CUSTOM
;added code by post processing
;script: ChangeAtHeight.py
;current z: 0.600000
M300 ;Beep
M400
M25

;LAYER:2
;TYPE:WALL-OUTER
;MESH:imbuto.stl
G1 F1800 E1.08315
G1 F1500 X123.597 Y131.358 E0.08025
G1 X122.73 Y132.824 E0.07987
G1 X121.964 Y134.345 E0.07987
G1 X121.3 Y135.914 E0.0799
G1 X120.76 Y137.475 E0.07746
G1 X120.743 Y137.53 E0.0027
G1 X120.308 Y139.122 E0.0774
G1 X119.967 Y140.791 E0.07989
G1 X119.741 Y142.48 E0.07991
G1 X119.629 Y144.179 E0.07985
G1 X119.631 Y145.882 E0.07987

[fcwilt]

@Touchthebitum

Thanks.

I don't see anything odd there - all looks fine.

Hmm... My slicer allows me to add my own gcode at different points in the printing

• the beginning
• the end
• layer change
• tool change
• filament retraction

Does yours have different places? If so is there anything in them?

Frederick

[Touchthebitum]

@fcwilt
it seems not
I can only edit the gcode on dwc

[fcwilt]

@Touchthebitum said in Pause/Resume print:

@fcwilt
it seems not
I can only edit the gcode on dwc

So that code at the point of a layer change is being inserted by something the the DWC?

I didn't know that was possible.

Frederick

[Touchthebitum]

@fcwilt
no, I can do it manually on the DWC

[fcwilt]

I did my testing with a Duet 3 Mini 5 - no SBC attached.

I created a ultra simple test print file - you could do it in notepad if that is all you have.

G91
G1 X100
G1 X-100
G1 X100
G1 X-100
M226
G1 X100
G1 X-100
G1 X100
G1 X-100

the pause file:

M291 P"PAUSE" R"PAUSE" T1

the resume file

M291 P"RESUME" R"RESUME" T1

It all worked fine.

I suggest you do the same and see if you have a different result

Frederick

[Touchthebitum]

@fcwilt
The solution was M226 instead of M600.
I had to edit and place M226 at the right layer.
I kepts my pause and resume files and it worked.
Thanks for your help

[fcwilt]

@Touchthebitum said in Pause/Resume print:

@fcwilt
The solution was M226 instead of M600.
I had to edit and place M226 at the right layer.
I kepts my pause and resume files and it woked.
Thanks for your help

Glad to hear you got it working.

I will need to test M600 as it is documented as being the same as M226 with the exception that if a file filament_change.g is present that is run instead of instead of pause.g.

So in theory if filament_change.g is NOT present it should work just like M226.

Frederick

[Touchthebitum]

@fcwilt
ok