"feature request" show information's of prints from OctoPrint

[Strankler]

Description: While prints initiated from OctoPrint, the display shown no progress of the print, but only the home screen (plus temps, nozzle height, speed ratio and material).

Feature request: Show same information's in the display for prints initiated from OctoPrint as for print jobs from USB drive, at least progress in percent, printing and remaining time, like the MK3 does. Also the option to stop or pause the print would be great.

[Impatience71]

+1

I would also upvote this feature. Missing the octoprint features a lot !

[rainer1146]

+1

[Soulofdestiny]

Yes please!

[Jackjan4]

+1 Bump.

[getgray]

Octoprint full compatibility is a need not a want. Please implement ASAP

[ScottWell1]

+1

[WimRos]

+1

[ghoeffner]

Please implement this :) So much unused screen real estate during octoprinting!

[Jinra]

Having a 3+ year old issue for this feature doesn't bode well for the MK4. +1 anyway

[TheNore]

Would it be possible to Please consider this a higher priority? As more mk4 units are being shipped more octoprint users are becoming frustrated and loosing functionality they have had in the MK3 printers for years!

[ghoeffner]

Wait until you find out that the filament runout sensor doesn't work with octoprint anymore...

[fergymcferguson]

Nor can you see any of the files on the USB drive...

[beelsebob]

+1

[Ikario]

This is a must. I get that Prusa is interested in people using their Prusaconnect/Prusalink option but it is nowhere close to having the same features as Octoprint.

[jvasileff]

Pause print (M601 added by PrusaSlicer) also doesn't work. I just built my MK4 yesterday, and I'm pretty disappointed that OctoPrint isn't really usable with it.

[yahbluez]

i second that.

[goyetus]

Please Prusa, fix this or update. I have all my printers (mk3s+) with Octoprint. Prusa connect is not enough at this moment to change. Give us full Octoprint Support , or at least, fix the minimun ( filament change and on-screen info)

Thanks!

[tideline3d]

24x MK3 farm here looking to expand soon. MK4 will have to be off the list for refusal to support 3rd party integrators with basic telemetry. My entire production process is built around OctoPrint.

I realize Prusa and Octoprint aren't on the best of terms but consider your customers rather than FOSS ecosystem politics here.

[Madad1996]

Please fix, wont upgrade till i get fill Octoprint support.

[FliesWithWind]

+1

[rnbarrett]

Count me in the upvote support!

[osbock]

Upvote for me too! I just ordered the Mk4 upgrade, and had I known that Octoprint didn't work as well as it does on the Mk3, I would not have purchased. I want to support you, please support us!

[satchm0h]

+1

Please consider prioritizing support for the same interfaces/protocols/APIs the Mk2->Mk3 supported. Your community have come to rely on many FOSS solutions that build upon these!

[SalmonSays]

+1 for interest, this feels like a massive oversight in MK4 release.

[shalmi]

@Prusa-Support PLEASE FIX THIS. It may not be important to you, but it IS important to your customers!

[Monkopedia]

@Prusa-Support +1 to everything here. I back ordered an mk4 a few days ago, but now must consider cancelling it given the lack of support here.

[kukulin]

+1

[goyetus]

~~Not a single answer from @michalxfanta since 2020 , no response also from @Prusa-Support This is not the way~~

[hstag]

Prusa support responded. https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/189#issuecomment-1585703918

[getgray]

I just cancelled my orders. I'm seeing early adopters with issues, and Octoprint compatibility is a high priority for me. I don't want to spend a grand to get upgrades that come with downgrades.

[jim-roberts]

+1

PrusaConnect/Link is not a suitable replacement.

[Monkopedia]

I just rebased @coaxial 's PR #1497 and have it building, however I don't have a suitable printer to try it on. So if anyone here is brave and wants to test #3147, please do. Otherwise, I guess I won't cancel my order, and hope we can manage to fix this ourselves.

[jvasileff]

@Monkopedia I cloned your repo, but then discovered there are no instructions for flashing custom firmware to the MK4. I asked Prusa support via chat if it is possible, and the response was "I don't think is possible at this point".

Also note that for the MINI, the instructions say:

To flash your own (or a community-made) unsigned firmware, you’ll have to break the appendix on the logic board (called the Buddy board) and move the jumper in a correct position. Breaking the appendix on the Buddy board is irreversible and voids the warranty of your printer’s electronics.

So having a community fork won't help many people. We'll really need Prusa to help with this.

The earlier comment from Prusa Support isn't encouraging:

Our developers should stick to tight development plans at the moment but they will gladly look into this and other requests in the future. Until then, because the firmware is open source, I'm positive that the community's contribution can make a difference.

Ironically, this regression with the MINI and MK4 actually cuts off a massive "community contribution" in the form of OctoPrint, which adds a ton of value to Prusa printers. I hope I'm wrong, but so far it looks like they aren't really interested in community contributions in this area, or they'd spend a little effort helping to fix the firmware for the huge gain of OctoPrint support.

[Ikario]

People expect this machines to improve upon their predecessors and have the same features + improvements. If Octoprint compatibility was deprecated as a feature it should be clarified on their shop, but then again, the website advertises input shaping as a feature, so I'm not holding my breath on them either being up front about intentional lack of Octoprint support to push Prusaconnect/Prusalink or bringing that feature back any time soon.

[coaxial]

We've been making this point in this issue but also #283 (as the firmware doesn't support the "pause print" command either), or #1542 where the filament runout sensor still doesn't work with Octoprint.

It's been over 3 years now with no technical help or input from anyone at Prusa (other than the support comments saying that basically it's an out-of-scope, nice-to-have feature)...

Hopefully the fact that the MK4 has these issues too will bring more visibility to this issue as the Mini clearly isn't a priority at Prusa.

This is very frustrating and disappointing overall, I will very seriously consider alternatives to Prusa when buying my next printer as a result.

Edit to add: #334 has also been around for ever without any change on Prusa's side. This is standard in virtually any other printer no matter their price point, but not in the newer Prusas. M300 (play a sound) is arguably not as crucial as the other codes discussed in this and the other issue but still.

[marek26340]

+1

[kaydeeH]

Not that Prusa seems interested in dealing with this, but I'll throw my own +1 into this. When my MK4 arrived and I found out about the almost complete lack of support for Octoprint on the new printers, I was flabbergasted. HUGE functionality to cut. Please add this functionality asap.

[alexhocks]

+1 from me as well. This feature is essential for anyone doing a bit more than the occasional hobby printing.

[fergymcferguson]

Bump.

Thanks for your solicitations, our developers and the whole company have great consideration for the community. Our developers should stick to tight development plans at the moment but they will gladly look into this and other requests in the future. Until then, because the firmware is open source, I'm positive that the community's contribution can make a difference. 🙂

For the records, the cameras are supported via Prusa Link (MK3 + Raspberry) or Prusa Connect. Unfortunately, we still have a lack of documentation, but this was announced in the release logs, and here is a list of supported cameras. Alternatively, a "smart" camera device (smartphone, tablet, laptop...) can be connected via Prusa Connect very easily (QR code scan).

Michele Moramarco Prusa Research

The developer of Octoprint has commented on the Prusa forums: “ No, "they" do not. Let me tell you about the reality of developing OctoPrint.

There's at this point what could be considered hundreds if not even thousands of firmware variants out there. Vendors randomly break things left and right. But do they tell me or anyone else? Of course not! We usually discover that something is broken because some affected users show up in our forums, Discord or bug tracker and tell us that something is not working like it should. If we are lucky, they do so in a nice tone and collaborate with us to figure out WHAT exactly is broken and if there's an easy way to work around it on OctoPrint's side (preferably through a plugin because every single workaround that makes its way into core now has to be maintained there for all eternity). Sadly all to often however, we rather see entitled passive aggressive stuff like also visible here, where people treat us like we owe them our time and resources to make THEIR specific workflow work for them, for free.

It is not my job to keep OctoPrint compatible to Prusa Research's Marlin derivatives just as it is not my job to keep OctoPrint compatible to any other printer vendor's firmware derivatives. We have an established communication protocol for the serial interface between hosts and printers. THAT is what I have to be compatible to, everything else I do my best to find the greatest common divisor for, so that implementing one feature for one derivative doesn't break stuff for everyone else. And if one vendor decides to go out of their way to do things differently, well, that is their decision. Protocol extensions are of course always an option, but that's something that needs to be documented and also needs to be discussed so it doesn't break stuff for everyone else.

So, to sum things up here - no, as always there has not been any kind of communication here (just as there wasn't any for other developments in the past that then cost me an arm and leg in user support overhead). That is not my decision, that is Prusa Research's decision. My job is to keep OctoPrint working and keep improving it for hundreds of thousands of users out there, and only a fraction of those have a MK4 or another Prusa printer to begin with. Things work flawlessly for people who do not have a MK4, so whatever the issue is here, it very much sounds like it's a firmware issue specific to the MK4 firmware flavour. As always, I'm happy to assist the firmware devs in figuring out what's wrong if I get tagged in a public ticket somewhere (THAT is something I consider part of my job, within sensible limits), and if something more in depth is needed I'm also open to contracting work upon request, but that's all I can offer given my responsibilities towards ALL of OctoPrint's user base here.”

It sounds to me like the community is trying to contribute but have been unable to make any progress because of Prusa’s developers. C’mon guys - 2 years of this is outright ignoring what your users are asking for. Either flip the switch to enable the feature which is already available on MK3’s or let us flash our own firmware without voiding our warranty.

[ghoeffner]

^ Here is the original post: https://forum.prusa3d.com/forum/postid/662700/

[dMAC95]

I build farm software for a company that runs 100+ MK3s. We had a sizeable MK4 order placed and also received an early pre-built MK4 to run preliminary testing on. When we found out the MK4 didn't support host communications like the MINIs and MK3s do and also came to realize prusa wasn't prioritizing the development of it we canceled our order. I tried building custom firmware, but that's out of my league so now we have a spare MK4 collecting dust with a cut appendix.

[Monkopedia]

@dMAC95 Any chance you're looking to offload that mk4 to someone who is willing to do custom firmware development?

[dMAC95]

@dMAC95 Any chance you're looking to offload that mk4 to someone who is willing to do custom firmware development?

I'm not sure how to DM on github, but we may be interested. If you can build firmware to support octoprint I'll be sure that our business interests don't get in the way of it being released publicly.

[dMAC95]

Also I'd be interested in learning the basics of building that kind of firmware. In time I'd love to jump in on your Buddy pull request. I have a web application background, but I can figure things out with time and the right resources (if you have any guides that can point in the right direction)

[fergymcferguson]

This is the third oldest and most commented open feature request in this repo.

If you’re stalling to drive people to PrusaConnect/PrusaLink, I think the only thing you’re gong to accomplish is to drive people to other brands. How unfortunate when the community at large is already saying Prusa is falling behind the curve of innovation and this makes the newest flagship printer a downgrade for many.

PrusaLink is a joke in its current state and PrusaConnect is not much better (and I’m really trying to give it a fair shot here). If you want people to use Prusa’s solution for remote/farm management, it needs to be way better. Prusa is clearly limited in what they can do in terms of development since you’re sticking to your “tight schedule” and in the mean time users have to suffer. Octoprint works great because any dev can make plugins to add functionality instead of waiting for an official release from Prusa to add even the most basic features like a legitimate camera stream which vanilla Octoprint does.

I wish some of the prominent social media content creators would pick up this thread and start shining some light on this issue and maybe then it will get some traction.

[jvasileff]

so now we have a spare MK4 collecting dust with a cut appendix.

@dMAC95 do you have any more info about the appendix? I see where it is on the board, but is there also a jumper that needs to be set? I only found official docs for the mini.

[dMAC95]

so now we have a spare MK4 collecting dust with a cut appendix.

@dMAC95 do you have any more info about the appendix? I see where it is on the board, but is there also a jumper that needs to be set? I only found official docs for the mini.

I only had to cut the bridge to get it working. I also came across the same resources as you describing moving a board component to a different connection as with the MINI, but the MK4 board is similar to the MK3. I remember when I opened the MK4 the appendix bridge was within the two slot holes near to the top left of the board while it was still upright within the housing. I didn't need to remove the board to cut the appendix.

Also important to note that the custom firmware I built didn't boot, and while I wholly believed it wouldn't boot, I'm not ruling out that there may still be a component that needs to be physically moved. It did give me the prompt to install the custom firmware and didn't raise the error that the appendix wasn't broken though (as happened before I broke the appendix). Just a heads up that I didn't test it in full. Reinstalling official firmware worked fine afterwards.

[Ikario]

This is the third oldest and most commented open feature request in this repo.

If you’re stalling to drive people to PrusaConnect/PrusaLink, I think the only thing you’re gong to accomplish is to drive people to other brands. How unfortunate when the community at large is already saying Prusa is falling behind the curve of innovation and this makes the newest flagship printer a downgrade for many.

PrusaLink is a joke in its current state and PrusaConnect is not much better (and I’m really trying to give it a fair shot here). If you want people to use Prusa’s solution for remote/farm management, it needs to be way better. Prusa is clearly limited in what they can do in terms of development since you’re sticking to your “tight schedule” and in the mean time users have to suffer. Octoprint works great because any dev can make plugins to add functionality instead of waiting for an official release from Prusa to add even the most basic features like a legitimate camera stream which vanilla Octoprint does.

I wish some of the prominent social media content creators would pick up this thread and start shining some light on this issue and maybe then it will get some traction.

I could not agree more. What makes it more infuriating is that this is not just some random requested new feature, this was something that was actually removed. I can tolerate (though I don't agree and I think is very shady) advertising input shaping and pressure advance when none of those features are actually working as they should (an alpha release is not a stable release and crash detection does not work with input shaping at all, another feature removed if you want to get the capabilities you paid for), but actively removing features to push for a propietary system that is extremely slow (115200bps max), basic and feature incomplete is, to say it lightly, not in the spirit of openness and to be real, very anti-competitive. I read this a few months ago on reddit and had not realized how right this person was up until now: "Remember a while ago when Josef Prusa sent out a request for people to vote on the things they wanted to see most on the MK4? Well, he took the top 10 of those and added them to the MK4 sales brochure just before he released it. He hasn't added them to the MK4 yet, though." The strategy seems to be getting input shaping on the mk4 firmware ready first, then focusing on Prusalink/Prusaconnect to get feature parity with Octoprint so that people will drop the subject but everyone that follows prusa development knows this is in no way shape or form realistic because they don't usually do well with schedules and there are features on the mini, around 3 years ago, that were promised and they never got around to it. This is a really big issue that needs to be addressed as it severely handicaps the MK4 that is already arguably an inferior product compared to the competition at this same price point.

[jvasileff]

@dMAC95 @Monkopedia I removed the appendix and attempted to install custom firmware. But it failed to boot. I'll share exactly what I tried in #3147

@Prusa-Support In your last message, you punted development on this issue to the community. Can you at least provide firmware build & installation instructions for the MK4?

[Monkopedia]

I'm not sure how to DM on github, but we may be interested. If you can build firmware to support octoprint I'll be sure that our business interests don't get in the way of it being released publicly.

@dMAC95 try hitting me up on reddit, or most platforms with the same username.