Stepper Sync causes MCU 'mcu' shutdown: Timer too close

[HelgeKeck]

Hi,

im getting the famous MCU 'mcu' shutdown: Timer too close error, when using a additional MCU.

Running the latest Klipper on a Raspberry Pi4 4GB with an Octopus V1.1 Board.

The error happens randomly when i try to use some manual steppers from my MMU2S unit. I thought its because im using an old Trigorilla board for it, but after switching to a brand new SKR Mini V2.1 the error still happens.

The error happens once in a week or so, the last time (the attached klippy log), it happend after the print was already finished and the MMU tried to eject the filament.

As far as i can tell, it happens only when i try to sync a manual stepper with the extruder stepper, like:

MANUAL_STEPPER STEPPER=gear_stepper MOVE=-20 SPEED=10 SET_POSITION=0 SYNC=0
G1 E-20 F600
MANUAL_STEPPER STEPPER=gear_stepper SYNC=1

The raspberry pi defintiely didnt do anything unusual in this moment, so i dont know how to fix that

thanks

PS: not sure if this is correct, but i had to zip the klippy log in order to upload it here.

klippy.log.zip

[HelgeKeck]

so it just happed again and i thought i share the new logfile

klippy.log.zip

[0Jayy07]

Hi, it happened to me 4 times already... :(

[0Jayy07]

klippy (1).log

[Teila]

I am also receiving this issue with my ERCF mcu (seeduino). This has also happened outside of printing via GCode IE just testing tool changes
klippy (11).log
.

[HelgeKeck]

bump

[0Jayy07]

I fixed it whit OC. I overclocked my pi zero 2W to 1.1Ghz or something like that. And locked it to that. Am Di., 15. Feb. 2022 um 23:22 Uhr schrieb HelgeKeck < ***@***.***>:

…

bump — Reply to this email directly, view it on GitHub <#5093 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXDVBUFGO2YQO47DNYUJ34TU3LGYLANCNFSM5LCIAGNQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[jrhelbert]

I've been fighting this for a couple months now. Raspberry Pi 4 with a BTT Octopus. Mainsail/moonraker/klipper are the only things running on it. I have a webcam running, but have seen the error both with and without the webcamd service disabled.

It always happens in the first part of my print, while printing the skirt. I can always tell its about to happen because my extruder goes into "funky noise land" and I get some really crazy movements and overextrusions. You can see in my klippy.log that it actually triggers my filament encoder sensor and if I resume the print and let it go I will end up with the aforementioned mcu error.

If I do a firmware restart and reprint the exact same gcode it will have no problems and print successfully.

My utilization numbers on the pi are usually only around a 0.2 load average and at 94% idle. I've done everything I can think of, disabling power saving the pi so it never clocks down, disabled as many services as I can think of, decreasing my microsteps on all steppers, etc. Nothing has seemed to improve the issue. I'm running pretty much the fastest, most overkill, hardware you can put klipper on with the least amount of stuff running on it, so I can't believe its a utilization issue.

klippy.log_mcu_error_011222.log
.

[HelgeKeck]

not sure if it is important, im using TMC 2209s in UART Mode

[jrhelbert]

not sure if it is important, im using TMC 2209s in UART Mode

I am as well.

[hugoalves6]

Having this issue also, im using pi zero 2w, with fysetc spider with all tmc2209, trying to do my own color selector, but when i try to move the manual_stepper less than 10-20sec of each movement it triggers this kind of error...

[SkyLuke91]

Hi there I'm having same issue.
The error occurs randomly, motly when printing longer prints. (For example i had no issue printing 2h prints, but when i try to print 8h print it stops after 1hour or so [randomly])
This one failed in layer #13
HT50 HOLDER-PLA-0.2mm-10%-3h10m-55g.txt
Running on Rpi zero 2W, Moontracker, Fluidd, Klipper without any cameras.
Gcode from SuperSlicer without any postprocess.
Klippy log attached.
klippy.log

Is there something I can do to eliminate those?
Thanks

[github-actions]

It looks like this ticket is a request for help (or similar). Many helpful people will not see your message here and you are unlikely to get a useful response. Instead, see the contact directions at: https://www.klipper3d.org/Contact.html

We use github to share the results of work done to improve Klipper. We don't use github for requests. (In particular, we don't use github for feature requests, to answer questions, nor to help diagnose problems with a printer.)

Please follow the directions at: https://www.klipper3d.org/Contact.html

This ticket will be automatically closed.

Best regards,
~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being.

[Sineos]

This topic is getting out of control.
The first few relates to MANUAL_STEPPER and the rest is mainly the "generic" Timer too close issue, probably mostly caused by weak or overloaded Pis.

If the SYNC topic is still present, it would make sense to open a new thread on https://klipper.discourse.group and likewise for the unrelated to SYNC, please open an own topic or search on discourse as enough topics are already existing.

[psyvision]

Another user with Timer too close errors when using MANUAL_STEPPER even with SYNC=1. I am running multiple MCUs, TMC2208 driving the manual stepper.

klippy (10).log

[iplayfast]

I've just updated my software (klipper/moonraker/mainsail on raspberry pi3, octopu mcu).
Turns out it was that I hadn't updated the frequency of the MCU. (things to check if you have this problem).

[phil2sat]

Don`t know if its the issue, but on my Pi zero W i got the same. Driven me Mad, sometimes 20 times reconnect until it got connected. What it fixed for me was:

[delayed_gcode delayed_homing]
gcode:
G28
STAR_TREK
initial_duration: 8 <--- Set this from 0.1 to a value higher wich works

So on connection its time to settle down before the Printer begins to auto home and so on.

[jpsilvashy]

It's a shame this issue is getting so little attention and this issue was closed. I too have a Pi4 B+ with a 16gb v90 UHS-II SD card, no webcam, no other software running on the pi besides klipper and mainsail, both updated to the most recent version.

Watched htop as the crash happened last time, max load was 11% and very little ram in use.

[Sineos]

Sorry, but it is the right thing:

1. The OPs issue was very specific
2. All the following me-too's had the same error message but not the same setup
3. The error can come from multiple sources: Unstable voltage, errors on the SD, other devices hogging the USB bus, out of memory, CPU load, too much IO activity, overheating, other throttling scenarios etc
4. GH is not used to work on individual error scenarios
5. Open an issue on https://klipper.discourse.group with your individual case. Make sure you have checked / ruled out all under 3. because it is the first answer you will receive there as well