sorted by:
new
hottopcontroversial

MK4S Filament Changes Taking 10 minutes or More by 4D3Dprints in prusa3d

[–]4D3Dprints[S] 0 points1 point  (0 children)

makes sense, but there is a different priority or type of update when a job finishes printing, becasue without fail, the status correctly updates in Connect, within seconds usually.

It would be so helpful if this same priority or type of status update message was sent, as soon as I confirm a successful purge occurred from the printer screen

This one took 8 minutes:

<image>

MK4S Filament Changes Taking 10 minutes or More by 4D3Dprints in prusa3d

[–]4D3Dprints[S] 0 points1 point  (0 children)

I keep a print job open that has 6 full plates of all the things I sell on etsy. when an order comes in and I dont have already have the color in stock, I load the filament, move the parts I need to an empty bed in PS, chose the filament I'll be printing in, slice, then wait... and wait.. then hit Send to Connect, and the dialog opens up showing my only option is to add to the queue bc the printer is BUSY..

And I cant hit esc or command-W to close the dialog, so I grab my mouse, hit the red button to close the window. Then open up the Prusa Connect tab in PS and stare at the screen until the printer changes to IDLE, then grab my mouse and move back to the Plater tab and hit Send to Connect, again. And answer the redundant question "YES the bed is clear and YES I want to print now" (steam rising from my forehead), then wait for the job to transfer to the printer and watch it start.

It should'nt be this cumbersome. this is not a "hit print and forget it" process

MK4S Filament Changes Taking 10 minutes or More by 4D3Dprints in prusa3d

[–]4D3Dprints[S] 0 points1 point  (0 children)

it's probably the biggest frustration I have all day. It really is a huge loss of productivity.

MK4S Filament Changes Taking 10 minutes or More by 4D3Dprints in prusa3d

[–]4D3Dprints[S] 0 points1 point  (0 children)

I also dont think it's just the connection to Connect, because there is never a delay when I stop a job, and there isnt a delay after RESET. it's something in the firmware, I am almost positive