I’m not sure if I’m the only one experiencing this, but my H2C printer is having issues. Just before starting a print—after completing all the calibration steps—it suddenly displays an error message: “Liveview initialization failed.” At that point, the printer becomes unresponsive, keeping the nozzle heated but not moving any further.
I have contacted support multiple times and even replaced the liveview camera, but that didn’t resolve the problem. I mentioned to them that, on a few occasions, I could still see the liveview image even after the error appeared.
It seems the issue might be with the AP board (possibly the CPU is stuck) or a firmware error, although I doubt the latter since I have already reset the printer to factory settings, and the problem still occurs—even with the models included with the printer.
This has been going on for more than two weeks now. I’m becoming desperate because support doesn’t seem to understand or help with my issue. I’ve sent them logs, but I’m not even sure if they’ve looked at them.
The problem seems to be either coming from AP board (CPU is stuck) or firmware error but I don’t think so since I performed the resume to factory setting and it happens even with included models in the printer.
It is lasting for more than 2 weeks. I become to be desperated because the support doesn’t seem to understand/help me on my issue. I sent them logs but I even wonder if they looked at them…
If you carry out any actions that support has not explicitly requested and the AP board appears to be damaged, you may not be eligible for a replacement unit. If they ask you to remove it or to perform specific checks, you are safe as long as you follow their instructions.
In my case, I had to purchase new eddy sensors because mine were glued to the TH board, even though both the TH board and the eddy sensors must be removed (from connectors) to replace the hotend cooling fan.
It is very frustrating to be stuck in the support loop and forced to play the waiting game.
You’re not the only one seeing this on H2; there are documented “liveview initialization/startup” and “camera connection” issues that match your symptoms.
From the H2 troubleshooting docs, there are three relevant cases:
Described as an abnormality during startup of the liveview camera that causes the video stream to fail.
There is a known firmware bug in version 01.01.01.00 and earlier: if the printer is started with a USB drive plugged in, this error can appear. The workaround is:
Power off the printer.
Remove the USB drive.
Power on the printer without the USB drive.
After it boots, plug the USB drive back in.
If the error still appears without a USB drive, the docs say:
Restart the printer and see if the HMS alarm disappears.
If it disappears, it’s treated as a software timing issue and support will want logs.
If it persists, it’s treated as a hardware problem and you move on to checking the liveview camera connection.
Liveview fails to initialize / AI functions disabled (HMS 0C00_0400_0002_0026 or similar text)
Described as “when the liveview camera fails to initialize, some AI detection functions such as foreign body detection and spaghetti detection will fail, and the device will pop up this alarm prompt.”
The official process is:
Check that the liveview image is normal and the privacy cover is not blocking the lens.
Restart the printer.
Update firmware to the latest version.
If the issue persists after multiple restarts on the latest firmware, contact customer service.
Liveview camera connection/signal issue (HMS 0500_0600_0002_0004 or similar)
Described as the AP board not being able to detect the liveview camera due to signal loss (loose cable, bad camera, or AP board failure).
The H2 procedure is:
Step 1: With power off, check and re‑seat the liveview camera connector on both the AP board side and the camera side, then restart. If the HMS error disappears, it was a loose connector.
Step 2: If the error persists, replace the liveview camera.
If the issue still persists after replacing the liveview camera, the docs say to provide logs and contact customer service for further confirmation.
In your case:
You’ve already reset to factory settings and the problem occurs even with built‑in models, which strongly suggests it’s not a slicer/profile issue.
You’ve already replaced the liveview camera, and you sometimes still see the liveview image even when the error appears. That fits better with a startup/initialization or AP‑side problem than with a simple dead camera.
The official documentation does not give a user‑level procedure to definitively test or replace the AP board on H2; it stops at:
Check/re‑seat camera connectors.
Replace the camera.
If the error persists, collect logs and escalate to customer service.
So, within what’s documented, the concrete things you can still verify yourself are:
Confirm the exact HMS code shown with “Liveview initialization failed.”
On H2, the behavior you describe could be:
0C00_0400_0002_0026 or similar (liveview fails to initialize / AI functions affected).
0500_0600_0002_0004 (liveview camera connection issue).
Knowing which one it is matters, because the steps differ slightly.
If it’s 0500_0100_0002_0001 and you ever boot with a USB drive inserted, rule out the known USB‑boot bug:
Power off, remove any USB drive, power on without it, then plug it back in only after the printer is fully started.
With power off, re‑seat the liveview camera connectors on both ends, even though the camera is new:
Open the AP board cover and unlatch/re‑insert the liveview camera connector on the AP board.
On the camera side, unplug and re‑plug the connector as per the liveview camera replacement guide.
Then restart and test again.
Make sure you’re on the latest firmware and try several restarts plus a small built‑in model.
If you’ve:
Ruled out the USB‑boot bug,
Confirmed connectors are firmly seated on both AP and camera sides,
Already replaced the liveview camera,
Are on the latest firmware and have tried multiple restarts,
and the printer still freezes at “Liveview initialization failed” right after calibration, then you’ve effectively exhausted all user‑level steps that the official documentation describes. At that point, the docs explicitly say to provide logs and work with customer service, because further diagnosis (including AP board) is not user‑serviceable in the guides.
When you go back to support, it may help to:
Tell them the exact HMS code and that you have already followed all steps from the corresponding H2 wiki page (restart, USB‑boot check if applicable, connector checks, camera replacement).
Emphasize that the issue persists on factory‑reset firmware and built‑in models, and that the liveview image sometimes still appears even when the error is raised.
I’m limited to what’s in the official knowledge sources, so I can’t confirm from here that your AP board is faulty, but your description is consistent with a problem beyond the camera itself, and the next step per the docs is indeed deeper hardware diagnosis by support
Hello, thanks for the advice. To be honest, I spoke about the AP board because I saw it in the help but I didn’t carry any action on it and they didn’t ask me anything about it. I am very happy at the end because they asked me to send back the printer to replace it. I thing it is the best solution for them and for me because it could have last for a very long period of time if not…So finally I am happy with their support because they gave me a solution and issues can happen whatever the quality of your product and they have been very professional with me even though it took a while