Basic Information:
Ender 3 V2/ Sptite extruder
P HP ProDesk 600 G4
Intel® Core™ i5-8500T × 6
klippy.log (2.0 MB)
moonraker.log (15.9 KB)
I start the print and the printer shuts down halfway through the print.
Stats 10040.0: gcodein=0 mcu: mcu_awake=0.014 mcu_task_avg=0.000032 mcu_task_stddev=0.000029 bytes_write=2271326 bytes_read=399575 bytes_retransmit=9 bytes_invalid=0 send_seq=39627 receive_seq=39627 retransmit_seq=2 srtt=0.003 rttvar=0.000 rto=0.025 ready_bytes=8 upcoming_bytes=0 freq=72002602 sd_pos=661238 mcu_temp: temp=101.7 heater_bed: target=60 temp=60.6 pwm=0.000 sysload=0.23 cputime=64.030 memavail=13630996 print_time=1241.420 buffer_time=2.274 print_stall=0 extruder: target=210 temp=209.5 pwm=0.437
Stats 10042.0: gcodein=0 mcu: mcu_awake=0.014 mcu_task_avg=0.000032 mcu_task_stddev=0.000029 bytes_write=2274113 bytes_read=400091 bytes_retransmit=9 bytes_invalid=18 send_seq=39673 receive_seq=39673 retransmit_seq=2 srtt=0.003 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=671 freq=72002603 sd_pos=661750 mcu_temp: temp=101.5 heater_bed: target=60 temp=60.4 pwm=0.000 sysload=0.23 cputime=64.044 memavail=13661932 print_time=1242.423 buffer_time=1.193 print_stall=0 extruder: target=210 temp=209.2 pwm=0.445
MCU 'mcu' is_shutdown: Missed scheduling of next digital out event
clocksync state: mcu_freq=72000000 last_clock=89731601234 clock_est=(10012.130 87214861810 72002603.622) min_half_rtt=0.000376 min_rtt_time=9376.043 time_avg=10012.130(843.522) clock_avg=87214861810.631(60735757050.785) pred_variance=3602328.734
Dumping serial stats: bytes_write=2274481 bytes_read=400264 bytes_retransmit=9 bytes_invalid=18 send_seq=39679 receive_seq=39676 retransmit_seq=2 srtt=0.004 rttvar=0.003 rto=0.025 ready_bytes=4481 upcoming_bytes=8
...
Sent 87 10040.588528 10040.583924 61: seq: 1f, queue_digital_out oid=17 clock=3385550080 on_ticks=3206817, queue_step oid=9 interval=111505 count=3 add=-8203, queue_step oid=2 interval=56487 count=8 add=-895, queue_step oid=5 interval=274216 count=2 add=24939, queue_step oid=9 interval=87839 count=8 add=-3623, queue_step oid=2 interval=51303 count=8 add=1465, set_next_step_dir oid=5 dir=0
...
Receive: 97 10042.040056 10040.686491 15: seq: 19, analog_in_state oid=16 next_clock=3851722496 value=31175
Receive: 98 10042.067033 10042.054261 11: seq: 1a, clock clock=3832255314
Receive: 99 10042.067196 10042.054261 7: seq: 1a, is_shutdown static_string_id=Missed scheduling of next digital out event
3832255314 - 3385550080 = 446705234
446705234 / 72000000 = 6.2
Hmm…
From the Stats, there is a 2-second pause, and almost zero CPU usage time.
Something is blocking Klipper from doing its own job.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.