# Help with Troubleshooting: MCU timer too close error

**URL:** <https://klipper.discourse.group/t/help-with-troubleshooting-mcu-timer-too-close-error/15913>\
**Category:** General Discussion\
**Created:** [April 20, 2024, 8:36pm UTC](https://klipper.discourse.group/t/help-with-troubleshooting-mcu-timer-too-close-error/15913 "2024-04-20T20:36:26Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![koconnor](https://avatars.discourse-cdn.com/v4/letter/k/aca169/32.png) [@koconnor](https://klipper.discourse.group/u/koconnor)\
**Post date:** [April 24, 2024, 12:43am UTC](https://klipper.discourse.group/t/help-with-troubleshooting-mcu-timer-too-close-error/15913/21 "2024-04-24T00:43:34Z")

</div>

> [@Bcouter](#):
>
> Then the status will change to UP and reads:  
> 3: can0: \<NOARP,UP,LOWER\_UP,ECHO\> mtu 16 qdisc pfifo\_fast state UP group default qlen 10  
> link/can

Note the `qlen 10`. As described at [CANBUS Troubleshooting - Klipper documentation](https://www.klipper3d.org/CANBUS_Troubleshooting.html#use-an-appropriate-txqueuelen-setting) this indicates that your txqueuelen setting is not being applied.

I recommend following the directions at [CANBUS - Klipper documentation](https://www.klipper3d.org/CANBUS.html#host-hardware) , and use the `/etc/network/interfaces.d/can0` settings exactly as stated there. Restart the rpi, and then run the `ip link show can0` and verify you see `qlen 128` before proceeding with further tests.

-Kevin

---

<div class="post-metadata">

**Author:** ![Bcouter](https://avatars.discourse-cdn.com/v4/letter/b/258eb7/32.png) [@Bcouter](https://klipper.discourse.group/u/Bcouter)\
**Post date:** [April 24, 2024, 4:30am UTC](https://klipper.discourse.group/t/help-with-troubleshooting-mcu-timer-too-close-error/15913/22 "2024-04-24T04:30:14Z")

</div>

TEAM! GREAT NEWS

I used the EXACT klipper suggested settings for can interface file… And for the first time, my printer booted up AND connected to the ebb36 without needing to SSH a command. I’ll be heating up the bed and home/probe everything first thing in the morning. The can network is reporting the proper txqueuelen. I removed the  
` pre-up ip link set can0 type can bitrate 1000000 pre-up ip link set can0 txqueuelen 1024` lines

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\
**Post date:** [May 24, 2024, 2:30pm UTC](https://klipper.discourse.group/t/help-with-troubleshooting-mcu-timer-too-close-error/15913/23 "2024-05-24T14:30:51Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

[Previous page](https://klipper.discourse.group/t/help-with-troubleshooting-mcu-timer-too-close-error/15913.md?page=1)