# Timer too close with SB2040 **URL:** \ **Category:** General Discussion\ **Created:** [December 9, 2023, 4:00pm UTC](https://klipper.discourse.group/t/timer-too-close-with-sb2040/12184 "2023-12-09T16:00:16Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![hcet14](https://avatars.discourse-cdn.com/v4/letter/h/ecd19e/32.png) [@hcet14](https://klipper.discourse.group/u/hcet14)\ **Post date:** [December 9, 2023, 4:09pm UTC](https://klipper.discourse.group/t/timer-too-close-with-sb2040/12184/2 "2023-12-09T16:09:54Z")
Do you know Sineos’ “Knowledge Base”? > [@Timer too close](https://klipper.discourse.group/t/timer-too-close/6634): > > 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. warning 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 … Good luck, hcet14 --- _[View the full topic](https://klipper.discourse.group/t/timer-too-close-with-sb2040/12184)._