I usually say that CFX plates are nearly indestructible, but today Bambu Lab’s excellent firmware managed yet another scenario where the nozzle crashes into the plate—and this time it was extremely chaotic. The nozzle was completely destroyed, and even the poor CFX plate, which normally withstands extremely rough treatment, had a splinter carved out of it.
So now I’m approaching nearly 40 scenarios where the nozzle can and will damage the equipment…
The plate isn’t completely destroyed, and most damage will fade with continued use, but this incident gave me an incentive to purchase a satin/CFX combo plate instead. Let’s hope your new toy, the H2C, hasn’t had these phenomena copy-pasted into its firmware, because they’re really annoying, and there’s no warning when it happens unless you know in advance which parameters trigger it.
I’m curious, is there something I can watch for on my A1 that you are aware of? Can you share that?
I’ve had one “Glacier” plate destroyed by my A1. (In hindsight I bought a Kedavi plate to replace it, so it was kind of a win/loss thing) I opened a ticket uploaded logs, etc… and never really determined what caused it. I wrote it off as a one-time thing, but your post makes me think maybe there is something I don’t know that may help me avoid another one getting eaten.
I have had a lot of issues with my A1 trying to raise itself to high during pre-print calibrations. This used to never occur, and I’ve seen others complain so I’m sure Bambu knows about it, and I just expect it to get fixed in a firmware update. Until that time I just know to push my extruder down low before every print as it only occurs when the extruder is above a certain height before I send a print job.
I’ve been using my A1 less and less as my two H-Series printers are beasts and I love both of them. My A1 is used mainly for prototype testing and quick little things, or just when I want to work it out… I think my A1 will always be my favorite (you always remember your 1st) even though its nowhere near my H2D or H2C.
No, there’s no custom code involved — at least nothing that moves the print head.
This is something that can, and will, occur even with all factory settings.
Not entirely sure whether my findings apply to the firmware of any printers other than the X‑series and the H2D. Of course, I still remember the first printers – mine was from the RepRap era, when absolutely nothing was automated. Since most of these findings are part of an ongoing case, I am not able to discuss them in detail yet, but I will share more information as soon as I am allowed to.
Thanks for the response. I initially thought I was in the A1 Series category when I responded and now realize this post is under H2. Sorry for my confusion, looking forward to any info you can share in the future!
I will get back when I can. Bambu Lab should get an honest chance to fix this before I have to release these Issues. These cases seems to have low priority at som instances so It’s kind of waiting game here
Release the issues! No sense in holding something back that can affect everyone negatively.
I am pretty interested in what causes this, because I haven’t had an instance of it yet between the 3 H printers I own. Just curious, not trying to dismiss.
As previously mentioned, this finding, together with other related findings, is being used in ongoing legal proceedings against Bambu Lab. In order not to compromise those proceedings, no further technical details can be disclosed at this stage. While this vulnerability may indeed pose a risk to other users, Bambu Lab has expressly stated that no such issue exists. Even after being provided with a step‑by‑step video demonstration, they maintained that there is no flaw in the firmware.
Exposing the fact that there is a genuine risk is the entire point, even if that is not immediately understood by everyone.
The first issue received nothing more than an automated response, and the subsequent reports were largely ignored.
They also claimed that the problem was caused by my use of a third‑party build plate, so I deliberately chose to sacrifice my original textured PEI plate. I recorded a video and prepared step‑by‑step instructions while reproducing the procedure in which the nozzle destroys the build plate and, in some cases, the nozzle itself.
However, if you consider this an unnecessary thread, I can certainly stop reporting issues of this kind.
Accordingly, this will be my final response here on these matters.
I still need to verify the last one, but yes, there were a few homing incidents where the printer performed some abnormal movements during homing.
As for why I am doing this, some might ask: I became frustrated with Bambu Lab’s refusal to acknowledge that this problem exists, even though it affects at least two different machines. When you inform support that the issue is damaging the printer and potentially affects many users, and the only response you receive is essentially “No, we do not have a problem and will not fix this,” you are forced to take more drastic measures.
I got you now, I remember. I agree with your sentiment.
Side note: I’m not willing to try for science, but I wonder if they fixed the end stop sensor bypass issue when moving the bed up manually yet. I remember seeing a few people bend their upper Z screw mounts when using cleaning tools and pressing up one too many times.
So this came up for me today. I wonder if it’s related to your topic. It only says it’s for the H2C though. I did also notice there’s a beta H2C firmware available but I haven’t seen what it includes yet.
Being a preset and not a firmware update, it could only change the printer preset. I should have recorded the H2C preset before and after the update to look at the changes that may then be modified manually in the H2D preset.
Strange, it’s only a preset because I wonder how this could apply to a re-print pre-preset…
Not entirely sure, as I don’t own an H2C and probably never will. It’s not that it’s a bad machine, but given what I do with my printers, I just can’t justify the price for it. That said, it is definitely an interesting platform.
One major issue with these kinds of problems is that they are very hard to properly diagnose, since Bambu Lab is extremely secretive about its firmware. Sometimes it almost feels like the only way to really understand what is going on would be to bribe an underpaid employee for access to the source code – you’d just have to find the right person and offer the right amount of money.
I am laughing just for the ending, scaring the poor people 
