Error Heater_ID: 0 with cura 4.3

Get Help
1

What is the problem?
When i use cura 4.3 and upload in octoprint, the print start and after 1 layer it stop.

What did you already try to solve it?
I have print same file 5 times and each time the error was at same place of print.
when i use cura 3.6, i don't have the error

Logs (octoprint.log, serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support!)

Send: N2377 G0 F4800 X26.923 Y109.40669
Recv: ok
Send: N2378 G1 F1500 X35.133 Y101.196 E114.416725
Recv: ok
Send: N2379 G0 F4800 X34.503 Y101.26173
Recv: ok
Send: N2380 G1 F1500 X26.987 Y108.777 E114.770256
Recv: Error:Thermal Runaway, system stopped! Heater_ID: 0
Recv: Error:Printer halted. kill() called!
Changing monitoring state from "Printing" to "Error: Thermal Runaway, system stopped! Heater_ID: 0 - Printer halted. kill() called!"

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible)
Octoprint: Version 1.3.12
octopi: Version 0.16.0

Plugin:
Dashboard]
DisplayLayerProgress Plugin
EEPROM Marlin Editor Plugin
Themeify

2

You might want to read this.

1 Like
3

why with same 3d model, in cura 3.6 its work and cura 4.3 doesn't work?
i dont understand

4

Already considered a fault with the slicer?
You may compare the produced gcode files of both.

5

I have compare 2 files but its not same syntax to gcode

image
image.png1476×596 36.6 KB

6

The syntax is the same - the values are different.
Of more interest is the header, the very beginning of the file where the settings are made.
It would be quite handy if the gcode files are from the same model at the same/middle position.

7

But it is the same 3d model...
3.6.gcode (712.1 KB) 4.3.gcode (706.2 KB)

8

So there are differences.
I found this in the Cura 4.3 gcode file (not in the 3.6 file):

M140 S60
M106 S255

M106 S255 powers the part cooling fan up to the maximum. And depending of the position of the print area, it can cool the bed or the hotend so much down, that the thermal runaway protection is triggered.
If it is the bed, you may reposition the object, lower the the fan speed or make a slight correction to the firmware (the value the firmware recognizes a variation as thermal runaway issue.
If it is the hotend, the part cooling fan nozzle should be repositioned or redesigned.

2 Likes
9

@Ewald_Ikemann I didn't recognize you at first because of your new profile picture :smiley:

1 Like