[GH-ISSUE #264] [Bug]: AMS Mapping Fails on H2D Pro #160

Closed
opened 2026-05-06 12:26:34 +02:00 by BreizhHardware · 2 comments

Originally created by @cimdDev on GitHub (Feb 4, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/264

Originally assigned to: @maziggy on GitHub.

Bug Description

AMS filament mapping is incorrect when starting a multi-material print from the queue on the Bambu Lab H2D Pro.
The automatic mapping swaps the nozzle assignments:
Left nozzle (HT-A) → incorrectly mapped to AMS filament
Right nozzle (AMS-A, slot 3) → incorrectly mapped to left filament

Image

Using the automatically proposed mapping, the print begins and fails in the first layer. the first color is incorrect (white is printed where black is expected) after nozzle change the print fails with this error:
"Failed to get AMS mapping table, please select "Resume" to retry"

when setting the correct mapping in Bambuddy:

Image

the print fails on startup when loading the filament with the same error:
"Failed to get AMS mapping table, please select "Resume" to retry"

Image

Expected Behavior

The print from Bambuddy should follow the slicer configuration, using left and right nozzle assignments as defined and the correctly mapped AMS slots at print start like when printing from the printer:

Image Image

Steps to Reproduce

Prepare a dual-color test file
-Left nozzle → Black PLA cube
-Right nozzle → White PLA cube

Verify AMS mapping on printer (prints correctly when started locally)

Add the same job to the queue

Start the print from the queue. leave mapping as proposed:
-> print starts and fails in first layer at nozzle change:
"Failed to get AMS mapping table, please select 'Resume' to retry [1800-8012 143604]"

Start the print from the queue and correctly mapped Filaments"

Print fails on first filament loading with error:
"Failed to get AMS mapping table, please select 'Resume' to retry [0700-8012 154204]"

Printer Model

H2D Pro

Bambuddy Version

0.1.8b Commit 6420e9d

Printer Firmware Version

01.01.00.00

Installation Method

Manual (git clone)

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package


Screenshots

No response

Additional Context

I tested this on two different H2D Pro with the same results. On both printers printing from sdcard at the printer works fine.

Checklist

  • I have searched existing issues to ensure this bug hasn't already been reported
  • I am using the latest version of Bambuddy
  • My printer is set to LAN Only mode
Originally created by @cimdDev on GitHub (Feb 4, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/264 Originally assigned to: @maziggy on GitHub. ### Bug Description AMS filament mapping is incorrect when starting a multi-material print from the queue on the Bambu Lab H2D Pro. The automatic mapping swaps the nozzle assignments: Left nozzle (HT-A) → incorrectly mapped to AMS filament Right nozzle (AMS-A, slot 3) → incorrectly mapped to left filament <img width="389" height="727" alt="Image" src="https://github.com/user-attachments/assets/9288c69f-5509-4bb9-aae4-537da76a968d" /> Using the automatically proposed mapping, the print begins and fails in the first layer. the first color is incorrect (white is printed where black is expected) after nozzle change the print fails with this error: "Failed to get AMS mapping table, please select "Resume" to retry" when setting the correct mapping in Bambuddy: <img width="378" height="719" alt="Image" src="https://github.com/user-attachments/assets/0cf4d021-8395-4885-a4c6-c83394271923" /> the print fails on startup when loading the filament with the same error: "Failed to get AMS mapping table, please select "Resume" to retry" <img width="374" height="318" alt="Image" src="https://github.com/user-attachments/assets/1e4f9e89-d034-4699-9b8c-1c23bdcde3ee" /> ### Expected Behavior The print from Bambuddy should follow the slicer configuration, using left and right nozzle assignments as defined and the correctly mapped AMS slots at print start like when printing from the printer: <img width="795" height="268" alt="Image" src="https://github.com/user-attachments/assets/76f2908c-cec0-4bdd-a9c3-1460ea22a6bf" /> <img width="872" height="498" alt="Image" src="https://github.com/user-attachments/assets/1e20188c-5cf7-40d5-9eea-49ef078be42b" /> ### Steps to Reproduce Prepare a dual-color test file -Left nozzle → Black PLA cube -Right nozzle → White PLA cube Verify AMS mapping on printer (prints correctly when started locally) Add the same job to the queue Start the print from the queue. leave mapping as proposed: -> print starts and fails in first layer at nozzle change: "Failed to get AMS mapping table, please select 'Resume' to retry [1800-8012 143604]" Start the print from the queue and correctly mapped Filaments" Print fails on first filament loading with error: "Failed to get AMS mapping table, please select 'Resume' to retry [0700-8012 154204]" ### Printer Model H2D Pro ### Bambuddy Version 0.1.8b Commit 6420e9d ### Printer Firmware Version 01.01.00.00 ### Installation Method Manual (git clone) ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package ```shell ``` ### Screenshots _No response_ ### Additional Context I tested this on two different H2D Pro with the same results. On both printers printing from sdcard at the printer works fine. ### Checklist - [x] I have searched existing issues to ensure this bug hasn't already been reported - [x] I am using the latest version of Bambuddy - [x] My printer is set to LAN Only mode
BreizhHardware 2026-05-06 12:26:34 +02:00
  • closed this issue
  • added the
    duplicate
    label
Author
Owner

@maziggy commented on GitHub (Feb 4, 2026):

Cany you please check again with branch 0.1.8b? I just pushed a related fix (but not yet tested).

<!-- gh-comment-id:3848041766 --> @maziggy commented on GitHub (Feb 4, 2026): Cany you please check again with branch 0.1.8b? I just pushed a related fix (but not yet tested).
Author
Owner

@maziggy commented on GitHub (Feb 4, 2026):

This is already covered in #245

<!-- gh-comment-id:3848104548 --> @maziggy commented on GitHub (Feb 4, 2026): This is already covered in #245
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/bambuddy#160
No description provided.