Timer too close with MCU shutdown on almist every print

General Discussion
1

Basic Information:

Kingroon KP3S Pro:
rp2040+stm103f / a 4 core arm64 SOC with linux:
^^^
klippy.log

Describe your issue:

Only 2 models out of more than 40 were successfully printed. Most get stuck on the first/second layer, almost in the same place. Using both OrcaSlicer or Cura.
klippy.log (8.0 MB)

2

Hallo @0486 !

TCC usually is a hardware issue: Timer too close

3 
....
Stats 28572.1:
  gcodein=0
  mcu: mcu_awake=0.023 mcu_task_avg=0.000064 mcu_task_stddev=0.000126 bytes_write=458941 bytes_read=1732389 bytes_retransmit=0 bytes_invalid=0 send_seq=23881 receive_seq=23881 retransmit_seq=0 srtt=0.001 rttvar=0.001 rto=0.025 ready_bytes=39 upcoming_bytes=0 freq=72000909
  MKS_THR: mcu_awake=0.002 mcu_task_avg=0.000006 mcu_task_stddev=0.000008 bytes_write=129706 bytes_read=977992 bytes_retransmit=1894 bytes_invalid=0 send_seq=15859 receive_seq=15859 retransmit_seq=15852 srtt=0.001 rttvar=0.001 rto=0.025 ready_bytes=51 upcoming_bytes=0 freq=12000457 adj=12000309
  heater_bed: target=60 temp=60.0 pwm=0.291 mcu_temp: temp=35.3 Pi: temp=47.7 sd_pos=104269 sysload=1.73 cputime=615.628 memavail=639976 print_time=13917.416 buffer_time=2.154 print_stall=0 extruder: target=230 temp=229.3 pwm=0.321
Stats 28573.1: 
  gcodein=0  
  mcu: mcu_awake=0.018 mcu_task_avg=0.000054 mcu_task_stddev=0.000113 bytes_write=460479 bytes_read=1732793 bytes_retransmit=0 bytes_invalid=0 send_seq=23914 receive_seq=23914 retransmit_seq=0 srtt=0.001 rttvar=0.001 rto=0.025 ready_bytes=7 upcoming_bytes=0 freq=72000909
  MKS_THR: mcu_awake=0.002 mcu_task_avg=0.000006 mcu_task_stddev=0.000008 bytes_write=130086 bytes_read=978151 bytes_retransmit=2254 bytes_invalid=0 send_seq=15867 receive_seq=15867 retransmit_seq=15862 srtt=0.001 rttvar=0.001 rto=0.025 ready_bytes=50 upcoming_bytes=0 freq=12000457 adj=12000242
  heater_bed: target=60 temp=60.0 pwm=0.351 mcu_temp: temp=35.4 Pi: temp=47.7 sd_pos=104377 sysload=1.67 cputime=615.717 memavail=641480 print_time=13918.472 buffer_time=2.208 print_stall=0 extruder: target=230 temp=229.3 pwm=0.321
....
MCU 'MKS_THR' shutdown: Timer too close
clocksync state: mcu_freq=12000000 last_clock=167073537313 clock_est=(28542.388 166711191907 12000457.160) min_half_rtt=0.000111 min_rtt_time=27704.997 time_avg=28542.388(861.950) clock_avg=166711191907.554(10343790669.503) pred_variance=11892339.199 clock_adj=(-6.749 12000251.622)
Dumping serial stats: bytes_write=130319 bytes_read=978206 bytes_retransmit=2254 bytes_invalid=0 send_seq=15871 receive_seq=15871 retransmit_seq=15862 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0
...
Sent 99 28573.308702 28573.308702 52: seq: 1e, queue_digital_out oid=9 clock=3871743581 on_ticks=323847, queue_step oid=5 interval=7631 count=28 add=-22, queue_step oid=5 interval=7079 count=33 add=-3, queue_step oid=5 interval=7037 count=62 add=3, queue_step oid=5 interval=7184 count=384 add=0, queue_step oid=5 interval=7197 count=30 add=8, queue_step oid=5 interval=7481 count=24 add=28
...
Receive: 99 28573.309366 28573.308702 12: seq: 1f, shutdown clock=3873492881 static_string_id=Timer too close

(3873492881 - 3871743581) / 12000000 = 0.145s

Hmmm…
Seems like it is late by 145ms, which is a lot.

Unfortunately, I can’t spot anything to guide where to look at.
There are some bytes_retransmit, but they do not seem critical.

4

klipper is running at ARM64 printer board with two MCUs on it. I can not just pick up and replace the board. Is there any way to tune config fix the issue ?

5

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.