I’ve had this happen to me twice just now. Thankfully it was only about 10mins in both times. Although was ghost canceled at different layer heights. Did anyone ever figure out the cause of this? I’m so tired of loosing money on these machines to flook events like this.
Update. Since my last fail print, I didn’t change ANYTHING. I didn’t change or format the card, still on version 1.07. I’m monitoring my print all the time (I have a laptop near me Iand I check my print from Bambu Studio almost full time). But no time lapse video.
I’ve print around 20 plates of 4-6 hours without any problems. I think it’s a random problem, but they must find how to correct the issue!
Just had this happen. Printed this same model yesterday fine. Printing again first time today, with a new color, model cancelled some time in for no reason.
Machine: P1S + AMS
Stock Card: Yes
Slicer: 1.10.1.50
Printer Firmware: 01.07.00.00
Approx Layer Failure: 194 / 527
Approx Time Elapsed: 1h 42 mins
Just had this happen, second time has happened , one in december and one today
Machine: P1S + external spool
Stock Card: Yes
Slicer: 1.10.1.50
Printer Firmware: 01.07.00.00
Approx Layer Failure:
Approx Time Elapsed: 1 hour
Just happened to me too, i will try reverting to previous firmware i just find it strange i printed over 400 hours on version 01.07.00.00 without a issue.
Stock SD card: No (Samsung 64gb) Been using for a couple months since my stock one died mid print.
Machine; P1S no ams
Bambu Lab Slicer Version: 1.9.3.50
P1 Firmware version: 01.07.00.00
Approximate layer number where it failed: 40/50
Approximate time elapsed between print start and failure 4.5 hours
This just happened to me , an 11 hr print gone
Edit: Something I just noticed that I found interesting.
The filament information from that slot in my ams was gone when I booted up my printer this evening. I don’t know what that means but I thought it strange.
Please follow these steps to resolve the issue:
Unfortunately, I had the same issue several times.
I have:
- Bambu Lab P1S
- FW = 01.07.00.00
- Stck SD-card = yes
I printed both from SD-card as via Bambu Cloud, it happened in both cases.
Also I did not get any error message in both cases.
One time it happened during the print preparation/calibration.
But it also happened mid-way a 3 hour run.
Question
- What can I further investigate
- Or what can I further do to prevent this?
I just had this happen after a print was 7 hours in. No reason, just stopped, super weird.
Just had this happen to me… So annoying
So I beat them by 8 days?
Thanks Timborino!
I will follow your advice and return with feedback.
I’m really not convinced a new SD or reformatted SD is gonna do the trick, plenty of replies above have replaced the SD card already with decent brands but still had this issue.
Virtually no-one reported the issue until the new FW came out so feels like its related the FW more than peoples SD cards randomly failing at the exact time a new FW comes out.
Hardest part is its not that common so you may fit a new SD card and it may work for ages or maybe never have an issue again, but that doesnt mean the replacement SD resolved the issue. I havent replaced my SD or even reformatted since I originally posted the issue, it hasnt failed a print since but at 153 replies, you can see its affecting others too.
I have created the ticket = US250212446001
And uploaded the Logs and the 3MF file.
Arrggh and again.
I had formatted the SD card and turned off image captures.
Anyone know if lan only mode fixes it? Or just downgrade to 1.06?
Matt
I must have forgotten to remove my cloak of invisibly.
Annnnnd downgrading via the Bambu handy app to 1.06.01.02 hangs download at 32%. . I see other people saying turn off the machine, remove the SD-CARD worked for them to update. Will try that next.
<edit all I needed to do was power off and off, no need to remove the SD-CARD downgrade worked>
I’ve also ordered a new SanDisk Max Endurance SD-CARD should be here in a few days.
Huge thanks to the community here (particularly @Lexi )
Would be nice to hear from Bambu even if it was just an acknowledgement they know about the issue and are on it…
Matt
Trying firmware 1.06.01.02 now that I’ve also had this issue