# MCU Shutdown Timer too close

**URL:** <https://klipper.discourse.group/t/mcu-shutdown-timer-too-close/15702>\
**Category:** General Discussion\
**Created:** [April 12, 2024, 6:46pm UTC](https://klipper.discourse.group/t/mcu-shutdown-timer-too-close/15702 "2024-04-12T18:46:05Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![MightyRaith78](https://avatars.discourse-cdn.com/v4/letter/m/ecccb3/32.png) [@MightyRaith78](https://klipper.discourse.group/u/MightyRaith78)\
**Post date:** [April 12, 2024, 6:46pm UTC](https://klipper.discourse.group/t/mcu-shutdown-timer-too-close/15702/1 "2024-04-12T18:46:05Z")

</div>

### Basic Information:

Sovol SV07+  
 MCU / Printerboard: - stock  
 Host / SBC - stock  
 klippy.log

\*Fill out above  
[klippy-1.zip](https://klipper.discourse.group/uploads/short-url/tVCSWAGgRjIzHFXcPBYdCuTxvN6.zip) (4.7 MB)

On 2 or 3 occasions I have lost a print to the dead mcu shutdown timer to close any input would be greatly appreciated as I’m fairly new to Klipper.  
…

---

<div class="post-metadata">

**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:** [April 12, 2024, 6:47pm UTC](https://klipper.discourse.group/t/mcu-shutdown-timer-too-close/15702/2 "2024-04-12T18:47:28Z")

</div>

Hello @MightyRaith78 !

On Timer Too Close

> [@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 …

---

<div class="post-metadata">

**Author:** ![MightyRaith78](https://avatars.discourse-cdn.com/v4/letter/m/ecccb3/32.png) [@MightyRaith78](https://klipper.discourse.group/u/MightyRaith78)\
**Post date:** [April 13, 2024, 6:28pm UTC](https://klipper.discourse.group/t/mcu-shutdown-timer-too-close/15702/3 "2024-04-13T18:28:51Z")

</div>

I should add this happened 2 days into a 3 day print and I’m not running any webcam or any extra addons,

On a unrelated note when my printer arrived the RF filter was rolling about in the box so I attached it to the bed power cable before the bed is this where it should have gone.

---

<div class="post-metadata">

**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:** [April 14, 2024, 8:10am UTC](https://klipper.discourse.group/t/mcu-shutdown-timer-too-close/15702/4 "2024-04-14T08:10:37Z")

</div>

I don’t see any communication concerns with bytes retransmitted or anything like that.

My first thought would be the SDCard. MicroSD cards are notorious for being shotty, even the “Industrial” ones can be iffy.

Consistently reading from a card for 2 days straight can have the potential issues. They’re not really designed for “sustained” usage despite what everyone tries to use them for.

If you’re ultra curious here’s a paper on the phenomenon of “read disturb”, where reading a flash cell slowly discharges the cells around it which have to be updated by the controller which degrades them over time.

> **[flash-read-disturb-errors\_dsn15.pdf](https://users.ece.cmu.edu/%7Eomutlu/pub/flash-read-disturb-errors_dsn15.pdf)**
>
> 3.17 MB

If you’re serious about running prints for multiple days without issue I’d seriously consider something more robust…

> **[Installing Mainsail or Fluidd on an SSD](https://docs.vorondesign.com/community/howto/Takuya/Installing_on_an_SSD.html)**
>
> Voron Official and Community Documentation

---

<div class="post-metadata">

**Author:** ![MightyRaith78](https://avatars.discourse-cdn.com/v4/letter/m/ecccb3/32.png) [@MightyRaith78](https://klipper.discourse.group/u/MightyRaith78)\
**Post date:** [April 14, 2024, 3:15pm UTC](https://klipper.discourse.group/t/mcu-shutdown-timer-too-close/15702/5 "2024-04-14T15:15:48Z")

</div>

Thank’s for the input most appreciated I actually have a PI 4 with a SSD in a tiny enclosure that I’m not using for anything at the moment! Just need to investigate how to get the printer to use that instead of the MKSPI that’s onboard.

---

<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:** [June 13, 2024, 3:16pm UTC](https://klipper.discourse.group/t/mcu-shutdown-timer-too-close/15702/6 "2024-06-13T15:16:04Z")

</div>

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