Heaters remain on after upgrade from version 3.3 to 3.4

Phaedrux

@gloomyandy My understanding is that if stop.g is present, M0 will call that macro and nothing else. Also from my understanding, M0 without stop.g should turn off the heaters. Waiting for DC42 to investigate.

I'm not sure if there is another way to turn off all the heaters at once. Possibly with a loop that cycles through the heaters and turns them off?

chrishamm

@trobison M0 and M1 turn off the heaters only if stop.g/sleep.g is NOT present. If you have stop.g or sleep.g, you must turn off the heaters in those files. You may do that using M568 and M140.

Since M0 invokes stop.g, it's a bad idea to put M0 in stop.g (same applies to M1 and sleep.g).

trobison

I removed the M0 from the stop.g and inserted the commands below:

M140 H0 ; Set bed heater to 0
M568 P0 R0 S0 ; Set T0 off
M568 P1 R0 S0 ; Set T1 off
M568 P2 R0 S0 ; Set T2 off
M568 P3 R0 S0 ; Set T3 off

At the end of the print, T1 (in this test) dropped to the standby temp, and the bed remains active. I then typed in "M568 P1 R0 S0" at the console and the heater was set to 0. Typing "M140 H0" turned off the bed.
It appears that commands in stop.g are not processed at the end of a successful print, and I might have to put these in the slicer's end G-Code.

infiniteloop

@trobison said in Heaters remain on after upgrade from version 3.3 to 3.4:

It appears that commands in stop.g are not processed at the end of a successful print

The stop.g macro will only be invoked if your slicer puts a M0 at the end of its file. Are you sure this gCode is there?

To verify, insert this line into your stop.g file:

M291 P"stop.g is executed"

It will alert you when the macro is called. If not, I'm pretty sure there's no M0 in your slicer's output.

trobison

@infiniteloop
I can try that. The second paragraph of my initial post I said that I opened up the gcode generated from SuperSlicer, and there is a "M0" command in there. This was inserted from the End-gcode field in the slicer. The heaters remained on.

trobison

The command did not echo anything to the webpage or screen at the end of print.

trobison

I believe I have it working. I added the following to my End-Gcode in the slicer (SuperSlicer)"

M140 H0 			; Set bed heater to 0
M568 P0 R0 S0		; Set T0 off
M568 P1 R0 S0		; Set T1 off
M568 P2 R0 S0		; Set T2 off
M568 P3 R0 S0		; Set T3 off
M84                     ; disable motors
M291 P"Print Finished"

The print finished and popped up a friendly message. I am still unclear why M291 P"stop.g is executed" in the stop.g didn't echo a message.

infiniteloop

@trobison said in Heaters remain on after upgrade from version 3.3 to 3.4:

I added the following to my End-Gcode in the slicer (SuperSlicer)"

Instead of all these lines, simply add a M0 to the end-gCode of SuperSlicer.

trobison

@infiniteloop
A test print has completed with a M0 command at the end of the End-gcode, and the heaters are still on.
I typed in a M0 in the console - the heaters remain on.

ÖrjanE

@trobison Setting the temperature to zero is not the same as turning the heater off. You can use the A-parameter of M568 to change the heater state to off:
M568 P0 A0
To turn off the bed, you need: "M140 H0 S-274".

Normally, all these commands should be in stop.g while the End-gcode in the slicer should only contain a single M0.

trobison

@örjane Cheers. A single M0 doesn't seem to work since the firmware update. I will make the changes you have suggested.