Printer gets Killed

Get Help
1

What is the problem?
printer get killed during the printing is best case scenario mostly during the heating part

What did you already try to solve it?
I read about this problem and someone was saying it's firmware problem but I need a confirmation from you bc my knowledge in this field is almost zero so I didn't want to jump to conclusions

octoprint log


serial log serial log wasn't enable when I enable it, it got way worse I couldn't have any control over the printer all other logs were saved before I do this bc it was the last one in the list https://gist.github.com/AbdelrahmanSherifHadeya/572226e815351d7ef9bc367a2a575817
dmesg
https://gist.github.com/AbdelrahmanSherifHadeya/0f6f308bbed52b8ad6f49472506c5d2f
cat /var/log/syslog
https://gist.github.com/AbdelrahmanSherifHadeya/3f84a7644f4da52b9fa24ea4b6106721
cat /var/log/messages
https://gist.github.com/AbdelrahmanSherifHadeya/ed3df268f234a9af7fffffc87169b82b

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible)
OctoPi: 0.17
OctoPrint: 1.3
Printer: Creality CR-10S4

2

this happens every time it get connected with octopi, whenever it was taken off and restarted it function normal

3

Your serial.log shows your printer never returning from an attempt of a directory listing of the printer's SD card. So first of all eject that card, it might be faulty and causing the firmware to hiccup. Then try to connect, reproduce and provide a clean serial.log of that.

2 Likes
4

SD card ejected, same problem all logs have been updated
octoprint log


serial log

dmesg

cat /var/log/syslog

cat /var/log/messages

5 
Recv: Error:Heating failed, system stopped! Heater_ID: 0

This is your firmware telling you that your hotend couldn't hold heat properly, which can be caused either by a mechanical issue (e.g. the thermistor and heating element are not seated properly anymore) or a firmware bug. In this specific case here I see that the problem happened after a print finished and the hotend was intentionally shut down. It strikes me as a bit weird that this would trigger this error on the firmware side, so I'm going with firmware bug here.

2 Likes
6

well it's my school printer which has been sat by inexperienced people, so how can I check to be certain.
if it was mine I'd install firmware but it's not, so I don't want to take the risk, since I'm inexperienced too

7

is this what I suppose to do?

8

I tell you what I see in your serial.log

2020-01-23 22:29:08,998 - Send: N988 M106 S0*110
2020-01-23 22:29:09,011 - Recv: ok
2020-01-23 22:29:09,014 - Send: N989 M104 S0*109
2020-01-23 22:29:09,026 - Recv: ok
2020-01-23 22:29:09,029 - Send: N990 M140 S0*101
2020-01-23 22:29:09,042 - Recv: ok
2020-01-23 22:29:09,045 - Send: N991 M84 X Y E*122
2020-01-23 22:29:19,011 - Recv: ok
2020-01-23 22:29:19,019 - Send: N992 M105*37
2020-01-23 22:29:19,028 - Recv: ok T:210.7 /0.0 B:49.7 /0.0 T0:210.7 /0.0 @:0 B@:0
2020-01-23 22:29:19,030 - Send: N993 M82*26
2020-01-23 22:29:19,043 - Recv: ok
2020-01-23 22:29:19,045 - Send: N994 M104 S0*97
2020-01-23 22:29:19,059 - Recv: ok
2020-01-23 22:29:19,062 - Changing monitoring state from "Printing" to "Finishing"
2020-01-23 22:29:19,099 - Send: N995 M400*34
2020-01-23 22:29:19,115 - Recv: ok
2020-01-23 22:29:19,128 - Changing monitoring state from "Finishing" to "Operational"
2020-01-23 22:29:20,174 - Send: M105
2020-01-23 22:29:20,194 - Recv: ok T:208.8 /0.0 B:49.7 /0.0 T0:208.8 /0.0 @:0 B@:0
2020-01-23 22:29:20,896 - Send: M104 S217
2020-01-23 22:29:20,914 - Recv: ok
2020-01-23 22:29:24,405 - Send: M140 S50
2020-01-23 22:29:24,422 - Recv: ok
2020-01-23 22:29:25,175 - Send: M105
2020-01-23 22:29:25,196 - Recv: ok T:201.2 /217.0 B:49.5 /50.0 T0:201.2 /217.0 @:127 B@:0
2020-01-23 22:29:27,176 - Send: M105
2020-01-23 22:29:27,192 - Recv: ok T:200.0 /217.0 B:49.4 /50.0 T0:200.0 /217.0 @:127 B@:0
2020-01-23 22:29:29,177 - Send: M105
2020-01-23 22:29:29,190 - Recv: ok T:199.5 /217.0 B:49.3 /50.0 T0:199.5 /217.0 @:127 B@:127
2020-01-23 22:29:31,181 - Send: M105
2020-01-23 22:29:31,219 - Recv: ok T:199.9 /217.0 B:49.3 /50.0 T0:199.9 /217.0 @:127 B@:127
2020-01-23 22:29:33,182 - Send: M105
2020-01-23 22:29:33,202 - Recv: ok T:200.6 /217.0 B:49.4 /50.0 T0:200.6 /217.0 @:127 B@:127
2020-01-23 22:29:35,183 - Send: M105
2020-01-23 22:29:35,199 - Recv: ok T:201.5 /217.0 B:49.5 /50.0 T0:201.5 /217.0 @:127 B@:127
2020-01-23 22:29:36,989 - Recv: Error:Heating failed, system stopped! Heater_ID: 0
2020-01-23 22:29:37,180 - Recv: Error:Heating failed, system stopped! Heater_ID: 0
2020-01-23 22:29:37,183 - Changing monitoring state from "Operational" to "Error: Heating failed, system stopped! Heater_ID: 0 - Heating failed, system stopped! Heater_ID: 0"

M106 S0 -> fanspeed to 0
M104 S0 -> hotend temperature to 0
M140 S0 -> bed temperature to 0
M84 X Y E -> disable all steppers

So there is everything in your gcode you would expect as an end gcode.
But then the print suddenly gets continued, the temperatures getting raised again and everything.
Now your hotend can't reach the target temperature fast enough and drops under 200°C. That's when the firmwares thermal runaway protection steps in and turns everything down because it thinks something is going wrong.

So the question is how did you generate this gcode? It looks like you just merged two files or something.

1 Like
9

it was prepared with Ultimaker cura software
printing temperature 215
build plate temperature 50
fan speed 100
after the print is finished all of these reset to zero, so in order to print the second print I modify nozzle to 215 and bed to 50 before it reset to zero and this is when the kill most of the time happen, If I wait until they reach 0 I will lose time + before the raspberry and octopi I wasn't waiting I was doing exactly the same thing

10

I see.
Well I would try M109 instead of M104 or remove the cooling down part from the end gcode when you know you're going to print several pieces.

1 Like
11

I read this https://marlinfw.org/docs/gcode/M109.html but didn't understand actually,
how can remove the cooling down from the gcode

12

M104 is just changing the target temperature - M109 is changing it and waiting until it's reached.

The end gcode is in your printers settings in cura

grafik
grafik838×789 101 KB

1 Like
13

these are the settings I found in my ende G-Code
G91 ;Relative positioning

G1 E-2 F2700 ;Retract a bit

G1 E-2 Z0.2 F2400 ;Retract and raise Z

G1 X5 Y5 F3000 ;Wipe out

G1 Z10 ;Raise Z more

G90 ;Absolute positionning

Start G-Code
M201 X500.00 Y500.00 Z100.00 E5000.00 ;Setup machine max acceleration

M203 X500.00 Y500.00 Z10.00 E50.00 ;Setup machine max feedrate

M204 P500.00 R1000.00 T500.00 ;Setup Print/Retract/Travel acceleration

M205 X8.00 Y8.00 Z0.40 E5.00 ;Setup Jerk

M220 S100 ;Reset Feedrate

M221 S100 ;Reset Flowrate

G28 ;Home

G92 E0 ;Reset Extruder

G1 Z2.0 F3000 ;Move Z Axis up

G1 X10.1 Y20 Z0.28 F5000.0 ;Move to start position

G1 X10.1 Y200.0 Z0.28 F1500.0 E15 ;Draw the first line

G1 X10.4 Y200.0 Z0.28 F5000.0 ;Move to side a little

G1 X10.4 Y20 Z0.28 F1500.0 E30 ;Draw the second line

G92 E0 ;Reset Extruder

G1 Z2.0 F3000 ;Move Z Axis up

14

Scroll down the end gcode :wink:

1 Like
15

:sweat_smile: oppsie found it
G91 ;Relative positioning
G1 E-2 F2700 ;Retract a bit
G1 E-2 Z0.2 F2400 ;Retract and raise Z
G1 X5 Y5 F3000 ;Wipe out
G1 Z10 ;Raise Z more
G90 ;Absolute positionning

G1 X0 Y{machine_depth} ;Present print
M106 S0 ;Turn-off fan
M104 S0 ;Turn-off hotend I should change this to M109 S0 instated right
M140 S0 ;Turn-off bed

M84 X Y E ;Disable all steppers but Z

16

if you want to keep the printer in a ready to print state remove everything after G1 X0 Y{machine_depth} ;Present print
Then the hotend and bed will stay at their temperature and everything is ready for the next print.

The M109 thing was the other option if you don't want to remove the end gcode. In that case you would use it to warm the hotend up at the beginning of the next print.

Keep in mind that if you remove that part your heaters will always stay on and you have to turn them off by hand.

17

You need to get the proper power supply for the Pi as well as what the others have said.
I see multiple instances of the low voltage error from the Pi. That will wreak havoc with the comms etc...

18

the pi is already powered with 5V 2.8A I don't know why it give the voltage problem doesn't happen in regular basis

19

this might help with the undervoltage problems

20

voltage problem was solved but the heat problem I'm still facing the same thing even before I print any part I was just heating the printer up
Error:Heating failed, system stopped! Heater_ID: 0
for dmesg logs there was something strange I couldn't understand it
all logs updated
octoprint log


serial log

dmesg

cat /var/log/syslog

cat /var/log/messages