RE: Prusa MK4 & Octoprint
I can't flash the firmware. The only serial ports offered are ones the developers used (Bluetooth-Incoming-Port (/dev/cu.Bluetooth-Incoming-Port) wlan-debug (/dev/cu.wlan-debug). rescanning does nothing. suggestions?
RE: Prusa MK4 & Octoprint
Finally!! Thank you to everyone at Prusa who got this across the finish line!
RE: Prusa MK4 & Octoprint
Finally!! Thank you to everyone at Prusa who got this across the finish line!
RE: Prusa MK4 & Octoprint
And one nice thing I just noticed (and also tested on the MK4): When printing from OctoPrint it is possible to cancel objects if the file contains the necessary information. So that feature is also usable with OctoPrint now, which is kind of really neat! 👍
This also tells me the current implementation handles way more compared to what the old MINI OctoPrint screen would do. I hope Prusa keeps adding features to the screen and keeps this up with what can be done while using USB printing. For now they have done a really great job bringing the MK4 experience to what the MINI was before plus the new things they did add in general. 🥳
Things that just work now (on MK4):
- The OctoPrint screen is finally available (like we used to have on the MINI)
- The printer knows it is printing, this also shows in the LED bar + PrusaConnect
- Cancel object just works - in general the "Tune" menu better matches USB printing
- Probably the filament sensor works (Have not run out of filament yet, but I expect this to work)
- Maybe more things I just did not notice....
Now I would suggest adding things people are used from the MK3 again - as the MK4 will still be compared to this printer. First thing on my wishlist would be those details about the printing progress (percentage, ETA and current/total layers), see https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/189 for details. Also I really don't care about the OctoPrint logo, just put a progress bar up there and everything is fine.
RE: Prusa MK4 & Octoprint
I have a filament runout yesterday, but unfortunately the printing was not paused. I think the runout monitoring doesn't work yet.
RE: Prusa MK4 & Octoprint
I just tested the filament running out using Octoprint, and it worked perfectly. The printer parked, unloaded the filament, asked if it unloaded properly, then asked to load new. So it seems to be working as it should, for me at least.
I have a filament runout yesterday, but unfortunately the printing was not paused. I think the runout monitoring doesn't work yet.
RE: Prusa MK4 & Octoprint
I just tested the filament running out using Octoprint, and it worked perfectly. The printer parked, unloaded the filament, asked if it unloaded properly, then asked to load new. So it seems to be working as it should, for me at least.
I have a filament runout yesterday, but unfortunately the printing was not paused. I think the runout monitoring doesn't work yet.
That's good to know. What version Octoprint you using?
RE:
Mine works, but not perfectly at all . It oozes and purges ont print after the change after I confirm the color is correct it purges more.
I just tested the filament running out using Octoprint, and it worked perfectly. The printer parked, unloaded the filament, asked if it unloaded properly, then asked to load new. So it seems to be working as it should, for me at least.
I have a filament runout yesterday, but unfortunately the printing was not paused. I think the runout monitoring doesn't work yet.
RE: Prusa MK4 & Octoprint
Would be nice to see Prusa firmware and Octoprint versions in these posts.
RE: Prusa MK4 & Octoprint
That's not necessarily an Octoprint problem... I see the exact same happening when I print a model with a manual color change without Octoprint - after acknowledging that the color is correct, some 4-5 centimeters of filament are extruded. Very, very annoying as it's not easy catching that thread and picking it off while the extruder whizzes over to the print...
Mine works, but not perfectly at all . It oozes and purges ont print after the change after I confirm the color is correct it purges more.
I just tested the filament running out using Octoprint, and it worked perfectly. The printer parked, unloaded the filament, asked if it unloaded properly, then asked to load new. So it seems to be working as it should, for me at least.
I have a filament runout yesterday, but unfortunately the printing was not paused. I think the runout monitoring doesn't work yet.
RE: Prusa MK4 & Octoprint
Confirmed filament run out working with Octoprint finally!! Versions: Octoprint 1.9.3 | MK4 Firmware 5.1.0 | PrusaSlicer 2.7.0
Also, yeah the behavior of the purging during filament switch is by design.
RE: Prusa MK4 & Octoprint
anything unusual in your settings? I am running Octo 1.9.3, Prusa MK4 5.1.2 and slicer 2.7.1, printing works well but I tried to check filament run out by cutting the feed above the extruder. First time I did this, printer recognized no filament and stopped and asked for filament change. I inserted filament and printer loaded filament but did not go back to print. Instead, just sat waiting; printer screen said waiting to confirm filament. Every time after that the printer continued to print without filament and no warning (either on printer or Octoprint); just continued running layers as if it had filament. The print screen in Octoprint did not allow me to pause/cancel the print. This had to be done via printer screen.
RE: Prusa MK4 & Octoprint
I tested filament runout on the MK4 with OctoPrint during the last few days to use up spools which had just a bit of filament left on them. Worked every time for me. MK4 paused, beeped and I just had to follow the instructions on the printer's display screen to continue the print with the next spool. No interaction in OctoPrint was needed and no message was shown there. The prints were all finished successfully. Every interaction for filament change happened via the display screen on the printer.
Did you install the printer profile updates that came with the last update of PrusaSlicer?
I am on the same versions of OctoPrint, MK4 firmware and PrusaSlicer as you mentioned above.
RE: Prusa MK4 & Octoprint
anything unusual in your settings? I am running Octo 1.9.3, Prusa MK4 5.1.2 and slicer 2.7.1, printing works well but I tried to check filament run out by cutting the feed above the extruder. First time I did this, printer recognized no filament and stopped and asked for filament change. I inserted filament and printer loaded filament but did not go back to print. Instead, just sat waiting; printer screen said waiting to confirm filament. Every time after that the printer continued to print without filament and no warning (either on printer or Octoprint); just continued running layers as if it had filament. The print screen in Octoprint did not allow me to pause/cancel the print. This had to be done via printer screen.
I don't think this is your problem, but the firmware 5.1.0 release notes advised adding some Gcode commands to Octoprint's "Gcode Scripts". Look under the section titled "Improved Octoprint Support" in the release notes: MK4 Firmware 5.1.0 Release Notes
RE: Prusa MK4 & Octoprint
Could be the reason why it worked for me. I already had the M601 and M602 commands there because I had copied the profile from my MK3S+ which had those inserted already.
RE: Prusa MK4 & Octoprint
Also, make sure that the filament sensor is actually working. Mine stopped a few days ago (and was stuck, so the printer thought that the filament was still loaded, while I already removed it). This would also cause the problem above with Octoprint not recognizing the filament run out (happened to me exactly like this).
After fixing the filament sensor, it worked again. However, the filament sensor is stuck again now, so there seems to be some flaws in the design (last time, only a very small filament particle was stuck).
RE: Prusa MK4 & Octoprint
Thanks for the help. I inserted Gcode as specified in 5.1.0 release notes. I am by no means an expert on coding but inserted M601, M602 and M604 in the locations noted. There was existing code in the "After print job is cancelled" box, so I inserted "M604"after the existing text on a new line. Ran the printer from Octoprint and when filament ran out, printer stopped and asked to remove filament from sensor. I pulled remaining filament from extruder and closed latch. Printer continued to say please remove filament from filament sensor. Rebooted printer. Did not change anything else in Octoprint or the printer.
Ran a print directly from flash drive in printer and when the filament ran out, the printer stopped and asked to change filament and after loading, it resumed print job without a hitch.
Scott, I did change the settings you recommended in thread regarding MK4 and Ocotolapse. Kinda stumped. Must be something in Octoprint.
RE: Prusa MK4 & Octoprint
Figured I should run a print from Octoprint one more time to check after print from flash drive. This time when the filament ran out it stopped, asked for filament change and after loading it resumed the print correctly. Hopefully the additional code or possibly removing filament from the nextruder solved the issue. Either way, thanks for your swift response and suggestions!
RE:
Figured I should run a print from Octoprint one more time to check after print from flash drive. This time when the filament ran out it stopped, asked for filament change and after loading it resumed the print correctly. Hopefully the additional code or possibly removing filament from the nextruder solved the issue. Either way, thanks for your swift response and suggestions!
Cool -- hopefully it's fixed, because I can't really think of anything else to try.
I re-tested mine just a couple minutes ago, since I haven't had a filament runout lately. Started a print from Octoprint and then cut the filament. Worked as it should: Moved extruder to the front-right corner, unloaded filament, waited for reload, purged, and went back to printing (I did have to confirm a couple operations with knob-clicks).
For reference or comparison, my current environment is as follows:
- MK4 firmware 5.1.0
- Octoprint 1.9.3
- PrusaSlicer 2.7.1, with configuration bundle 1.11.9
- Octoprint Gcode Script "After print job is paused" contains only one line, "M601"
- Octoprint Gcode Script "Before print job is resumed" contains only one line, "M602"
- Octoprint Gcode Script "After print job is cancelled" has the "M604" as the first line, before the default moves/cooldowns (not sure it matters whether M604 is first or last, but it seems to work fine as first line).
RE: Prusa MK4 & Octoprint
Guys, I would like to ask where did you get MK4 profile for octoprint?
I tried to create profile copying MK3 profile with different print volume dimensions (MK4 have 220mm Z and MK3 have 210) but when I tried to print from latest octoprint 1.9.3 I had bluescreen on prusa.
I had to disconnect USB and perform calibration and test as right after this incident my MK4 could not get first layer correct.
Thanks