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.