# Suddenly "Timer too close" canbus errors? **URL:** \ **Category:** General Discussion\ **Created:** [November 20, 2022, 12:57pm UTC](https://klipper.discourse.group/t/suddenly-timer-too-close-canbus-errors/5025 "2022-11-20T12:57:51Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Arakon](https://avatars.discourse-cdn.com/v4/letter/a/f1d935/32.png) [@Arakon](https://klipper.discourse.group/u/Arakon)\ **Post date:** [November 20, 2022, 12:57pm UTC](https://klipper.discourse.group/t/suddenly-timer-too-close-canbus-errors/5025/1 "2022-11-20T12:57:51Z")
### Basic Information: Printer Model: VZBot MCU / Printerboard: SKR 1.4 Turbo + Fly-SHT36 `klippy.log` [klippy(1).log](https://klipper.discourse.group/uploads/short-url/18wgLm48ypj57Y80AcHMQpjYJwR.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, it aborts during the skirt now with a Timer too close error. Log also shows a bunch of stepcompress errors. Klipper version is v0.10.0-631-g8a065287, I believe I updated last night after the last print from 627. For testing purposes, I also ran an input shaper resonance test, which taxes the CAN bus pretty well as far as I know, and that ran through perfectly fine. Manual extrusion etc also does with no issues whatsoever. ---
**Author:** ![NAPCAL](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/napcal/32/1794_2.png) [@NAPCAL](https://klipper.discourse.group/u/NAPCAL)\ **Post date:** [November 20, 2022, 1:55pm UTC](https://klipper.discourse.group/t/suddenly-timer-too-close-canbus-errors/5025/2 "2022-11-20T13:55:43Z")
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. ---
**Author:** ![Bananenking](https://avatars.discourse-cdn.com/v4/letter/b/8e7dd6/32.png) [@Bananenking](https://klipper.discourse.group/u/Bananenking)\ **Post date:** [August 30, 2023, 2:59pm UTC](https://klipper.discourse.group/t/suddenly-timer-too-close-canbus-errors/5025/3 "2023-08-30T14:59:41Z")
Hi, I am getting the same error (see [https://klipper.discourse.group/t/timer-too-close-on-voron-2-4](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\ mtu 16 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1024 (UNSPEC) RX packets 165216 bytes 1056406 (1.0 MiB) RX errors 0 dropped 291 overruns 0 frame 0 TX packets 283127 bytes 2120877 (2.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ---
**Author:** ![NAPCAL](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/napcal/32/1794_2.png) [@NAPCAL](https://klipper.discourse.group/u/NAPCAL)\ **Post date:** [August 30, 2023, 3:38pm UTC](https://klipper.discourse.group/t/suddenly-timer-too-close-canbus-errors/5025/4 "2023-08-30T15:38:36Z")
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. ---
**Author:** ![Bananenking](https://avatars.discourse-cdn.com/v4/letter/b/8e7dd6/32.png) [@Bananenking](https://klipper.discourse.group/u/Bananenking)\ **Post date:** [August 30, 2023, 4:30pm UTC](https://klipper.discourse.group/t/suddenly-timer-too-close-canbus-errors/5025/5 "2023-08-30T16:30:55Z")
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? ---
**Author:** ![NAPCAL](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/napcal/32/1794_2.png) [@NAPCAL](https://klipper.discourse.group/u/NAPCAL)\ **Post date:** [August 30, 2023, 5:51pm UTC](https://klipper.discourse.group/t/suddenly-timer-too-close-canbus-errors/5025/6 "2023-08-30T17:51:37Z")
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! ---
**Author:** ![Bananenking](https://avatars.discourse-cdn.com/v4/letter/b/8e7dd6/32.png) [@Bananenking](https://klipper.discourse.group/u/Bananenking)\ **Post date:** [August 30, 2023, 5:56pm UTC](https://klipper.discourse.group/t/suddenly-timer-too-close-canbus-errors/5025/7 "2023-08-30T17:56:41Z")
![PXL_20230830_172017127~2](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/6/63685d61e83e1d3e932238c624e0b2012789e1db.jpeg) “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) ---
**Author:** ![Bananenking](https://avatars.discourse-cdn.com/v4/letter/b/8e7dd6/32.png) [@Bananenking](https://klipper.discourse.group/u/Bananenking)\ **Post date:** [September 1, 2023, 7:54pm UTC](https://klipper.discourse.group/t/suddenly-timer-too-close-canbus-errors/5025/8 "2023-09-01T19:54:47Z")
As described in the other discussion, probably I fixed my issue > [@Timer too Close on Voron 2.4](https://klipper.discourse.group/t/timer-too-close-on-voron-2-4/10103/13): > > 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 got the “Timer too close” error. Taking every failed print into acount it seems like I am getting these errors after about 35 minutes every time. Finally, I switched from UART to USB for my main MCU, the Fysetc Spider V1.1. The print (sliced the same object but again with OrcaSlicer, 4:40 hours print time) finally finished. smiley Thus, it look… ---
**Author:** ![LifeOfBrian](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/lifeofbrian/32/2380_2.png) [@LifeOfBrian](https://klipper.discourse.group/u/LifeOfBrian)\ **Post date:** [September 1, 2023, 8:26pm UTC](https://klipper.discourse.group/t/suddenly-timer-too-close-canbus-errors/5025/9 "2023-09-01T20:26:47Z")
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. ---
**Author:** ![Bananenking](https://avatars.discourse-cdn.com/v4/letter/b/8e7dd6/32.png) [@Bananenking](https://klipper.discourse.group/u/Bananenking)\ **Post date:** [September 1, 2023, 8:45pm UTC](https://klipper.discourse.group/t/suddenly-timer-too-close-canbus-errors/5025/10 "2023-09-01T20:45:59Z")
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. ![](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/0/05ef4ac85aa1fdfb0091ef27d0b321dfd08006b6.jpeg) ---
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [April 24, 2024, 1:51pm UTC](https://klipper.discourse.group/t/suddenly-timer-too-close-canbus-errors/5025/11 "2024-04-24T13:51:14Z")