MCU 'mcu' shutdown: Timer too close fault

[RodimusPrime98]

I updated Klipper, Moonraker, Fluidd, and my Raspberry Pi this last week and upon reboot I am receiving "MCU 'mcu' shutdown: Timer too close" right after I try any movement like a "Home all". I have rebuilt the MCU firmware and the issue persists. Any suggestions where to troubleshoot? Below is taken from the Klippy.log:

 

MCU 'mcu' shutdown: Timer too close
clocksync state: mcu_freq=400000000 last_clock=58355888839 clock_est=(108.649 47156152072 400014570.171) min_half_rtt=0.000059 min_rtt_time=72.653 time_avg=108.649(715.843) clock_avg=47156152072.574(286347568237.977) pred_variance=2343362254.840
Dumping serial stats: bytes_write=7491 bytes_read=28304 bytes_retransmit=9 bytes_invalid=0 send_seq=549 receive_seq=549 retransmit_seq=2 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0
 

[Crashdown]

Its really hard to know I'm afraid. This is a list of potential things to look at. https://www.lslabs.co.uk/docs/mcu-mcu-shutdown-timer-too-close/

How did the problem first present? Did it happen immediately after the software on the Pi was updated? or did you update any board firmwares using the 'make menuconfig'?

If it was just immediately after the software update my first thing to try would be a rollback to a previous build of klipper using Kiauh and seeing if that does anything. I have had times where updates and firmware flashes did not go smoothly and just needed to be rolled back and done again.

[bankian]

Strange as it may sound, assuming you're using CanBus, make sure that the plug is connected firmly into the print head assembly. I had random stopping like this and I (finally!!!!!!) discovered that on certain prints, the Canbus cable could get caught behind the gantry wiring chain, when it would tug enough on the plug to cause it to come loose. Once the plug was loosened any further attempt at movement would trip it. I've now rearranged things to stop the thing getting caught and also put a cable clip around the plug to keep it in as the stock bracket doesn't seem to work that well.

[Jaxt]

I have had a similar issue with CanBus. I used an external controller (U2C) connected to my Pi and needed to update the firmware on it. Take a look here for fixed firmware.

https://canbus.esoterical.online/can_adapter/BigTreeTech U2C v2.1/README.html

Good youtube video. 

 

[RodimusPrime98]

I just updated Klipper to today's latest version and the problem seems to have gone away. I will report back if it comes back. Also, I am not running canbus.

[gueee]

This is a known problem with commits 294 to 296 and fixed with commit 297, so it shouldn't come back!