I signed up a long time ago for the program to install beta firmware. During my experiments to try to solve the problem, I performed various firmware upgrades and downgrades, both beta and final versions. When I finally found the solution, I had installed a beta version of the firmware called 01.01.60, and I haven’t done any firmware upgrades since. I’m happy with it now; we’ll see what happens with future firmware releases.
I see.
Sorry for stupid questions, I am new to all this, but wouldnt the latest firmware have more (as in all) the latest fixes, developments and optimisations ?
I mean since whichever beta, there was more work done to the FW, which eventually resulted in the final release. Wouldnt it make more sense to use that instead of beta ?
After trying the various beta versions as they were released, I finally got to the official version, but like all the others, it gave me problems. At that point, I started doing various downgrades and upgrades until I had the idea of modifying the Z-hop mode. after that I didn’t touch anything anymore
Do you only have the H2C or do you have other Bambulab printers as well?
are there any other issues with the latest firmware ?
I am running it and your trick with ZHop mode did fix it for me…
I own an A1 as well but not using it since I got H2C, which is like 6 months now.
I am absolutley shocked with Bambu now that I learned what the actual situation is.
When I first reached out to support over a month ago, I first was issued a set of screws and nuts, then the z motor, then this was forwarded to RnD and eventually they gave me the gcode attempt that did nothing.
At no point did anyone from Bambu tell me its a known issue since a long time.
Quite the oppostite. The front liners seem totally unaware about this, which is why they tried to “fix” my printer with replacement parts, but then even the RnD team did not say anything and gave that gcode which did nothing.
Considering they are very clearly aware of this since beta, left it in the public, and 3 months later there sitll is no fix, I dont know man, doesnt look good to me…
NOTHING takes 3 months to fix. 3 months you take to develop a new feature from scratch, test it and roll it out. Not fix a bug …
… especially when the bug is not some obscure edge case almost never occuring, but one that happens during everyday normal operation using default, reccomended settings … bonkers !
oh and a P.S. - I love it how Bambu keeps telling me (us) to keep using the printer as the knocking will not cause any damage to anything nor will it affect print quality. GREAT, how about you explain to me (us) the exact mechanism of where the knock is coming from, why is it generated and what you are doing to get rid of it? If Bambu is so sure about their claim, why not just give us some transparency on the matter. Surely they wouldnt just say it if they werent absolutley sure this is correct, now would they .. ?
I agree with you. However, I must also say that during the beta testing of the firmware here on this forum, I heard people say everything was fine, and I heard people say everything is fine with the final firmware as well. It’s difficult for me to give a definitive opinion on Bambulab. I appreciate their effort to help me solve the problem. Of course, if I hadn’t found the z-hop solution, I would have gone back to the latest working firmware. I certainly wouldn’t have continued using the machine with that annoying and possibly even harmful metallic noise.
absolutley.
DId you notice any quality degradation when using normal z hop instead of spiral?
Also, I think we need to keep complaining, keep the presusre on, to get Bambu do something about this sooner rather than later.
I mean, if we just sit and wait, whos to say another 3 months wont pass and there still will be no fix.
I mean.. its been 3 months already. 3 months. Crazy. This falls into ignoring the problem rather than trying to fix it.
If enough peopple start complaining, I would expect it to finally generate a response.
maybe a few more spiderwebs of filament but nothing serious, all in all the quality remained good.
Has anyone raised a support ticket with Bambu about this?
Could you please let us all know how its going?
As for me, Bambu has sent me two more GCode files to run, which were meant to resolve this. Neither did. The only difference between the three I have been issued in total is with each one, there is less and less instructions, they strip away commands but the rest of the code is identical.
They also told me that when they give that to others affacted, which I suppose it means there ARE more, it resolves the issue for them.
Has anyone had a GCode from Bambu. Has it worked. Let us know please.
They are being extrememly unhelpful and not transparent about this. I cannot count the number of times they told me that “the best course of action is to patiently wait for the firmware update”.
Well, it has been nearly 2 months since I reported this to them, and nearly 5 months since they knew about this since Beta … what the ■■■■ Bambu ?!?!?!
Hi,
i have exactely the same issue as its desribed here with H2D version 01.04.00.00 (20260826)
After finding reddit thread that pointed me here, i have reverted FW version to 01.03.00.00 (20260303) and can hear the sound while zhop no more.
I created ticket US260903378001 with video and the sound, also referencing your ticket number in it as well.
Hopefully, it will get resolved in next version.
I find it very strange that FW 01.03.00.00 resolves it for you.
For H2C’s the noise was introduced with FW 01.02.00.00 (20260601) which brought the new motor noise cancellation and Bambu has sort of confirmed this is what is causing the issue.
But for H2D that same motor noise canclellation was intruduced in FW 01.03.00.00.
There is something more to it, it would seem… ?