"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.

[michalxfanta]

Thank you for an interesting idea, we will consider its implementation.

[fawick]

I second this feature request.

In particular, it would be great to see support for the following codes when printing via USB cable from Octoprint

• M73
• M117

[steve220]

I'll third this request :-)

[6ffm70]

I fourth this request

[jonasniesner]

+1 this would be really helpful and add value and the code to display is already there because it can display it when printing from USB.

[naltatis]

A year ago I've built this octoprint based flexi-rex progress indicator with an e-paper display on a raspberry pi. I'd love to see the magic octopus slowly getting filled on the Prusa mini screen.

[mucek4]

Any news on this? I really miss that information and a picture of octo is useless.

[gimpfenlord]

i also "upvote" this.
currently my LCD is useless 99% of the time. so much unused potential

[Joshi425]

this would be awsome please @michalxfanta

[w90]

Great idea! Upvote!
Now in order to see the status of my print, I need to visit the octoprint.local page in browser

[LimeAyy]

Here to also request this.

[aguschanchu]

Please implement this!

[DerGolo]

+1

[Gordontgopher]

What does this give you that setting "Action Command Prompt Settings" to 'never' in Octoprint doesn't give you?

[mosal1]

+1

[thefreewheeler]

Any news on this? Hugely disappointing that the Mini's LCD shows no useful info.

[Reetro]

Any update?

[matthewlloyd]

Anyone following this issue may be interested to know that I just released custom firmware that adds support for M73 (print progress) and M117 (LCD messages):

http://github.com/matthewlloyd/Llama-Mini-Firmware#readme

[coaxial]

This is sorely missing. The Mini LCD is so large, why take all the space up with an Octoprint logo? It’s cumbersome to go and find a computer or phone and visit the Octoprint page just to find out how far along the print is…

[redPanther]

It's a pitty that we have a nice screen with so little information. In the meanwhile I have a workaround:
if octoprint is used, install DisplayLayerProgress Plugin. I use this for printer message: [progress]% L=[current_layer]/[total_layers]

then when printing, select "tune" scroll all the way down to "messages". Then you see the progress in % and current and max layer. Temperatures and z height are already displayed at the bottom. Looks absolutely not so nice as it could, but it provides necessary information during print.
(stock firmware 4.3.1)

[coaxial]

Anyone following this issue may be interested to know that I just released custom firmware that adds support for M73 (print progress) and M117 (LCD messages):

http://github.com/matthewlloyd/Llama-Mini-Firmware#readme

Would love to try your firmware, but really not keen on voiding my warranty just to get M117 and M73 support. And there is no other way at the moment, I think.

[theHalo]

Was hoping this would have been included in today’s release. Bump.

[pat1121]

+1 would also like to see this!

[coaxial]

I have a PR (#1497) that would enable this based on the work done for the llama firmware but its not building for some reason (can't see why.) I wish someone more comfortable with C could give feedback and help pinpoint what's going on, because if the build for that PR is green then it has more chances of getting merged.

[mtaumike]

Bumping this, however it gets done.

Be fun to get some progress for when walking up to the printer, and even better, if any thumbnail that was created in the gcode file could also be shown vs 'the octopus'

[atxkev]

+1 to add this in. My MK3s screen with octoprint is more useful.

[HolgerMA]

+1

[Alshootfa]

+1 will allow us to take advantage of the Prusa Mini's awesome color display instead of covering it up.

[ScottWell1]

The "progress" display with Octoprint is a part of standard, basic Marlin M117 support. In my opinion, there is simply NO EXCUSE for Prusa's Buddy firmware omitting M117 support. Whether YOU need it or not, it is part of baseline features that should be included in any Marlin branch.

[coaxial]

All I really want is Octoprint to be fully integrated so I can print using it.

This is moving the goal posts. Octoprint support is table stakes when it comes to 3D printers nowadays, much more so when it's a major, premium brand's flagship model. It should have been there from day one instead of the half broken Prusa connect thing that nobody ever asked for.

M117

Same for this code, it comes with Marlin and is a basic, standard feature. How is it that 4+ years after the Mini (aka the "print farm workhorse") has been released and months after the MK4 is out we still don't have support for such a basic feature and have to beg/lobby Prusa to do anything about it in threads like this?

Had MK4 users not felt the pain of missing features in the buddy firmware, I'm not sure anything would have moved for existing Mini owners. We've been asking for these features for years and barely ever got any attention.

[hstag]

I FULLY agree with @coaxial. This should be done before releasing a mk4 and mini too. I sold my mk3's and bought mk4 because I thought the new version will be superior and will be an upgrade. I made a mistake.

And as an owner of mini I am really disappointed.

Begging and waiting years to implement things that was promised in the beginning is really not a respectable way of treating the customers.

[ddanier]

Just a note: You can view the progress if you go to "Tune" -> "Message History" (last element in menu list). This shows a log of messages which should include progress and current layer.

I know this is not optimal and I myself wish the integration would be better. However you can look at the progress this way, which is still a good thing. ;-)

[coaxial]

I'm not sure if this has been fixed, but using this menu to watch progress made the filament runout sensor not trip anymore when running out of filament on the Mini.

[dirkvranckaert]

Just a note: You can view the progress if you go to "Tune" -> "Message History" (last element in menu list). This shows a log of messages which should include progress and current layer.

I know this is not optimal and I myself wish the integration would be better. However you can look at the progress this way, which is still a good thing. ;-)

Indeed, saw that menu too but some basic info should simply be available on screen immediately...

[ddanier]

One nice thing I just noticed (and tested on MK4): The "Tune" menu is now much more in sync with what is possible during USB printing. You for example can use "Cancel object" while printing using OctoPrint. Also the LED status bar matches what is happening + this also shows up in ProseConnect. Pretty neat.

Now I'm waiting for some print job details (progress, current/total layer, ETA)....as this is what is issue is originally all about.

[Prusa-Support]

For not natively integrated features - or not yet implemented - please consider opening new issues.
I recommend opening issues with a clear title and description for each single request.
This allows for better tracking of specific requests and bug reports in general.

Michele Moramarco
Prusa Research

[coaxial]

@Prusa-Support: created #3653

[hstag]

It's great that after 4 years you opened a new issue with the same description instead of implementing it.

4 years.

[timur-tabi]

See also See also #3846.

[github-actions]

This issue has been flagged as stale because it has been open for 60 days with no activity. The issue will be closed in 7 days unless someone removes the "stale" label or adds a comment.

[Silvenga]

Bump.

[coaxial]

Not stale, just being ignored :)

[nealzip]

I'd like to upvote this.

[jerekarsten]

I guess it's easier to attach a 16X2 lcd display to my raspberry to monitor printing progress like it's 2018, as this apparently is impossible to do with the firmware. They put a man on the moon you know?

[timur-tabi]

Let's be perfectly clear, this is not a hard problem. Prusa could do it easily. Heck, they could have an intern do it. They've had years to fix this problem. No, the reason this problem exists is because Prusa does not care. It's just not important enough to them.

[tkircher]

The MK3 had hardware support for a Pi Zero running Octoprint and it looked like Prusa was committed to freedom. At some point since then, they must have had some very bad advice from a consultant, and decided to close the platform and commit to a proprietary lock-in like Bambu Labs has. There was obviously huge backlash and I think they did realize they made a mistake but it may take a very long time for them to fully support an open platform.

[Prusa-Support]

I guess it's easier to attach a 16X2 lcd display to my raspberry

I think Octoprint could entirely replace the printer firmware for the most part so if that is actually possible, the user shouldn't refrain from using other screens too. If I got this right, it wouldn't be much different than controlling the printer from a computer via Pronterface or similar, with the only exception that Octoprint is designed to work from remotely in the first place, probably without printer-LCD boundaries.

Prusa could do it easily.

At this point, probably literally anyone can do it, in a similar fashion they do for Octoprint.

The MK3 had hardware support for a Pi Zero running Octoprint and it looked like Prusa was committed to freedom

We may have a different idea of "freedom" and I hope freedom is granted on both ends or maybe I'm not entirely sure what you mean.
Yes, we tried to support Octoprint compatibility more actively from our side in the past and we know it takes special maintenance and attention but this is not all! Certain features that are almost entirely based on Octorpint are not directly compatible unless the printer's firmware is substantially modified and thoroughly tested.
Other than "freedom" I would like to talk about Open Source which seems to be the only bridge between our company and Octoprint. Prusa is a huge supporter of Open Source, in fact, everyone can contribute to the project and feel free to customize the firmware to their liking, for themselves and/or for the community.

We will continue monitoring and making considerations.
Thanks for your trust in the Open Source and for your understanding.

Michele Moramarco
Prusa Research

[timur-tabi]

we tried to support Octoprint compatibility more actively from our side in the past and we know it takes special maintenance and attention but this is not all!

We're not asking for Octoprint support, we're asking you to support the serial connect that is part of your hardware. The giant Octopus that you display on the screen, instead of useful data, is completely unnecessary and no one asked for that. You invented that all on your own. What we want is for you to restore the same functionality that you used to deliver in your previous product. That's it.

[Ikario]

This whole post says literally nothing when it's all about standard basic functionality that was removed and replaced with a silly picture. I don't know what this rant is about other than saying "we couldn't care less". Disappointing and a shame. At least it's signed so we know who we can't rely on to significantly improve user experience on prusa printers, thank you for that.

…

On Fri, 11 Oct 2024 at 4:17 PM Prusa-Support ***@***.***> wrote: Prusa could do it easily. At this point, probably literally anyone can do it, in a similar fashion they do for Octoprint. The MK3 had hardware support for a Pi Zero running Octoprint and it looked like Prusa was committed to freedom We may have a different idea of "freedom" and I hope freedom is granted on both ends or maybe I'm not entirely sure what you mean. Yes, we tried to support Octoprint compatibility more actively from our side in the past and we know it takes special maintenance and attention but this is not all! Certain features that are almost entirely based on Octorpint are not directly compatible unless the printer's firmware is substantially modified and thoroughly tested. Other than "freedom" I would like to talk about Open Source which seems to be the only bridge between our company and Octoprint. Prusa is a huge supporter of Open Source, in fact, everyone can contribute to the project and feel *free* to customize the firmware to their liking, for themselves and/or for the community. We will continue monitoring and making considerations. Thanks for your trust in the Open Source and for your understanding. Michele Moramarco Prusa Research — Reply to this email directly, view it on GitHub <#189 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXTHVUZDISD7CVC26OQ2VTZ3AP4ZAVCNFSM4KSCWAQKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TENBQG44TSMZYGE2Q> . You are receiving this because you commented.Message ID: ***@***.***>

[tkircher]

The MK3 had hardware support for a Pi Zero running Octoprint and it looked like Prusa was committed to freedom

We may have a different idea of "freedom" and I hope freedom is granted on both ends or maybe I'm not entirely sure what you mean.

It means you commit to supporting open source tools, not your own inferior proprietary solution (Prusa Connect) which takes away freedom. And I'm not sure what you mean by both ways. Prusa is a corporation, not a person, and should have no freedom. Its only purpose is to do what customers want.

[ScottWell1]

Blah blah blah...
We will continue monitoring and making considerations.
Blah blah blah...

This entire post is one of the most insulting missives I have ever seen any company employee make towards their customers. If anyone spoke to customers of my company this way, they would be looking for a new job.

And calling it "Octoprint support" is either deliberately disingenuous or shows a huge amount of ignorance. What is being asked for are standard two-way communication support for Serial Print control -- commands like M117, which have been COMMONPLACE in virtually every printer manufactured in the last decade -- including Prusa's own MK3 line. These are not "unique" to Octoprint -- rather, they are DeFacto standards supported by virtually every Marlin derivative and are needed for ANY serial print controller (not just Octoprint) if Prusa wants to sell printers that can integrate with non-proprietary tools.

Stop gaslighting and telling us to "go support ourselves." Prusa printers come at a premium price, and all we want is for it to live up to "standard" support -- so please quit making excuses and support your customers with the features they need.

[kbranch]

The fact that the Prusa "solution" (PrusaLink) is so, so much worse than Octoprint makes this much more frustrating. I don't care about Octoprint on my Klipper machine because Klipper is powerful and open (both in terms of source and communication protocol). Prusa has had 5 years to either add support for a couple simple gcodes that the MK3 supported or develop an alternative that's any good.

Prusa is struggling hard right now to keep up with its competitors in terms of hardware and value. Support for the community and easy interoperability are two of the few strong points they can still claim. Both the tone and content of this response are disappointing.

[lucasoskorep]

Certain features that are almost entirely based on Octorpint are not directly compatible unless the printer's firmware is substantially modified and thoroughly tested.

Standards exist for a reason. As has been stated - nobody is asking you to support Octoprint specific features or rewrite your entire firmware. Its one thing to have an "open source" product with all contributions funneled through a for profit company, and another entirely to actually embrace open source and support open standards.

The ask on this thread is official support for 2 small open standards in M73 (print progress) and M117 (text updates). This should not required "substantial modifications", its all a matter of supporting an open standard instead of funneling people into your own tech stack.