Pause.g Resume.g problems

Deluxe 600

@Phaedrux The bl touch has a mechanical offset so its ok, but thank you . I added the F0 to the tool definition (now looking like this"M563 P0 D0 H1 F0" correct?) . Doesnt seem to change anything, the fan still doesnt turn back up. Any other ideas what could i try? This is realy strange.

dc42

How did you set the fan speed before the pause: did you use M106 with or without the P parameter? If you used it without (the usual way that slicers generate it) then your pause/resume code looks OK to me.

Deluxe 600

@dc42 Its set by the Slicer. So no ideas? Ow man

Deluxe 600

Well didnt know this would be such a problem

Phaedrux

an you share a sample gcode file? What slicer?

Deluxe 600

@Phaedrux Hi.
Im using PrusaSlicer for slicing.
Here is a gcode i tried printing.
test 1_0.3mm_PLA_MK3.gcode

Phaedrux

So basically it turns the fan on with M106 S255 and leaves it on a full power for the duration of the print and then turns it off at the end.

If that's normally the case, as a work around, why not just set the fan speed to 100% in resume.g?

Phaedrux

Now that 3.2 is released can you test with that?

Deluxe 600

It is S255 for PLA but once you start printing PETG the speed changes how its needed. No i havent tried 3.2 yet. Could it solve this problem?

Phaedrux

@Deluxe-600 said in Pause.g Resume.g problems:

Could it solve this problem?

I don't know, but testing on the most recent code base would be ideal in case it has been solved and any work to fix it if it is a bug would happen there. Since you're on 3.1.1 it's an easy update by uploading the Duet2and3CombinedFirmware zip file to the system tab.

Deluxe 600

@Phaedrux Hi.
So i have updated to 3.2 and tried the pause.g with M107 and also with M106 S0 and the resume.g with M106 R1 and also with M106 R2 but still no luck. Seems like the M106 R1 command sets the speed always to 0rpm. Thank you guys for helping.

Deluxe 600

I think its a bug in the software. There is no reason why should this not work, you guys dont use pause on your printers? I went trough every forum i could find and the M106 R1 command should turn the print fan back on...but it doesnt for unknown reason.

Phaedrux

Your gcode all looks ok, so it may be a bug. We're looking into it.

Deluxe 600

@Phaedrux Thank you. Meanwhile i will try to figure it out, if i find any way to solve this problem i will let you know.

dc42

I have just tested that on my delta running 3.2 and it works properly for me.

Pause.g:

; Pause macro file
if state.currentTool != -1
  M83					; relative extruder moves
  G1 E-4 F2500		; retract 4mm
G91					; relative moves
G1 Z5 F5000			; raise nozzle 2mm
G90					; absolute moves
G1 X0 Y85 F10000
M106 S0

Resume.g:

; Resume macro file
M106 R1
G1 R1 X0 Y0 Z2 F5000	; move to 2mm above resume point
G1 R1 X0 Y0 Z0		; lower nozzle to resume point
if state.currentTool != -1
  M83			; relative extruder moves
  G1 E4 F2500		; undo the retraction

The GCode file I am printing uses M106 S0 at the start, M106 S255 at the start of the second layer, and M106 S0 at the end. My M563 command in config.g does not have a F parameter.

Deluxe 600

@dc42 said in Pause.g Resume.g problems:

if state.currentTool != -1 M83 ; relative extruder moves G1 E-4 F2500 ; retract 4mm G91 ; relative moves G1 Z5 F5000 ; raise nozzle 2mm G90 ; absolute moves G1 X0 Y85 F10000 M106 S0

Ok...so i have found out what was the problem with the FAN. I cant believe it was this trivial, any way the only reason the FAN didnt start up on resume was that the M106 R1 has to always be on the first place otherwise it just doesnt work. When i found out it was this all along i was happy and mad at the same time. Thank you all for your help we finaly did manage to get it working. Have a great day

fcwilt

@Deluxe-600 said in Pause.g Resume.g problems:

M106 R1 has to always be on the first place

Do you mean the first line in the file?

Thanks.

Frederick

Deluxe 600

@fcwilt Yes the very first line in the file.

fcwilt

@Deluxe-600 said in Pause.g Resume.g problems:

@fcwilt Yes the very first line in the file.

That seems very odd.

Thanks.

Frederick