EBBCan shutdown – Timer too close error

[fputra]

Basic Information:

Printer Model: Voron Switchwire
MCU / Printerboard:BTT E3 V3
Host / SBC: Raspberry Pi 5
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

MCU ‘EBBCan’ shutdown: Timer too close
This often indicates the host computer is overloaded.

[fputra]

klippy (1).log (1.5 MB)

Apologies, I had to trim the log file as the original was too large to upload.

[3dcoded]

Hi @fputra ,

I would take a look here:

Timer too close

Timer too close Background A “Timer too close” error occurs when the MCU is asked to schedule an action at a time that is already in the past. This typically results from delayed communication between the host and the MCU - for instance, if the host was busy or the message was blocked en route. Important: Klipper can identify what command was too late, but cannot determine why the delay occurred. The root cause is often external - such as USB congestion from a webcam or high system …

[nefelim4ag]

Dumping serial stats: bytes_write=57651 bytes_read=154397 bytes_retransmit=3100 bytes_invalid=0 send_seq=5325 receive_seq=5323 retransmit_seq=5325 srtt=0.002 rttvar=0.001 rto=0.800 ready_bytes=0 upcoming_bytes=0

High RTO - communication issue.

b’Got error -1 in can write: (105)No buffer space available’ looks suspicious to me. Assuming a default TX length of 128 and only 1 device on the bus.

[EddyMI3D]

@fputra

I had to trim the log file as the original was too large to upload.

For we don’t know what you trimmed away:

[fputra]

klippy (1).zip (147.4 KB)

[fputra]

hi, I have found the couse of this proble :

Now I set it up like this :

sudo ip link set can0 txqueuelen 128

It’s been running for 12 hours now without any issues. However, I’m wondering if the qilen 128 settings I changed will be permanent when I restart the printer, or if it will revert to the old qilen 10 settings.

[mykepredko]

Where did you get your setup process? I’m curious as to why you had a qlen of 10.

I always highly recommend the Esoterical process:

Home

[fputra]

@mykepredko

Where did you get your setup process? I’m curious as to why you had a qlen of 10.

I followed the standard CAN bus setup from the Klipper documentation and a few community guides. I didn’t specifically change the txqueuelen, so it stayed at the Linux default of 10. I wasn’t aware that Klipper recommends setting it to 128 until it was pointed out here. I’ve now updated it to qlen 128 and will monitor to see if it resolves the issue.

[mykepredko]

The Esoterical guide is recommended because it is constantly updated - other instructions around the web can be old and the instructions can be incomplete (as you found) or out of date.

[fputra]

Thanks for the tip! I’ll switch over to the Esoterical guide for my setup from now on.