One of our library branches has the Mini 3 and out of the box it was working fine, not issues that was reported to me… However, I’m getting reports from that branch that the machine is having constant issues with Moonraker and Klipper disconnecting.
According to the branch they ran into the errors 3 times in a row while trying to print something for a patron. Previously they have done multiple restarts of the machine and sometimes when these errors occur the system will retry on its own (with Moonraker coming back up but Klipper needing several more tries).
Now I’m not at that location right now so I’m looking for any ideas of what we might do to solve this issue before heading out to that location to troubleshoot?
Below is what they have told me along with a photo of the error on the machine:
I have some bad news about the 3D printer…It has quit with this error three times in a row. I mentioned before that it required multiple system restarts to function after it turned on and sometimes after printing. It says “Moonraker: disconnected, Klipper: disconnected” but the machine will retry them on its own, and the Moonraker comes back after the first try. The Klipper takes more than one retries. A few times, it would do it mid-print (showing the error message in the picture) but usually not more than once. Today, it seems to not want to print at all.
I tried looking online, and the popular answer is that it’s an issue with the usb cord, which we don’t have, or the Klipper needs updating, but the machine says it’s up to date. However, the USBs have a weird thing too. When connecting the USB to the Surface, it claims that there’s an error that needs fixing, but says no errors were found after scanning and repairing it…This could potentially be related?
Some info here:
Timeout with MCU / Lost communication with MCU - Knowledge Base - Klipper
If you’re not having problems with the display, the other MCUs involved in the Mini3 that would most likely have intermittent loss of communication would all be in the toolhead. Loose harness or bad wiring would be the first thing to be looking for.
So far what I’m seeing happening
Turning on the machine gives the issue for both Moonraker and Klipper. Moonraker solves itself but Klipper has to restart itself before going to the menu screen. I took a look at the wiring around the toolhead and nothing appears to be loose (disconnected and reconnected a few things at the toolhead). When printing I’m being told by staff that at around 30 minutes to an hour when it also decides to give the error as well (did a rocktopus as a 34 minute print according to cura LE, mini 3 screen said print took 43 minutes, no error). One of the thoughts is maybe something with the wifi connection, though I have my doubts since it doesn’t seem like Moonraker/Klipper need a wifi connection at all times? The staff did say when the prints do stop because of the error that the machine does go offline (disconnects from the network).
When looking at the notifications after startup, this is what I’m seeing (this was before and after prodding around the toolhead’s connections)
You might have a problem with the CB1 or Manta board.
The screen is essentially a BTT HDMI5 with klipperscreen installed. Not sure what customizations exist beyond the firmware and graphics on the board, but klipperscreen does not connect directly to the board for communication (just power). Everything is done through the network via moonraker api running on the CB1 board.
Klipper runs on the Manta board doing the direct control of the printer.
Moonraker is the interface layer between the network and Klipper and runs on the CB1. Mainsail also runs on the CB1, providing a web interface for control/configuration of the printer.
Klipperscreen on the HDMI5, giving you a GUI to control the printer.
Since the Mini3 runs Mainsail, connecting to the printer directly in your browser may give you more detailed error information, and access to the logs to see what errors are occurring.
Okay so I may need a little more info on accessing that. This is our system’s first Mini as we are used to troubleshooting the Taz 6. I am wondering how problems are happening after only having the machine running for a month with no modifications made to said machine on our end.
If it’s that new, Lulzbot’s support really should be handling this.
I don’t have any hands-on with the Mini3, but pretty extensive experience with the Mini2, Taz6, and Taz Pro.
Hmm alright I guess next step will be support as soon as I hear back from the branch that has the machine
