Basic Information:
Printer Model: Elegoo Neptune 3 Pro
MCU / Printerboard: stock mainboard
Host / SBC: Raspberry Pi 4 over USB
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:
I’ve been encountering a pretty weird issue lately. I recently moved and connected my printer to a different wifi than it had been prior. I had no issues with this, and the printer worked as normal. I then would notice that during a print, I would no longer be able to connect to the printer (mainsail could not connect to Moonraker). The print would continue with no issues, and after a day or two it would reconnect. A couple print attempts in, I had noticed that the printer began having mcu ‘mcu’: Unable to connect errors. When I noticed these, I would simply firmware restart and all was well after a few minutes. The other day I started a temp tower to run, and the connection dropped as it usually did. The print continues, and I thought nothing else of it. It took about 3 days to connect back to the printer, and ever since then I have been unable to get past the mcu ‘mcu’: Unable to connect errors.
Some things I thought of to help narrow it down:
There was no power outage or brown out in this timeframe
Nothing has been unplugged since then
The printer itself has been powered off once between the print finishing and the printer reconnecting
I do not have Ethernet to test this out
There were no changes to any config files
In an attempt to remedy the issue, I fully updated everything in the mainsail update manager
logs-20240729-194031.zip (8.1 KB)