[PR #847] [CLOSED] Fix nozzle mapping logic for single active extruder scenarios in 3MF …

No labels

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#1120

BreizhHardware commented

2026-05-06 12:35:10 +02:00

Owner

📋 Pull Request Information

Original PR: https://github.com/maziggy/bambuddy/pull/847
Author: @behrinml
Created: 3/29/2026
Status: ❌ Closed

Base: dev ← Head: fix/wrong-filament-mapping

📄 Description

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.

Fixes #827

Type of Change

Bug fix (non-breaking change that fixes an issue)
New feature (non-breaking change that adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Documentation update
Code refactoring
Performance improvement
Test addition or update

Changes Made

short check during filament mapping if only one extruder is active. If this is true, the filament mapping leads to groupId 0 as this is the only one reported from the slicer.

Screenshots

Previous:
issue
Afterwards:
solution

Testing

I have tested this on my local machine
I have tested with my printer model: H2C

Checklist

My code follows the project's coding style
I have commented my code where necessary
I have updated the documentation (if needed)
My changes generate no new warnings
I have tested my changes thoroughly

Additional Notes

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/maziggy/bambuddy/pull/847 **Author:** [@behrinml](https://github.com/behrinml) **Created:** 3/29/2026 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `fix/wrong-filament-mapping` --- ### 📄 Description ## 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. ## Related Issue Fixes #827 ## Type of Change - [X] Bug fix (non-breaking change that fixes an issue) - [ ] New feature (non-breaking change that adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Documentation update - [ ] Code refactoring - [ ] Performance improvement - [ ] Test addition or update ## Changes Made  - short check during filament mapping if only one extruder is active. If this is true, the filament mapping leads to groupId 0 as this is the only one reported from the slicer. ## Screenshots Previous: <img width="654" height="494" alt="issue" src="https://github.com/user-attachments/assets/e7b8b03f-85e6-4150-884c-eec4923d9521" /> Afterwards: <img width="662" height="499" alt="solution" src="https://github.com/user-attachments/assets/ee90d0a9-2d20-43e9-92a6-47f798e102d5" />  ## Testing  - [X] I have tested this on my local machine - [X] I have tested with my printer model: H2C ## Checklist - [x] My code follows the project's coding style - [x] I have commented my code where necessary - [ ] I have updated the documentation (if needed) - [x] My changes generate no new warnings - [x] I have tested my changes thoroughly ## Additional Notes  --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

BreizhHardware

closed this issue
added the
pull-request
label

Rows
Columns

[PR #847] [CLOSED] Fix nozzle mapping logic for single active extruder scenarios in 3MF … #1120