# Suddenly "Timer too close" canbus errors?

**URL:** <https://klipper.discourse.group/t/suddenly-timer-too-close-canbus-errors/5025>\
**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:** 1\
**Showing post:** 3

<div class="post-metadata">

**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")

</div>

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\<UP,RUNNING,NOARP\> 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

---

_[View the full topic](https://klipper.discourse.group/t/suddenly-timer-too-close-canbus-errors/5025)._