Prints crashing, "MCU shutdown"

General Discussion
1

Basic Information:

Printer Model: Ender 3 Pro 2020
MCU / Printerboard: BTT SKR Mini e3 V1.2
klippy.log

I had to delete a small block from the middle of klippy log because of character limit. This is the 4th time my print has crashed in the middle. The error message on mainsail.xyz was not helpful and just said “mcu shutdown, restart firmware to reconnect.”

I’m running klipper on an eMachines T3612. Is it possible I’m just maxing out the computer?
Thanks in advance

EDIT: FULL KLIPPY LOG LINK IS IN PARENT POST

2

Please upload the klippy.log here. That site you used modifies too much.

If it is too long, you can zip it.

And please the full log

3

The full log is 28mb, too big to upload here. Pastebin won’t take it, the site I used is the first I tried that actually gave a helpful error and told me it was 750 chars too long. I zipped and tried to upload it here and the site says “sorry, an error occurred.”

The section I removed was about 800 characters from the middle of the block.

I left intact the end of the log, which I assume is where the fatal error is occurring.

4

It crashed again on the same print in a different spot. This time Mainsail told me the extruder wasn’t heating at the expected rate. I already ran PID autotune after the first time I received this error. What else could be causing it? Discourse is still giving me the unspecified error when I try to upload klippy log directly

5

zip the Klippy.log file, it will bring it sufficiently down in size to post here.

1 Like
6

As in a previous comment, I have zipped the klippy file, and when I try to upload it, this website gives me an error that says “Sorry, an error has occurred.”

7

What is the process that you are using?

  1. If you have a Windows PC, then you should right click the file and select “Send to” and then “Compressed (zipped) folder”.
  2. “Reply” to this comment.
  3. Drag the zipped file (which looks like it’s a folder with a zipper on it in Windows) over the new reply.

I just tried it with a klippy.log from one of my printers (which is 43MB)
klippy.zip (4.1 MB)

If you have a Mac or Linux system, the process is very similar.

8

I mean yeah, I know how to upload a file to a reply. But as I keep saying, whenever I try to, this website gives me an unspecified error. It’ll upload to 100% and then pop “sorry, an error has occurred.” Not sure how else to get you guys the klippy.log without linking it, as I already did in the original post…

9

I just downloaded the one that you posted at https://rentry.co/kwsuu and it’s 192k long, no zipping.

klippy.log (192.9 KB)

What browser are you using and what operating system?

Please try again with the full log (zipped).

10

I copy/pasted the contents into the webpage. I don’t know what to tell you.

I’m using Windows 10 and up to date Firefox. No matter how many times I try to upload the full log (zipped) I get “Sorry, an error has occurred.” obviously uploading it here isn’t working.

Let’s try this: OneDrive

I don’t think you need to waste time scratching your head about filesize. Like I said, I copy/pasted the contents of klippy.log into the hosting site. Obviously that’s not working for people for some reason.

The OneDrive link I’ve just shared will bring you to webpage where you can download the 28 MB Klippy.log. If you need the exact filesize for some reason, it’s technically 27,693 KB.

11

Let’s first figure out why you’re saying that the file is 28MB in size, but all I’m seeing is 192k. Where are you getting the klippy.log file in the first place?

In Mainsail, you should be getting it from the “Machine” page and then from the block entitled “Log files”. It is produced when you click on “Klipper”. Is this where you’re getting it? What size file do you get?

Now, have you tried uploading the file using Chrome or Edge? I wonder if there is a settings issue with Firefox.

12

I know how to get the klippy.log. That’s how I got it to share here in the first place.

Yes, that’s where I’m getting it. The filesize I get is 28MB. Issues were in sharing the file, not obtaining it. Proper link is now reflected.

No, I have not tried using Chrome or Edge. I don’t use chromium browsers.

13

I’m not an expert at reading klippy.log files but two things jump out at me:

  1. Your Moonraker installation is “dirty”. Have you modified it in any way? Generally, results are suspect when you have applications marked as “dirty”.
  2. In the second “Stats” line (58259.0), your send/receive sequence numbers are different (send_seq=44978 receive_seq=44977). Does this happen every time you try and start a print?

Maybe somebody with more expertise will look at this.

Then again; maybe they won’t. I took the time to download (twice) what you put up on different sites and load it into a browser. I know the developers have tools that automate this task as well as run analysis tools on the klippy.log’s contents. Since you haven’t provided the klippy.log on the page in the manner they have requested it may be some time before they get around to it.

A good rule of thumb in life is to make it as easy as possible for the people who are going to help you. I highly recommend that you upload the zipped klippy.log file into this threat using Chrome or Edge.

14

I’m doing the best I can mate. I can’t help that this site won’t accept my klippy.log. That’s literally not my fault. I did not write this website.

I’ve literally provided links to download the log. I can’t exactly do anything else if this website won’t accept the upload, can I? Not quite sure what else you expect me to do. Not asking you to wipe my ass.

Hopefully someone with more expertise can chime in and we can stop going back and forth about uploading the klippy.log which has already been sitting in the parent post for hours.

Previously, I took the time to describe the error this site gave me (in 3 separate posts) and you were still asking me to upload it here. A good rule of thumb in life is to read the messages people have specifically written to you in full before proceeding.

  1. I’ve added the IP addresses Mainsail needs to work. Kiauh installed it.
  2. yes, that appears in multiple klippy.logs from failed prints
15

All I can say, again, is the Klipper support people (who aren’t paid, they’re doing it out of the goodness of their hearts) are quite insistent that the klippy.log file of the problem system is uploaded to the site. You got that message very clearly from one of the senior guys as well as from me. I, and many others, do not have a problem uploading their klippy.log files on this webpage and I suggested using Chrome or Edge because I use that without any issues to upload log (and other files).

Chances are somebody further up the food chain will reply and try to help you out because they are really good people here and will work with you despite your attitude.

Bonne chance, mon ami.

16 
b'Got EOF when reading from device'
Stats 7195.8: gcodein=0  mcu: mcu_awake=0.011 mcu_task_avg=0.000020 mcu_task_stddev=0.000042 bytes_write=3720879 bytes_read=2325037 bytes_retransmit=0 bytes_invalid=0 send_seq=132408 receive_seq=132408 retransmit_seq=0 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=561 freq=71997602 sd_pos=1006749 heater_bed: target=75 temp=75.0 pwm=0.004 sysload=2.05 cputime=215.268 memavail=541956 print_time=6896.873 buffer_time=2.685 print_stall=0 extruder: target=250 temp=250.5 pwm=0.310
Stats 7196.8: gcodein=0  mcu: mcu_awake=0.011 mcu_task_avg=0.000020 mcu_task_stddev=0.000042 bytes_write=3720879 bytes_read=2325037 bytes_retransmit=0 bytes_invalid=0 send_seq=132408 receive_seq=132408 retransmit_seq=0 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=685 freq=71997602 sd_pos=1006881 heater_bed: target=75 temp=75.0 pwm=0.004 sysload=2.45 cputime=215.282 memavail=542108 print_time=6897.196 buffer_time=2.008 print_stall=0 extruder: target=250 temp=250.5 pwm=0.310
Stats 7197.8: gcodein=0  mcu: mcu_awake=0.011 mcu_task_avg=0.000020 mcu_task_stddev=0.000042 bytes_write=3720879 bytes_read=2325037 bytes_retransmit=0 bytes_invalid=0 send_seq=132408 receive_seq=132408 retransmit_seq=0 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=1272 freq=71997602 sd_pos=1007143 heater_bed: target=75 temp=75.0 pwm=0.004 sysload=2.45 cputime=215.300 memavail=538028 print_time=6898.868 buffer_time=2.679 print_stall=0 extruder: target=250 temp=250.5 pwm=0.310
Stats 7198.8: gcodein=0  mcu: mcu_awake=0.011 mcu_task_avg=0.000020 mcu_task_stddev=0.000042 bytes_write=3720879 bytes_read=2325037 bytes_retransmit=0 bytes_invalid=0 send_seq=132408 receive_seq=132408 retransmit_seq=0 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=1353 freq=71997602 sd_pos=1007176 heater_bed: target=75 temp=75.0 pwm=0.004 sysload=2.45 cputime=215.313 memavail=535304 print_time=6899.232 buffer_time=2.041 print_stall=0 extruder: target=250 temp=250.5 pwm=0.310
Timeout with MCU 'mcu' (eventtime=7199.754965)
Transition to shutdown state: Lost communication with MCU 'mcu'

See Got EOF when reading from device

1 Like
17

Thank you Sineos.

At this point I’ve wiped the host and started fresh with Lubuntu to minimize resource use - I also had a feeling I could be overloading the host’s processor. I’ve only installed a single instance of Klipper this time.

As of writing I am now able to finish prints. Updating in case this helps someone else troubleshoot

1 Like