When got back on the next morning to check on some of the suggestions, I noticed that Octoprint reported that it had lost connection with the printer with an error related to something else taking the port. Basically I left it overnight while I waited for feedback from this forum. I will start off with a positive update that I am now able to connect to my MK3! The bad news is that I have absolutely no idea what changed to make it work. Very much appreciate the response and thoughts. There are also a few versions of the Prusa stock firmware that have some buffer issues which cause problems, there is a forum post about it: Happens regularly to me and then works fine. If it throws an error change the firmware to something else, change it back to the correct and hit "retest", most of the time this will cause it to fix and jump to the next stage of testing just fine. Make sure to pick the correct firmware type in the "Add Printer" options too and then test. Next - when setting up the printer under the USB Select the correct USB port listed (not the default one it picks, make sure to use a direct link to the tty/SO USB port) and also set the baud to 115200 for the Prusa MK3. This can cause noise and dirty signals depending on the power source and is also just annoying - I suggest at first taping over the 5V line, this made my USB in general so much more stable on all my 3D Printers. If you ever noticed when you switch the printer off but it's connected to your NUC and the printer screen or some sensors stay on - that is because it's leeching 5V. Take special note of the Solutions section where you void the "5v" line on USB adapters. It would be helpful if you could specify what NUC you have and how it connects - built in USB ports? How many are there? etc.Īnyway this article (it's for Raspberry but even if you use another NUC it applies): In my case there were a few things I did to drastically improve overall USB performance. I had and randomly have the issue(s) you describe primarily on printers running firmware that is older than Marline 2.0.x aka Marline 1.x like many printers do. A single RPi 2 (yes 2, not 3B or 4) is running 3 printers with 0 issues for 6 days and huge GCode files. RS is so much more stable and light-weight it's insane. Just ahead of the curve I'll tell you - it's worth it. Same scenario as you with several printers and I had to discover some fixes. Thanks in advance for any and all help figuring this - I am not official staff at all but I also recently moved my whole print farm to RS and love it. I did not find anything that pointed to a solution.
I have read through the FAQs and troubleshooting articles. The printer itself stays in a continuous reboot loop while the connection is attempted. Closing connection" This repeats every 2 seconds. The System Error reported "error: Reading serial connection failed: End of file. I have used all variants of the buffering options. I have also modified device/port info to match the physical usb address as well as the same ttyACM0 that works with octoprint. My first attempt at R-S connection settings
Octoprint connects flawlessly with the following settings Prusa MK3s connected via usb to Intel based NUC running Ubuntu 20.04.2 LTS So far I am not able to connect to my Prusa MK3s. I am a new user looking to move from Octoprint to Repetier-Server.
0 kommentar(er)
