[PR #851] [MERGED] Fix/wrong filament mapping

## 📋 Pull Request Information **Original PR:** https://github.com/maziggy/bambuddy/pull/851 **Author:** [@behrinml](https://github.com/behrinml) **Created:** 3/30/2026 **Status:** ✅ Merged **Merged:** 3/31/2026 **Merged by:** [@maziggy](https://github.com/maziggy) **Base:** `dev` ← **Head:** `fix/wrong-filament-mapping` --- ### 📝 Commits (6) - [`435ada4`](https://github.com/maziggy/bambuddy/commit/435ada4a819ac5bb63404ccd7e153aad9279fbd4) Fix nozzle mapping logic for single active extruder scenarios in 3MF parsing - [`eebaf7c`](https://github.com/maziggy/bambuddy/commit/eebaf7c694cfb8b3cd1fd0b89f46f7591cb8fc30) fix: nozzle mapping logic for single active extruder in 3MF - [`8201372`](https://github.com/maziggy/bambuddy/commit/8201372b4377d90ea5bf0523a1f8bf7a7b91245e) Merge branch 'dev' into fix/wrong-filament-mapping - [`4ef6d8c`](https://github.com/maziggy/bambuddy/commit/4ef6d8c5b62efb1e00e14aaef6e6b12548a122bb) Refactor active extruder detection in threemf_tools.py - [`9369bf2`](https://github.com/maziggy/bambuddy/commit/9369bf20e853603d079d44c4234f5a84211fa5e6) Enhance comments for extruder nozzle stats - [`bedfcad`](https://github.com/maziggy/bambuddy/commit/bedfcad895004f53f23b4347812d385bdbef8500) Merge branch 'dev' into fix/wrong-filament-mapping ### 📊 Changes **1 file changed** (+26 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `backend/app/utils/threemf_tools.py` (+26 -0) </details> ### 📄 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. (Replaces the previous PR (#847) with a cleaned up commit history based on the latest dev branch. Sorry, I messed up my history and was not able to repair it.) ## 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. This is done for the active extruder. If there are more or less than one active extruder, we stay with the current filament mapping. ## Screenshots <img width="654" height="494" alt="issue" src="https://github.com/user-attachments/assets/1a62b1ff-670e-434c-85b7-0293cffdcb9c" /> <img width="662" height="499" alt="solution" src="https://github.com/user-attachments/assets/00e3e040-415f-403d-8dc9-9d37098586ad" /> ## 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 Replaces the previous PR (#847) with a cleaned up commit history based on the latest dev branch. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

BreizhHardware commented

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

Owner

📋 Pull Request Information

Original PR: https://github.com/maziggy/bambuddy/pull/851
Author: @behrinml
Created: 3/30/2026
Status: ✅ Merged
Merged: 3/31/2026
Merged by: @maziggy

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

📝 Commits (6)

435ada4 Fix nozzle mapping logic for single active extruder scenarios in 3MF parsing
eebaf7c fix: nozzle mapping logic for single active extruder in 3MF
8201372 Merge branch 'dev' into fix/wrong-filament-mapping
4ef6d8c Refactor active extruder detection in threemf_tools.py
9369bf2 Enhance comments for extruder nozzle stats
bedfcad Merge branch 'dev' into fix/wrong-filament-mapping

📊 Changes

1 file changed (+26 additions, -0 deletions)

View changed files

📝 backend/app/utils/threemf_tools.py (+26 -0)

📄 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.

(Replaces the previous PR (#847) with a cleaned up commit history based on the latest dev branch. Sorry, I messed up my history and was not able to repair it.)

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. This is done for the active extruder.
If there are more or less than one active extruder, we stay with the current filament mapping.

Screenshots

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

Replaces the previous PR (#847) with a cleaned up commit history based on the latest dev branch.

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

BreizhHardware

closed this issue
added the
pull-request
label

Rows
Columns

[PR #851] [MERGED] Fix/wrong filament mapping #1121