klippy.log (134.5 KB)
moonraker.log (31.0 KB)
I have an Ender6 with klipper direct extruder, lately it throws min_extruder_temp(midway or almost end print).
Only thing i can see in the logs is that the temp is slowy declining to below 170 and then stops. becuase it is below minimum temp. i now this is not the reasen of the slowy droping of the temp. a few lines higher i can see a high numer in “ready_bytes=1235” a few lines thurther de extruder temp is set to zero, some how. Any has any idea what the problem could be
1 Like
Hello @Rene !
Did you have a look on the gcode file?
The attached logs ain’t a big help, because the issue (min_extruder_temp) does not appear in them.
I also noticed the changes in this section:
[verify_heater extruder]
As far as I understand, due to the values you use, the thermal runaway protection is almost - if not definitely - out of function. I mean a max_error of 20000°C 
For more thermal stability, you should run a PID (auto-)tune.
[verify_heater extruder], because i tried this hope this would help!, new log uploaden witch
klippy (1).log (634.0 KB)
is a bit longer, pid tune i also did. What am i looking for in de gcode file?
You may upload it here as a zipped file
Milwaukee M18 Battery Holder.zip (560.2 KB)
Yesterday it was the last line of the print, mostly it is on the 80 % of the print it stops.
We would need the sliced gcode file and not the source stl file.
Your log clearly shows:
Your extruder is receiving a new target temperature (from 195 to 0). When the extruder has cooled down enough, the safety measures of Klipper kick in and prevent further extrusion.
There is no way that Klipper decides this on its own. Most likely you have some screwed slicer settings that change the temperature at some point.
Sorry, but it’s still the same file as above.
Not only the extruder is turned foo, the bed too.
But there is no gcode command in the file to turn them off.
What is the host softwar you run Klipper with?
i use a raspberry pi 3/mainsail/moonraker, on an ender 6, i use super slicer.
I see. I’m not an expert with Mainsail and if it is able to run plugins.
But maybe something there is going wrong.
Desktop.zip (2.0 MB)
Wel again a failed print, i switch to Fluid so it looks like not a software problem. Anyway it could be the mainboard v4.2.7?? any way to check this, or a faulty mini usb reader. I switch out the cable so !
b'Got EOF when reading from device'
Stats 24165.5: gcodein=0 mcu: mcu_awake=0.023 mcu_task_avg=0.000038 mcu_task_stddev=0.000033 bytes_write=49363722 bytes_read=8109177 bytes_retransmit=366 bytes_invalid=0 send_seq=845341 receive_seq=845338 retransmit_seq=845341 srtt=0.002 rttvar=0.000 rto=0.100 ready_bytes=413 stalled_bytes=663 freq=72000781 sd_pos=27460792 mcu_temp: temp=38.5 raspberry_pi: temp=47.2 heater_bed: target=60 temp=60.0 pwm=0.066 sysload=0.56 cputime=529.087 memavail=1602200 print_time=24175.629 buffer_time=2.057 print_stall=0 extruder: target=200 temp=200.0 pwm=0.378
Stats 24166.5: gcodein=0 mcu: mcu_awake=0.023 mcu_task_avg=0.000038 mcu_task_stddev=0.000033 bytes_write=49363722 bytes_read=8109177 bytes_retransmit=366 bytes_invalid=0 send_seq=845341 receive_seq=845338 retransmit_seq=845341 srtt=0.002 rttvar=0.000 rto=0.100 ready_bytes=413 stalled_bytes=3482 freq=72000781 sd_pos=27462157 mcu_temp: temp=38.5 raspberry_pi: temp=45.8 heater_bed: target=60 temp=60.0 pwm=0.066 sysload=0.56 cputime=529.105 memavail=1604604 print_time=24176.680 buffer_time=2.107 print_stall=0 extruder: target=200 temp=200.0 pwm=0.378
Stats 24167.5: gcodein=0 mcu: mcu_awake=0.023 mcu_task_avg=0.000038 mcu_task_stddev=0.000033 bytes_write=49363722 bytes_read=8109177 bytes_retransmit=366 bytes_invalid=0 send_seq=845341 receive_seq=845338 retransmit_seq=845341 srtt=0.002 rttvar=0.000 rto=0.100 ready_bytes=413 stalled_bytes=5502 freq=72000781 sd_pos=27464302 mcu_temp: temp=38.5 raspberry_pi: temp=46.7 heater_bed: target=60 temp=60.0 pwm=0.066 sysload=0.56 cputime=529.122 memavail=1607624 print_time=24177.762 buffer_time=2.188 print_stall=0 extruder: target=200 temp=200.0 pwm=0.378
Stats 24168.5: gcodein=0 mcu: mcu_awake=0.023 mcu_task_avg=0.000038 mcu_task_stddev=0.000033 bytes_write=49363722 bytes_read=8109177 bytes_retransmit=366 bytes_invalid=0 send_seq=845341 receive_seq=845338 retransmit_seq=845341 srtt=0.002 rttvar=0.000 rto=0.100 ready_bytes=413 stalled_bytes=7208 freq=72000781 sd_pos=27466447 mcu_temp: temp=38.5 raspberry_pi: temp=46.7 heater_bed: target=60 temp=60.0 pwm=0.066 sysload=0.56 cputime=529.141 memavail=1602196 print_time=24178.841 buffer_time=2.266 print_stall=0 extruder: target=200 temp=200.0 pwm=0.378
Stats 24169.5: gcodein=0 mcu: mcu_awake=0.023 mcu_task_avg=0.000038 mcu_task_stddev=0.000033 bytes_write=49363722 bytes_read=8109177 bytes_retransmit=366 bytes_invalid=0 send_seq=845341 receive_seq=845338 retransmit_seq=845341 srtt=0.002 rttvar=0.000 rto=0.100 ready_bytes=413 stalled_bytes=9199 freq=72000781 sd_pos=27468728 mcu_temp: temp=38.5 raspberry_pi: temp=47.2 heater_bed: target=60 temp=60.0 pwm=0.066 sysload=0.60 cputime=529.160 memavail=1602932 print_time=24179.708 buffer_time=2.132 print_stall=0 extruder: target=200 temp=200.0 pwm=0.378
Timeout with MCU 'mcu' (eventtime=24170.526852)
Transition to shutdown state: Lost communication with MCU 'mcu'
Dumping gcode input 0 blocks
Dumping 20 requests for client 3040844168
This error is different from the one posted above.
Got EOF when reading from device happens when the Linux systems on your RPi detects an issue with your USB connection. Short while later Klipper shuts down as it has lost the connections to your MCU.
So i assume, u think it is also the usb mini port? I already changed the usb cable.
Has this ever been definitively resolved? I am having the same problem, at random times, completely out of the blue. It might be 30% through a print, or it might be 96%, but it is definitely random. I can’t seem to find a cause, or a solution.
Sounds good, new thread created.