"Timer too close" after update | Mainsail | Page 1

limber haven Apr 10, 2023, 8:29 PM

#

"MCU 'mcu' shutdown: Timer too close
This often indicates the host computer is overloaded. Check
for other processes consuming excessive CPU time, high swap
usage, disk errors, overheating, unstable voltage, or
similar system problems on the host computer.
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown"

After updating today I get this error when trying to home my printer. As soon as the Z axis has moved a bit down that message comes. Also it sounds weird, when the Z goes down and it is slower than before... Like there is something holding the motors back.

Have also tried a clean install with no result.

klippy.log right here; https://pastebin.com/B7i16z9E

Pastebin

Klippy.log - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

tight dirge Apr 11, 2023, 5:05 AM

#

Do you use a multi mcu setup? Especially where one mcu contains the z motors and a other contains the endstop/probe that works as endstop for Z?

limber haven Apr 11, 2023, 5:44 AM

#

Only one MCU and the Raspberry Pi.

#

As of your question in the other thread: “I guess you mean an Klipper update with moonraker and then the hard part begins as you do not know from what version you where coming.”

It was Klipper and moonraker if I’m not mistaken. Everything was on the latest Update as I always Update When there is an update. Everything worked fine half an hour earlier where I actually printed some Stuff. Then turned off the printer and half an hour later turned it on again where those updates where present and I could not do anything before updating and reflashing MCU and RPI. Then I did that and all turned on. But When I Home my printer the Z axis lowers 5mm and then shuts Down with the before mentioned message.

tight dirge Apr 11, 2023, 6:17 AM

#

So you update regular, do you remember when about last time, 1 week 1 day … That would be helpful to check the last Klipper checking to see if there is some suspicious checkin that it would be worth to look in.

#

I quickly checked there a updates from the last 4 days and then 2 weeks ago. So it would be helpful if you updated within the last 2 weeks. And also it would be good to know if the printer was successful running after the last Klipper update (the update before this one)

#

Have you generated a new fw for your mcu? And what mcu do you use?

#

from the checkins that https://github.com/Klipper3d/klipper/commit/22ee889f41249a00664d3ccd7e12696975bd4fde could be the issue. But I am really not sure as it is a simple renaming of an value, but it is part of the communication queue between mcu and host

#

I quickly checked my V2 and it homes normal so it must be something more related to your setup

#

In the other I read you build a new FW so it could also be that https://github.com/Klipper3d/klipper/commit/e5ed245ff2cc04f80fa248c18ea18535cc06e553 I can not test that as my mcus do not use a STM32

limber haven Apr 11, 2023, 7:04 AM

#

It works again. Somehow the flashing of the MCU did fail the first time around even though the firmware.bin file was loaded and written to the MCU (was renamed to FIRMWARE.cur on the SD-card used). So everythings good again.

If you want any of the above information anyways to investigate or something just tell me 🙂

#"Timer too close" after update