mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #807] [Bug]: H2D Pro - The extrusion motor is overloaded #540
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy#540
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cadtoolbox on GitHub (Mar 25, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/807
Originally assigned to: @maziggy on GitHub.
Bug Description
We're seeing more "extrusion more is overloaded" errors lately. It seems to be happening more often with our H2D Pros when using Bambuddy to print.
See attached MQTTX Log. I want to be able to rule out Bambuddy as the root cause and am going to do some offline testing comparison on prints that failed and send using the same using Bambu Studio.
3DP-239-559.json
Expected Behavior
No errors: "The extrusion motor is overloaded"
Steps to Reproduce
See above
Printer Model
H2D Pro
Bambuddy Version
v0.2.2.1
Printer Firmware Version
01.01.00.00
Installation Method
Other
Operating System
Windows
Relevant Logs / Support Package
bambuddy-support-20260325-054941.zip
Screenshots
No response
Additional Context
No response
Checklist
@maziggy commented on GitHub (Mar 25, 2026):
A few observations:
The captured print (box bottom_3.24) was sent from the slicer directly (print_type: local), not through Bambuddy's queue or reprint system. Bambuddy was monitoring it via MQTT only.
The error 0x0300801E is a motion controller error (extrusion motor overloaded) — this is a firmware/hardware-level error that Bambuddy doesn't have control over during a print.
There are also 5 HMS errors active on that printer simultaneously, and ext_tool.low_prec: true (low precision calibration flag) — which may point to something going on with that specific machine.
Your plan to do comparison testing (same prints, same printers, with and without Bambuddy) is exactly the right approach. That will tell us definitively whether Bambuddy's presence is a factor.
A couple of questions:
@cadtoolbox commented on GitHub (Mar 25, 2026):
We're using Bambu Studio, 2.5.0.66. It seems consistent on all (3) H2D Pros. For that particular job, the user must have sent a reprint after the first failure from the actual printer screen.
I'll have more information today or tomorrow with some comparison logs.
@Keybored02 commented on GitHub (Mar 25, 2026):
Any chance this a resurrection of #245 ?
@cadtoolbox commented on GitHub (Mar 26, 2026):
@Keybored02 I don't think so. That issue was 100% failure rate. This is more like 10-15% of the jobs. Today we had 100% success rate so I'm leaning more towards AMS issues than anything Bambuddy related.
I'm also of the opinion now that the H2D Pro is not the greatest designed Bambu printers. The dual nozzle sounds great in theory but it's actually more limiting than what it should be providing.
@maziggy commented on GitHub (Mar 31, 2026):
Any news?
@cadtoolbox commented on GitHub (Mar 31, 2026):
The issue seems to have subsided with some AMS reconfiguring. I feel confident it's not Bambuddy related now.