RE: Prusa MK4 & Octoprint
So this firmware has all interesting reporting features not compiled in (even if these are inside of source code) like:
Cap:PROGRESS:0 Cap:BUILD_PERCENT:0 Cap:AUTOREPORT_SD_STATUS:0
but manual M27 is supported at least. Could you send octoprint.log* from that time, too? I wonder if it contains anything about "autoreporting".
OctoPrint has functionality to automatically poll (via M27) the status of sd priting (it's position in bytes; not position it time but that's better than nothing).
It should activate it if "SD status interval (polling) s When printing from the printer's SD" (Settings->Serial connection->Intervals & timeouts) is set to > 0 (default is 1s) and if it doesn't detect autoreporting.
RE: Prusa MK4 & Octoprint
I just repeated the same print with that option set to 0. Both log files are in the zip.
RE: Prusa MK4 & Octoprint
Here is the photo of the print job with color change that I did on the MK3S+ and the MK4 via Octoprint.
RE: Prusa MK4 & Octoprint
Set to > 0 was supposed to mean "bigger than 0" (default 1s was ok).
Anyway these settings don't matter if printing is done via USB and not from SD card, doh.
OctoPrint should calculate internally where it is in g-code file and show that as progress.
Could you try starting OctoPrint in safe mode and print from there? (power icon -> "Restart OctoPrint in safe mode"). I see no reason for it to not show printing progress with MK4 when printing over USB (other that some plugin breaking this, like PrintTimeGenius). Safe mode will not load plugins, so that's a good test.
RE:
The mouse-over info for that option says that a value of 0 will force polling. I thought that was the intention. It was on 1 before. Should I repeat the print with another value greater than 1 s? No problem at the moment because I have completed all the prints that I wanted so far. Not sure if the guys at Hermes will find another reason not to deliver my enclosure today that was announced at first for delivery on Saturday.
RE: Prusa MK4 & Octoprint
I will repeat the print in Safe Mode, but I need my coffee first! 🙂
RE:
So here are the logs from Safe Mode. You mentioned "not showing progress". Perhaps this is a misunderstanding. Octoprint does show the progress of the print job, just the display screen on the MK4 does not show progress when printing from Octoprint.
RE: Prusa MK4 & Octoprint
Not showing on LCD is because that functionality from MK3* firmware is missing in MK4 firmware.
Your serial.log files show that M73 PX (where X is % progress) is sent to printer, printer in theory supports that:
but doesn't do anything with that (it should show that on LCD).
There is more missing from MK3 firmware like M73 reporting back to host over serial:
https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/189
M117 seems also not supported on MK4, so no way to workaround this via octoprint plugin.
New firmware unfortunately lacks a few features that were available on 8bit firmware 🙁
RE: Prusa MK4 & Octoprint
Thank you. We'll have to wait and see. So far the usual things for me seem to work. I will try out more things in the coming days. Filament runout without losing connection seems to work, just tested with color change in the g-code, but not with actual runout yet. I will also test if Octolapse works with this. More rivets ... 🙂
RE: Prusa MK4 & Octoprint
I'm honestly now thinking of cancelling my preorder, not because of M117 not being supported, but because if such a basic command isn't supported and hasn't been added in the last 5 years, I'm wondering what else is not supported and will never be.
This is quite worrisome and I'm also starting to get fed up by the radio silence from Prusa.
RE: Prusa MK4 & Octoprint
The problems with Octoprint seem to be marginal compared to the yammering that is going on about the transfer speeds in the threads about PrusaLink and PrusaConnect. I think the missing support for the M117 command was referring to the MK4, not the MK3*?
RE: Prusa MK4 & Octoprint
The MK4 firmware doesn't support host communication (Octoprint "M876 P1") at the moment. This means that filament run outs don't get communicated to the host. If an M600 is already embedded in the gcode coming from host then it will prompt a filament change. I'm interested to see if crashes are detected or if the printer simply continues printing.
RE: Prusa MK4 & Octoprint
I had one crash with something being in the way of the bed. The printer just went on with a layer shift. But that was my very first print of the badge from the USB.
RE: Prusa MK4 & Octoprint
OctoPrint should calculate internally where it is in g-code file and show that as progress.
Or use the M73 plugin in Octoprint because the MK4 profile is set to emit them and Prusaslicer is about the most accurate I've seen for time estimates as long as you're not overriding speed at the LCD.
RE: Prusa MK4 & Octoprint
From my obervations over the last few days the progress values displayed in Octoprint are very accurate.
RE: Prusa MK4 & Octoprint
Same here. Octoprint itself works fine as long as you're not modifying gcode from it.
From my obervations over the last few days the progress values displayed in Octoprint are very accurate.
RE: Prusa MK4 & Octoprint
I've been through all this on the Octoprint discord. Nothing can be done to coax out the printer's display to show progress if the print was sent via host (e.g. Octoprint), if that's what you're referring to. At least not until Prusa gets their heads out of their butts.
OctoPrint should calculate internally where it is in g-code file and show that as progress.
Or use the M73 plugin in Octoprint because the MK4 profile is set to emit them and Prusaslicer is about the most accurate I've seen for time estimates as long as you're not overriding speed at the LCD.
RE: Prusa MK4 & Octoprint
Not at all what I'm saying. I'm saying if you're using Octoprint then why do you care if it shows progress at the printer? Just let Octoprint read the M73 updates from the gcode as it sends it to the printer and have the most accurate progress data already.
I've been through all this on the Octoprint discord. Nothing can be done to coax out the printer's display to show progress if the print was sent via host (e.g. Octoprint), if that's what you're referring to. At least not until Prusa gets their heads out of their butts.
OctoPrint should calculate internally where it is in g-code file and show that as progress.
Or use the M73 plugin in Octoprint because the MK4 profile is set to emit them and Prusaslicer is about the most accurate I've seen for time estimates as long as you're not overriding speed at the LCD.
RE: Prusa MK4 & Octoprint
It's not Prusa's responsibility to make things like Octoprint work how folks want it to. The MK4 works as-is out of the box. Prusa may step in and help, but, honestly, it's all open source so the Octoprint folks could step in themselves if they want/need something specific implemented in firmware. Sit down with their favorite IDE, make a branch, then PR it. If Prusa comes along and helps, that's great and going above and beyond, not "getting off their butts".
I've been through all this on the Octoprint discord. Nothing can be done to coax out the printer's display to show progress if the print was sent via host (e.g. Octoprint), if that's what you're referring to. At least not until Prusa gets their heads out of their butts.
OctoPrint should calculate internally where it is in g-code file and show that as progress.
Or use the M73 plugin in Octoprint because the MK4 profile is set to emit them and Prusaslicer is about the most accurate I've seen for time estimates as long as you're not overriding speed at the LCD.
RE: Prusa MK4 & Octoprint
While that's absolutely fair, they did create an expectation by supporting it in the Mini then saying this was basically the Mini's firmware. So I could see a slight argument for it being an expected feature and wouldn't be surprised if it's on their todo list but not a priority since this printer does support Link and Connect out of the box.
It's not Prusa's responsibility to make things like Octoprint work how folks want it to. The MK4 works as-is out of the box. Prusa may step in and help, but, honestly, it's all open source so the Octoprint folks could step in themselves if they want/need something specific implemented in firmware. Sit down with their favorite IDE, make a branch, then PR it. If Prusa comes along and helps, that's great and going above and beyond, not "getting off their butts".