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 #420] [Bug]: Filament usage not counted correctly for multi-color prints and wrong AMS slot mapping with dual AMS setup #264

New issue

Closed

opened 2026-05-07 00:08:12 +02:00 by BreizhHardware · 7 comments

BreizhHardware commented

2026-05-07 00:08:12 +02:00

Owner

Originally created by @pichler583-cell on GitHub (Feb 17, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/420

Originally assigned to: @maziggy on GitHub.

Bug Description

There are two related issues when printing multi-color jobs with a dual AMS setup:

Filament usage is not properly counted during multi-color prints.
Incorrect AMS slot mapping is displayed when printing from the second AMS.

Issue 1 – Filament usage not counted for multi-color prints
When performing a multi-color print, filament consumption is only deducted for the first filament used.
All additional filaments involved in the print remain unchanged in weight tracking.

Issue 2 – Incorrect AMS slot display with two AMS units
With two AMS units connected:
When printing from AMS #2 – Slot 1, the UI displays that the print is running from AMS #1 – Slot 1.
Only the filament in AMS #1 Slot 1 is correctly deducted.
Filaments from the second AMS are not properly tracked or deducted.

Expected Behavior

Filament consumption should be deducted individually for every filament used in the multi-color job.

Only the first filament used is correctly deducted.
All other filaments used in the same print job remain at their original weight and are not updated.
The UI should correctly display the active AMS unit and slot.
Filament deduction should apply to the actual physical slot being used (including AMS #2).

Steps to Reproduce

2 AMS and MultiColor Print

Printer Model

P2S

Bambuddy Version

0.2.0

Printer Firmware Version

01.01.01.00

Installation Method

Docker

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package

Screenshots

bambuddy-support-20260217-135422.zip

Additional Context

No response

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 @pichler583-cell on GitHub (Feb 17, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/420 Originally assigned to: @maziggy on GitHub. ### Bug Description There are two related issues when printing multi-color jobs with a dual AMS setup: Filament usage is not properly counted during multi-color prints. Incorrect AMS slot mapping is displayed when printing from the second AMS. **Issue 1 – Filament usage not counted for multi-color prints** When performing a multi-color print, filament consumption is only deducted for the first filament used. All additional filaments involved in the print remain unchanged in weight tracking. **Issue 2 – Incorrect AMS slot display with two AMS units** With two AMS units connected: When printing from AMS #2 – Slot 1, the UI displays that the print is running from AMS #1 – Slot 1. Only the filament in AMS #1 Slot 1 is correctly deducted. Filaments from the second AMS are not properly tracked or deducted. ### Expected Behavior Filament consumption should be deducted individually for every filament used in the multi-color job. - Only the first filament used is correctly deducted. - All other filaments used in the same print job remain at their original weight and are not updated. - The UI should correctly display the active AMS unit and slot. - Filament deduction should apply to the actual physical slot being used (including AMS #2). ### Steps to Reproduce 2 AMS and MultiColor Print ### Printer Model P2S ### Bambuddy Version 0.2.0 ### Printer Firmware Version 01.01.01.00 ### Installation Method Docker ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package ```shell ``` ### Screenshots [bambuddy-support-20260217-135422.zip](https://github.com/user-attachments/files/25372633/bambuddy-support-20260217-135422.zip) <img width="2160" height="416" alt="Image" src="https://github.com/user-attachments/assets/472e0e9d-5485-4a91-b552-36dcc4297f78" /> <img width="598" height="279" alt="Image" src="https://github.com/user-attachments/assets/8c13daa6-aee4-4f66-bc26-a601d6a8fe15" /> <img width="690" height="698" alt="Image" src="https://github.com/user-attachments/assets/f9fe8e34-871d-4a08-81e4-892fef1e89f4" /> ### Additional Context _No response_ ### 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-07 00:08:12 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

2026-05-07 00:08:12 +02:00

Author

Owner

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

I'm currently redesigning these functions. May I ask you please to pull branch 0.2.1b and try again? It's not yet finished, but already has a patch for the P2S which hopefully already fixes your issue.

@maziggy commented on GitHub (Feb 18, 2026): I'm currently redesigning these functions. May I ask you please to pull branch 0.2.1b and try again? It's not yet finished, but already has a patch for the P2S which hopefully already fixes your issue.

BreizhHardware commented

2026-05-07 00:08:12 +02:00

Author

Owner

@pichler583-cell commented on GitHub (Feb 18, 2026):

Tested with 0.2.1b:

The filament usage is now correctly deducted from the actual physical slot that is printing — so the weight tracking on the filament itself works correctly.

However, the UI still shows the print running on the wrong AMS (wrong AMS unit is displayed), even though the correct slot is being used and counted internally.

So the deduction logic seems fixed, but the visual AMS mapping in the UI is still incorrect.

@pichler583-cell commented on GitHub (Feb 18, 2026): Tested with 0.2.1b: The filament usage is now correctly deducted from the actual physical slot that is printing — so the weight tracking on the filament itself works correctly. However, the UI still shows the print running on the wrong AMS (wrong AMS unit is displayed), even though the correct slot is being used and counted internally. So the deduction logic seems fixed, but the visual AMS mapping in the UI is still incorrect.

BreizhHardware commented

2026-05-07 00:08:13 +02:00

Author

Owner

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

Please try again with latest beta release 0.2.1b.

@maziggy commented on GitHub (Feb 19, 2026): Please try again with latest beta release 0.2.1b.

BreizhHardware commented

2026-05-07 00:08:13 +02:00

Author

Owner

@pichler583-cell commented on GitHub (Feb 19, 2026):

The update is installed, but unfortunately the display is still wrong: B2 is printed while A2 is shown. Tracking still seems to be correct.

@pichler583-cell commented on GitHub (Feb 19, 2026): The update is installed, but unfortunately the display is still wrong: B2 is printed while A2 is shown. Tracking still seems to be correct. <img width="725" height="660" alt="Image" src="https://github.com/user-attachments/assets/36a7c93e-c537-472c-950a-8e7df9777add" /> <img width="468" height="740" alt="Image" src="https://github.com/user-attachments/assets/b420afc6-e670-4d3d-ae96-e61d5c031439" />

BreizhHardware commented

2026-05-07 00:08:13 +02:00

Author

Owner

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

Need a support package please.

https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

@maziggy commented on GitHub (Feb 20, 2026): Need a support package please. https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

BreizhHardware commented

2026-05-07 00:08:13 +02:00

Author

Owner

@pichler583-cell commented on GitHub (Feb 20, 2026):

bambuddy-support-20260220-073712.zip

@pichler583-cell commented on GitHub (Feb 20, 2026): [bambuddy-support-20260220-073712.zip](https://github.com/user-attachments/files/25442041/bambuddy-support-20260220-073712.zip)

BreizhHardware commented

2026-05-07 00:08:13 +02:00

Author

Owner

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

Should be fixed in branch 0.2.1b2. Please let me know how it goes.

If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!

@maziggy commented on GitHub (Feb 21, 2026): Should be fixed in branch 0.2.1b2. Please let me know how it goes. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/bambuman/bambuddy) — it helps others discover the project!