MCU 'mcu' shutdown: Timer too close error after update

[jmillerhyetech]

I updated my OpenNept4une N4plus the other day and started getting this MCU error after uploading certain gcode files. After some research it appears it is a problem with the display from the latest update. This did not happen with v0.1.5. Disabling display.service and affinity.service via systemctrl allows me to print again, but disables touchscreen obviously.

[halfmanbear]

Are you using a 3rd party bed probe?

[jmillerhyetech]

Are you using a 3rd party bed probe?

No. Pure stock N4Plus

[user-536]

It alsso just happened to me but I'm usigng a Btt eddy with the eddy-ng repository
I hope someone can help us or have the solution

[jmillerhyetech]

Posting logs would probably help. I plan on doing this, but I have a lot of prints to finish up first. are the logs out of klipper enough of are there some debug commands that would help more?

[user-536]

Now I'm reinstalling OpenNept4une but if it still won't work I'm happy to help with my logs

[breaki1904]

Yesterday i flashed my emmc to install the newest version of openNeptune. I have also the BTT Eddy probe with the eddy-ng firmware installed. After some problems with the latest Klipper version (changes in how the probe position results get handled) it worked well for 2 test prints. Then i got the same error with "Timer too close". Tried it several times with bed mesh adaptive and bed mesh rapid_scan. Sometimes all works, sometimes i get the error. Here is the klippy.log, maybe it helps to address the error. Thanks for your good work, using openNeptune from the beginning, worked always like a charm 😃

klippy.log

[halfmanbear]

Please switch to dev branch as mentioned earlier in this chat. I'm in the process of applying patches for these 3rd party probes.

[breaki1904]

I switched to the dev branch and updated both things i was prompted. The result is, sometimes it works, most times not. A normal bed mesh works without any errors, rapid scan and adaptive.

Here is the new klippy.log

klippy.log

[user-536]

I also have your same configuration but now I've installed the 0.15v and the same error appear there, I'll try 0.17v on the dev branch

[breaki1904]

I followed the advice on the Klipper Discourse to harden Klipper against disruption by background tasks by adding

[Service]
Nice=-18
IOSchedulingPriority=1

to /etc/systemd/system/klipper.service . Since this change no more errors or failures occurred. But I don't know if that has an impact on other areas.

[user-536]

Thank you, I will try this option while waiting for the official fix

[jmillerhyetech]

Nice=-18
IOSchedulingPriority=1

I re-enabled the display and affinity services and added the above.
This seemed to work so far. My touchscreen works again and I was able to send a print. I couldn't even get past a bed level before.

[user-536]

Me too, it made me able to print again but now some calibrations like the input shaper and the pid couldn't save the new configs becasue klipper crashes and need a reboot(no errors appear).
Thank you anyway for the probvisory fix