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.lo…

Hallo @0486 ! [image] 0486: Using both OrcaSlicer or Cura. TCC usually is a hardware issue: Timer too close

.... 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=7200…

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 ?

Timer too close with MCU shutdown on almist every print

General Discussion

EddyMI3D May 26, 2025, 6:25am 2

Hallo @0486 !

TCC usually is a hardware issue: Timer too close

Topic		Replies	Views
Getting MCU 'mcu' shutdown: Timer too close starting print General Discussion	2	118	September 15, 2024
Mcu shutdown: Timer too close General Discussion	8	763	July 29, 2023
Another MCU 'mcu' shutdown: Timer too close General Discussion	4	554	January 11, 2024
"MCU 'mcu' shutdown: Timer too close" - unknown cause General Discussion	1	1011	July 9, 2023
"MCU 'mcu' shutdown: Timer too close.... Random General Discussion	5	1231	March 18, 2024

Timer too close with MCU shutdown on almist every print

Related topics