Feature Request: Per-nozzle tracking + material memory for Vortek hotends

Bambu Lab H2 Series
1

Feature Request: Per-nozzle serial number tracking + material allocation memory for Vortek hotends

Vortek hotends already broadcast identity data to the toolhead wirelessly (nozzle temp, heatsink temp, and apparently type/size info, based on the existing “Read nozzle info” auto-detect on the H2D TPU hotend). Given each Vortek nozzle already has a chip capable of two-way communication — and the printer already needs to know exactly which physical hotend is mounted in each of the up to 7 slots for the zero-purge swapping to work — it seems like a relatively small software/firmware addition to extend that existing per-unit awareness into persistent material allocation tracking.

The problem this would solve:
Many of us already do this manually — keeping a dedicated set of nozzles per material (PLA, PETG, PA, TPU, CF blends, etc.) to avoid cross-contamination, since even trace amounts of one material can affect surface finish or mechanical properties in another. Right now that’s entirely a manual bookkeeping exercise (labeling nozzles, remembering which one is “the TPU one”), with no help from the printer or Bambu Studio.

What I’d like to see:

  1. When a nozzle is installed, the printer reads its unique ID.
  2. In Bambu Studio / Handy app, let users label that specific nozzle (by serial number) with an assigned material — e.g., “Nozzle #A2F91 → TPU only.”
  3. The printer remembers this assignment persistently, even if the nozzle is removed and reinstalled later, or moved between machines.
  4. If a print job calls for a different material than what’s assigned to the loaded/selected nozzle, show a warning (“This nozzle is assigned to TPU — continue anyway?”) rather than silently printing.
  5. Optionally, track cumulative material usage/hours per nozzle for wear/maintenance reminders, not just material type.

This seems most naturally suited to Vortek hotends given their existing bidirectional comms and the fact that per-unit identification is already a requirement for the system to function. That said, if standard quick-swap hotends (H2D/H2S/H2C left nozzle) already carry a unique identifier internally for QC or other purposes — rather than just a shared type code — the same tracking could presumably apply there too. Curious whether that’s the case, or whether it really is Vortek-specific hardware that would be needed.

Would love to hear if this is already on a roadmap, or if there’s a technical reason (chip memory size, etc.) that makes this harder than it sounds from the outside.

2

Hasn’t this been done a long time ago???

And one more thing: Vortek hotends have one-way communication: from the hotend to the printer. The printer has nothing to write to the hotend, and there’s no reason for it to do so.

3

If it has, I have not found it. And I asked ChatGPT about it, and it said it didn’t exist, but could be done with software only.

And I am not suggesting any two-way communication. I am suggesting that Bambu Studio and/or Bambu Cloud keep track of the individual identification and material allocation/assignment. Nothing needs to be written back to the hotend. It’s just like the RFID chip on the Bambu filaments. Bambu Studio KNOWS it is PETG/PLA/etc., and automatically pulls that material into filament availability on AMS.

4

Correct me if I’m wrong, but isn’t that what the system already does?

The filament memory feature - quote:

Each Vortek hotend’s onboard PCB stores information about which filament it was last used with. When you start a new print, the printer reads each hotend’s stored assignment and suggests using the same material again. This removes the configuration step of telling the printer what each nozzle contains - it already knows, because the nozzle remembers. It also prevents the most common multi-material setup error, loading the wrong material into a slot that was previously used for something incompatible. The system surfaces a warning before it becomes a problem rather than after.

Screenshot 2026-08-28 233350
Screenshot 2026-08-28 2333501575×1271 238 KB

What features are you still missing?

5

Don’t put machine operating data on the cloud or on computers that aren’t permanently connected to the printer. They need to stay on the machine.

6

Here is an example. I have a Vortek hotend in Rack position 6 which has only printed TPU. I was going to print PETG, and had a blobby hotend on the toolhead, so I picked Vortek #6, and it said absolutely nothing. It was perfectly willing to use that hotend, whereas I would want it to warn me that the hotend on Vortek #6 last printed TPU, or has been allocated/reserved for TPU. That doesn’t seem all that complicated to accomplish.

7

I think like you that it does not use the info to select the nozzle by material. I also have a dedicated TPU nozzle but keep it off the rack and only install it when required.

This said, you can access type of material and color used on the printer. Go to « Nozzle and Extruder » menu, then click on « Hotends and Rack », at the bottom of the page click on « Hotends Info » and by clicking R to 6 at the top, you get material, color, usage and type of each hotend. I haven’t seen that in BS but same exists in bambu handy.

It may be also available in BS but my hotends screen is cut off at the bottom in my config so cannot access if it’s there

8

Requirements: Dedicated Hotend Reservation,
Preferential Assignment & Mismatch Protection
Reviewed draft - H2C/Vortek minimum viable feature plus optional extensions

  1. Objective
    Extend the H2C’s existing hotend memory and automatic filament-to-hotend mapping so a user can intentionally reserve a physical hotend for one or more compatible filament categories. The system should prefer that hotend during assignment and prevent an unintended material from being routed through it without an explicit user decision.
    The feature must distinguish factual history (what material last passed through a hotend), user policy (what material is allowed or preferred), and the current job mapping (what the slicer plans to use).

Motivating Use Cases

· A hotend reserved for TPU or another flexible material should not unintentionally receive rigid engineering filament. Cross-use can introduce residue and may create feeding, retraction, or extrusion problems when the hotend returns to flexible material.
· A designated abrasion-duty hotend should preferentially receive CF-, GF-, or otherwise abrasive filament, while hotends reserved for non-abrasive material should be protected from accidental abrasive use.
· A hotend maintained for color-pure, translucent, natural, or contamination-sensitive filament should not silently receive another color or material that could leave visible residue.
· A hotend reserved for support or interface material should not be reassigned to model material without warning when the user intends to keep those material paths separate.
· A hotend maintained under a user’s food-contact contamination-control practices should not receive an unintended material without an explicit override. This feature supports segregation but does not itself establish food-safety compliance.
· A hotend reserved for a material requiring specialized calibration, cleaning, or residue management should preferentially remain paired with that material family.

  1. Scope and Confirmed Existing Behavior
    Minimum viable scope: H2C, including the six interchangeable Vortek induction hotends and the fixed left hotend where that hotend has a stable system identity. The design may later be extended to H2D/X2D-class dual-nozzle printers, but that extension should not delay or complicate the H2C implementation.
    Bambu Lab states that each H2C hotend has onboard memory recording the filament last used, that the printer recognizes and suggests reuse of the matching hotend, and that its algorithm automatically assigns filaments to hotends. The requested feature therefore adds persistent user intent and an enforceable mismatch interlock to an existing identity, memory, and assignment framework; it does not prescribe where additional policy data must be stored.

  2. Definitions
    Physical hotend - An individually identifiable extrusion unit. For Vortek, identity follows the hotend, not the magazine slot or current mount position.
    Material history - Observed or user-declared information about material previously extruded through a hotend. History is evidence, not a reservation.
    Reservation - An explicit user policy defining which filament profiles or material classes a physical
    hotend should preferentially or exclusively serve.Job mapping The filament-to-hotend assignment selected for a specific plate or print job.
    Mismatch - A planned or actual routing that violates a hotend reservation or cannot be verified
    against it.Override An explicit user decision allowing a mismatch for the current job, with or without a separately confirmed reservation change.

  3. Minimum Viable Requirements
    4.1 Identity, History & Reservation State

REQ-1: The system SHALL bind every reservation to a stable physical hotend ID, not to a Vortek magazine slot. Moving a hotend between slots SHALL not change its reservation.
REQ-2: The system SHALL maintain material history, reservation policy, and current job mapping as separate states. Material history SHALL NOT create, change, or remove a reservation without explicit user confirmation.
REQ-3: A user SHALL be able to reserve a hotend using one or more matching criteria: exact filament profile, material family, material property class (for example abrasive, flexible, or support material), and optional color/profile identity when contamination or color purity matters.
REQ-4: Each reservation SHALL support an enforcement mode: Prefer only (automatic assignment when possible), Warn (default; stop for confirmation on a mismatch), or Strict (interlock until the user cancels or deliberately overrides).
REQ-5: The user SHALL be able to view, create, edit, clear, or copy a reservation. Any action that weakens or
removes an existing Warn or Strict reservation SHALL require confirmation.
REQ-6: Reservation and last-material state SHALL remain associated with the physical hotend across slot changes, printer restarts, Bambu Studio updates/reinstallation, and printer firmware updates. The implementation may store or synchronize this state on the hotend, printer, account, or a combination of these locations.

4.2 Preferential Assignment
REQ-7: Before applying a reservation preference, the assignment engine SHALL first filter for physical and slicing compatibility, including printer side/path, nozzle diameter, hotend type or flow class, temperature/material capability, and the active slicing profile. A reservation SHALL never cause an incompatible hotend to be selected.
REQ-8: When one available compatible hotend matches a filament’s reservation, the system SHALL preferentially map that filament to the matching hotend and display the resulting mapping before printing.
REQ-9: When multiple available compatible hotends match, the system SHOULD choose deterministically using existing job constraints, prior material match, and purge minimization, while allowing the user to change the mapping before submission.
REQ-10: If the reserved hotend is unavailable, incompatible with the sliced job, or already needed by a conflicting reservation, the system SHALL not silently choose a mismatched reserved hotend. It SHALL offer only
executable choices: install/select a matching hotend, select an unreserved compatible hotend for a one-time override, explicitly change a reservation, revise the job, or cancel.
REQ-11: For multi-filament and multi-plate jobs, the system SHALL evaluate the complete mapping, identify all conflicts together, and avoid resolving one filament in a way that creates a hidden conflict for another.

4.3 Validation and Interlock
REQ-12: The system SHALL validate reservations after the job’s hotend mapping is established and again at print submission.
REQ-13: Immediately before extrusion and after every actual hotend change, the printer SHALL revalidate the job mapping against the installed physical hotend ID and the selected material source. A manual swap after slicing SHALL therefore be detected.
REQ-14: Validation SHALL apply regardless of launch path, including Bambu Studio, Bambu Handy, the printer touchscreen, reprint of a stored job, and resume/recovery where the mapping could have changed. A launch path that cannot present a safe resolution workflow SHALL pause rather than bypass the reservation.
REQ-15: When a mismatch is found, Warn and Strict modes SHALL interrupt automatic or one-click continuation and identify every conflict in one dialog or screen.
REQ-16: An unrecognized or custom filament profile SHALL be treated as Unknown unless the user maps it to a reservation criterion. The system SHALL not infer compatibility solely from a profile name or color swatch.
REQ-17: If current hotend identity or reservation state cannot be read or is stale, the system SHALL say so explicitly. It SHALL not report a protected match based on unverified state.

4.4 Override Workflow
REQ-18: For a mismatch, the system SHALL offer: Cancel; Override once; or Override and edit reservation. The last option SHALL show the exact rule that will be added, removed, or changed before it is saved.
REQ-19: Override once SHALL apply only to the current print job and SHALL expire before the next job. It SHALL not alter the reservation.
REQ-20: An override SHALL require an affirmative, non-default action. The default action SHALL be Cancel or return to mapping.
REQ-21: After an overridden print actually extrudes material, material history SHALL record what was used even though the reservation remains unchanged.

4.5 UI and Diagnostics
REQ-22: The device and mapping views SHALL show, at minimum, a recognizable physical hotend ID/serial suffix, current slot or mount, nozzle diameter and type, last-known material, reservation rule, and enforcement mode.
REQ-23: Material identification SHALL include text labels; color alone is insufficient because different materials may use the same displayed color.
REQ-24: The mismatch screen SHALL state the physical hotend, its reservation, the planned or detected material, why they do not match, and the practical consequence where known (for example abrasion, residue, or process incompatibility).
REQ-25: Reservation management SHALL be available in Bambu Studio and on the H2C touchscreen. Bambu
Handy SHOULD at least display reservation state and allow resolution of a print-start mismatch.
REQ-26: The user SHALL be able to view at least the last-known material for each hotend. A longer recentmaterial history with timestamps SHOULD be provided where the printer/account already retains the underlying data.

4.6 State Controls and Replacement
REQ-27: Disabling the feature SHALL suspend preferential assignment and mismatch enforcement but SHALL retain reservations and material history. Re-enabling the feature SHALL restore the prior policy state.
REQ-28: When a different physical hotend ID appears in an occupied slot, the system SHALL use that unit’s own reservation or treat it as unreserved. It SHALL not silently inherit the prior unit’s reservation based on slot position. The UI MAY offer a deliberate Copy reservation action.
REQ-29: Reservation checks SHOULD add no material delay when current state is locally available. If synchronization is required or unavailable, the UI SHALL expose that condition rather than silently using uncertain data.

  1. Optional Later Enhancements
    • Reservation suggestion based on repeated observed use, provided it is always presented as a suggestion and never becomes a lock without confirmation.
    • Exportable per-hotend material and override history for troubleshooting.
    • Administrator-controlled override policy and audit notes for farms, labs, and classrooms.
    • Fleet-wide reservation templates and reporting.
    • Conflict notifications for rare simultaneous edits from Studio, Handy, and the touchscreen; a silent last-writewins policy should be avoided for protected state.

  2. Acceptance Criteria
    AC-1: Given a physical hotend has a Warn reservation for flexible/TPU materials, when a job maps PETG to that hotend, then print submission stops and names the hotend, TPU reservation, and PETG mismatch.
    AC-2: Given white TPU and white PETG are both present, when the mapping is displayed, then each is identified by material text/profile as well as color, and only TPU matches a TPU reservation.
    AC-3: Given a reserved 0.4 mm standard-flow hotend matches the material but the job is sliced for a 0.6 mm or high-flow hotend, when assignment runs, then the reserved hotend is rejected as incompatible rather than selected by preference.
    AC-4: Given the matching reserved hotend is not available, when the user submits the job, then the system presents only compatible actions and does not silently use a hotend reserved for another material.
    AC-5: Given the user selects Override once, when the job completes, then actual material history is updated, the reservation is unchanged, and the override does not carry into the next job.
    AC-6: Given multiple job filaments create two reservation conflicts, when validation runs, then both conflicts are reported together before printing.
    AC-7: Given a Vortek hotend is moved to another magazine slot, when the printer reads it, then its reservation follows its physical ID.
    AC-8: Given a different hotend replaces it in the same slot, when the printer reads the new ID, then the prior unit’s reservation is not inherited.
    AC-9: Given enforcement is disabled and later re-enabled, when the same hotend is viewed, then its prior
    reservation and material history remain intact.
    AC-10: Given a custom profile has not been mapped, when it is assigned to a protected hotend, then the system reports Unknown and requires an explicit decision rather than assuming a match.

  3. Basis for Existing-Capability Statements
    Bambu Lab, H2C: where Multi-Material Vortek System meets engineering precision (official product announcement describing six interchangeable hotends, automatic filament assignment, and onboard memory of the last-used filament).