Prusalink vs Octoprint for the MK4
I am currently running Octoprint with my MK3/S and it works fine. I built a plug-in to turn off all the power after a print is finished. With the Pi and Octoprint, this is fairly easy. I am using a Creality enclosure, and I get good prints, even with PETG.
Anyway, I ordered an MK4 and an XL, but I don't expect them any time soon. I do have a couple of questions:
1) Can you use the XL and MK4 with Octoprint? I know Prusa seems to have that capability built into the printers, but there doesn't seem to be much documentation on how to use it nor on how to connect a camera, or how to do custom things with it, like shut off power if things get too hot (enclosure plugin).
Is it better to stick with Octoprint, or try to use Prusalink to run the printers? I like the ability to watch the printer working remotely that Octoprint lets you do.
Steve
Senior Life member of IEEE.
RE: Prusalink vs Octoprint for the MK4
The MK4 doesn't really support printing via USB. I think some people have been using OctoPrint, but for me, I don't think it is viable right now because of the following limitations:
- The filament runout sensor doesn't work when printing via USB - once filament runs out, the printer just continues on printing air
- Pause print (`M601`) doesn't work
- The Prusa firmware doesn't go into "print mode", so you cannot manage the print from the printer's LCD. This includes canceling, pausing or tuning the print, or seeing progress.
- You have to disable WIFI on the MK4 for OctoPrint to connect. (Alternately uncheck "Request exclusive access to the serial port" in OctoPrint, but I'm not sure if this causes other problems.
- Since this isn't really supported by the firmware, other bugs may occur. When testing, I had to hard reset the printer's firmware a couple times when it got into a bad state.
So I think your best bet will be Prusa Link/Connect unless Prusa changes their mind about supporting USB printing.
RE: Prusalink vs Octoprint for the MK4
I used OctoPrint with my MK3S+. I figured once I got my MK4 I’d right away have to work on hacking some other solution. But I’m “happy enough” using Prusa Connect - my needs are simple. The camera setup in Connect is too limited so instead I just use a cheap web cam check on prints using it’s app. You can find some rather “warm” threads on the forum regarding the limitations vs OctoPrint.
RE: Prusalink vs Octoprint for the MK4
For me, I just plugged my Octopi into the MK4 usb-C, and it worked right away with no adjustments needed.
I never turned on the WiFi on the printer, but have seen the print keep going when filament runs out. You can cancel and move the tool head from octoprint if needed, just like before.
RE: Prusalink vs Octoprint for the MK4
Hi, seems that the issue with USB-C port is solved with recent firmware versions. I have active WIFI and PrusaLink running and can still print via USB-C connection without any issues.
RE: Prusalink vs Octoprint for the MK4
I realized that most stuff is still working using octoprint, but its way slower then the prusa ways of printing.
RE:
I realized that most stuff is still working using octoprint, but its way slower then the prusa ways of printing.
What? Where do you see an increase in time? I see no time difference printing the same model from USB stick vs Octoprint. All Octoprint does is spool the exact same Gcode to the printer, how would it print slower? Please give some details, as if you're seeing slower printing via Octoprint then something is amiss with the configuration.
RE: Prusalink vs Octoprint for the MK4
I realized that most stuff is still working using octoprint, but its way slower then the prusa ways of printing.
What? Where do you see an increase in time? I see no time difference printing the same model from USB stick vs Octoprint. All Octoprint does is spool the exact same Gcode to the printer, how would it print slower? Please give some details, as if you're seeing slower printing via Octoprint then something is amiss with the configuration.
my last print should run ~1h but took ~2h and also I noticed that it doesn't run smooth.
But I had prints in the past days where I didn't noticed a big time difference, its pretty strange.
RE: Prusalink vs Octoprint for the MK4
Hmm have you tried running via usb incase it's the slicer giving wrong estimate
Please help me out by downloading a model it's free and easy but really helps me out https://www.printables.com/@Hello_474427/models
RE: Prusalink vs Octoprint for the MK4
Hmm have you tried running via usb incase it's the slicer giving wrong estimate
it's about printing by octoprint 😉
Printing by usb/prusalink/prusaconnect is correct
RE:
my last print should run ~1h but took ~2h and also I noticed that it doesn't run smooth.
But I had prints in the past days where I didn't noticed a big time difference, its pretty strange.
I have never seen the slicer estimate as very accurate. The only way to compare would be to print the same sliced Gcode from USB stick, then from Octoprint, and compare the actual time of each.
But you also mention "doesn't run smooth". What type of device is running Octoprint? I have seen cases where high resolution gcode can cause "stuttering" if Octoprint is hosted on a less capable board, like a pi zero. However, I have never seen that issue on a Pi 3 or better. A poor cable could cause that as well, but that would show up in the Octoprint UI as a high "resend ratio" (directly under the "State:" frame in Octoprint UI).
RE: Prusalink vs Octoprint for the MK4
my last print should run ~1h but took ~2h and also I noticed that it doesn't run smooth.
But I had prints in the past days where I didn't noticed a big time difference, its pretty strange.
I have never seen the slicer estimate as very accurate. The only way to compare would be to print the same sliced Gcode from USB stick, then from Octoprint, and compare the actual time of each.
But you also mention "doesn't run smooth". What type of device is running Octoprint? I have seen cases where high resolution gcode can cause "stuttering" if Octoprint is hosted on a less capable board, like a pi zero. However, I have never seen that issue on a Pi 3 or better. A poor cable could cause that as well, but that would show up in the Octoprint UI as a high "resend ratio" (directly under the "State:" frame in Octoprint UI).
No its a Pi4, it drives the mk3s+ before long time and has no issues. It looks like the printer handles the gcode faster than octoprint is aware of.
RE: Prusalink vs Octoprint for the MK4
No its a Pi4, it drives the mk3s+ before long time and has no issues. It looks like the printer handles the gcode faster than octoprint is aware of.
That's odd, if it communicated fine with the MK3S+ then it should communicate fine with the MK4. I haven't experienced anything like that (I also have Octoprint on a pi4), nor have I seen any other reports of "stuttering" or slow transmission with the MK4 either here or on the Octoprint forum.
You seem satisfied with the alternatives, so I don't know how much more effort you want to put into finding the problem. If you do want to investigate further, I can think of a few possibilities:
- Try another cable. Cable problems would probably show up as a high "resend ratio" in the Octoprint UI, though, so unless you see high numbers there then the cable is probably okay. But since it is a different cable than you were using with the MK3S+, it is worth checking.
- Do you have wifi enabled on the mk4? I know there were early reports of conflicts between the wifi module and the usb-C port. Later reports seem to indicate that has been resolved, but you might try disabling the mk4 wifi to see if that resolves printing via the usb-C port.
- Try Octoprint in "safe mode". Despite being a branch of Marlin, the MK4 firmware doesn't currently report all the data that the MK3 did over the serial connection. It is possible you have a plugin that is expecting data the MK4 isn't yet providing, and then malfunctioning in some way.
If none of that helps -- and you still want to get your MK4 and Octoprint working -- drop by the Octoprint forum and post in the Get Help section. Lots of really experienced and helpful folks there that can help find the issue.
RE: Prusalink vs Octoprint for the MK4
Oh the Cable is a good point, I'm not sure whats going on there, because I think not every print has such issues about the time.
But I like octoprint, because of statistics/filament tracking and cancel objects.
Currently my solution would be, wait and see 😀
RE:
Oh the Cable is a good point, I'm not sure whats going on there, because I think not every print has such issues about the time.
But I like octoprint, because of statistics/filament tracking and cancel objects.
Currently my solution would be, wait and see 😀
Probably a good strategy. 🙂 I am hopeful that the missing firmware items (like the firmware telling a serial host that filament has run out, M117 handling, etc.) are going to be delivered in future firmware updates. Those are needed for any serial host (including, but not limited to Octoprint) to handle certain events. I am still giving Prusa the benefit of the doubt here that they are prioritizing things like reboot loops, lockups, and input shaping right now -- and hopefully when those are resolved, the serial host interactions will get some love.
RE: Prusalink vs Octoprint for the MK4
did you just use a USBA to USB C cable? anything special?
For me, I just plugged my Octopi into the MK4 usb-C, and it worked right away with no adjustments needed.
I never turned on the WiFi on the printer, but have seen the print keep going when filament runs out. You can cancel and move the tool head from octoprint if needed, just like before.
RE: Prusalink vs Octoprint for the MK4
Thanks. I haven't gotten the MK4 yet, but my mk3 works great with Octoprint.
I have never gotten the filament runout sensor to work properly. Filament runout doesn't stop the printer, so I just quit using it.
Senior Life member of IEEE.
RE: Prusalink vs Octoprint for the MK4
Nothing special required. Just a USB-A connector at the Pi end, and a USB-C connector at the printer end. I am using this one.
did you just use a USBA to USB C cable? anything special?
RE:
did you just use a USBA to USB C cable? anything special?
No just a simple A->C cable of a phone. Now I have no issues beside the known octoprint issues (no filament sensors)
RE: Prusalink vs Octoprint for the MK4
Sounds like a bad cable. Printing via Octoprint over USB should have absolutely no effect on on print performance. You can improve speed with ArcWelder and MeatPack.