[BFW-5403] [ENHANCEMENT] Show Image of object to be printed on Display in more situations

[Mike-FUT]

Printer model

MK4S / XL

Describe the enhancement

Currently I can see an image of the object to be printed in many situations.
Please consider showing the image additionally:

• when a print is waiting in the connect queue and the current one finishes and I remove the objects from the plate, choose "set ready" from the printer screen. Currently it will just start printing without showing an image.
• during a print it would be really nice to be able to see the object on the screen, too, probably by turning the knob or using an alternating screen

Expected functionality

No response

[Printer606]

Yes, this would be nice.

[CZDanol]

We have some ideas like this as part of BFW-5403

[Mike-FUT]

Hi @CZDanol,

In the meantime I learned the one part of my enhancement request is actually a bug in the firmware.
My MK4S is on firmware 6.1.3 and during the print it only shows the image of the currently printing object if I set the display time to larger 30 s. I had mine on 30 s (which is the default I believe) and I never saw an image during print but now I set it to 32 s and the image shows up during print now.

So this part of my enhancement request is actually not needed if the firmware bug will be fixed.

• during a print it would be really nice to be able to see the object on the screen, too, probably by turning the knob or using an alternating screen

It currently works when setting the time > 30 s and I guess it will work with smaller times when the bug is fixed.

[Mike-FUT]

It currently works when setting the time > 30 s and I guess it will work with smaller times when the bug is fixed.

One more update of what I noticed:
The image of the item to be printed never shows with the default setting of 30 s on my MK4s with 6.1.3
But, contrary to what I wrote above, with 32 s set the image didn't show up for several minutes last time I tried a longer print. So there is something rather buggy there...

[CZDanol]

That part of your issue we're dealing with as a part of #4184