MAX_TEMP triggered

What is the problem?
Offline (Error: MAXTEMP triggered, system stopped! Heater_ID: 0 - MAXTEMP triggered, system stopped! Heater_ID: bed)

What did you already try to solve it?

Worked with Cura on the 10 5s I have, reseated the plugs for the bed and the nozzle. Reinstalled Octopi from scratch on my raspberry Pi

Logs (octoprint.log, serial.log or output on terminal tab, browser error console ...)

Changing monitoring state from "Offline" to "Detecting serial port"
Serial port list: ['/dev/ttyUSB0']
Connecting to: /dev/ttyUSB0
Changing monitoring state from "Detecting serial port" to "Opening serial port"
Connected to: Serial<id=0x686ba810, open=True>(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Starting baud rate detection...
Changing monitoring state from "Opening serial port" to "Detecting baudrate"
Trying baudrate: 115200
Send: N0 M110 N0125
Recv: start
Changing monitoring state from "Detecting baudrate" to "Operational"
Recv: echo: External Reset
Send: N0 M110 N0
125
Recv: Marlin
Recv: echo: Last Updated: 2015-12-01 12:00 | Author: (CR-10 500)
Recv: Compiled: Jun 8 2018
Recv: echo: Free Memory: 1119 PlannerBufferBytes: 1232
Recv: echo:Hardcoded Default Settings Loaded
Recv: echo:Steps per unit:
Recv: echo: M92 X80.00 Y80.00 Z400.00 E93.00
Recv: echo:Maximum feedrates (mm/s):
Recv: echo: M203 X300.00 Y300.00 Z5.00 E25.00
Recv: echo:Maximum Acceleration (mm/s2):
Recv: echo: M201 X300 Y300 Z100 E5000
Recv: echo:Accelerations: P=printing, R=retract and T=travel
Recv: echo: M204 P500.00 R500.00 T1000.00
Recv: echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/s), Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s)
Recv: echo: M205 S0.00 T0.00 B20000 X5.00 Z0.40 E5.00
Recv: echo:Home offset (mm):
Recv: echo: M206 X0.00 Y0.00 Z0.00
Recv: echo:Material heatup parameters:
Recv: echo: M145 M0 H185 B0 F0
Recv: echo: M145 M1 H240 B0 F0
Recv: echo:PID settings:
Recv: echo: M301 P22.20 I1.08 D114.00 C100.00 L20
Recv: echo:Filament settings: Disabled
Recv: echo: M200 D3.00
Recv: echo: M200 D0
Recv: echo:SD card ok
Recv: Init power off infomation.
Recv: size:
Recv: 591
Recv: init valid:
Recv: 0
Recv: 0
Recv: ok
Send: N1 M115*39
Recv: FIRMWARE_NAME:Marlin 1.1.0 From Archive SOURCE_CODE_URL:http:// ... PROTOCOL_VERSION:1.0 MACHINE_TYPE:www.cxsw3d.com EXTRUDER_COUNT:1 UUID:00000000-0000-0000-0000-000000000000
Recv: ok
Send: M21
Recv: echo:SD card ok
Recv: ok
Send: M20
Recv: Begin file list
Recv: Error:MAXTEMP triggered, system stopped! Heater_ID: 0
Recv: Error:MAXTEMP triggered, system stopped! Heater_ID: bed
Changing monitoring state from "Operational" to "Error: MAXTEMP triggered, system stopped! Heater_ID: 0 - MAXTEMP triggered, system stopped! Heater_ID: bed"
Changing monitoring state from "Error: MAXTEMP triggered, system stopped! Heater_ID: 0 - MAXTEMP triggered, system stopped! Heater_ID: bed" to "Offline (Error: MAXTEMP triggered, system stopped! Heater_ID: 0 - MAXTEMP triggered, system stopped! Heater_ID: bed)"
Connection closed, closing down monitor

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ...)

OctoPrint: 1.3.11, Creality 10 5s. Don't know the printer firmware because Creality gave me a new version

Hi @Frank_Haggar!

Recv: Error:MAXTEMP triggered, system stopped! Heater_ID: 0
Recv: Error:MAXTEMP triggered, system stopped! Heater_ID: bed

This tells, that the bed temperature sensor has a problem.
What does the display of the printer show for the bed? Something like the temperature like the hotend (room temperature), or is it exactly 0°C ?
If it is 0°C, then the temperature sensor of the bed has an issue: either the lines are broken, a plug got lose on the printer board or the thermistor is broken.

1 Like

The bed temperature reads like my Ender 3 does. Shows the temperature. Creality had me unplug one of the two (nozzle or bed) and check the display to make sure they were correctly plugged in. They were indeed correct. I reseated the cable and it worked for a BREIF period before doing this again. Creality does not think it's an issue because the USB works and they do not have Octoprint.
One more thing.... It does this INSTANTLY as it connects. Without preheating anything or doing anything.

Any ideas?

Then I almost assume this is a firmware issue. Even when Creality say this is a new firmware. Creality is known for doing weird things with Marlin: Temperature info not parsed correctly