3D Printing

Yesterday, I couldn't print on #4 due to filament clog or jam in the nozzle. I removed the feed gearbox mechanism and cleared the filament and reassembled it. When I restarted the printer to heat up the nozzle, an error message came up on the screen, saying that Klipper needed to restart and the firmware needed to be updated. I shut it down twice leaving it off for about 15 minutes each time, but the error message remained.

I'm hoping someone may be able to shed some light on this as I have no idea on how to proceed from here.

Nicholas suggested that it might be the USB cable to the print head?

Tim

I tried following the instructions online to fix the problem. Parts are on order.

More specifically i followed the instructions for the MCU protocol error and arrived at the System Starts Abnormally error.

https://wiki.qidi3d.com/en/X-Smart3/error

The part in ordered is a new EMMC module. I ordered 4 in case this happens again.

Thanks Grant. 😊

Printer 3 is now having communication issues as well. It quits giving the Klipper/Firmware error but it clears after rebooting. It failed 3 of the last 4 times I tried to print on it.

Perhaps it needs the same fix as #4?

Printer 3 has no hot end. I couldn't un-jam it. I will order more.

I installed the new EMMC modules on printers 3 and 4 but didn't follow the instructions saying I had to pre-program them. I kinda hoped that the part I ordered would just work.

I ordered 4 EMMC modules and need for someone to program all 4. We can keep 2 as spares.

This is the link to the instructions for the programming:

https://github.com/billkenney/revert_qidi_software/tree/main

Here is a video of someone suffering through the process.

https://www.youtube.com/watch?v=Q2OuJwvWVeg

I tried to follow the update instructions as listed, but when I installed Putty on my laptop, I could not communicate with #4's IP address. I powered off the printer and back on again, but still can't communicate with it.

I was able to see #1 and #2 printers with Putty, but #4 seems to have lost it's networking.

Perhaps our network guru (Nicholas?) can jump in with advice..