# Timer too close in one of my Can Devices

**URL:** https://klipper.discourse.group/t/timer-too-close-in-one-of-my-can-devices/22330
**Category:** General Discussion
**Created:** [March 4, 2025, 3:03pm UTC](https://klipper.discourse.group/t/timer-too-close-in-one-of-my-can-devices/22330 "2025-03-04T15:03:39Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![hcet14](https://avatars.discourse-cdn.com/v4/letter/h/ecd19e/32.png) [@hcet14](https://klipper.discourse.group/u/hcet14)
#### Post date: [March 4, 2025, 4:56pm UTC](https://klipper.discourse.group/t/timer-too-close-in-one-of-my-can-devices/22330/2 "2025-03-04T16:56:20Z")

</div>

Could it be your CB1? Pretty hot.

 ![cb1_graph](https://global.discourse-cdn.com/free1/uploads/klipper/original/3X/2/8/28bdee0717de185eb3f27925a3cb557a98575567.png)

I mentioned this link [MCU 'mcu' shutdown: Timer too close still present · Issue #124 · Frix-x/klippain-shaketune · GitHub](https://github.com/Frix-x/klippain-shaketune/issues/124#issuecomment-2265221868) here [Random Shutdown - #4 by hcet14](https://klipper.discourse.group/t/random-shutdown/21368/4).

Good luck, hcet

---

_[View the full topic](https://klipper.discourse.group/t/timer-too-close-in-one-of-my-can-devices/22330)._