# Mcu shutdown: Timer too close **URL:** \ **Category:** General Discussion\ **Created:** [July 27, 2023, 8:47pm UTC](https://klipper.discourse.group/t/mcu-shutdown-timer-too-close/9683 "2023-07-27T20:47:07Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![jermaine](https://avatars.discourse-cdn.com/v4/letter/j/9de0a6/32.png) [@jermaine](https://klipper.discourse.group/u/jermaine)\ **Post date:** [July 27, 2023, 8:47pm UTC](https://klipper.discourse.group/t/mcu-shutdown-timer-too-close/9683/1 "2023-07-27T20:47:07Z")
### Basic Information: Printer Model: Own constrction simular to Rat Rig V-Core 3 MCU / Printerboard: Btt Octopus v1.1 `klippy.log` [klippy 2.log](https://klipper.discourse.group/uploads/short-url/isHrmq5gSnr1mwJeGnjAmqci2xh.log) (1.2 MB) ### Describe your issue: Hey guys, every time i‘m try to home my y-axis my printer runs in the „ ‘mcu’ shutdown: Timer too close“ Error. I tried serval hours to find the issue, but my programming skills are too poor to solve this problem or basicly read/ understand the log file. Can you please help me to find the reason/ solution for the issue and bring the printer alive for the first time. … ---
**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 27, 2023, 8:48pm UTC](https://klipper.discourse.group/t/mcu-shutdown-timer-too-close/9683/2 "2023-07-27T20:48:16Z")
Hello @jermaine ! You may have a look in this: > [@Timer too close](https://klipper.discourse.group/t/timer-too-close/6634/1): > > 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 … ---
**Author:** ![jermaine](https://avatars.discourse-cdn.com/v4/letter/j/9de0a6/32.png) [@jermaine](https://klipper.discourse.group/u/jermaine)\ **Post date:** [July 28, 2023, 7:01am UTC](https://klipper.discourse.group/t/mcu-shutdown-timer-too-close/9683/3 "2023-07-28T07:01:25Z")
Hey @EddyMI3D , I read serval posts about this error. I tried all solutions but nothing helped. Best regards ---
**Author:** ![mykepredko](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/mykepredko/32/2085_2.png) [@mykepredko](https://klipper.discourse.group/u/mykepredko)\ **Post date:** [July 28, 2023, 7:09am UTC](https://klipper.discourse.group/t/mcu-shutdown-timer-too-close/9683/4 "2023-07-28T07:09:23Z")
Could you describe your host system you’re using including the operating system and what’s running on it (all the applications)? ---
**Author:** ![jermaine](https://avatars.discourse-cdn.com/v4/letter/j/9de0a6/32.png) [@jermaine](https://klipper.discourse.group/u/jermaine)\ **Post date:** [July 28, 2023, 7:24pm UTC](https://klipper.discourse.group/t/mcu-shutdown-timer-too-close/9683/5 "2023-07-28T19:24:37Z")
I’m running a RPI4 8GB with and OctopusV1.1 board. Before i tried the RPI 4 i used a RPI3b with the same error. The raspberry runs klipper with the newest updates etc… I installed only Klipper on The RPI nothing else. Stepper drivers are TMC2209. What do you mean with application ? Best regardes ---
**Author:** ![mykepredko](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/mykepredko/32/2085_2.png) [@mykepredko](https://klipper.discourse.group/u/mykepredko)\ **Post date:** [July 28, 2023, 8:27pm UTC](https://klipper.discourse.group/t/mcu-shutdown-timer-too-close/9683/6 "2023-07-28T20:27:42Z")
I’m wondering about anything else running on the rPi - any webcams or any other devices? ---
**Author:** ![jermaine](https://avatars.discourse-cdn.com/v4/letter/j/9de0a6/32.png) [@jermaine](https://klipper.discourse.group/u/jermaine)\ **Post date:** [July 29, 2023, 12:21pm UTC](https://klipper.discourse.group/t/mcu-shutdown-timer-too-close/9683/7 "2023-07-29T12:21:40Z")
Hey, there is no webcam or such things running. The printer is in a prototype state where it only can print. If it finally runs (to minimize error origins) I add things like a webcam. ---
**Author:** ![hcet14](https://avatars.discourse-cdn.com/v4/letter/h/ecd19e/32.png) [@hcet14](https://klipper.discourse.group/u/hcet14)\ **Post date:** [July 29, 2023, 1:55pm UTC](https://klipper.discourse.group/t/mcu-shutdown-timer-too-close/9683/8 "2023-07-29T13:55:40Z")
Starting from line 12 in your klippy.log: > Unable to open config file /home/pi/printer\_data/config/printer.cfg > Traceback (most recent call last): > File “/home/pi/klipper/klippy/configfile.py”, line 158, in \_read\_config\_file > f = open(filename, ‘r’) > FileNotFoundError: [Errno 2] No such file or directory: ‘/home/pi/printer\_data/config/printer.cfg’ > Config error Where is your printer.cfg located on your RPi? I would not expect such an error. Good luck, hcet14 ---
**Author:** ![jermaine](https://avatars.discourse-cdn.com/v4/letter/j/9de0a6/32.png) [@jermaine](https://klipper.discourse.group/u/jermaine)\ **Post date:** [July 29, 2023, 2:41pm UTC](https://klipper.discourse.group/t/mcu-shutdown-timer-too-close/9683/9 "2023-07-29T14:41:51Z")
hey @hcet14, thx for your replay. I search for the config-file. It’s located in /home/pi/printer\_data/config/\*. I don’t know the reason for this error but for me it seems the path is correct. ---
**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 24, 2024, 1:53pm UTC](https://klipper.discourse.group/t/mcu-shutdown-timer-too-close/9683/10 "2024-04-24T13:53:01Z")