I just sent and it was then ln the internal memory. Chose start print from the printer selecting the file from inside internal memory folder and off it goes. Only a small extra step needed nothing major
1 Like
I just hope that when the cloud gets back up it doesnât start printing over the (then) finished print!
yup, that works for me as well
1 Like
How do you see if the cloud is down or if it is back up?
Use the status link thats been posted above a couple of times
just updated all my printer to the new firmware, now nothing with print⌠it appears to send file, and camera pops up but no file send no bed heating or nozzle, i can turn them on manually but but no printâŚ
i think there is a glitch somewhere⌠hope they fix this issue quick⌠dead in water on all printers
You should be able to still send prints to the printer just not print plate. But even that should be coming back up, it appears that things were fixed. I hope.
1 Like
it appears sending file to SD card works, just not sending to print plateâŚ
like many i wish they just let us use our own network⌠there cloud is less than stellar to say the least
1 Like
Cloud printing works now from Bambu studio. Thank you.
I can confirm, it works again sending prints through the cloud
Hi All,
So I experienced the same thing prints sent to the clound did not end up on the printer.
many reboots and the printer eventually dissapeared from studio altogether.
I couldnât report a ticket with the handy app as it needs the printer connected 
I was able to hop onto the same network segment as the printer and rebind it to my account with the handy app.
It then appeared back in studio but still wouldnt print.
I have downgraded and things are currently working fine.
The only thing that happened for me in the downgrade was that all the AMS slots lost their settings.
when I hit âsendâ it tells me âAn SD card needs to be inserted before send to printer SD cardâ, which is why I was asking why doesnât it send to internal memory instead. Iâm using the linux version of BS 1.6.0.65 and the new firmware
Turns out that it wasnât the firmware at all, but a problem with cloud printing that occurred at nearly the same time. What a mess.
1 Like
I read this thread and sometimes Iâm really amazed at what people think here.
Do you really think they will release firmware that will have such fundamental problems?
Do people really think we beta testers didnât intervene?
you could have found out so easily that it is not the firmware that causes these problems, but the cloud, I am also surprised that there are people who do not know that you can simply download a sliced file from the Bambu Studio and e.g. import via SD card or just send without printing.
Well, the firmware is to blame if youâre too lazy to just deal with the matter properly.
2 Likes
lolâŚwow buddyâŚI am happy we have smart people like you that we can followâŚ
Many companies have released many firmwares with many many fundamental problems. Itâs not uncommon, nor is it unheard of so I think your comment is very narrow minded.
If you have a âthingâ and âthat thingâ is working fine until all of a sudden it stops working after a firmware update the first place you will look as the firmware.
The fact that the cloud was down was a secondary thought to most people, because nobody knew the cloud was down until they join the forum, and started reading.
The big fundamental problem here is that the firmware was released just as a cloud problem is emerging. Thatâs the problem. Nobody was lazy âŚif you took the time to really read through all the comments, everybody was experimenting, rolling back, firmware, reinstalling, firmware, and doing different kinds of tests to try and see if we could find a workaround. I didnât see you anywhere in this thread trying to help at allâŚ
So Typical, youâre the troll that comes in the end when everythingâs fixed and criticizes everyone for everything they did âwrongâ.
Good job buddy.
2 Likes
Yeah itâs bad when they donât even read the whole thread and just blindly post.
FYI, the Cloud failed 12 hours after the firmware was released and almost 8 hours after this announcement was posted not ârightâ after it was released. All firmware now goes through a BETA before being released. A failure of this magnitude would never get past our Beta Test, and our final tests before releasing it.
People could also learn to visit our status.bambulab.com page to check the status when something like this fails. Also could subscribe to updates to be notified of a problem.
Iâm not faulting anyone for assuming it was the firmware update. But even after commenting and replying to users many times the cloud was the cause, not the firmware, some still didnât see that and assumed it was the firmware and commented on the firmware problem before reading any of the recent comments even. I think that was the OPâs Point. FYI, I was in this thread responding multiple times.
The key takeaway from this is we need to 1) Improve our cloud resiliency still 2) We at Bambulab need to respond faster when there is a cloud issue. We are committed to both.
4 Likes
You guys are doing a great job. I truly love my X1
â â â â happens and I am glad you guys were able to address it relatively quickly.
Personally speaking, I am happy you guys are committed to improving the service.
That being said, âright afterâ was not meant to be literal, but instead to illustrate very close proximity. 12 hours is not a long time considering different time zones around the world, and when people decide to actually update the firmware. In my case, I updated my firmware when the cloud issue just started so from my perspective, it happened at exactly the same time.
Secondly, I didnât know a status page existed until it was posted. Perhaps it would be a good idea to put it on the main website so everybody can see it. Having a static page is great, but if people donât know itâs there itâs useless.
Thirdly, I just want to reiterate that no matter how many testers you have bad firmware can make it out to the public. Itâs happened time and time again with many other companies. I appreciate the confidence you have in your beta testers, but I just want you to be open to the possibility that it could happen, not that it would happen.
Lastly, I want to say that, although I accepted that it was a cloud problem, and I did follow the instructions about using an SD card or sending the job to the printer over the LAN, I was still having problems with the bed, refused to start heating up at the beginning of the process. Magically the problem went away as soon as the cloud was fixed. So there might be something in the firmware that requires the cloud to work in order to allow the printer to start the printing process.
At least thatâs my logical assumption based on what I experienced in my testing. Iâm open to the possibility that Iâm wrong.
I like to keep an open mind when there are problems, and if we can all work together as a community to find work arounds when problems happen helps to keep people printing and also build the community.
Ripping people for the effort they put in is not a good way to move forward. Learning from mistakes and trying to help each other when a crisis is happening always the best course of action.
Again, I appreciate your comments and I understand your point of you, but everyone looks at the situation differently.
I have a suggestion to help in the future. On the main page and the community forum page, perhaps putting a link or an icon at the top that relates to the status of any issues currently happening in real time.
Just a suggestion
Have a wonderful day.
Please see my example
1 Like
Itâs SO nice to have the fan shut down while in standby. Thanks!
Silence is Golden!
4 Likes
How to get into beta testing program?