mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #1217] [Bug Report] Hello I have had a few prints that have given a 07ff-8012-260714 failed to get #883
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#883
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 @maziggy on GitHub (May 5, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1217
Originally assigned to: @maziggy on GitHub.
Hello I have had a few prints that have given a
07ff-8012-260714 failed to get ams mapping table errors on my h2s and h2d, neither have ams hooked up to them right now. i can cancel the print from the printer and restart it from the usb drive and the will print fine. and it doesnt do it every time.
Reporter Contact
Email: 3gcustoms@gmail.com
System Information
Logs (sanitized): bambuddy.log
Submitted via BamBuddy Bug Report
@maziggy commented on GitHub (May 6, 2026):
First of all I would strongly suggest to use Docker network mode host - as per the docs.
@maziggy commented on GitHub (May 6, 2026):
Quick read on what's happening:
07FF-8012 is a printer-side HMS error ("Failed to get AMS mapping table"). Bambuddy already handles this case for cloud/library prints (we rewrite the AMS mapping the same way Bambu Studio does), but USB-stick prints start on the printer itself — Bambuddy doesn't send the mapping at all in that path, so the printer is using whatever is baked into the 3MF on the stick.
Most likely cause: the 3MF was sliced with an AMS-attached profile (so the file references AMS slots), but the H2S and H2D have no AMS connected. The firmware then can't resolve the mapping and emits 07FF-8012 intermittently. "Resume" or restart works because the second attempt tends to succeed once the firmware falls back.
Two things to try:
About the attached support package: the bundled log only covers about 2 seconds and doesn't include the failure event. If it happens again, please flip on Settings -> Advanced -> Debug Logging, reproduce, and grab a fresh support package within a minute or two of seeing the error on the screen — that's the trace I need to confirm exactly what the firmware sent us.
And yes, please also switch Docker to network_mode: host as I noted above; bridge mode breaks SSDP discovery and also tends to cause MQTT push timeouts that can masquerade as unrelated errors.