Well, this is a thing now.
Cover image: Reddit / u/beehphy
Ever had that situation on your old inkjet printer where you sent a job, but it wouldn’t print. The usual excuses, “printer offline”, or my favourite, “spooling”. Then later, randomly, you’d turn the printer on, or maybe the network router would be rebooted, and the printer suddenly spits out 41 pages of something you no longer need.
Well, Bambu users overnight on the 14th August found out to their surprise that the Bambu cloud apparently can do this too.
This is obviously…ungood. But what to do about it? I guess the obvious thing to do while Bambu try to fix this is to:
- Never leave a thing on the build plate.
- Turn off the printer when not in use
The second one seems obvious to me, as an “on” printer is always a risk. I’ve seen idle printers just spontaneously develop MOSFET issues and start smoking at the hot end. You should never leave a printer unattended, idle and on.
As some users found out, the hard way.
Anyway here at Lost HQ we had no issues, because, our printers were idle and off, because we were no doubt editing video instead.
Bambu can absolutely fix this if they please – they could check time of print against current time and ignore anything over a few hours (minutes?) old, or add a prompt on the UI.
The moral of the story: Turn off your printers when not in use.
Leave a Reply