MINTEMP Triggered. HEATER_ID: 0

Get Help
1

Trying out Octoprint for the first time on Raspberry Pi 4.2 for CR-10S. Repeatedly getting the message "Your printer's firmware reported an error. Due to that OctoPrint will disconnect. Reported error: MINTEMP triggered, system stopped! Heater_ID: 0 - Printer halted. kill() called!". Can I get some advice on what am I doing wrong?

Logs pasted below:

Changing monitoring state from "Offline" to "Opening serial connection"
Connecting to port /dev/ttyUSB0, baudrate 115200
Changing monitoring state from "Opening serial connection" to "Connecting"
Connected to: Serial<id=0xa83703d0, open=True>(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Send: N0 M110 N0*125
Recv: start
Send: N0 M110 N0*125
Recv: echo:Marlin 1.1.6
Recv: 
Recv: echo: Last Updated: 2019-07-26 | Author: CR-10S
Recv: echo:Compiled: Aug  3 2019
Recv: echo: Free Memory: 1642  PlannerBufferBytes: 1232
Recv: echo:V41 stored settings retrieved (498 bytes; crc 3508)
Recv: echo:  G21    ; Units in mm
Recv: echo:  M149 C ; Units in Celsius
Recv: 
Recv: echo:Filament settings: Disabled
Recv: echo:  M200 D1.75
Recv: echo:  M200 D0
Recv: echo:Steps per unit:
Recv: echo:  M92 X80.00 Y80.00 Z400.00 E93.00
Recv: echo:Maximum feedrates (units/s):
Recv: echo:  M203 X500.00 Y500.00 Z5.00 E25.00
Recv: echo:Maximum Acceleration (units/s2):
Recv: echo:  M201 X500 Y500 Z100 E1000
Recv: echo:Acceleration (units/s2): P<print_accel> R<retract_accel> T<travel_accel>
Recv: echo:  M204 P500.00 R500.00 T1000.00
Recv: echo:Advanced: S<min_feedrate> T<min_travel_feedrate> B<min_segment_time_ms> X<max_xy_jerk> Z<max_z_jerk> E<max_e_jerk>
Recv: echo:  M205 S0.00 T0.00 B20000 X10.00 Y10.00 Z0.40 E5.00
Recv: echo:Home offset:
Recv: echo:  M206 X0.00 Y0.00 Z0.00
Recv: echo:Material heatup parameters:
Recv: echo:  M145 S0 H185 B45 F255
Recv:   M145 S1 H240 B70 F255
Recv: echo:PID settings:
Recv: echo:  M301 P22.57 I1.72 D73.96
Recv: echo:TF init fail
Recv: echo:TF init fail
Recv: ok
Send: N0 M110 N0*125
Changing monitoring state from "Connecting" to "Operational"
Recv: ok
Send: N0 M110 N0*125
Recv: ok
Send: N1 M115*39
Recv: FIRMWARE_NAME:Marlin Creality 3D SOURCE_CODE_URL:https://github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:CR-10S EXTRUDER_COUNT:1 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff
Recv: Cap:EEPROM:1
Recv: Cap:AUTOREPORT_TEMP:1
Recv: Cap:PROGRESS:0
Recv: Cap:PRINT_JOB:1
Recv: Cap:AUTOLEVEL:0
Recv: Cap:Z_PROBE:0
Recv: Cap:LEVELING_DATA:0
Recv: Cap:SOFTWARE_POWER:0
Recv: Cap:TOGGLE_LIGHTS:0
Recv: Cap:CASE_LIGHT_BRIGHTNESS:0
Recv: Cap:EMERGENCY_PARSER:0
Recv: ok
Send: M21
Recv: echo:TF init fail
Recv: echo:TF init fail
Recv: ok
Send: M155 S2
Recv: ok
Recv:  T:-15.00 /0.00 B:21.25 /0.00 @:0 B@:0
Recv:  T:-15.00 /0.00 B:21.25 /0.00 @:0 B@:0
2

Your thermistor is showing a temperature of -15 degrees, check that it is plugged in. This is the firmware's safety features here, not OctoPrint.

1 Like
3

Thanks for the response. I am new to all this so maybe a dumb question - Is this thermistor for the bed heater or the nozzle?

4

Thermistor - bed looks right as it is reporting 21.25 degrees.

1 Like
5

Is there an easy way to identify the hardware and associated wiring? I have traced the white wires going from the hotend and reconnected the cables going to it.

6

Thanks for suggestions. I was able to get it sorted out. The Octoprint is working now.

7

Great! Would you please share your solution, so it can be helpful for others too.