Set Up Material Mapping and Loading

A multi-material job has at least two maps: the physical map from spool or inlet to slot, gate, extruder, or tool, and the job map from a slicer filament or tool number to that physical position. Write both down. A profile can look correct in the slicer while the spool, tube, sensor, or printer menu still describes something else.

Start with a system identity card

Before loading anything, record:

• printer model and exact variant, feeder or tool-changing system, generation, and slot or tool count;
• printer firmware, feeder firmware, slicer and release, printer profile, filament presets, and the date of the check;
• spool brand and product, material family, diameter, dry state, spool dimensions, and any flexible, brittle, soluble, or fiber-filled warning;
• nozzle or tool identity, plate and model context, and whether a buffer, hub, cutter, selector, PTFE route, or external spool path is installed;
• the physical position assigned to each material, the material the system believes is loaded, and the filament or tool number assigned in the sliced job.

Keep this as a current setup record. Do not infer compatibility from a familiar product name. Prusa’s MMU3 guidance, for example, makes the printer family, MMU firmware, printer firmware, kit, extruder parts, and G-code/profile family one compatibility decision. QIDI’s guide likewise asks for printer, nozzle, filament, and process presets before slicing.

Inspect the physical path before the software map

Follow the exact manual for the named system. Check that each spool turns freely and that the tube route is not kinked, crushed, contaminated, or routed to the wrong inlet. Inspect buffers, hubs, selectors, cutters, bearings, PTFE collets, and filament sensors where the manufacturer includes them. A sensor state is an observation, not proof that filament can travel through the complete path.

For a Prusa MMU2S/MMU3, the documented workflow includes sensor state, selector and cutter inspection, idler or pulley condition, PTFE orientation, filament-tip shape, and a controlled test of positions. Other systems need their own sequence. A Creality CFS uses its own slot codes and printer connection; a Flashforge AD5X IFS guide ties holder number, installation position, and configured channel together. Those are useful examples of state to record, not a portable wiring rule.

Check material boundaries before forcing a load. The Bambu A1 AMS Lite guide warns against several flexible, absorbent, hard, brittle, or third-party fiber-filled material classes and gives spool dimensions for that system. The Bambu AMS HT guide has a different product-specific material list and feed path. A filament that works in one feeder is not thereby approved for another.

Reconcile the slicer and printer maps

In the slicer, assign each model part, support feature, or tool call to the intended material. Inspect the preview after slicing. For systems that expose a printer-side remap screen, verify the resulting assignment there as well. Prusa documents different mapping availability by printer family and connection path; Bambu Studio requires model parts to be assigned before slicing and uses the sliced preview to inspect assignments. OrcaSlicer also distinguishes single-extruder multimaterial mode, manual changes, and multi-extruder execution.

Use system-specific tool identifiers. Prusa MMU2S/MMU3 documents five positions and T0–T4 tool identifiers; that does not establish how another feeder names its channels. If the actual filament differs from the preset, correct the mapping rather than relying on color or a remembered slot. Metadata such as RFID can reduce typing, but it does not prove material identity, dryness, or physical feed success.

Verify one small change

Use the manufacturer’s normal preload, load, unload, or tool-change operation. Then run a small test object or a short sequence that exercises the mapping. Verify that the intended material reaches the nozzle or tool, the sensor state changes as expected, the change completes without unusual resistance, and the previewed assignment matches the result. Record the first failing position and stage.

If the test fails, keep the map and the observed state. Do not change firmware, filament, path routing, and slicer settings together. Move to diagnose failed tool changes and feed errors . If a hardware, firmware, or profile change caused the mismatch, use compatibility and versioning before repeating a long job.

A successful small change is evidence for that named system, material, profile, and test—not a universal guarantee. Never bypass a sensor, force filament through a blocked path, or reach into moving or hot hardware. Use the exact manufacturer service procedure when inspection requires access or power isolation.