Here’s my extra two worthless cents about all this.
The new noise cancellation algorithm is working on a vast majority of printers without a problem. I believe H2D’s (and H2S?) have had it for a while now and they all use the same XYZ motion system. So it would be logical to assume H2C would work exactly the same, right ?
Well, I have had the unfortunate pleasure to go through several H2C units, which were returned due to various defects with them. This took place over several months, since launch. I did have a launch unit.
From that experience I have learned that even in the span of 3-4 months, the units I was receiving have had part variations in them, for the worse.
The launch unit developed a fault with XY motors. Its replacement did also, but that one also came with extremely noisy exhaust fan. I had both units for a short duration together and was able to take the fans out to inspect – they were completely different ! With the newer unit being so bad it was shocking. I kept the original fan moving forward, and several printer replacements later, that same original fan is still with me as every single one after the launch unit came with the new, horrible one.
I already mentioned that I received a replacement Z motor for this current one, which is also completely different from the stock one, having both visual physical differences, but more importantly – mechanical/electrical ones as well as it runs smoother and quieter. This kind of variation is not acceptable to me! I hate that Bambu is doing it. It is NOT like-for-like. The exhaust fan is absurdly worse than the original unit I cling on to. The Z motor is audibly inferior as well. I am scared to think just how many other, far less noticeable components are exposed to this kind of “variations”.
I know manufacturers source components from multiple sources, that’s how mass manufacturing works, but more often than not, new sources are introduced due to costs cutting measures.This approach does not always produce a like-for-like component. Exhaust fan and Z motor are two examples of that, I am sure if I had more components to replace, I would notice more of that.
Personally – I am convinced this is what is happening here with the knocking again, an alternative component (that is obviously saving Bambu money) started making its way into newer units, and it turns out - is not behaving the same as the original and Bambu now needs to scramble to try to work it out as – even if they noticed an issue and corrected it by going back to original part - until all of those affected units trickle out of the supply chain, this is what a lot of users will get. And I bet recall is not a financially viable option.
They could simply identify the offending part, and send out replacements though. However, what I really hate about this situation is that they are not admitting or revealing which part is at fault. Which, to me, means they prefer to hide it and try to mask with firmware they are supposedly working on.
What concerns me is that they offered me to replace this printer quite early on, at the same time saying that the replacement “may” also end up having the same problem. Which could mean this potential new component made its way to a lot of new units already and its just a matter of time more and more users start noticing the issue.
Then again, if new unit is sold and from the start is used with new firmware, the user might not even know the printer should not be doing this knocking and would assume this is just how it works. Perhaps this is part of their strategy ? Then again, it cant be, as there already are the likes of us, which will hold Bambu accountable and will not accept anything less than a full resolution to this.
Don’t really know what to say. The fact they are both keeping quiet about this and are extremely slow with replying to me, making little to no progress in fixing it, does give me reasons for concern.
Their very first response I received when I reported this problem was, and I quote: “rest assured that the sound you have noticed falls within the normal operating range of the printer, so there is no need for concern in this regard”. Which, pardon for my French, effin sent me ballistic.
Their first attempt at fixing it did nothing (gcode). It sure feels like they didn’t even bother to get a unit with the same exact issue, replicate the problem in the lab, and work on a reliable fix there and provide one ASAP.
Instead, it feels like they are making very relaxed “stab-in-the-dark”, “try-this” attempts, using our printers to test if it has worked or not.
If this is how they are going to be developing a fix for this, it will take years of back and forth.
I am sure I have made a ton of logical errors and/or I am simply wrong about a lot of what I wrote. I accept it and apologise if anyone is offended by my stupidity. I just wanted to vent a little as it has been well over a month and Bambu seems very relaxed about this and is yet to provide a fix.