i have a strange problem with my H2C (Firmware: 01.02.00.00).
I start a print (it does not matter if Studio or Handy). The print finishes without any problem. After that i start another print (no power cycle between prints). This print will fail.
It starts during the foreign object detection task. First there is a warning like “nozzle camera malfunctioning”, which shows up in the assistant but the printer continues. A few moments later the task stops with the “tool head camera initialization failed” error from the below screenshot. If i power cycle the printer everything is good again. The first print never fails.This also happens via Bambu Handy.
Yeah Im having the same issues with my H2C, I would say for the first 10 or so prints it was fine, but now I get this error on every print…if I reboot the machine and give the lens a wipe I found it wont give me the error for a single print, but then it happens again for every print thereafter, I havent opened a ticket for it myself yet as Ive only just recovered fro mthe PTSD incurred from fixing my H2S, but i would be interested to hear if any outstanding issues are acknowledged as lots of people are reporting this same issue.
„Glad” i am not the only one. So far the only Suggestion from Bambu was to check both ends of the usb c Kabel between toolhead and ap board - which would mean I would have to disassemble the whole back of the toolhead with all its tiny cables and connectors.
I already tried a software downgrade, reset and then upgrade again. I now cannot calibrate the Vortek rack anymore. There also now always is a camera error during the calibration. Even a power cycle does not help.
The Toolhead Camera was replaced first, and it worked for a few days before the same Toolhead Camera initialization failed error returned.
I replaced the TH Board and the USB-C cable, and the camera worked again for a few days, but the same error came back. The camera and its cable/connector were also replaced.
Has anyone experienced the same sequence of failures, and what did Bambu replace next?
I didn’t have the exact same sequence of errors, but the past couple weeks I began having intermittent “Nozzle Camera malfunctioning” errors, which became constant and not intermittent after a few days, and was soon followed by “Toolhead Camera Initialization Failed” errors.
Bambu first told me to disassemble the toolhead and remove the Extruder Interface board so I could unplug the connectors for both cameras and plug them back in. Then reasssemble the entire thing just to learn it did not work. So they offered to send me a new nozzle camera which requires the same disassembly/reassembly process.
They refused to send a new toolhead camera or TH board until they see if the Nozzle camera alone fixes it. Which is great for them, not so great for me and all the hours I have to spend tearing apart and putting the toolhead back together time and time again.
In the meantime, someone different at Bambu support told me to try rolling back the firmware which suggests to me this isn’t an unknown problem to them at this point.
I’m still in the process of sorting the issue out but the entire process has really soured me on Bambu a bit. Disassembling the toolhead with all the tiny fragile cables is not an easy task. And worse, the support website is hard to navigate, unclear in many cases, has multiple instances of different procedures for the same task, and in some cases links to pages in Chinese for users of the English language site.
It’s just insane that rather than providing proper warranty service, they are asking consumers to undertake precision electronics repair on a seriously complex piece of electronic machinery.
I have the same problem with the cameras, too. Bambu offered to replace them, but I don’t think the issue is the hardware.
I think it’s the firmware.
I just ignore the error messages since they don’t affect the print quality, but it’s still annoying.
If it for instance also contains several configuration files that contain settings for certain devices, it might just be that some files were not part of the previous version and therefore the rollback doesn’t fully restore.
It is just a thought. But could explain why rollbacks don’t always seem to exactly restore the previous state.
The printer contains several microcontrollers that run firmware. An update always includes the firmware for all the printer’s microcontrollers, as well as updates for the AMS/AMS2/AMS-HT firmware. During the update process, all firmware components are updated sequentially. Rolling back always restores the system to its previous state (except in cases where the manufacturer states that “rollback is not possible after this update”). However, this has not yet occurred with these printers.
That said, performing a full printer reset when downgrading the firmware is always a good idea, as it can sometimes resolve certain issues.
I was basically comparing this to a software update method that is commonly used.
Initial installer contains all executables and configuration files.
Updates (MSP’s) usually only contain the files that have changed since the initial release.
So take this hypothetical scenario:
Initial install contains 50 files
Update 1 contains 10 files (only changed) files
Update 2 contains 15 files (the 10 from the previous update plus 5 new updated files
What would happen if you restore only the 10 files? Normally you would have to do the initial install and then the required update 1.
But in this case. Based on what you are telling me, each version contains all the files required for that version.
It’s pretty annoying. Not only the issue itself and that it does not seem to be clear what the actual issue is, but also that I am not able to fully use the printer anymore since I am not able to configure the Vortek rack.
When updating the printer over a network, the manufacturer may use a “delta update” system to reduce processing time by updating only those firmware modules that contain changes.
However, when updating or downgrading the firmware using a file, all modules are completely overwritten, regardless of whether they contain changes.
Also, when you downgrade over the network, you get the “full version” containing all the modules. A delta update can only be applied when upgrading between two consecutive firmware versions. I’m not sure if Bambu uses this method. I wouldn’t…
I have an X2D for 2 weeks now, current FW 01.02.00.00, BambuStudio Beta 2.8.4.57.
Printed fine all the time until yesterday evening.
It finished some fidgets and when I wanted to print a new project the toolhead initialization error appeared.
A restart didn’t work.
Created a ticket now, uploaded the logs. Have to check the cables next.
Wanted to share that it’s happening also to the X2D and according to other posts to multiple people.
I’ve received a message from Bambu saying that they’ll send me the two cameras and explain how I can fit them into the printer.
But when I read this, it doesn’t seem to work. It’s a firmware error.
Fitting the cameras is also very complicated, and if it doesn’t work, I won’t bother doing it.
Based on my ticket, I had to check / reconnect the cam cable (which I did).
First print went fine without the initialization error, but already the second one came back with it.
Updated the ticket and will receive now also a new cam.
Once I exchanged it, i can give an update…
