Strange Behavior , after "Pause" 'Cancel ""print again"

moth4017

Phaedrux

Can you try copying your cancel.g to stop.g?

moth4017

; stop.g
; called when M0 (Stop) is run (e.g. when a print from SD card is cancelled)
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Thu Dec 30 2021 11:07:38 GMT+1300 (New Zealand Daylight Time)

;cancel.g
G28 X Y

Copied cancel .g to stop.g

Did "Pause" "M0" stop.g ran perfectly

Did "Pause " "cancel" ran perfectly

Did "Print again" after cancel
Cancelled printing file 0:/gcodes/Body1_0.2mm_ABS__9h28m.gcode, print time was 0h 1m
Error: Failed to home axes
Error: Driver 0.4 error: over temperature shutdown
Error: Driver 0.5 error: over temperature shutdown
Error: Driver 0.4 error: over temperature shutdown
Error: Driver 0.5 error: over temperature shutdown
Error: Driver 0.4 error: over temperature shutdown
Error: Driver 0.5 error: over temperature shutdown
Error: Driver 0.4 error: over temperature shutdown
Error: Driver 0.5 error: over temperature shutdown
Error: Driver 0.4 error: over temperature shutdown
Warning: Driver 0.5 warning: over temperature warning
Warning: Driver 0.5 warning: over temperature warning

Phaedrux

I just noticed in your pack of files that cancel.g has a leading blank space character.

2d257d8b-aba0-4070-8242-dd1f69d558cb-Screen Shot 2022-03-22 at 12.16.36 AM.png Screen Shot 2022-03-22 at 12.16.36 AM.png

Phaedrux

@moth4017 said in Strange Behavior , after "Pause" 'Cancel ""print again":

Did "Print again" after cancel
Cancelled printing file 0:/gcodes/Body1_0.2mm_ABS__9h28m.gcode, print time was 0h 1m
Error: Failed to home axes

Do you have a start.g file? If not, can you create one and add G28 to it?
That should make sure all axis are homed before the sliced gcode is executed.

I think the over temperature warnings on drivers 0.4 and 0.5 may be related to stall detection on the Z axis.

moth4017

@phaedrux
Will do ill test now so you have results in the morning

moth4017

@phaedrux
Interesting after removing the "space " from the "cancel.g" file the commands now work
also the over temperture errors seem to have stopped, will do more checks to confirm

moth4017

@phaedrux

After testing , I can confirm all the above issues are caused by the space in front of the " Cancel.g" file , including the errors below.

Thanks for the help. im guessing you will want to trap this issue some how, help happy to help test if needed .

Cancelled printing file 0:/gcodes/Body1_0.35mm_PLA__17m.gcode, print time was 0h 0m
Error: Probe was not triggered during probing move
Error: Driver 0.4 error: over temperature shutdown
Error: Driver 0.5 error: over temperature shutdown
Error: Driver 0.4 error: over temperature shutdown
Error: Driver 0.5 error: over temperature shutdown
Error: Driver 0.4 error: over temperature shutdown
Error: Driver 0.5 error: over temperature shutdown
Error: Driver 0.6 error: over temperature shutdown
Error: Driver 0.5 error: over temperature shutdown
Error: Driver 0.4 error: over temperature shutdown

Phaedrux

Well I think what's happening here is that with the cancel.g basically missing when the print is canceled it's getting sent M0

https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m0-stop-or-unconditional-stop

Then when trying to print again the machine is not in a ready state. When the motors are in stealthchop mode they require a short tuning move and I guess that's not happening, hence the errors.

It would be best to have a cancel.g and stop.g file present with the commands you wish to happen. Use M0 as your slicer end gcode, then have all your ending commands in stop.g.

You can also use a start.g file that has any preparation commands you want. Like homing the printer, pre-heating, etc.

That should give you more predictable behaviour.

moth4017

@phaedrux
Thank you for the advice, please close thiis thread