Basic Information: Printer Model: VZBot MCU / Printerboard: SKR 1.4 Turbo + Fly-SHT36 klippy.log klippy(1).log (307.0 KB) Describe your issue: After printing perfectly fine several times yesterday (and several weeks before), I swapped to PLA from ASA today and attempted a print.. every time, …

Use ifconfig to check for error counts on the CAN bus. Dropped frames and errors Run before and note current numbers, then run again after failures to see if they grow in numbers.

Hi, I am getting the same error (see https://klipper.discourse.group/t/timer-too-close-on-voron-2-4 ) @NAPCAL thank you for that hint, I got some dropped RX frames, but what should I do against it? I am using the BTT U2C v2.1 and the EBB2209 board. Here is the output of ifconfig: can0: flags=193<U…

Lower the speed to 500K and check for errors. If none the bump it up to 750K If still high number lower it to 250K If you still get errors there might be a connection problem, CAN bus wires too close to stepper wires.

Thank you! I just reduced the speed to 500k and started a 5h print. I have another question: The CAN cable (the one, which came with the EBB2209) and the wires for A and B stepper motors are all in the cable cain for the z-axis. Is it worth a try to use shielded cables for the stepper motors?

The better would be to add a braided shield to the cable with the CAN bus wiring. I have been planning to do this but my spool of braided shield has gone missing!

[PXL_20230830_172017127~2] “Timer too close” again … But this time, there were no errors or dropped packages. However I noticed, that the print failed 2 times at the same spot (see image)

As described in the other discussion, probably I fixed my issue [image] Timer too Close on Voron 2.4 General Discussion Update: I reinstalled MainsailOS, I am using another SD-Card and another Raspberry Pi 4. I also switched from OrcaSlicer to PrusaSlicer and again, I go…

I have the feeling that UART connection requires short and not too thin cables that do not interfere with other cables and of course a good connection.

I totally agree with you. However, I had no troubles using the UART connection with the stock cables. Some days ago I got this error the first time. This is the stock cable, which I was using. [image]

Suddenly "Timer too close" canbus errors?

General Discussion

Bananenking September 1, 2023, 7:54pm 8

As described in the other discussion, probably I fixed my issue

Topic		Replies	Views
Timer too close on ebb36 General Discussion	1	131	October 25, 2024
Timer too close with SB2040 General Discussion	12	645	December 12, 2023
Timer too close - only in Copy/Mirror-Mode - Idex General Discussion	14	269	April 22, 2025
"Timer Too Close" at a consistent time in file General Discussion	6	1578	March 21, 2024
MCU 'EBBCan' shutdown: Timer too close General Discussion	23	677	December 26, 2024

Suddenly "Timer too close" canbus errors?

Related topics