#MCU Timer too close.

10 messages · Page 1 of 1 (latest)

gaunt vine
#

Hi All, I have sporadically been having issues with MCU timer too close. It always seems to happen during QGL, normally if I get past QGL the print is fine.

I always though it was a mechanical issue, as the previous times I have had this before have been down to the CAN cable pulling out slightly and QGL goes to the far corners. I replaced the cable as I though there might be internal damage to it. I also examined the CAN board for any damage around that connection it looks fine. I also printed and installed a better PUG cable support that clamps the cable. I also have plenty of slack. I finished that work today and managed to print for several hours, before it started happening again. Now it is constant.

I do not think it an overheating/overloading issue as keeping an eye on the system loads when it happens and they all look fine.

I'm running a BTT PI, BTT Octopus Pro, BTT EBB SB2209 & Cartographer with the latest version of everything.

I'm not sure where to go from here, my logic says it must be something hardware but I do not know how to prove/troubleshoot.

Thanks,
Chris

📎 klippy.log
hushed comet
#

The solution for me was replacing the btt pi with an rpi4

sly helm
#

As someone with the exact same setup, one of the things that helped the most for me was the txqueuelen. The kit I put together had it set to 1024 and bumping it down to the recommended 128 eliminated almost all of my issues. I had one timer too close a few weeks after that and I ended up updating all my Klippers and haven't had an issue... Yet...

radiant rune
gaunt vine
#

This made no difference it immediately failed again.

safe solstice
#

32 or 64bit on the pi?

I would get the same failure exactly 28mins into a print. I changed to 32bit and it all went away.

twin ivy
#

I’m having this issue too when trying to run belt comparison tests. Also had mine set to 1024 and tried 128 with no change. Not too sure why this is happening