The X1 Carbon pauses a print and shows an HMS code on the screen and in Bambu Studio, each code pairing a module number with an error number that points to a specific subsystem.
The X1 Carbon reports faults as HMS codes where the first segment is the module (AMS, motion, heat, toolhead) and the second segment is the specific error. The table below maps the codes we interpret most often and what you can check before sending logs.
| Cause | Likelihood | First Check |
|---|---|---|
| AMS slot filament not feeding (HMS 0Bxx / 03xx family) | High | Confirm the spool is seated, the PTFE path is clear, and the AMS buffer shows the correct slot in Bambu Studio |
| Toolhead heartbeat / MC board communication loss (HMS 05xx / 07xx) | Medium | Re-seat the toolhead cable on both ends and note whether the code returns after a clean power cycle |
| Chamber or nozzle temperature deviation (HMS 08xx / 09xx) | Medium | Compare the set point to the live reading and capture the temperature graph from the log |
| Motion system limit or stalled axis (HMS 04xx) | Low–Medium | Check for a blocked belt path or a part knocked into the travel range before resuming |
| Filament runout sensor false trigger | Low | Clean the runout sensor window and confirm the filament passes the sensor without slack |
Work through these in order. Every step is something you can do and report back on without opening the electronics enclosure or swapping parts.
Note the complete code shown on the printer and in Bambu Studio, including the module and error numbers. The exact string decides whether the fault is AMS-side, motion-side, or heat-side.
The leading number tells you which subsystem raised the fault. AMS and filament-feed codes are almost always clearable from the slicer; motion and MC-board codes usually need a cable and power-cycle check first.
For feeding codes, reload the spool, clear the PTFE path, and retry the load sequence. Many AMS faults clear after a single reseat and do not need a part.
From Bambu Studio or the printer, export the diagnostic log and the temperature graph. The log timestamps which module faulted and whether it repeated after a reset.
Share the exact HMS string plus the exported log. We map it to the module and tell you whether it is a remote-clearable software state or a physical part to inspect.
An HMS code is the X1 Carbon's structured way of reporting a subsystem fault, not a confirmation that a board or motor is dead. The module segment tells us whether the issue lives in the AMS and filament-feed path or in the motion and control electronics, and the error segment narrows it to a specific check. Most feeding and sensor codes clear remotely; only a small share point to a physical connector or part that needs hands-on inspection.
When you are unsure which subsystem owns the fault, the broader collections help: Error code / fault buffer covers how manufacturers encode faults, and 3D printing & toolhead systems explains AMS, heat, and motion behavior. For the same printer family, also see Bambu Lab X1 Carbon — Not Extruding and Bambu Lab AMS — Not Feeding, which share several HMS codes with this page.
If the code returns right after a clean power cycle and a reseat, treat it as a persistent hardware signal rather than a transient software state, and send the repeated log so we can confirm the subsystem before you order anything.
Send the exact HMS string and the exported log. We decode the module and error number remotely so you know which faults clear in software and which need a physical inspection — no part swap on our call.
Submit Your Case Connect With SpecialistsWe do not perform hardware repair, we do not replace parts, and we cannot promise a 100% resolution. Our role is limited to remote diagnostic and step-by-step guidance based on the information, photos and logs you share.
An HMS code is Bambu's structured fault report. The first segment names the module (AMS, motion, heat, or toolhead) and the second names the specific error. We read the full string and the log to tell you which subsystem is involved.
AMS and filament-feed codes, runout-sensor false triggers, and many heartbeat faults clear after a reseat, reload, or clean power cycle. We confirm the pattern from your log before you assume a part is needed.
A code that returns immediately after a reset usually points to a persistent physical signal — a loose toolhead cable or a failed sensor — rather than a software state. We compare the repeated log entries to confirm the subsystem.
Almost never on the first report. We resolve most codes from the string and log and only suspect hardware when the fault repeats after a clean reseat and power cycle, which we verify with you.
When an HMS feed code turns into no filament at the nozzle.
The AMS-side cause behind many 0Bxx / 03xx codes.
When the fault is link loss rather than a subsystem error.