This is 2nd time this has happened to me,1 replaced my SD card after it happened for the first time as bamboo support suggested to change SD card, now I am not sure what could be the root cause.
Still printing without unintended cancellations?
Yes - thanks, about 15 prints completed (about 50% above 2 hours long) following the previoiusly captured rules without issue - and also realise I have another self-enforced rule in that I:
- no longer use the handy app to monitor how things are going.
As discussed within the thread no easy way of knowing which one or combination are preventing the reoccurrence for me, but given how frequently it was happening when it went wrong, following these rules seems to be working for me and I am able to user my printer again with reasonable confidence.
Same problem as many others.
2 multi-hour long prints cancelled for seemingly no reason mid-print.
Got a notification on my phone saying
Replaced the stock SD card with a better quality, larger capacity one (SanDisk 256GB), had a failed print. Then, I turned off timelapse, and still, same issue occurred on the next print.
Figured firmware was the next step but didn’t want to go through the hassle of reverting it so I figured I would see if there were other likely problems/solutions first.
After browsing this post (again) and a couple others like it, as well as mentally cataloging exactly what I did for each failed print in case of user-error, I realized that there was a common action among all my failed prints.
Each time a print of mine failed, it failed shortly after I had checked the camera feed from my phone mid-print (possibly from my computer as well, can’t recall at this point).
After realizing this, I stopped using the live-feed to check on my prints from my phone and voila, I have had approximately 1 dozen prints since then, no random print stops.
I can’t say for certain it’s the live feed. Perhaps it’s a problem with how the app communicates with the printer or the camera or the firmware, but I haven’t had a single failed print since I stopped using the live-feed to check my prints mid-print (from my phone).
Lastly, for full disclosure, I now close the bambu studio app on my computer after the print has fully downloaded on my P1S, and never open my phone app while a print is printing because of my new-found paranoia of accidentally clicking on the live-feed button and screwing up another 8+ hour long print.
Hope this helps someone, cheers.
Has Bambu acknowledged this fault yet?
Has anyone actually told Bambu about it yet?
I am seeing this issue on the facebook groups almost daily since it occured to me over xmas.
They have been told and they ignore the firmware issue and blame your SD card everytime.
Asking Bambu to admit that something is wrong is like asking creality to do QC it’s just not going to happen.
Hi all,
It has just happen to me after about 2h of printing.
It’s my first printer and and was my first “long” print.
Machine: P1S + AMS
Stock SD card: Yes - Lexar 32Gbs
Bambu Lab Slicer Version: Bambu Studio 1.10.1.50
P1 Firmware version: 01.07.00.00
Approximate layer number where it failed: around 250/765
Approximate time elapsed between print start and failure : approx 2 hours
File size: ~ 250 MB. Might have an influence if it’s a read / write error with the SD-card.
I’ve just formatted the SD Card and try to relaunch a shorter print (about 30min) but I’m not confident.
Bambu reaction blaming the SD Card is surprising because most f the error occurs with their own stock SD.
I didn’t read the old messages but is that problem new or is it a known issued of the P1 ? I may have not bought this model if I was aware about it…
Happened 2 times in one day with different SD cards.
Machine: P1S + AMS
Stock SD card: Yes and No (happened on stock and non-stock)
Bambu Lab Slicer Version: 1.10.1.50
P1 Firmware version: 01.07.00.00
Approximate time elapsed between print start and failure: 46m and 1h 15m
Downgraded to 1.06.01.02, started 16h print, 12h printed already with no issue so far. The strange part is that on 01.07.00.00 worked fine for couple weeks.
Sent a ticket, response:
*Dear Customer,
I am sorry you are having this issue, I am here to help
Thank you for the information and the log files
Upon review of the log files, it shows an issue on the SD card is not reading at the correct speed,
I would advise replacing the SD card with an SD card with a Class 10 or U1 rating (minimum write speed of 10MB/s) or higher. Make sure it’s formatted as FAT32.*
-_-
Quick Update - still no issues.
Last night I did a 10+ hour print without problems and the reason for this post is to say I did have timelapse on. With this thread leaning towards the problem being the use of the camera to “check on” the print through the app, and really wanting a timelapse of this print I decide to risk it and there were no issues in doing so on this occasion.
I appreciate this doesn’t prove anything but I feel adds more weight to the suspicion that the problem lies not with SD cards but with monitoring the print through the camera. Of my previous “rules” I have also broken my switch the printer off every time rule without issue on occassion so again feeling less like that one is a factor. The others were more one off actions than repeating rules.
I still haven’t moved back up to 1.07 so it could be multiple factors at play still, but I will probably re-upgrade soon if I continue to have no return of the issues.
Update:
Turns out my issues were based on a defective SD-Card (the one included withh the printer).
When checking and repairing the file system on it at my computer m,ultiple defective storace cells were detected and exclusion of these was attempted. However, the mid-print stops or straight up cancellations persisted.
I upgraded now to a MAX Enduranbce SD-card from SanDisk, designed for continuous read and write cycles. Which resolved my issue. To exclude any othher influence I also went ahead and reset the printzer to factory settigs after removing the old SD-card, before installing the new one.
Make sure to format the new SD-card with a Fat32 formatter first on your pc and then, after inserting it into the printer, format it there again to install the specific filesystem for the Bambu printer. Also make sure to never remove the card from the printer before ejecting it in thhe printers menu (in the setting on the priter itself) to prevent damage or corruption.
In the mean time I printed multiple long duration prints (<5h) and even a 2,5d, comples 150Mb file size one with timelaps enabled and multiple check-ins from both the bambu smartphone and desktop application without issue.
I also contacted Bambu’s customer support, who offered me a SD-card replacement. I did not take up this offer tough, as the SanDisk one seems to be a much better quality card.
Hope this might help some of you with similar issues and I would highly recommend to get buy an endurance card or similar, if you’re looking to upgrade or replace the stock one.
Greetings,
Bomby
Might be interesting to see what happens if you use the old card. Restoring factory settings may have corrected the issue. You cannot pinpoint the cause when you make multiple changes at the same time.
For people saying its the camera or card. I have used several different types of cards across multiple machines it does not fix the issue it just gives you some more time before it fails again. Same as reformating the cards. Also I do not use the camera on any of my machines and experienced failures on all my P series printers. Reverting back to 1.06 is the only fix that holds you can even go back to your “bad” SD card with 1.06 and it will magically work again.
The issue is in the way the firmware interacts with the SD card could be a timing read/write change or a different type of error checking I am not sure without looking at the code but it is a firmware issue.
Yes, that could also be good.
Otherwise, it would be possible that a pause has been inserted in the print profile, which you don’t notice especially when you start a print from the mobile phone app.
However, it is rather unlikely that a pause in the print profile will completely end a print.
Just happend to me also
Machine: P1S
Stock SD card: yes
Bambu Lab Slicer Version: Bambu Studio 1.10.1.50
P1 Firmware version: 01.07.00.00
Approximate layer number where it failed: approx 500of 610
Approximate time elapsed between print start and failure : approx 1.5 hours
Update: It has been running fine on version 1.06 since then. It was definitely not an SD card issue because, even after I replaced the stock SD card, the print still got interrupted in the same way as with the stock (lexar) one. I am now using the same card on 1.06, and it works without any problems. The only issue is that it keeps prompting me to update all the time. Bambu should review whatever they changed, fix it, and provide a clear explanation of the fix in the changelog.
Bambu would need to recognise and accept that there is an issue first, instead of just saying it might be the SD card ( that they supplied).
I’ve had a few variations of the P1 series, and they’ve all randomly done this a few times. I figured upgrading the stock SD card might help, so I replaced them all with MAX Endurance U3 SD cards, hoping for a fix. Unfortunately, on the very first print after the upgrade, two of them still canceled mid-print—right in the middle of a five-hour job.