RE:
Thanks!
The MK3S had to be setup with a custom bounding box of X: 0/250, Y: -4/210, Z: 0/210.
Obviously the Z max needs updated to 220, but is the minimum for X, Y, or Z different than the MK3S?
The Mini had X: 0/180, Y: -3/180, Z: 0/180.
RE: Prusa MK4 & Octoprint
The Z speed increase is mainly to impress people for demos on YouTube 😉 (look how fast it goes!!!), during printing i won't do much, I think. 🙂
I think there will be a lot of updated guides and specs in the next weeks, but just to get going this is probably enough.
RE: Prusa MK4 & Octoprint
Dont worry... even a raspberry pi 2 is not gonna be as slow as transferring files over wifi or ethernet to the printer.
The speed its using is something similar to a LAN party in the 90´s, its embarrazing to even think to ship units with that p** poor performance on wifi and cable.
1. its 2.4 ghz tech (not a good choice)
2. even low budget stuff uses better performance chips for wifi. I can find several wifi controllers that allows for way better speeds than the supplied printer.
RE: Prusa MK4 & Octoprint
The -4 minimum value on the Y axis for the bounding box on the MK3S is probably to allow for the prime line at the front of the bed. The MK4 does the prime line in a different spot, near the printed object, not like the MK3, so it probably won't need the -4 explicitly.
RE: Prusa MK4 & Octoprint
@jeremy-3 Also, did you compare the hardware limits in octoprint for acceleration to the values in the profile for the MK4 in PrusaSlicer? There is certainly no risk that the values in octoprint will be too low! 🙂
I'm just now setting this up. Recognition seems to work okay. I did not want to copy over the profile from the pi on the MK3S+ but start with a clean system, so this will take a bit longer until everything works the same. But so far it is looking good and I don't have the same problem as Uncle Jessy on YT, who had the fans connected the wrong way around. 🙂
RE: Prusa MK4 & Octoprint
First print with octoprint on the MK4 is running. Procedure is just the same as with my MK3S+. So far at least ... 🙂
RE:
Great thought. Just entered them as;
- X = 200
- Y = 200
- Z = 40
- E = 100
RE: Prusa MK4 & Octoprint
I just left the values in Octoprint as is. The g-code is generated by PrusaSlicer and the limits are set there as well. The values in Octoprint have no influence on this. They would probably only if they were lower than the ones in PrusaSlicer.
RE:
Clearly there is no intent in slicing using Octoprint, but wasn't sure if those came into play at all when using manual controls with the interface. I'm guessing not as it should just be sending through the move command, not the speed.
RE: Prusa MK4 & Octoprint
Octoprint is just spooling the g-code file to the printer, it does not change it. Some people said there would be problems for octoprint plugins that insert commands into the g-code, like Octolapse does to move the toolhead to the side. So we should not use plugins like that (yet). Perhaps also not change the print speed or flow rate in Octoprint, but I never did that anyway.
RE:
I have been using OctoPrint with my Prusa printers for several years now. Although I did experiment with PrusaLink on my MK3S+ for a while, I found that I still prefer using OctoPrint (PrusaLink and Prusa Connect miss many useful features). Therefore, I plan to continue using OctoPrint even with my new MK4 printer.
I am curious about whether the MK4 experiences the same problem with non-updating printing stats during USB/OctoPrint printing as the MK3. If there is an owner of an MK4 who could check this for me, I would greatly appreciate it.
RE: Prusa MK4 & Octoprint
Running this setup since yesterday. What do you want to know or see (screenshots)?
I can just say that the screen on the MK4 does not show any info about the progress of the current job that was started from Octoprint. The screen on the MK3S+ does that. But as I monitor this from my PC in the next room, this is okay for me so far. Everything (so far anyway) from the Octoprint interface behaves the same as the MK3S+.
RE: Prusa MK4 & Octoprint
@walter-layher thank you - I mean if the overall printer stats (Statistics-> Filament used and Print time) are being updated while printing from OctoPrint (that doesn't work on MK3S+ - I never print anything from the SD card, so my MK3S+ still shows zeros and I'm curious if this issue has been resolved in the MK4 firmware)
RE: Prusa MK4 & Octoprint
The display for the amount of used filament does not work, shows 0. On my MK3S+ it sometimes shows a value that is not zero, but that is useless in general. I rely on the displays for time, gcode and layer time of the dashboard plugin, which is the same on both printers and corresponds to the real job progress. And I have a camera where I can see the spools from the next room.
RE: Prusa MK4 & Octoprint
Just a quick note: I received my MK4 2 days ago and just connected an old Raspberry Pi 3b to it yesterday running OctoPrint. Printing did just work out of the box and the print finished without any issues - no special settings or anything needed, everything with auto detect. I expect part of the problems people might have being bound to the cable you are using. There are some "charge only" USB type A to USB C cables out there that for sure will not work.
Regardless the clean print, the whole integration still seems to be shaky. The MK4 did display its normal main menu during the print, meaning it did not switch to this OctoPrint screen it does in the MINI for example. This means I could have made things break here. Also this means the tuning menu is missing, which you normally have during the print.
Anyways I tend to keep using OctoPrint for now, as it still is superior to PrusaLink/Connect, if only for the good camera support (the missing camera support was the main reason I did set this up while a new Raspberry Pi 4 is still missing). So I hope Prusa/OctoPrint gets the remaining issues solved soon.
RE:
Has anybody using the MK4 with Octoprint observed so far what happens if the filament runs out? On my MK3S+ this is no problem: the printer goes beep, I change the filament via the knob on the printer screen and the print continues, no problem at all. But I somehow expect this will not work for the MK4, would be too easy, right? 🙂 The MK4 does not show any progress or info about the running print when printing from Octoprint like the MK3S+ does. You can see the realtime info from the sensors in the menu, but no job progress.
I also saw this morning that when I performed a filament change on the printer before a print job, that this caused a disconnect from Octprint and I had to perform reconnect. So I expect that filament changes during a print will probably not be a pleasant experience and should be avoided for the time being ...
I will try to print something with a filament change added in PrusaSlicer and see what happens then. Will report back ...
RE: Prusa MK4 & Octoprint
Would be nice if you could enable serial.log logging in octoprint, restart octoprint (so initialization is also logged in), send some short (like 1 minute) print and publish serial.log (ssh pi@ip; file is as ~/.octoprint/logs/serial.log) file somewhere. That would be useful for seeing what printer reports to octoprint, what's put into serial from printer while print happens etc.
RE: Prusa MK4 & Octoprint
Yes, that is a good idea. I'll do after the print that is currently running. In about 4 hours or so. I'll print a few orange push rivets for the enclosure. 🙂
RE:
@arek Okay, here is the serial log of my "riveting" experience printing one of these. I had enabled the serial log before powering the Pi and the printer down. Then I powered on the printer and the Raspberry Pi together via a socket switch. Autoconnect to printer was not enabled, I clicked on "Connect" and Octoprint connected at the first try. Then I sent the print job over from PrusaSlicer and started the print.
If you need any more info or want me to try something else, just ask.
RE: Prusa MK4 & Octoprint
I just started a print job that contains a filament change that was setup in PrusaSlicer. Behaviour was just the same as with my MK3S+. Extruder moved to the side of the bed, the printer went beep and demanded that I changed the filament. Everything went smoothly, the print went on and the printer was still connected to Octoprint. Looking good! 🙂