Preventative maintenance that listens to the printer
The Bambu printer already knows when something needs attention. SimplyPrint just turns that signal into a scheduled, assignable task on the right machine, with the right template, instructions and spare parts.
How SimplyPrint reads Bambu HMS
Every Bambu Lab printer raises HMS codes (16-character hex strings, e.g. 0501040000030002 for "threaded rods need lubrication") and device error codes (8-character hex) as it detects issues. SimplyPrint ingests every code your Bambu fleet raises, matches it against a built-in mapping of "this code means this maintenance task", and if a match exists, can auto-create the task on the printer that raised it.
The mapping ships out of the box. You can extend it by attaching notification-based triggers to your own maintenance task templates - pick the codes that should trigger this template, and we handle the wildcards (e.g. AMS-A through AMS-H) for you.
Add your own HMS-driven templates from day one
The built-in mapping is opinionated, not exhaustive - and customisation is a first-class flow, not an advanced afterthought. To add a code SimplyPrint doesn't already map - or to route a code to a different template - open any task template, set the trigger type to notification-based, and pick the printer notifications that should fire it. Choose match mode "any of these" to fire on the first matching notification or "all of these" to require every code to have been raised at least once.
Threshold + window controls let you avoid noise: "create a job only after this code has fired 3 times in the last 7 days". Useful for transient warnings you don't want to schedule the team for on the first occurrence.
What's mapped out of the box
SimplyPrint ships with mappings for the most common HMS codes - see the full HMS reference for the complete table. Each one wires to a recommended template you can adopt or replace with your own.
HMS code raised when threaded rods need lubrication.
Carbon rods, linear rods or rails dirty or resonance-frequency off.
Extruder clog, failed extrusion or purge timeout across AMS slots.
Foreign objects, spaghetti failure or bed-laser obstruction detected.
Purged filament piled up in the chute - tool-head collision risk.
Micro-Lidar lens dirty or laser readings too weak.
X or Y belt loose - homing or resonance frequency off.
AMS-aware, not just printer-aware
Bambu HMS codes embed the AMS unit and slot in the code itself (positions like 07xx for AMS A-H or 18xx for AMS-HT A-H). SimplyPrint's matcher handles those wildcards - one trigger like "extruder clog on any AMS slot" maps to all 16 underlying code variants without you having to enumerate them.
This means a template you author once works across every AMS configuration in your fleet - whether the customer is running a single P1S, a stack of X1Cs with multiple AMS units, or the high-temperature AMS-HT.
What happens when Bambu raises a code we don't know yet?
If Bambu raises an HMS code SimplyPrint doesn't recognise, the raw code is logged on the print job and surfaced as a generic "printer reported maintenance issue" event. You can then create your own HMS-triggered template against that code in two clicks - the notification picker shows every code your fleet has ever raised, with timestamps and the printer that raised them, so you have the data you need to decide what to map.
Stack HMS with time and usage triggers
HMS isn't an island. Most farms running Bambu fleets pair HMS-driven templates with time-based and usage-based schedules: lubricate every 200 print hours or when the rod-lubrication code raises, whichever comes first. The maintenance system creates one job, with whichever trigger fired - and the team doesn't end up doing the same task twice in a week.
Print-hours, filament-grams, print-count, time-based and HMS triggers all evaluate every hour against every active schedule. You define the rules; SimplyPrint creates the work orders.
All the maintenance feature on top
The HMS integration isn't a separate product - it's a trigger type on the standard maintenance system. You get reusable task templates, scheduled work orders with assignees and audit trails, batch jobs across the fleet, spare parts inventory with auto-deduction, problem reporting and the printer-maintenance-mode toggle (which removes the printer from rotation while the job runs) - all already covered on the main maintenance feature page.
See the full maintenance featurePlan access
HMS-driven scheduling is part of the standard maintenance suite. No separate add-on, no Bambu-specific surcharge.
| Feature / Limit | Free | Basic | Pro | Print Farm | Enterprise | School | Cloud Slicer | Filament Manager |
|---|---|---|---|---|---|---|---|---|
|
Printer maintenance
Master maintenance feature - included on Print Farm, Enterprise and School.
|
||||||||
|
Maintenance schedules
Includes notification-based triggers (HMS + device error codes) alongside time, print hours, filament use and print count.
|
||||||||
|
Task templates
Author HMS-mapped templates with thresholds and match modes (any / all).
|
Want to learn more about our plans?
View full pricing & feature comparison