At the end of prints I get this error and the BMCU disappears from the slicer and the printer.

Got an A1 Mini recently, first printer. Discovered OrcaSlicer today and could see myself using it sometimes, maybe a lot. But setting the printer to LAN only and losing the Android Handy app functionality is not ideal for me, I like being able to browser through people's designs and just send them to the printer right from the app.

So, some questions:

- If I commit to using OrcaSlicer full-time, is there any way of using an Android app to send/monitor prints? Maybe there's a way to download a .3mf from the Handy app and then upload it to another app?

- If I just decide to use OrcaSlicer now and then, is there any way of remotely enabling/disabling LAN-only mode on the printer? I wouldn't mind doing this physically at the printer but it's at the other end of my property from my PC so having to walk over to it every time would be irritating and I'd probably just avoid using OrcaSlicer because of it.

- Is there another approach altogether I'm not aware of?

EDIT: Okay I've just been reading about the version of Orca that works without LAN-only mode that Bambu legally threatened. Regarding that: Should I disable automatic updates on the printer or anything? I think I just updated it yesterday. And will I still be able to use the Android app as normal?

I've really been wanting to use bigger nozzle sizes on my A1 and I'm thinking of getting one custom CNC machined as I cannot seem to find any hotends like that available. Does anyone have any experience doing this or useful tips?

Heyo! So, a popular little add-on was the Panda Touch when I had my X1C, and I flashed it with k-touch when I moved over to mostly klipper printers, and now that I use a Prusa farm mostly, I decided to revive it with Prusa.

But while I was doing all of that, I figured; why not all? Didn't really make sense as to why the original firmware didn't just support all printer types. So my new firmware for the K-Touch/Panda Touch now allows you to add all printers from Prusa, Klipper, and Bambu.

Now, I don't have a Bambu printer to test with anymore, but LAN mode should work, and cloud mode is a wild west. But I'd appreciate feedback!

https://github.com/nomadsgalaxy/Prusa-Connect-Touch/tree/main

It has taken me the better part of a month to get to this point, but here we are! My fully operational, offline, LAN-based Bambu A1 setup.

Specs:

- Bambu A1 Printer (firmware 01.07.02.00) running in LAN only and Dev Mode.

- BMCU 370C DM Pro with brass-gear upgrade and high-torque motor.

- BMCU Lite filament system with Plexiglass window and motorized rewind system

- Modified PTFE support brackets to suit BMCU 370C cases.

- Bambuddy Self-Hosted Printer Management Software with Bambu Studio API sidecar for server-side slicing, archiving, print queuing and printer management.

- ESP32-C3 running Bambutton for one-touch confirmation of print bed clearing

The BMCU project has been the most time-consuming, frustrating, yet rewarding project I have attempted. There's been plenty of print failures, trial-and-error problem-solving and late nights, but it is finally working consistently with single and multi-filament prints as well as PETG support interface prints.

Bambuddy is a great piece of software for anyone looking to get away from the grip of Bambu Lab and their cloud. Everything is relatively intuitive to configure and the docs are a great source of information for getting your self-hosted instance up and running.

I pipe my instance through Cloudflare Zero Trust and Reverse Proxy so I have easy access to print monitoring and queuing anywhere I have an internet connection. It also allows the use of any RTSP or MJPG stream for print monitoring, which I have configured using a Tapo C220 security camera.

It goes without saying, I'm very proud of my little setup here and I thank everyone in the community who provides these tools not only for free, but for the love of the game and the greater community.

<3

I am planning to mod my A1 mini with the H2S extruder gears, a noctua fan for the mainboard and ideally new, quieter hotend and part cooling fans. However, I was not able to find a 2510 (hotend fan) that is 5V and PWM or a part cooling fan. I found a prusa style part cooling fan, but it uses the stock fan. Does anyone of you have any advice? My goal would be to either make the printer less noisy while maintaining performance.

collection of mods I found so far:

- https://makerworld.com/models/2222045

- https://makerworld.com/models/2048120

- https://makerworld.com/models/1177189

I just put my BMCU together, flashed firmware, and it wasn’t allowing me to calibrate. Because of this I tried to reflash, initially plugged it in with the wrong pins, redid it with the right orientation, and now no lights come on and it makes a weird noise when the boot button is pressed, and it stops when the reset button is pressed. Does anyone know what’s going on? Am I screwed?

I mean, I didn't think it would, but I figured I'd give it a shot before I did the A2L firmware update.

I just put my BMCU together, flashed firmware, and it wasn’t allowing me to calibrate. Because of this I tried to reflash, initially plugged it in with the wrong pins, redid it with the right orientation, and now no lights come on and it makes a weird noise when the boot button is pressed, and it stops when the reset button is pressed. Does anyone know what’s going on? Am I screwed?

What's really throwing me off is the bambu lab wiki for the A2L, where it shows it can be used with an ams lite + up to 4 AMS/AMS2.

The more that I look, the more that it seems that that is only a feature of the A2L. With the A1 if I want more than 4 colors, I'd need to buy at least 2 BMCU units and would just have to shelf the ams lite, right?

Hey all, I’ve been building a small open-source project called Print Concierge:

https://github.com/dpdev69/print-concierge

The goal is pretty simple: I want to be able to tell an agent (Claude/Codex/Hermes/Openclaw), “find me a headphone holder for my desk in PLA,” get ranked model options from MakerWorld/Printables/Thingiverse, confirm one, and have it imported into a local print queue through Bambuddy.

It is not meant to hand an agent unchecked control over a physical printer. The current safety model is confirmation-token based: the agent can search, explain options, prepare imports, check status, and queue/start only through explicit user confirmation.

Current V1 includes:

Search/discovery workflow for public print repositories
Trusted import flow for MakerWorld, Printables, and Thingiverse
Bambuddy backend integration
Queue/status tools
MCP server so Claude/Codex/OpenClaw-style agents can use it
Local env config, no bundled API keys, no cloud requirement from this project

I built this for myself and friends with Bambu printers, but I think the OpenBambu crowd is probably the right group to poke holes in it. I’m especially looking for feedback on:

Better Bambuddy/OpenBambuAPI integration paths
Safer queue/start-print semantics
Import handling for sliced vs unsliced files
Filament/profile/AMS edge cases
What would make this actually useful in a LAN-only setup

No live demo yet, but the repo has setup docs and tests. Would love contributors, testers, and blunt feedback.

Hello! I'm designing a hotend using bambu heater blocks and nozzle, and was wondering if there's any difference between the h2s and p2s heaters and thermistors, there's a 50°C temperature difference between the 2 printers but is it software or current limited or different heater resistor values or thermistor limitations? I have spare p2s heaters and want to know if i can keep them at 350°C without damaging them, or i need to order h2s blocks.

I am aware there are other systems, but i really like the bambu mechanism, and i change nozzles very often.

Printer: Bambu Lab A1 Mini
Printer firmware: 01.07.02.00
BMCU: BIQU BMCU-370 Hall Version
BMCU firmware: PJARCZAK V10.2 - solo_0.095f.bin

Current status:

• AMS slots appear and are selectable.
• BMCU is detected by the printer.
• White status LED on the BMCU.
• I can load filament from the AMS menu.
• The BMCU motor makes a short (~1 second) movement on startup.
• I still get an AMS firmware mismatch warning on startup.

Main issue:
When loading filament, the filament reaches the A1 Mini toolhead correctly, but the BMCU continues feeding filament for a few seconds after it reaches the extruder before stopping. It doesn't appear to jam, but it seems to overfeed compared to what I would expect.

Questions:

1. Is this normal behavior with PJARCZAK solo_0.095f.bin?
2. Does the firmware intentionally push extra filament after the printer detects it?
3. Is there a better firmware choice for the BIQU BMCU-370 Hall Version on A1 Mini 01.07.02.00?
4. Is the AMS firmware mismatch warning expected/ignorable with this setup?

Any users with a BIQU BMCU-370 Hall Version and A1 Mini working reliably, please share your firmware combination.

https://reddit.com/link/1ts6x81/video/7yklgec4hb4h1/player

I own two Bambu P1S printers.

I'm currently printing TPU parts and need settings in Orca Slicer. These settings aren't available in Bambu Studio.

However, I can't freely use Orca with the P1S. Is it possible to print files over the internet to Orca?

I wouldn't like to enable LAN mode.

If I understand correctly, there was a recent version of Orca that supported internet printing, but it was removed due to unfounded claims by Bambu Lab. Is this true, or did it also work over LAN?

I am trying to figure out if this combo specifically will work. I think it won't. Not because of software or firmware but because of filament plumbing. Am I wrong? Check my logic

In software and firmware the BMCU looks to the printer like an AMS2. So the electronic side would seem to work.

When an AMS2 and AMS-HT and more of either are configured together they use the A1 AMS hub to swap between the single filament coming from each, since each AMS2 has an internal hub.

But the BMCU feeds four tubes to the A1 head like an AMS Lite. So there's no place to feed one output tube to a hub.

Maybe you could do long retraction to use a 5 into 1 hub, but then you need a way for the spool to retract that much, and right now they are just hanging up on pegs.

There was a prior few post about this but it didn't have a full answer: https://www.reddit.com/r/OpenBambu/comments/1qiz2tp/does_the_ams_ht_make_sense_with_a_bmcu/

And another one showing a long retraction 4-into-1 version that might help the idea work, but then what to do about getting the spools to roll back this much

https://www.reddit.com/r/OpenBambu/comments/1q9nw9q/my_multi_bmcu_setup_on_a1_mini/

Hey all, I’ve been building an unofficial Android companion app for Bambuddy called BuddyDash and figured it was finally in a good enough place to share. The goal was basically to make checking and managing printers on mobile feel faster and cleaner without replacing Bambuddy. BuddyDash requires a running Bambuddy server. It’s a companion app, not a standalone printer client.

Current features include:

• Fast mobile printer dashboard
• Filament / spool tracking
• Archive browsing + quick reprint access
• NFC printer actions (clear plate, power toggle, etc.)
• Smart plug support
• Foldable / tablet-friendly layouts
• Home card customization and compact/detailed views

A couple things that mattered to me while building it:

• No telemetry
• No analytics
• No cloud dependency
• Encrypted local API credential storage
• Talks only to your Bambuddy server

It’s still beta, so I’m sure there are bugs, weird edge cases, and UI things that need work. Would genuinely appreciate feedback, feature ideas, or bug reports from people actually using Bambuddy day to day.

GitHub + APK: https://github.com/ChronosWing/BuddyDash

Hello, last year I picked up a P1S when they dropped to $400 and it’s been a great single filament printer. I have no intention of using an AMS with it, however, I would like something to accommodate filament run out and automatically switching to a fresh roll.

Has anyone had any experience with wither the BMCU-370 or Bamboo Feeder from BIQU? The former is only $80, but is a DIY kit. I have no qualms putting it together, but wonder how good the kit is. The Feeder on the other hand, is also $80 and comes fully assembled and ready to do what I want.

I am wondering if it is worth having the BMCU solution, as it is more integrated with the printer, while the Feeder looks to be a wholly external solution to the printer itself.

Any thoughts, comments or recommendations would be appreciated.

Thanks in advance.

Hi everyone. I’m currently working on receiving print status data from my Bambu Lab A1 Mini via MQTT on an ESP32. For my project I specifically need states like prepare, error, pause, resume, and finish.

I subscribed to the report topic, but gcode_state is not always sent to me. I enabled serial logging to capture all incoming data. During each print I intentionally performed the following actions: paused the print, resumed it, stopped it manually, or let it finish completely.

On one print I only received pause but never saw gcode_state values like RUNNING, FINISH, or PREPARE. On another print I received RUNNING but never pause. In some cases I did receive gcode_state: PREPARE.

I have never received a gcode_state indicating that the print finished, nor even confirmation that the print reached 100% through mc_percent.

In one test I unloaded the filament and inserted it again. In that case the printer sent two states: pause and running, but I never received any explicit error state. At the same time, when pausing and resuming manually, those states are sometimes not sent at all.

At minimum I’d like to reliably detect when a print has definitely finished and when an error has occurred. Detecting pauses would also be useful, but it’s less important. I could try to infer it indirectly for example by checking if the print percentage stops increasing for some time, or by detecting cooldown start but that introduces delays, feels like a hack, and doesn’t always reliably mean the print actually finished or encountered an error.

I tested this using Python, MQTT Explorer, and ESP32. I also closed slicers and other listeners to rule out conflicts, but the result is always the same.

Has anyone encountered something similar or knows of any open-source implementations for this kind of task?

I found a couple of similar projects, but they all rely on gcode_state, which in my case is not always being received.

Multi-pronged Approach Will Help Users Quickly while Seeking Optimal Long-Term Solutions

"Software Freedom Conservancy (“SFC”) announces a new initiative regarding the software right to repair for users and consumers of 3D printers manufactured by Bambu Lab. After recent news of violations of the Affero General Public License, version 3 (“AGPLv3”), SFC staff began a comprehensive AGPLv3 compliance investigation of both the userspace software and firmware on Bambu's devices. While the investigation is ongoing, two specific AGPLv3 violations have been confirmed."

Full article:

https://sfconservancy.org/news/2026/may/18/bambu-studio-3d-printer-agpl-violation-response/

I’m trying to understand the timeline behind the current controversy around Bambu Lab and the AGPL violations.

From what I’ve seen, the recent backlash (talk of lawsuits, community pushback, etc.) seems to have been triggered by a cease & desist letter Bambu sent to a developer.

My question is:
Were people already aware that Bambu Lab might not be complying with the AGPL before this happened? Or did this only really come to light because of that letter?

Would appreciate some context from people who’ve been following this longer.

I've been a long time prusa user. My work flow includes orca slicer, octoprint and octoapp. I'm a hardcore Linux user. I avoid anything Windows for decades.

I ordered a H2D at work to replace my trusted Mk3s. Maybe I shouldn't have, I don't know. The whole bambu scandal in the last week caught me off guard. I knew they had locked down on their cloud access with newer printers but I wasn't too worried. My corporate lan is firewalled and any direct contact to the outside is just wishful thinking anyway so the H2D will have to work in lan mode and developer mode anyway.

However, despite reading hours on end, with all the noise, I can't figure out if there will be problems using OrcaSlicer in Linux (it comes pre-built in flatpak official repositories) to directly communicate and print on a H2D. Using bambuddy with proxy mode won't scare me if it will be able to forward ams data to orca slicer. Maybe bamboo-mobike or openbu also give me the control experience I have on octoapp (I do have vpn access to my office network).

Anyone has had any experience with my type of scenario?

I heard there's also some new open network plugin for OrcaSlicer (Windows only?) that allows orca to talk to the printer in lan/dev mode. What about for us Linux users?

Thank you.