Ive got Voron 2.4 with Octopus and SB2209 CAN board all connected to PI4, everything seems fine but ive got error in the middle of print as shown in photo attached.
What is the solution for that error? Normally printer is doing everything as normal, it just starts printing after leveling and all that stuff, and after around hour or so it just shut down. klippy.log (3.4 MB)
âMCU âEBBCanâ 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â
Check our Knowledge Base. Here you will find the common Klipper errors and their typical reasons / solutions.
Edit: And in general, I will stop answering to any request that is not accompanied by a klippy.log as indicated in every new postâs template (which you also ignored in your first post).
Got error -1 in can write: (105)No buffer space available
So far you both are first ones, where I see this error. So I would guess it is not a common problem, given the fact that CAN usage in Klipper is quite widespread nowadays.
Unfortunately I cannot contribute more than referring to the CAN Troubleshooting document as linked above.
You might also try to increase the queue length, e.g.:
allow-hotplug can0
iface can0 can static
bitrate 500000
up ifconfig $IFACE txqueuelen 2048
post-up /sbin/ip link set up $IFACE type can bitrate 500000
I went through the docs before I made this thread, I would try to update the buffer size with something bigger, but honestly I really donât know how it could helpâŚ
I would really appreciate if I could be able to see at least something in the logs, all we can see is service restart with no exception thrown before it. Even it would be unstable CANbus communication I would expect to see something, uptime of the Pi is not affected, Pi is not reporting throttling event, so the OS could be I hope excluded.
My observation ( @Kromka_z_maslem please confirm / reject ) it happens mostly in first few minutes of print. I.e. I had ~7hrs print which was affected in like first 10s, then maybe after 2 minutes, then it was printed without any error. Same file, just after FIRMWARE_RESTART
So I have some guesses about what is causing this problem. First of all, I know for sure I should reroute my can cable, and I will do it after my print maybe is done. So far, so good. I need to make it shorter and better for me; i have U2C close to hole in bottom i also disconnected completly toolhead leds, turned all neopixel off completly. My printer stopped pretty much in a kind of random place; yesterday I got two times around 1 hour of printing time, today twice in 30 minutes. Never before. Everything works smoothly, like bed leveling. The adaptive mesh is great; it prints the first layer very well. Everything seems okay until it randomly stops working.
So first i got new SB2209 board and new PI4, second i installed new PSU just for toolhead, very clean wiring. Got suggestion to type: âsudo ip link sec can0 txqueuelen 1024â than it was showing 1024 but after reset it goes back to 10. so than: âls -l /etc/network/interfaces.dâ showed files can0 and cad0. That means cad0 was interrupting my whole config. After command âsudo rm /etc/network/interfaces.d/cad0â everything started to work finally. Now im happy printing with no errors. Also i experienced error âno buffer size availableâ. Now ive got very clean klippy.log file. So my setup might looks like overkill, but i think it makes sense.
So basically very similar issue to mine - small buffer set on OS level. Conclusion is if the buffer is very small, klippy service tends to quietly crash.
i also disconnected completly toolhead leds, turned all neopixel off completly. My printer stopped pretty much in a kind of random place; yesterday I got two times around 1 hour of printing time, today twice in 30 minutes. Never before. Everything works smoothly, like bed leveling. The adaptive mesh is great; it prints the first layer very well. Everything seems okay until it randomly stops working.