# MCU 'sb2040' shutdown: Timer too close **URL:** \ **Category:** General Discussion\ **Created:** [May 6, 2023, 7:52am UTC](https://klipper.discourse.group/t/mcu-sb2040-shutdown-timer-too-close/8248 "2023-05-06T07:52:07Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![JesNoFear](https://avatars.discourse-cdn.com/v4/letter/j/a87d85/32.png) [@JesNoFear](https://klipper.discourse.group/u/JesNoFear)\ **Post date:** [May 6, 2023, 7:52am UTC](https://klipper.discourse.group/t/mcu-sb2040-shutdown-timer-too-close/8248/1 "2023-05-06T07:52:07Z")
### Basic Information: Printer Model: Voron 2.4 R2 - CanBus MCU / Printerboard: Octopus Pro, Klipper Expansion board, Fly SB2040 v2 `klippy.log` [Klippy-5-6-23.log](https://klipper.discourse.group/uploads/short-url/kyzOgcxm4B3O2EEpKq4Sy5JXqc7.log) (7.0 MB) ### Describe your issue: Since upgrading from Fly 2040 v1 to v2 I keep getting “MCU ‘sb2040’ shutdown: Timer too close” after a “Hold till temp is meet” command finishes. I am trying to print a temperature tower and it is consistently shutting down after the temperature is meet with this error. I have read other post where neopixle seems to be the issue, so on my last run (Line 12508) I stopped all LED effects to rule that out and it still occurred. Lines 15844 is adjusting the temp and 15854 it reaches temp to then line 15870 where klipper shuts down. I did re-flash everything twice, and updated my repo. not sure what else to look for. My host computer peaks out at 2% utilization, so that isn’t the issue. Non-Temp changing prints are completing with no issue. ---
**Author:** ![JesNoFear](https://avatars.discourse-cdn.com/v4/letter/j/a87d85/32.png) [@JesNoFear](https://klipper.discourse.group/u/JesNoFear)\ **Post date:** [June 6, 2023, 4:43am UTC](https://klipper.discourse.group/t/mcu-sb2040-shutdown-timer-too-close/8248/2 "2023-06-06T04:43:51Z")
_BUMP_ Still having this issue, Can’t print temperature towers, crashes after wait on new temp mid-print. [klippy\_6-5-23.log](https://klipper.discourse.group/uploads/short-url/54WQwrQYSHmyze1MwLJrYeYb6ck.log) (5.2 MB) ---
**Author:** ![jakep\_82](https://avatars.discourse-cdn.com/v4/letter/j/ea666f/32.png) [@jakep\_82](https://klipper.discourse.group/u/jakep_82)\ **Post date:** [June 6, 2023, 5:11am UTC](https://klipper.discourse.group/t/mcu-sb2040-shutdown-timer-too-close/8248/3 "2023-06-06T05:11:12Z")
The log indicates the host is running on a core i7 12th gen processor. Is Klipper running on a VM? ---
**Author:** ![JesNoFear](https://avatars.discourse-cdn.com/v4/letter/j/a87d85/32.png) [@JesNoFear](https://klipper.discourse.group/u/JesNoFear)\ **Post date:** [June 6, 2023, 6:51am UTC](https://klipper.discourse.group/t/mcu-sb2040-shutdown-timer-too-close/8248/4 "2023-06-06T06:51:48Z")
Nope, fit a whole motherboard into my printer ![IMG_20230302_015704385_HDR](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/f/f7b3005a6ed2de594f30a2b4af7064cea08c7306.jpeg) ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [June 6, 2023, 6:55am UTC](https://klipper.discourse.group/t/mcu-sb2040-shutdown-timer-too-close/8248/5 "2023-06-06T06:55:18Z")
This sounds like a smart plan to counter the chip shortages on Raspberry Pis 🤦 ---
**Author:** ![JesNoFear](https://avatars.discourse-cdn.com/v4/letter/j/a87d85/32.png) [@JesNoFear](https://klipper.discourse.group/u/JesNoFear)\ **Post date:** [June 6, 2023, 6:59am UTC](https://klipper.discourse.group/t/mcu-sb2040-shutdown-timer-too-close/8248/6 "2023-06-06T06:59:01Z")
I had a Pi in it before, but maxed out its bus with 2 1080P cameras running, so I needed something with a faster bus, and wanted native NVME. So this is what I settled on. I had my eye on another motherboard, but it was 300 more with less power, so I went the cheaper route and have a power house 🙂 OctoPrint runs great on it ---
**Author:** ![koconnor](https://avatars.discourse-cdn.com/v4/letter/k/aca169/32.png) [@koconnor](https://klipper.discourse.group/u/koconnor)\ **Post date:** [June 13, 2023, 2:05am UTC](https://klipper.discourse.group/t/mcu-sb2040-shutdown-timer-too-close/8248/7 "2023-06-13T02:05:54Z")
It looks like you’ve customized the Klipper code. I’d recommend reproducing the error on the pristine Klipper code to see if the error persists. If it does, please attach the Klipper log file from that event. (Though, note, there are reports that the rp2040 code is not working properly in the very latest master Klipper code.) -Kevin ---
**Author:** ![JesNoFear](https://avatars.discourse-cdn.com/v4/letter/j/a87d85/32.png) [@JesNoFear](https://klipper.discourse.group/u/JesNoFear)\ **Post date:** [June 13, 2023, 3:50am UTC](https://klipper.discourse.group/t/mcu-sb2040-shutdown-timer-too-close/8248/8 "2023-06-13T03:50:35Z")
i am using the most current from git, didn’t customize anything in klipper, just macros. Unless you mean by customize I installed the canboot and klipper-led\_effect, then yes its customized in that way, but i did not edit any source code. do you know what code version is known to work properly with the rp2040 code? ![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/c/c69023f602f4a3daeac52ac2d9e3bf150d474606.png) ---
**Author:** ![jakep\_82](https://avatars.discourse-cdn.com/v4/letter/j/ea666f/32.png) [@jakep\_82](https://klipper.discourse.group/u/jakep_82)\ **Post date:** [June 21, 2023, 3:58pm UTC](https://klipper.discourse.group/t/mcu-sb2040-shutdown-timer-too-close/8248/9 "2023-06-21T15:58:16Z")
Led\_effects is not a part of mainline Klipper, and the screenshot notes that file as untracked in your local directory. That would need to be removed to do any further diagnosis. ---
**Author:** ![JesNoFear](https://avatars.discourse-cdn.com/v4/letter/j/a87d85/32.png) [@JesNoFear](https://klipper.discourse.group/u/JesNoFear)\ **Post date:** [September 29, 2023, 8:35am UTC](https://klipper.discourse.group/t/mcu-sb2040-shutdown-timer-too-close/8248/10 "2023-09-29T08:35:46Z")
Still an ongoing issue, i switched out the Fly SB2040 with the BTT SB2209 since it didn’t have the RPI dependency. [klippy.TimerTooClose.zip](https://klipper.discourse.group/uploads/short-url/3l3ZMPnXBbutkTNUmj4SzU9V2UL.zip) (1.7 MB) ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [September 29, 2023, 9:34am UTC](https://klipper.discourse.group/t/mcu-sb2040-shutdown-timer-too-close/8248/11 "2023-09-29T09:34:31Z")
Did you actually read what @koconnor and @jakep_82 told you? ```auto Args: ['/home/pi/klipper/klippy/klippy.py', '/home/pi/printer.cfg', '-l', '/tmp/klippy.log'] Git version: 'v0.11.0-276-ge9bf2d4c-dirty' Untracked files: klippy/extras/led_effect.py Modified files: klippy/mcu.py Branch: master Remote: origin Tracked URL: https://github.com/Klipper3d/klipper ``` ---
**Author:** ![damoura](https://avatars.discourse-cdn.com/v4/letter/d/58956e/32.png) [@damoura](https://klipper.discourse.group/u/damoura)\ **Post date:** [May 4, 2024, 11:54am UTC](https://klipper.discourse.group/t/mcu-sb2040-shutdown-timer-too-close/8248/12 "2024-05-04T11:54:25Z")
@JesNoFear You resolved this issue ? Found a solution ? ---
**Author:** ![TheFuzzyGiggler](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/thefuzzygiggler/32/12313_2.png) [@TheFuzzyGiggler](https://klipper.discourse.group/u/TheFuzzyGiggler)\ **Post date:** [May 4, 2024, 2:24pm UTC](https://klipper.discourse.group/t/mcu-sb2040-shutdown-timer-too-close/8248/13 "2024-05-04T14:24:27Z")
That is by far one of the funniest Voron’s I’ve ever seen, major props. ![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/5/5366e1bd505d28ca57b9d6f709cb3fd7faa90f29.jpeg) Also, Purple Voron gang. Mines a darker purple though. My only pic on hand ![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/e/ea4d6026d5e2acb789129f8f6eba213d2f922725.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:** [May 4, 2024, 6:33pm UTC](https://klipper.discourse.group/t/mcu-sb2040-shutdown-timer-too-close/8248/14 "2024-05-04T18:33:01Z")
> [@damoura](#): > > You resolved this issue ? Found a solution ? Why do you ask? Do you have a solution? ---
**Author:** ![damoura](https://avatars.discourse-cdn.com/v4/letter/d/58956e/32.png) [@damoura](https://klipper.discourse.group/u/damoura)\ **Post date:** [May 4, 2024, 6:44pm UTC](https://klipper.discourse.group/t/mcu-sb2040-shutdown-timer-too-close/8248/15 "2024-05-04T18:44:15Z")
No, i have the same issue ! ---
**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:** [May 4, 2024, 6:46pm UTC](https://klipper.discourse.group/t/mcu-sb2040-shutdown-timer-too-close/8248/16 "2024-05-04T18:46:24Z")
Maybe you can help the OP to solve the issue… ---
**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:** [July 30, 2026, 5:16am UTC](https://klipper.discourse.group/t/mcu-sb2040-shutdown-timer-too-close/8248/17 "2026-07-30T05:16:45Z")