mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 13:45:32 +02:00
[GH-ISSUE #245] [Bug]: H2D Pro Print Errors (The extrusion motor is overloaded) #150
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#150
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 (Feb 3, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/245
Originally assigned to: @maziggy on GitHub.
Bug Description
H2D Pro error only when sending from Bambuddy:
HMS_0300_0900_0002_0001: The extrusion motor is overloaded. The extruder may be clogged or the filament may be stuck in the tool head.
Now that I'm back in the office and doing some more testing with the full print on the H2D Pro, it appears some logic in sending jobs to the H2D Pro are still a little off. See attached "good" MQTTX using Bambu Studio vs. the "bad" using Bambuddy.
bad3DP-239-110.json
good3DP-239-110.json
Expected Behavior
All H2D Pro jobs are successful like Bambu Studio jobs
Steps to Reproduce
Printer Model
H2D Pro
Bambuddy Version
v0.1.7
Printer Firmware Version
01.01.00.00
Installation Method
Manual (git clone)
Operating System
Windows
Relevant Logs / Support Package
Screenshots
bambuddy-support-20260203-095655.zip
Additional Context
No response
Checklist
@maziggy commented on GitHub (Feb 4, 2026):
I see the problem.
The actual bug: Bambuddy ignores the tray_info_idx field in the 3MF file. This field uniquely identifies which spool was selected when the user sliced in Bambu Studio. The current auto-matcher only looks at type+color, not the specific spool identity.
Let me fix that.
@maziggy commented on GitHub (Feb 4, 2026):
Please use branch 0.1.8b and let me know if it works now.
@cadtoolbox commented on GitHub (Feb 4, 2026):
Tested update: The print always starts correctly but before it can finish printing, it faults. It seems like it has some spaghetti build up when using Bambuddy vs sending the same print using Bambu Studio.
H2DProErrors.json
bambuddy-support-20260204-045855.zip
@maziggy commented on GitHub (Feb 4, 2026):
Thanks for the additional logs. I've analyzed them:
Findings:
To compare with Bambu Studio, I need one more piece of data:
Could you please capture the print start command that Bambu Studio sends? Here's how:
"command":"project_file"in the payloadI want to compare what parameters Bambu Studio sends vs what Bambuddy sends. The key differences might be in:
cfgparameterextrude_cali_flagAlternatively, if Bambu Studio logs the MQTT commands somewhere, that would work too.
What I've compared so far:
Bambuddy print command:
```json
{
"print": {
"command": "project_file",
"param": "Metadata/plate_1.gcode",
"url": "ftp://H2D-CIRCLE.3mf",
"bed_type": "auto",
"timelapse": false,
"bed_leveling": true,
"vibration_cali": true,
"layer_inspect": false,
"use_ams": true,
"cfg": "0",
"extrude_cali_flag": 0,
"nozzle_offset_cali": 2,
"ams_mapping": [0],
"ams_mapping2": [{"ams_id": 0, "slot_id": 0}]
}
}
```
I suspect the
cfgfield might need to be different for H2D Pro. The printer reportscfg: "1817DA9B"in its status messages.@maziggy commented on GitHub (Feb 4, 2026):
Should be fixed in branch 0.1.8b.
@cadtoolbox commented on GitHub (Feb 4, 2026):
@maziggy Not sure if you still needed the MQTTX from Bambu Studio:
{ "command": "project_file", "file": "CIRCLE.gcode.3mf", "param": "Metadata/plate_1.gcode", "url": "ftp://CIRCLE.gcode.3mf", "md5": "B988D7E5356E6AEF7F060B317338D3A9", "result": "SUCCESS", "reason": "SUCCESS", "err_code": 0, "sequence_id": 20002, "subtask_name": "CIRCLE", "subtask_id": 0, "task_id": 0 }@cadtoolbox commented on GitHub (Feb 4, 2026):
Error is still present in 0.1.8b:
bambuddy-support-20260204-090827.zip
H2DproERROR.zip
@maziggy commented on GitHub (Feb 4, 2026):
Thanks for the updated logs! I've analyzed the support package and MQTTX captures.
Current Understanding
The print starts correctly now (the tray_info_idx fix is working), but fails mid-print with the extrusion motor overloaded error and spaghetti detection triggering.
What I Still Need
The JSON you posted from Bambu Studio:
This is the response from the printer after the print started, not the actual command Bambu Studio sent.
To help debug this, I need to see the actual
project_filecommand that Bambu Studio sends. Here's how to capture it:Option 1: MQTTX (Recommended)
#(all topics)requesttopic that contains"command": "project_file"device/[YOUR_SERIAL]/requestand will have fields like:cfgextrude_cali_flagnozzle_offset_caliams_mappingOption 2: Bambu Studio Network Logs
Bambu Studio may log MQTT commands somewhere. If you can find those logs, look for the
project_filecommand it sends.What Bambuddy Currently Sends
For reference, here's what Bambuddy sends:
I suspect one of these parameters needs to be different for the H2D Pro. Once I can see what Bambu Studio sends, I can compare and identify the difference.
@cimdDev commented on GitHub (Feb 4, 2026):
The proposed mapping is correct now:
but the print still fails at startup on filament load with the same error:
"Failed to get AMS mapping table, please select "Resume" to retry"
I tested this with 0.1.8b Commit
39f9061@maziggy commented on GitHub (Feb 4, 2026):
Yes, I tested with a normmal H2D and it works. We have to find the difference (I know that already too good!). Waiting for @cadtoolbox to provide the requested information.
@cadtoolbox commented on GitHub (Feb 4, 2026):
@maziggy Do you need more than this? https://github.com/maziggy/bambuddy/issues/245#issuecomment-3847897366
@cadtoolbox commented on GitHub (Feb 4, 2026):
I think this is what you needed from Bambu Studio:
{
"print": {
"command": "project_file",
"file": "CIRCLE.gcode.3mf",
"param": "Metadata/plate_1.gcode",
"profile_id": "0",
"project_id": "0",
"sequence_id": "20002",
"subtask_id": "0",
"subtask_name": "CIRCLE",
"task_id": "0",
"url": "ftp://CIRCLE.gcode.3mf",
"use_ams": true,
"ams_mapping": [...],
"ams_mapping2": [...],
"auto_bed_leveling": 1,
"bed_leveling": 1,
"bed_type": "auto",
"cfg": "0",
"extrude_cali_flag": 0,
"extrude_cali_manual_mode": 0,
"flow_cali": 0,
"layer_inspect": 1,
"md5": "",
"nozzle_offset_cali": 2,
"timelapse": 0,
"vibration_cali": 1
}
}
@maziggy commented on GitHub (Feb 5, 2026):
H2D Pro is using integers, other models are using booleans in print commands. This is so annoying. Anyway...please test with branch 0.1.8b.
@cadtoolbox commented on GitHub (Feb 6, 2026):
I haven't had a chance to test this myself (been asleep with the flu)
https://github.com/maziggy/bambuddy/issues/285 is preventing testing now. I'm looking into as much as I can.
@maziggy commented on GitHub (Feb 7, 2026):
Get well soon!
@cadtoolbox commented on GitHub (Feb 7, 2026):
The H2D Pro is proving to very stubborn. Print still fails at around 75% complete.
3DP-239-110.json
bambuddy-support-20260207-141848.zip
@maziggy commented on GitHub (Feb 8, 2026):
Hopefully fixed in branch 0.1.9b.
If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!
@cadtoolbox commented on GitHub (Feb 8, 2026):
Fixed in branch 0.1.9b!!! Thank you for your persistence.
@cimdDev commented on GitHub (Feb 10, 2026):
I finally was able to test my two nozzle test print with 0.1.9b on the H2D Pro, but I still get the "Failed to get AMS mapping" error as described in issue #264
bambuddy-support-20260210-085626.zip
should I open a new issue?
@maziggy commented on GitHub (Feb 10, 2026):
Yes, please open a new issue. Thanks.