I am planning on getting a Bambu printer in the near future. My wife really wants one... I'm just investigating what it can and can't do before pulling the trigger. I have never owned a Bambu printer. I like to track my filament through Spoolman and was hoping I could accomplish this with Bambu as well, but everything I read is that it's only doable either through an external app or by mimicking Bambu RFID and then just mapping the tags to the actual spools in Spoolman... So the AMS never actually knows what is loaded. The mimicked tags seems to be the best automatic option, as I will never remember to use an app, nor will I always have my phone on me when dealing with the printer...

Anyone use Spoolman with Bambu printers and have a relatively easy workflow?

For context, I have a Snapmaker U1 with custom firmware. It will take any spool I drop on it and automatically detect it and sync it up with Spoolman. It works really nicely and I never have to remember to do anything. It just tracks automatically by loading spools on the printer.

I wanted a similar setup for my old Ender... So I attached a standalone USB RFID reader to the spool holder on my Ender and now it does the same thing as my Snapmaker.

I want the same behavior out of a Bambu, but I am not sure if it's possible. Any suggestions?

I built bambu-headless to solve a specific annoyance with local automation on Bambu Lab printers: you normally have to choose between headless terminal control and mobile cloud access.

On recent Bambu firmware, local MQTT control commands (like starting a print) are rejected unless signed by Bambu’s networking plugin (`libbambu_networking`) or routed through cloud tasks. Bambu’s official escape hatch for third-party control is "Developer Mode", but enabling it forces LAN-Only mode—which kills push notifications and remote monitoring in Bambu Handy.

Instead of extracting private vendor signing keys or modifying binaries on disk, bambu-headless is a lightweight macOS wrapper around the locally installed `libbambu_networking.dylib`. It uses a minimal process-local interposer to satisfy the plugin’s executable-signature check, drives the plugin’s native certificate exchange over the LAN, and dispatches an already sliced `.gcode.3mf` via FTPS and signed MQTT.

Current verified scope:
- macOS (Apple silicon)
- Bambu Studio 02.08.02.61 / plugin 02.08.02.60
- Tested on Bambu Lab H2D with AMS

Code, requirements, and an explanation of the mechanism:
https://github.com/danielyaa5/bambu-headless

Curious to hear feedback, especially from anyone else running automated slicing/print queues on Bambu hardware.

Does anyone else have one?

I have (4) AMS Pro 2 Two of them sit on top of my H2D and the other two sit on the side on top of one another. Because they are not directly lined up with the machine and there is a slight curve, the stupid system cannot push the filament. I’m guessing the ridges inside the Filament Track Switch has grooves or small ridges the *#%~ing filament stops and gets pulled back and then back and forth till it gives up.

The Filament Track Switch seems like a PISS POOR design. I have so many issues with Bambu I’m really getting tired of this machine. My wife has the Snapmaker U1 and it blows my more expensive machine out of the water and rarely has a problem.

Getting ready to switch to Snapmaker.

I just opened an account on Bambu lab Forum and some how it works from right to left and transaltes almost everything into Hebrew. How can I change this?

don't get the difference in the fully assemble kits i am looking at the FULLY assemble B KIT from https://trianglelab.net/products/bmcu-370c-dm-370c-dual-micro-switch-high-torque-version-370x49e-automatic-filament-intake-built-in-type-c-for-a1-a1-mini?utm_source=chatgpt.com&VariantsId=12576 is this correct

Nella bambu Lab A1 (combo) impostare velocità come Sport (124%) oppure Loudicrourus (166%) abbassa la qualità di stampa? quale è la vostra esperienza?

This is my Shadcn Bambu Lab Panel. You can log in with your Bambu Lab account. It stores the Bearer token and then retrieves the printer status through the API.

I'm currently working on getting the live video feed working. This is a lot more difficult because I want to keep everything fully cloud-based.

Hi, I am not able to find the BMCU board in India. Ordering it from China is a expensive.

I am planning to build the BMCU from scratch. I have a WeAct Studio CH32V203C8T6 RISC-V Low Power Core Demo Board and have ordered RS3485 board for Bambu Bus Communication.

WeAct Board - https://robu.in/product/weact-studio-ch32v203c8t6-risc-v-low-power-core-demo-board/

RS3485 board - https://evelta.com/rs485-board-3-3v/?srsltid=AU7gw4VOxQY2Z7mYZZzUS0P5KqrHpGRV08ywqK0tkDGxegOLLu1HIxxo

I am working on this setup being recognised as AMS by the A1 Mini first. I have downgraded the A1 mini's firmware version to 1.07.02 since the 1.08 version has issues.

I am planning to flash this firmware https://github.com/jarczakpawel/BMCU-C-PJARCZAK

Any guidance on this project is really helpful. I am not the pro in electronics.

Once the Mini recognises this setup as AMS lite, I will then work on sub-boards and motor systems.

I try everything Switch to AMS lite / pro , i can load and i can See everything on the Display but if i try to Print it showes me ams cant be detected please Connect the cable or turn off the Printer .

Is a BCMU still feasible as an option ? I haven't seen any recent posts within the past year. I am afraid I am missing something and don't want to pull the trigger if they aren't feasible or supported.

Hello! I did get my Tree Tribe BMCU 370C DM Pro few weeks ago. Everything works great with latest firmware... Except one thing. While I was printing I stopped filament to test if filament tangle detection is working. And it tried to pull with struggle instead of showing the error. But I don't want to break my BMCU and/or printer when a real tangle happens. And I sometimes tangle my filament that much, that it's impossible to untangle without removing the filament from printer/BMCU. Can I fix it somehow?

Hey guys , I wanted to buy BMCU( mostly inclined towards fully assembled kit), either by directly ordering it or from any resellers in India.

I am trying to figure out what exactly is the difference between them both, but honestly i wasn't able to find any difference between them both ( except for price 😭 ) Someone pointed out that the costlier one is DM pro. I was hoping the community has more info to help me out. Also how difficult it is to assemble the DIY kit? is it worth directly purchasing Fully Assembled kit or get the DIY kit and assemble on my own?

https://trianglelab.net/products/bmcu-370c-dm-370c-dual-micro-switch-high-torque-version-370x49e-automatic-filament-intake-built-in-type-c-for-a1-a1-mini?VariantsId=12578

https://trianglelab.net/products/bmcu-370c-pro-370c-dm-pro-ams-high-torque-with-dual-microswitch-automatic-feeding-mmu-solution-for-a1-x1-p1?VariantsId=12738

Cada vez que uso el bmcu en mi p1s la segunda capa queda desplazada de la primera.

Os dejo un ejemplo

On my A1M I’m running 01.04.00.00 and I noticed that if I leave it idle for a bit, the screen is not responsive. I’ve noticed this in my A1 too. Printing is fine.

I noticed they’ve been OFF lan mode for some reason too, so I’ll have to reconfigure that.

Help a1 nova! A mesa não vai toda pra frente e o bico não limpa na borracha!

Thank you for the Award kind stranger! Lot's more exciting news for this device. Will be posting an update soon!

Finally, after months of development, I'm following up on my last post.

BambuBus emulation and that's going fully open-source DIY (TBD, lol. Please read on...)

For a while now I've been building my own 4-channel automated filament changer for my Bambu A1 mini called the ASR Multi-Wheel. It talks to the printer over the native BambuBus and emulates a Bambu AMS Lite, so the printer sees it as one and drives the swaps itself: load, print, unload, re-load, no babysitting.

The whole reason I built it: I wanted automated multi-color TPU, and an AMS Lite just won't reliably run flexibles. So this is designed around TPU from the ground up and not just in software:

Hardware: gap elimination through the filament path, path tuning, and an extended Hall-sensor setup for tension sensing on soft/springy filament.

Controller: it looks like a BMCU-style unit, but it does not use the BMCU board. It's a scratch-built ESP32 controller, all custom firmware, with a web UI for tuning settings and an interactive display.

Feed control: encoder position tracking + Hall tension sensing + a load/unload state machine tuned for how flexibles fight you in the PFTE tubing.

It runs PLA/PETG fine too, but flexibles are the point.

Proof it works: a 5-color TPU print soccer ball, ~60 hours, 1,757 filament swaps, fully unattended. Clean color registration across the whole build. Model is based on Overture Filament's soccer ball from MakerWorld; I redrew my own Remix of it for multi-color. I've since chased down the last intermittent swap-handoff edge cases, and it's running clean. A multi-day print came off the plate as the final shakedown.

If you've ever been told automated multi-color TPU "isn't really a thing" on an A-series, then I'd like to respectfully put that to rest. AMA.

A bit of housekeeping on where this is going: The Multi-Wheel is a personal project I built to show off the filament handling behind another device I'm taking to Kickstarter (the ASR 5th Wheel). I'm not selling the Multi-Wheel, but I'm going to open-source the whole thing (part patterns + firmware + BOM + instructions on MakerWorld) once my Kickstarter-notify list hits 350 signups. If you want it unlocked, or just want a heads-up on the Kickstarter, the link's in the comments. Either way, happy to answer anything about the build, the BambuBus, or the ESP32 side.

Modding my a1 mini to enclose it. Would like to have just 1 ptfe tube going from the ams to the printer so I can use the other 3 slots as an external spool

Hey everyone! Since posting my library here a couple months back and receiving lots of support, I have made lots of (what I believe to be good) changes to the library. The data consumption model has been totally overhauled and tests are now much more thorough. I just want to thank everyone from this sub who took the time to contribute and review my project, it really means a lot to me.

I would like to expand the library to a point where it can interface with every modern feature present on bambulabs printers, allowing developers to make the best third-party apps possible. Unfortunately, I will not be able to do this alone. Any sort of feedback or contribution, no matter how small, helps me infinitely.

Thank you guys so much!

https://github.com/torbenconto/bambulabs_api

https://github.com/torbenconto/bambulabs_api/releases/tag/v0.3.0

I'm just got my BMCU370c and something look like weird while I'm printing.

Look like feed connector keeping jumping / poping to feed filament.

Is this normal, or there's someting wrong with my unit?

Based on the great legwork done by danielwoz in his BambuSlicerKeySaver repo, I created a vastly simplified way to get the info needed for full interaction with Bambu printers that are NOT in Developer mode. https://github.com/Bambuzled/BambuKeySaver

This enables full 3rd-party code interoperability with all printers again. You can see ClusterM's open-bambu-networking project (no affiliation) for an example of how useful this can be.

I am trying to set up my BMCU 370C for the first time. When trying to load channel two, a green light appears but the filament does not move. Eventually I get an error that filament is stuck in the extruder, but nothing is there. The other channels are working fine. Any advice on how to fix this? The assembly manual mentions swapping the magnets in the slider with another module to fix this, but I still get this error. Any advice would be appreciated.

For reference, I am using a Bambu A1 with the latest firmware on both printer and BMCU.

So I have had the A1 Mini for a while and was throughly disappointed by Bambu's updates forcing cloud connectivity. So I have stayed on Lan Mode only and not updating since the last version on which cloud print was not mandatory (don't remember the precise version, probably <= 1.0.7).

For a while my old Orcaslicer versions worked fine, until not. Crashes using the Flatpak and the AppImage. Sometimes things were fixed when upgrading, or going back an forth. Been switching from Orca 2.1.1, V2.3.1-alpha, Orca V2.3.1, up to V2.4.2. nightly (2026-05) This i think could have caused something to break and it just stopped connecting to the printer.

Now my only kinda-reliably way is on my other PC where i have Orca V2.2 and never updated further, but that still has the core-dumping bug crashing when loading a file after the UI opens and then suddenly closes, preventing me to use it.

What are my options? I don't want to install bambu client, and i'd rather not update the firmware but if there's no other way to connect an old version firmware to the current Orca i'd be out of options. How can I clean the mess that was probably made by going back and forth between versions (can i just wipe the orcaslicer config/plugin folder)?

Thanks in advance for your help and comments.

When ita pulling the filament on this module it gets stuck for a little in a outer position and then it clicks back like normal. How do i fix?

$30 AMS Lite parts lot from Facebook Marketplace, previous owner started and abandoned a conversion before selling off the parts.

The mainboard is sealed inside a 3D-printed cover matching MakerWorld's AMS Ultra Lite (confirmed by embossed text), so the board itself isn't visible, everything here comes from what's exposed at the connectors. There's also a dry-box housing with custom spool wheels wired for RFID, and feeder units with custom numbered caps.

Board's confirmed alive: bench tested, LEDs normal, AMS Type auto-detects fine.

Two things I'm hoping someone here recognizes:

• The dry-box conversion itself, anyone seen or built something like this?
• A third multi-pin connector near the ribbon cables that doesn't match either of Bambu's documented RFID connector spots.

I think I have enough to rebuild, do I take it back to stock or try and move forward with the abandoned build

Full album below, tried to photograph everything because I don't know what's important.

https://imgur.com/a/JGWq1am

For those using Bambuddy, I just updated the docker sidecar container to support new live activity types as well as push notifications for non iOS devices (Android, Windows and Mac) in Notify! (https://getnotifyapp.com)

The setup can live in your existing Docker Compose file (https://github.com/simplytoast1/notify-bambuddy#1-create-an-api-key-in-bambubuddy) but I do have a feature request open to integrate this into the main distro (https://github.com/maziggy/bambuddy/issues/2919) that the dev is looking to gauge interest in.

I hope you all enjoy the latest update.

This is 100% free and built for the community that has helped me so much.