starred/bambuddy-maziggy-1

Fork 0

mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 08:25:54 +02:00

[GH-ISSUE #827] [Bug]: Wrong filament mapping – dual extruder (H2C) has only one active nozzle #558

New issue

Closed

opened 2026-05-07 00:11:36 +02:00 by BreizhHardware · 3 comments

BreizhHardware commented

2026-05-07 00:11:36 +02:00

Owner

Originally created by @behrinml on GitHub (Mar 26, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/827

Originally assigned to: @behrinml on GitHub.

Bug Description

The H2C allows a nozzle size to be selected in the Vortek system that is not available in the left extruder—for example, 0.4 mm on the left and 0.2 mm on the right.

If a print is then started that exclusively uses the corresponding nozzle on the right extruder, a setup is created which erroneously claims that the nozzle in use is the one on the left. This occurs because only one extruder is detected, leading the system to assume the groupID must address that specific one.

Consequently, the filament assignment selected in the slicer cannot be chosen within the UI of Bambuddy.

Happens with docker and git clone, Linux and MacOS

Expected Behavior

The same filament mapping/slot should be possible between Bambuddy and Bambu Studio

Steps to Reproduce

Use different nozzles in the vortek system than in the left nozzle (e.g., only 0.2 in L but at least one 0.4 in R)
Sync the nozzles with Bambu Studio. You should receive Left Nozzle (0), Right Nozzle (1+) if you select 0.4 as nozzle size
Slice the model with 0.4 and select the corresponding filament from the AMS (I used AMS B)
Upload print to Bambuddy, press print and look into the filament mapping, this shows now only the option to select filament from AMS A

Printer Model

H2C

Bambuddy Version

0.2.2.1

Printer Firmware Version

01.01.05.00

Installation Method

Manual (git clone)

Operating System

macOS

Relevant Logs / Support Package

No response

Screenshots

Same 3mf

Current Bambuddy version. Only AMS A, wrong colors:
Issue

Fix (and correct color mapping)
Solution

Additional Context

Already fixed, if interested and assigned I happily create the corresponding pull request

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
My printer has Developer Mode enabled

Originally created by @behrinml on GitHub (Mar 26, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/827 Originally assigned to: @behrinml on GitHub. ### Bug Description The H2C allows a nozzle size to be selected in the Vortek system that is not available in the left extruder—for example, 0.4 mm on the left and 0.2 mm on the right. If a print is then started that exclusively uses the corresponding nozzle on the right extruder, a setup is created which erroneously claims that the nozzle in use is the one on the left. This occurs because only one extruder is detected, leading the system to assume the groupID must address that specific one. Consequently, the filament assignment selected in the slicer cannot be chosen within the UI of Bambuddy. Happens with docker and git clone, Linux and MacOS ### Expected Behavior The same filament mapping/slot should be possible between Bambuddy and Bambu Studio ### Steps to Reproduce 1. Use different nozzles in the vortek system than in the left nozzle (e.g., only 0.2 in L but at least one 0.4 in R) 2. Sync the nozzles with Bambu Studio. You should receive Left Nozzle (0), Right Nozzle (1+) if you select 0.4 as nozzle size 3. Slice the model with 0.4 and select the corresponding filament from the AMS (I used AMS B) 4. Upload print to Bambuddy, press print and look into the filament mapping, this shows now only the option to select filament from AMS A ### Printer Model H2C ### Bambuddy Version 0.2.2.1 ### Printer Firmware Version 01.01.05.00 ### Installation Method Manual (git clone) ### Operating System macOS ### Relevant Logs / Support Package _No response_ ### Screenshots Same 3mf Current Bambuddy version. Only AMS A, wrong colors: <img width="654" height="494" alt="Issue" src="https://github.com/user-attachments/assets/ee5ac513-4557-4e5a-848a-24b68d15c5b5" /> Fix (and correct color mapping) <img width="662" height="499" alt="Solution" src="https://github.com/user-attachments/assets/4eec211d-41e6-40ca-806d-69343b4e79be" /> ### Additional Context Already fixed, if interested and assigned I happily create the corresponding pull request ### 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 - [x] My printer has Developer Mode enabled

BreizhHardware

2026-05-07 00:11:36 +02:00

closed this issue
added the
bug

contrib
labels

BreizhHardware commented

2026-05-07 00:11:37 +02:00

Author

Owner

@maziggy commented on GitHub (Mar 27, 2026):

Why reinventing the wheel? Please open a pull request and note our rules in CONTRIBUTING.md.

Thanks!

@maziggy commented on GitHub (Mar 27, 2026): Why reinventing the wheel? Please open a pull request and note our rules in CONTRIBUTING.md. Thanks!

BreizhHardware commented

2026-05-07 00:11:37 +02:00

Author

Owner

@behrinml commented on GitHub (Mar 27, 2026):

Thanks for assigning, I'm going to create the PR on during the weekend after additional tests.

What do you refer to with "the wheel"? Based on the Contributing.md:

"Every contribution starts with an issue. Before writing any code or opening a pull request:

Open a new issue or comment on an existing one describing what you'd like to work on
Wait for agreement — discuss the approach with a maintainer so we're aligned on scope and direction
Get assigned — once we agree, a maintainer will assign the issue to you
Then start coding — only open a PR for an issue that is assigned to you
No assigned issue = no PR. Pull requests without a corresponding assigned issue will be closed."

So I guess, I followed the rules?

@behrinml commented on GitHub (Mar 27, 2026): Thanks for assigning, I'm going to create the PR on during the weekend after additional tests. What do you refer to with "the wheel"? Based on the Contributing.md: "Every contribution starts with an issue. Before writing any code or opening a pull request: Open a new issue or comment on an existing one describing what you'd like to work on Wait for agreement — discuss the approach with a maintainer so we're aligned on scope and direction Get assigned — once we agree, a maintainer will assign the issue to you Then start coding — only open a PR for an issue that is assigned to you No assigned issue = no PR. Pull requests without a corresponding assigned issue will be closed." So I guess, I followed the rules?

BreizhHardware commented

2026-05-07 00:11:37 +02:00

Author

Owner

@maziggy commented on GitHub (Mar 28, 2026):

Yes, all is good.

@maziggy commented on GitHub (Mar 28, 2026): Yes, all is good.

BreizhHardware referenced this issue

2026-05-07 00:15:54 +02:00

[PR #601] [CLOSED] v0.2.2b1 #1083

BreizhHardware referenced this issue

2026-05-07 00:15:54 +02:00