Issue slicing resulting in false tripping of thermal runway protection Heater_ID: 0 - echo:Heating Failed

I have a Lulzbot Taz 6 that I got off of FB Marketplace. I’ve printed several things with it, some rather large, and last night decided to try to up the speed a bit, going to 50mm/s in Cura instead of the abysmally slow 20 - 30 mm/s default. (I had been wondering why it was so slow).

A few minutes into the print, I got “Heater_ID: 0 - echo:Heating Failed” from OctoPrint. Octoprint makes it very clear that the printer is finding the error and reporting it to Octoprint:


OctoPrint

    admin

Connection
Serial Port
Baudrate
Printer Profile
Save connection settings
Auto-connect on server startup
State
State: Offline after error
Heating failed, system stopped! Heater_ID: 0 - echo:Heating Failed
File:  
Uploaded: unknown
Timelapse: -
Approx. Total Print Time: -
Print Time: -
Print Time Left: -
Printed: -
Files
Birdhouse_Rook_Base_T6-SINGLE.gcode
Updated: an hour ago
Size: 4.3MB
Phone_stand_T6-SINGLE.gcode
Updated: 6 hours ago
Size: 684.5KB
jewelry_display_body_T6-SINGLE.gcode
Updated: 3 months ago
Size: 54.4MB
jewelry_display_T6-SINGLE.gcode
Updated: 3 years ago
Size: 59.4MB
rocktopus_T6-SINGLE.gcode
Updated: 3 years ago
Size: 1.9MB
Free: 23.4GB / Total: 28.1GB
Create folder...
Upload Upload to SD
Hint: You can also drag and drop files on this page to upload them.
Printer Notifications
There are currently no notifications from your printer.

    Temperature
    Control
    GCode Viewer
    Terminal
    Timelapse

X/Y
Z
Feed rate modifier:
%
Tool (E)
mm
Flow rate modifier:
%
General

    OctoPrint 1.10.3 Python 3.9.2 OctoPi* 1.0.0 (build 2024.11.05.092907)

    Web Donate About Achievements System 

Error reported by printer
Your printer's firmware reported an error. Due to that OctoPrint will disconnect. Reported error: Heating failed, system stopped! Heater_ID: 0 - echo:Heating Failed
×
There was an error reported by your printer

Your printer's firmware reported an error:

Heating failed, system stopped! Heater_ID: 0 - echo:Heating Failed

Due to this error, OctoPrint was not able to continue to communicate with your printer and sent an emergency stop command M112 to ensure all heaters are turned off, then disconnected.

You might be able to find more information on this error and how to solve it in this FAQ entry!

Here's the last communication with your printer before this error occurred:

Send: N2201 G1 F3000 X159.32 Y197.768 E791.37337*0
Recv: Not SD printing
Recv: ok N2201 P0 B3
Send: N2202 G0 F10500 X158.613 Y197.768*70
Recv: ok N2202 P0 B3
Send: N2203 G1 F3000 X184.601 Y171.78 E792.46799*15
Recv: Not SD printing
Recv: ok N2203 P0 B3
Send: N2204 G0 F10500 X184.601 Y171.073*71
Recv: ok N2204 P0 B3
Send: N2205 G1 F3000 X157.906 Y197.768 E793.59238*48
Recv:  T:223.75 /240.00 B:60.01 /60.00 @:127 B@:30
Recv: Not SD printing
Recv: ok N2205 P0 B3
Send: N2206 G0 F10500 X157.199 Y197.768*72
Recv: ok N2206 P0 B3
Send: N2207 G1 F3000 X184.601 Y170.366 E794.74655*48
Recv: Error:Heating failed, system stopped! Heater_ID: 0
Recv: echo:Heating Failed
Changing monitoring state from "Printing" to "Error"

This error is not caused by OctoPrint, it is a problem that was reported by your printer's firmware to which OctoPrint reacted!
Close

It looks like the gcode is getting made where the nozzle temp is being set to 240 C for some reason, and that’s usually about when it fails. I have set the material to 201 C, and even lowered it to 205 C, so I don’t know where 240 C is coming from. I’ve tried a few different slices of the same part, and they all fail a few mins in. The same gcode fails in the same spot, if I just try it again.

I tried a different part, upped the speed from default to to 40mm/s, and it ran fine for almost 2 hours.

Based on this, I don’t think I have a hardware problem, sounds like a slicer issue to me. While I’m kind of new to Lulzbot stuff, I’ve been using Cura for my Enders for many years and have not ran into this kind of issue. Nor have I ran into an issue like this with my Prusas.

My hotend is a single extruder 3mm nozzle, I think it was the first one they made for the Taz 6, but it’s called “v2.1”? The bed is upgraded to a magnetic PEI sheet. I’m using some old 2.85mm Inland PLA (not PLA+).

Back when I was trying to get my old Printrbot LC running good, I would notice heat creep up the hotend into the filament, so I had to rig up a fan to keep the incoming filament cool. The Taz 6 feeding mechanism reminds me of this issue, but there’s about 10 years of engineering in between, so hopefully that’s not related? I upgraded to bimetal heatbrakes in some of my other printers to address this issue, that’s really the only thing I could think of why upping the speed would impact a thermal sensor, but that’s kind of a reach.

I have not updated the firmware on the Taz 6, but that seems like it might be a good idea at some point. I see that I need to back up some info from the printer, so I haven’t done that yet.

I’m running Cura Lulzbot edition 4.13.10 on Windows 10. The printer has a Raspberry Pi 4 running Octoprint on it, and it has a wired network connection. I have 4 printers online right now with similar situations (2 Prusa I3, 1 custom Ender 3v2, and this Taz 6). The Taz 6 and it’s server are on a UPS.

What settings should I adjust in Cura that might fix this? I see there is a slightly new version available, I might try that.

My search has spidered all over the place, and I’m finding others with thermal runway issues, false thermal issues, etc.

Watching what the temperature was actually doing when this happens will explain a lot.

I can’t think why there would be any temp change without a filament change inserted in the GCODE, but posting the GCODE that it was trying to run will help figure that out.

Octoprint may be intervening and changing a temperature based on any number of plugins or configuration steps, so you have a lot of variables introduced by going through octoprint.

The temp is randomly set to like 240 C and the nozzle starts to heat up and then it all stops. This is the most recent example:

gcode:
Birdhouse_Rook_Base_T6-SINGLE.gcode (4.3 MB)

Model:

I have not added any plugins, but I have disabled a couple. I’ve been using Octoprint since 2010 and don’t usually configure much of it besides network and have not found any issues specific to it while troubleshooting things.

The printer says it has marlin 2.0.9.0.13 for firmware. The patch notes for the latest version of Cure LE says everything has been updated, do Cura and the printer have to be updated in sync?

4.13.16

Minor changes!

Firmware to 2.1.3.0.45

Small fixes included in the patched build of 4.13.15


4.13.15

Firmware on all current machines updated to 2.1.3.0.44

Main firmware changes are related to Dual Extruders

TAZ 8 and TAZ Pro BLTouch start gcodes now probe the bed once as a reference point prior to fully tramming/probing

Printers no longer disengage the X motor in their end gcode

Fixed an issue regarding a false positive when checking if a USB printer matched the current machine

USB Printer connection errors reviewed and rewritten for clarity

Small correction regarding maximum bed temperature for the Mini 3 on one profile

That is just bizarre that there would be an M104 in the middle of movement commands.

Re-slice and check for that stray M104 command. It’s so randomly placed I can only imagine it’s some strange unique glitch.

But that weird command aside, the system shouldn’t have a problem keeping the hotend at 240c. The screenshot of the temps show it’s increasing in temperature toward the target, but I’m not sure how fast the firmware is expecting the temperature to raise to be considered safe. If you’re shoving more filament through with increased feed rates, that could be slowing the temp increase too much that it’s giving the error.

That seems like it. I was only pushing it to 50mm/s, which I don’t think is especially fast. I did resize the part to 50% since it’s naturally big.

I just updated Cura, will slice and try again, thanks for investigating!

Line 1705 I get: M104 S210

Which is kinda weird, but more in line with what the settings show:

It’s been going good for a few mins now, so I guess it was a Cura issue.

Just weird that it wasn’t even on a layer change, filament change… glitchy.

1 Like