[GH-ISSUE #403] [Feature]: File Manager - Check if the nozzle in the file is compatible with the nozzle on the printer #254

Closed
opened 2026-05-06 12:27:36 +02:00 by BreizhHardware · 6 comments

Originally created by @aneopsy on GitHub (Feb 16, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/403

Problem or Use Case

It's actually possible to start a print with the wrong nozzle diameter, the printer will show a warning message.

Image

Proposed Solution

Display the nozzle diameter in the File Manager next to the printer model. When printing or scheduling a job, verify that the nozzle is compatible with the selected printer and flag a mismatch.

Bonus 1: Additionally, validate the nozzle flow rate and material compatibility, for example, flag a mismatch if a file is configured for a high-flow nozzle but the selected printer is equipped with a standard nozzle of the same diameter.

Bonus 2: If a job is already queued and the printer's nozzle is swapped after scheduling, the system should perform a compatibility check before sending the job to the printer.

Can integrate #399

Alternatives Considered

No response

Feature Category

File Manager

Priority

Nice to have

Mockups or Examples

No response

Contribution

  • I would be willing to help implement this feature

Checklist

  • I have searched existing issues to ensure this feature hasn't already been requested
Originally created by @aneopsy on GitHub (Feb 16, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/403 ### Problem or Use Case It's actually possible to start a print with the wrong nozzle diameter, the printer will show a warning message. <img width="720" height="960" alt="Image" src="https://github.com/user-attachments/assets/0af4d643-c268-4cb7-9118-b2d80af0c86a" /> ### Proposed Solution Display the nozzle diameter in the File Manager next to the printer model. When printing or scheduling a job, verify that the nozzle is compatible with the selected printer and flag a mismatch. Bonus 1: Additionally, validate the nozzle flow rate and material compatibility, for example, flag a mismatch if a file is configured for a high-flow nozzle but the selected printer is equipped with a standard nozzle of the same diameter. Bonus 2: If a job is already queued and the printer's nozzle is swapped after scheduling, the system should perform a compatibility check before sending the job to the printer. Can integrate #399 ### Alternatives Considered _No response_ ### Feature Category File Manager ### Priority Nice to have ### Mockups or Examples _No response_ ### Contribution - [x] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested
BreizhHardware 2026-05-06 12:27:36 +02:00
  • closed this issue
  • added the
    wontfix
    label
Author
Owner

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

Currently Bambuddy doesn't support different nozzle sizes. Needs to be implemented from scratch.

<!-- gh-comment-id:3908627888 --> @maziggy commented on GitHub (Feb 16, 2026): Currently Bambuddy doesn't support different nozzle sizes. Needs to be implemented from scratch.
Author
Owner

@aneopsy commented on GitHub (Feb 16, 2026):

Why not start with a lite version? Just check the nozzle size before printing and display it on some cards. I can work on it if you want.

<!-- gh-comment-id:3908671864 --> @aneopsy commented on GitHub (Feb 16, 2026): Why not start with a lite version? Just check the nozzle size before printing and display it on some cards. I can work on it if you want.
Author
Owner

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

Don't want to split it into separate tasks. Sorry.

<!-- gh-comment-id:3908679763 --> @maziggy commented on GitHub (Feb 16, 2026): Don't want to split it into separate tasks. Sorry.
Author
Owner

@aneopsy commented on GitHub (Feb 16, 2026):

Ok no problem, I will work on it on my fork

Image
<!-- gh-comment-id:3908712344 --> @aneopsy commented on GitHub (Feb 16, 2026): Ok no problem, I will work on it on my fork <img width="1450" height="455" alt="Image" src="https://github.com/user-attachments/assets/0acd37d5-7712-4249-b6d5-f46a5575d00e" />
Author
Owner

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

BTW: can you please check your github setup? I'm getting email notifications about failed CI runs every time you do a commit in your fork. Don't know where that comes from.

<!-- gh-comment-id:3908721894 --> @maziggy commented on GitHub (Feb 16, 2026): BTW: can you please check your github setup? I'm getting email notifications about failed CI runs every time you do a commit in your fork. Don't know where that comes from.
Author
Owner

@aneopsy commented on GitHub (Feb 16, 2026):

Strange GitHub bug, I will update my account to pro so the CI shouldn't failed

<!-- gh-comment-id:3908761911 --> @aneopsy commented on GitHub (Feb 16, 2026): Strange GitHub bug, I will update my account to pro so the CI shouldn't failed
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#254
No description provided.