MCU Shutdown Timer too close strange error

General Discussion
1

Basic Information:

Printer Model: Prusa i3MK3S+
MCU / Printerboard: Einsy
Host / SBC RPi5
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

Hello, I started a print job, waited for two hours and nothing wrong. Then I went out for a few hours. When I came back, I found that the print job did not complete. On the PC browser, I found “Klipper reports: SHITDOWN" MCU ‘mcu’ shutdown: Timer too close. This often indicates the host computer is overloaded. Check for other processes consuming excessive CPU,…”

What shall I do? I only use the Pi to run Klipper. Over the past few days, I noticed that on my 32GB microSD card used to install Klipper, I have used 22/29GB space. Also, prior to the start of the print job, I kept getting Connection Timed Out error when I attempted to send the file from Orca Slicer. Tired about 20 times and never worked. I ended up exporting the gcode file to the desktop of my PC and dragged the file to the browser GUI. Not sure if this is releated.

Even stranger is that after issuign M18, M84, the motors are still not disabled. I can’t move the buildplate nor extruder by hand. The nozzle stays on top of the unfinished print. I shut down the machine but still could not move them. Looks like the nozzle was stuck on the print. I had to use force to pull the build plate out. Could the impeeded motion be the cause of the shutdown?

klippy_shutdown.zip (4.4 MB)

2

I can’t find anything suspicious during shutdown.
The only suspicious thing that you have is a large number of invalid/retransmitted bytes.

Probably it is the same: MCU 'mcu' shutdown error

Did you update your USB2UART bridge firmware as suggested before?

3

Thanks for checking. How to update the USB2UART bridge firmware properly?

4

As mentioned in the: MCU 'mcu' shutdown error - #7 by koconnor

Probably this: Revive your Prusa Mk3s with Klipper 1/5 – Flash Bootloader – MyRigs

I never had such hardware.

5

FYI, Arksine also provided another link describing the solution: Lost communication with MCU and MCU shutdown: Timer too close after updating - #3 by Arksine

Note that print failures will continue to be a problem until the underlying issue with the usb chip is addressed.

-Kevin

6

Firmware shutdown twice this morning so I tried to fix the usb chip using the link provided.

GitHub - PrusaOwners/mk3-32u2-firmware: Updated Atmega 32u2 Firmware for the Einsy Rambo

After connecting the wires between the i3MK3S+ board and the Arduino UNO, where do I enter the commands to backup the Atmega32u2? I opened a command prompt window on Windowx 11 but it does not recognize the avrudude command.

7

The tutorial link in the instructions is broken…

image
image2155×274 44 KB

I think this is where it was supposed to go:
https://support.arduino.cc/hc/en-us/articles/4733418441116-Upload-a-sketch-in-Arduino-IDE

You need ArdiunoIDE on your PC to load the sketch onto the Uno. AFTER the sketch is loaded proceed with wiring the Uno to your printer board.

8

OK. I have flashed a new firmware to Einsy using the following steps up to Verify the installation.

GitHub - PrusaOwners/mk3-32u2-firmware: Updated Atmega 32u2 Firmware for the Einsy Rambo

It seems to have verfieid but when I clicked Print from OrcaSlicer, I still get the:

Error uploading to print host:
Connection timed out. Please check if the printer and computer network are functioning properly,
and confirm that they are on the same network.

I have been unable to print directly from the slicer for 1-2 months already.I thought flashing the new firmware would help but it looks like the problem has not been solved. What else can I try?

Previously, I followed the steps posted on Feb 12 to incrase the sending_interval to 100 but still not working.