I found my print half finished today morning in the printer. Nozzle and bed cooled down, display saying “Ready to print”. The nozzle was flush above the half-printed model.
I did not get any notification in the app or somewhere about anything. Enough filament in the AMS. Print looks good, but only finished to about 70%.
I accidentially cut the printer power the evening before. I turned it back on after a minute and could resume the print but apparently it did only continue a few more hours until it stopped without further notification.
I just had the same thing happen today, about 70% of the way through a 5.6hr print. Print stopped and then the fans cut off and all 4 AMS lights blinked red for a short period. Then printer showed available but no sign of the sliced print in the device tab, only in the preview tab. Submitted ticket to see what Bambu might say.
did you send your file to sd card first or print directly? It ever happend to me, the timelapse is error but the printing continue without a problem. I printed the file directly to cloud from PC without send it to sd card. it show the error at HMS but the printer continue without a problem.
I printed through cloud print, but this still uses the SD, it didn’t show any errors, it simply stopped printing, and the Studio app also showed as if printing hadn’t been started. i.e. couldn’t resume the print as it didn’t recognize I had started the original print. I replaced the SD card with a Samsung card and haven’t had an issue since. Bambu has indicated they will send a replacement SD card considering I had just purchased the P1S.
So this is still an issue… Trying a new SD card, and turning off time lapse.
I guess there is no way to continue the print. Would be nice if the status of the printer actually showed an error message of some sort. Looks fine on the Printer and from Bambu studio…
So, this happened yet again. Mid print the printer just stops. No error, sitting on the print. From Bambu Studio, I can see the SD card and all the data on it (3 3mf files).
This is a bit rediculous. There is no error, no way to resume the print, and I am sure again the print is stuck to the nozzle. Not to be rude, but WTF?
At least with my 4 year old Prusa, it would pull the nozzle off the print if it stopped so that the print would not stick to the nozzle, and, of course, give an error message. This is a brand new printer, and I have attempted 5 prints with 2 fails like this. Fresh out of the box.
I looked up support on this site and it points to a handful of documents, none of which cover this issue.
This is happening to me on both of my P1S’s but not having the issue on my X1C’s. The only difference is my x1c’s have name brand SD cards in them. The first time the one memory card was corrupted and I had to reformat it.
Going to try and replace both of these SD’s and see what happens. I’ve had my machines for over a year and never seen this before.
@Lexi I think the issue is the stock SD card. Jumped on to amazon and got a pair of 64GB SanDisk SD cards. Have been printing without issues now, at least 8 prints. Have not yet turned on the time lapse though.
@jjsaw5 - yes I tried to reformat too. The issue is that it was working some times. And when it failed, it must have failed for a brief moment, because examining the SD card when I got to the printer showed no issues. Even from Bambu Studio, it could read the 3mf files on the card…
When I put in a support ticket, the first thing they said was to try a replacement card, but nothing about what the log stated about the problem. They must know the P1 models are being shipped with crappy SD cards…
I’m Having the same problem - Stock Bambu Card, Slicer 1.10.1.50, FW 1.07, Fails twice 1st time layer 226 second layer 196. Paused and restarted and nothing worked. The Second time it re started but dropped the bed and was printing mid air.
I agree that the stock SD cards are junk. I replaced mine over a year ago.
But some of the people here having the issue are not using the stock SD cards.
Well I’ve been printing quite often now since I got that new SD card, including doing time lapse vids and all has been good since the change.
I guess my point here is that the error should indicate a communication error with the source file, if that is being read from the SD card and the fault is there. Seems like a very specific error that should be indicated from either the printer screen or bambu studio since that initiated the print.
Thanks for keeping up with this. All in all I love the printer. There are a few quirks coming from a Prusa printer, but they are clear now and all is good.
This isn’t a faulty SD card issue. It’s happened to several users at the same time frame which coincides with the firmware update. Also note, this problem hasn’t been reported on the X1 section of the forum and neither has my X1 suffered with this fault.
Well, I had to complete my print so I purchased a new 64Gb SD Card.
Printed no Issues and the next 3 prints have had no issues, So hopefully that was it! Would be nice to know its a memory or card issue though save wasting so much filament trying to print a second and 3rd time. Also Im more concerned the head sits there on full heat not moving for who knows how long???
Hello, OP here. Just to share an update from my side – 10 months later. I never had this happening again.
I kept the original SD card but I turned off timelapse recordings.
For me it makes sense that this might be a SD card issue. Timelapse might write very frequently in random sectors of the (low quality stock) SD card. This will at least over time result in faulty behavious I guess.
That is clearly the real issue, and should be listed as the actual fix to your problem. After spending $800 on the printer, another $30 bucks from amazon for a solid (larger) SD card means that I never have to worry that the card may randomly fail. For me, it was on and off, regardless of if I did time lapse or not. After the change out, I have been printing pretty heavily for a couple of weeks without issue. Some of those prints were 6+ hours. Would have hated to get to the 5 hour mark and have it fail with no recovery (wasted time and wasted filament)
