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 #1157] [Bug]: H2D Pro - Multi-Plate Print Issues #832

New issue

Closed

opened 2026-05-07 00:14:09 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

2026-05-07 00:14:09 +02:00

Owner

Originally created by @cadtoolbox on GitHub (Apr 28, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1157

Originally assigned to: @maziggy on GitHub.

Component

Bambuddy

Bug Description

We're still seeing failures when printing multi-plate prints using an H2D Pro.

When sending multiple-plates at once:

QTY of layers displays incorrectly at first then adjusts itself later.
All plates show as printing to the same printer at once.
Print ultimately fails.

Errors:

[backend.app.services.bambu_mqtt]
[03W09C430100429] MQTT disconnected: rc=Unspecified error, flags=DisconnectFlags(is_disconnect_packet_from_server=False)

Expected Behavior

Multi-plate prints should print successfully just as a single plate print does, 1 at a time.

Steps to Reproduce

Select a multi-plate print. Use the 'Schedule' command to print all plates at once to an H2D Pro.
Observe issues in the job queue.

Printer Model

H2D Pro

Bambuddy Version

v0.2.3.2

SpoolBuddy Version

No response

Printer Firmware Version

01.01.00.00

Installation Method

Other

Operating System

Windows

Relevant Logs / Support Package

bambuddy-support-20260428-100912.zip

Screenshots

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

Originally created by @cadtoolbox on GitHub (Apr 28, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1157 Originally assigned to: @maziggy on GitHub. ### Component Bambuddy ### Bug Description We're still seeing failures when printing multi-plate prints using an H2D Pro. When sending multiple-plates at once: - QTY of layers displays incorrectly at first then adjusts itself later. - All plates show as printing to the same printer at once. - Print ultimately fails. Errors: ``` [backend.app.services.bambu_mqtt] [03W09C430100429] MQTT disconnected: rc=Unspecified error, flags=DisconnectFlags(is_disconnect_packet_from_server=False) ``` ### Expected Behavior Multi-plate prints should print successfully just as a single plate print does, 1 at a time. ### Steps to Reproduce 1. Select a multi-plate print. Use the 'Schedule' command to print all plates at once to an H2D Pro. 3. Observe issues in the job queue. ### Printer Model H2D Pro ### Bambuddy Version v0.2.3.2 ### SpoolBuddy Version _No response_ ### Printer Firmware Version 01.01.00.00 ### Installation Method Other ### Operating System Windows ### Relevant Logs / Support Package [bambuddy-support-20260428-100912.zip](https://github.com/user-attachments/files/27169046/bambuddy-support-20260428-100912.zip) ### Screenshots <img width="568" height="503" alt="Image" src="https://github.com/user-attachments/assets/43e6c461-a7f6-4b31-9b25-16c2abf406be" /> <img width="716" height="405" alt="Image" src="https://github.com/user-attachments/assets/d524e921-af46-4e27-8593-6540ac41b640" /> <img width="494" height="285" alt="Image" src="https://github.com/user-attachments/assets/cdd8ee2a-8e04-4d8f-b874-fa9c44657362" /> ### 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 - [x] My printer has Developer Mode enabled

BreizhHardware

2026-05-07 00:14:09 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

2026-05-07 00:14:10 +02:00

Author

Owner

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

The H2D Pro sits at FINISH for 80-210 s after accepting project_file -- in your log, plate_1 was dispatched at 10:05:39 but only actually started at 10:09:10 (3.5 min later). The scheduler kept ticking and fired plate_2 and plate_3 in the meantime, which lines up with all your symptoms: 3x status='printing', layer count flapping (firmware compositing conflicting project_files), 33 MQTT disconnects, eventual failure.

Fix going into the next release: defensive in-memory hold. When project_file goes out, the scheduler holds the printer until it sees a real MQTT state transition (or 180 s hard timeout). Net effect: the 3 plates dispatch in lockstep with what the printer can absorb instead of all three landing inside a minute.

Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you.

@maziggy commented on GitHub (Apr 28, 2026): The H2D Pro sits at FINISH for 80-210 s after accepting project_file -- in your log, plate_1 was dispatched at 10:05:39 but only actually started at 10:09:10 (3.5 min later). The scheduler kept ticking and fired plate_2 and plate_3 in the meantime, which lines up with all your symptoms: 3x status='printing', layer count flapping (firmware compositing conflicting project_files), 33 MQTT disconnects, eventual failure. Fix going into the next release: defensive in-memory hold. When project_file goes out, the scheduler holds the printer until it sees a real MQTT state transition (or 180 s hard timeout). Net effect: the 3 plates dispatch in lockstep with what the printer can absorb instead of all three landing inside a minute. Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you.

BreizhHardware commented

2026-05-07 00:14:10 +02:00

Author

Owner

@cadtoolbox commented on GitHub (Apr 28, 2026):

@maziggy Test with dev seemed to correct the issues. Thank you!

@cadtoolbox commented on GitHub (Apr 28, 2026): @maziggy Test with dev seemed to correct the issues. Thank you!