I was instructed to move this here, from Clock Desync? - Crash Midway Through Print · Issue #5526 · Klipper3d/klipper · GitHub
I have been having prints freeze mid print, after using Klipper for 6 months. I have not introduced new hardware, and I have removed all variables which might be causing the problem. The only thing that I have changed is I changed ZV input shaper to MZV, but if I flip things back the issue still happens.
I am seeing this in logs:
Resetting prediction variance 48331.481: freq=49996692 diff=2502311 stddev=3050.493
Stats 48331.7: gcodein=0 mcu: mcu_awake=0.011 mcu_task_avg=0.000012 mcu_task_stddev=0.000010 bytes_write=41489249 bytes_read=12102994 bytes_retransmit=9 bytes_invalid=0 send_seq=866994 receive_seq=866994 retransmit_seq=2 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=0 stalled_bytes=0 freq=167994493 rpi: mcu_awake=0.000 mcu_task_avg=0.000009 mcu_task_stddev=0.000014 bytes_write=158298 bytes_read=489037 bytes_retransmit=0 bytes_invalid=0 send_seq=26358 receive_seq=26358 retransmit_seq=0 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 stalled_bytes=0 freq=50000360 adj=49998355 sd_pos=2435086 heater_bed: target=70 temp=70.0 pwm=0.363 raspberry_pi: temp=39.7 mcu_temp: temp=31.6 sysload=0.23 cputime=2094.753 memavail=595576 print_time=25864.784 buffer_time=2.402 print_stall=0 extruder: target=220 temp=220.1 pwm=0.506
Resetting prediction variance 48332.470: freq=50000360 diff=2400876 stddev=50000.000
Stats 48332.7: gcodein=0 mcu: mcu_awake=0.007 mcu_task_avg=0.000010 mcu_task_stddev=0.000009 bytes_write=41490253 bytes_read=12103488 bytes_retransmit=9 bytes_invalid=0 send_seq=867020 receive_seq=867020 retransmit_seq=2 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=0 stalled_bytes=0 freq=167994487 rpi: mcu_awake=0.000 mcu_task_avg=0.000009 mcu_task_stddev=0.000014 bytes_write=158304 bytes_read=489053 bytes_retransmit=0 bytes_invalid=0 send_seq=26359 receive_seq=26359 retransmit_seq=0 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 stalled_bytes=0 freq=50003770 adj=50040535 sd_pos=2435306 heater_bed: target=70 temp=70.0 pwm=0.393 raspberry_pi: temp=39.7 mcu_temp: temp=31.5 sysload=0.30 cputime=2094.846 memavail=595864 print_time=25865.557 buffer_time=2.175 print_stall=0 extruder: target=220 temp=220.0 pwm=0.533
Resetting prediction variance 48333.454: freq=50003770 diff=2296227 stddev=50000.000
And:
mcu 'mcu': got {'#receive_time': 819.066948802, u'next_clock': 744358144, u'oid': 24, u'value': 7539, '#name': u'analog_in_state', '#sent_time': 819.01618052}
mcu 'mcu': got {'#receive_time': 819.117116302, u'next_clock': 752758144, u'oid': 29, u'value': 31413, '#name': u'analog_in_state', '#sent_time': 819.01618052}
Klipper and Moonraker logs, my configurations, project files:
Klipper Error Log Config and Print.zip (376.2 KB)
I am not getting undervoltage warnings, and the only USB I have plugged in are: 1. the USB cable to the MCU, which is a nice thick shielded one provided by BTT with the SKR 2, and my Endoscope camera, which has been plugged in forever.
One additional weird point is that once I fully rebooted the Pi, and I issued a firmware restart- upon connecting it thinks the print is still in progress, it did not enter a status failed state.