search

prusa3d / Prusa-Firmware-Buddy

Firmware for the Original Prusa MINI, Original Prusa MK4 and the Original Prusa XL 3D printers by Prusa Research.
Other
1.17k stars 229 forks source link

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

Open Strankler opened 4 years ago

Strankler commented 4 years ago

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 commented 4 years ago

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

fawick commented 4 years ago

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

steve220 commented 4 years ago

I'll third this request :-)

6ffm70 commented 4 years ago

I fourth this request

jonasniesner commented 4 years ago

+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 commented 4 years ago

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 commented 3 years ago

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

gimpfenlord commented 3 years ago

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

Joshi425 commented 3 years ago

this would be awsome please @michalxfanta

w90 commented 3 years ago

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

LimeAyy commented 3 years ago

Here to also request this.

aguschanchu commented 3 years ago

Please implement this!

DerGolo commented 3 years ago

+1

Gordontgopher commented 3 years ago

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

mosal1 commented 3 years ago

+1

thefreewheeler commented 3 years ago

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

Reetro commented 3 years ago

Any update?

matthewlloyd commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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) mini_progress

coaxial commented 3 years ago

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 commented 3 years ago

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

pat1121 commented 3 years ago

+1 would also like to see this!

coaxial commented 3 years ago

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 commented 3 years ago

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 commented 2 years ago

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

HolgerMA commented 2 years ago

+1

Alshootfa commented 2 years ago

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

Aelirenn666 commented 2 years ago

I have recently started using OctoPrint with my Mini and I admit, this is one of the functions, that I miss most. I would really like to be able to see remaining print time on the display.

Rose-David commented 2 years ago

In my opinion, I'd rather that the Octopus logo only be used for when nothing's printing, but I can't see anything stopping the normal USB print UI from working here. Either way, I just wanna give my nice big LCD a nice big purpose.

neo666lis commented 2 years ago

+1 This quite annoying not having the progress status.

coaxial commented 2 years ago

As a reminder, #1497 is still open and failing. If someone who is more fluent in C than me could take a look, it would help us move closer to a fix.

pitops commented 2 years ago

@coaxial did you check latest comment in the PR ?

coaxial commented 2 years ago

@coaxial did you check latest comment in the PR ?

@pitops Yes, didn't have the time to do it. Feel free to lend a hand.

pitops commented 2 years ago

@coaxial did you check latest comment in the PR ?

@pitops Yes, didn't have the time to do it. Feel free to lend a hand.

Unfortunately i have zero C experience

coaxial commented 2 years ago

I have rebased #1497 to master but I'm unable to do any further work on it. If anyone (or, who knows, Prusa themselves??) wants to carry on this work, knock yourself out!

Prusa-Support commented 2 years ago

This is a quite hectic time for our developer team.

You may have noticed a rather large log for the recent pre-release. Probably you have also heard about other "big news" of announced products in the last year - which take up a little share of our developers' attention too.

Our developers will stick to a very tight and intense development plan for some time.

This doesn't mean your pull request will be forgotten. Your work is most valuable and truly appreciated, thanks. Our devs will find time to dedicate to yours and the other pull requests as soon as possible. I hope you can understand.

Michele Moramarco Prusa Research

hphp67 commented 2 years ago

+1

lukkigi commented 1 year ago

+1 interested in this as well

mow-jow commented 1 year ago

@Prusa-Support any news half year later?

Prusa-Support commented 1 year ago

No, I'm sorry, no news in this regard. The news is that the ESP Wi-Fi module & Prusa Link implementation was successful and taken very positively by the customers. Other than that, there is much more work going on under the hood - stay tuned.

The developers should find time to review this among a few more popular requests and I'm sorry I don't have an estimated time.

Michele Moramarco Prusa Research

arekm commented 1 year ago

About M73 reporting status. MK3* firmware supports that fine for years. MK4 firmware doesn't support this at all. So now this should be considered a functionality regression between MK3 and MK4 in i3 line.

Fortunately M73 support is already in Marlin2 (2.1.2+) and Firmware-Buddy is based on Marlin2. Unfortunately based on older version but backporting that code looks to be easy enough. It's guarded by M73_REPORT, SET_PROGRESS_PERCENT, SET_REMAINING_TIME and SET_INTERACTION_TIME ifdefs in the Marlin2 repository code.

Backporting that would get Firmware-Buddy into MK3 firmware feature parity regarding M73 g-code.

Relevant code is mostly: https://github.com/MarlinFirmware/Marlin/blob/0c2ed8688dd387b56b318f6207ee1cc70811b5a5/Marlin/src/gcode/lcd/M73.cpp#L58-L91

plus ui.get/set_XX() functions plus a bit more if M73 would have to affect also what's displayed on LCD (that's also desired).

In theory current firmware supports M73 PX (progress X) at least... in theory because it doesn't show that on LCD.

LordRaptor commented 1 year ago

Please implement this, a lot of us are using Octoprint to control our printers and the standard set of G-Codes should be supported by all printers.

SetupCoding commented 1 year ago

Any information when this might get tackled for the MK4? Not having this feels like a downgrade from the MK3s. Using PrusaConnect is also not an option without Webcam-Support, canceling singular objects mid print, sending GCODE commands directly or support for something like Octolapse.

Prusa-Support commented 1 year ago

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

Bpendragon commented 1 year ago

Using PrusaConnect is also not an option without Webcam-Support.

For me it's a lot more than just webcam support. I've been setting up and modifying my Octoprint setup for nearly a decade. Various plugins set up and doing things exactly how I want. I have multiple layers of access control and can hit my printer from anywhere in the world in a way I know is secure, or at the very least if it's insecure I have no one to blame but myself, and so on.

I get that Prusa wants to support first party stuff first, but without this it's a removal of what many consider a core feature of the Prusa i3 lineup.

LordRaptor commented 1 year ago

I completely agree with Bpendragon. Having the Mk4 regress in capabilities vs the Mk3 seems a very weird choice. And it's not like you guys don't have a firmware that does all of this, just allocate a developer that worked on the Mk3 firmware to port these capabilities to the Mk4, or review the pull requests from the community that integrate this functionality and merge them. You keep claiming that your developers have to stick to tight development plans, but this is an issue that's been open for over 3 years now, development plans don't go that far into the future.

fergymcferguson commented 1 year ago

+1 Bump

TravisWilder commented 1 year ago

+1

oxivanisher commented 1 year ago

Please work on this issue. Buying the MK4 feels like a big downgrade process and ease of use wise which is really sad! And no, for me and many others, PrusaConnect is no alternative since Octoprint does so much more and it is a tried and proven option. Also on a personal note, this leaves a sour taste since in the latest blog Joe talked about supporting open source (the reason I buy Prusa and not from the competition) and how a lot of companies just use open source when it's convenient but no longer really support it...