Ngl the whole thing is more personal, One time when I was moving the H2D (with help ofc) 1 out of the 4 rubber feet was still on the table and that memory has stuck with me and will probably stick with me for life cuz putting that thing back on required an extra person. Another time those rubber feet pissed me off was whenever the A1 was going full-auto and zoomed from one side of the gantry to the other after cutting the filament, there was a few times the AMS lite springed up and off of the rubber foot that was… GLUED TO THE THING?? WTH MAN. I highly doubt that this is solely a Bambu problem and I even doubt it even more that this has happened to most people but its just so annoying for some reason, and normally I don’t get mad over dumb things like a piece of foam but its just strange to think a high-tech machine’s major flaw was literally THAT.
Agree, and the real troubling thing is that even though Bambu Connect is supposed to solve that gap, I’ve not seen any possible way to open Orca jobs with Bambu Connect (for an H2D), even with the most basic single-nozzle files. Custom printer in Orca, matched settings, etc. No dice.
The other day I found a loose rubber foot on my desk… where did that come from? Went looking and sure enough one of my AMS had a missing rubber foot.
I enabled Developer Mode and OrcaSlicer can now connect to LAN-only printer.
It’s a real shame that Bambu Labs is putting such obstacles in my way. Unfortunately, the whole thing is becoming increasingly proprietary, which is a direction I don’t like at all.
I like my Plus4 printer. The Core X-Y belts are a little smaller than my H2C, but temperature control great (except doesn’t have controllable vents) and (hopefully) fewer things to go wrong … down side is: harder to get replacement parts; upside: faster personal service; downside: different style user base, compared to the dedication to Bambu of their users.
Had similar experience with my k2 plus. I went to move it and two of the feet stayed on the table, even though they were glued to the bottom of the printer. It’s a 100+ lb printer. Major pain to get those feet back on. I also had to glue the glass door back on one of the hinges, must be the glue they use? At least I can use orca with it though.
Už Orca slicer nejde propojit s X1C.
Well, a bit crusty, but it looks like it may be up and running:
Bambu Connect is still in beta. How well is it working from Windows?
I’ve read you can connect directly if you’re willing to run in lan-only mode with developer mode switched on, but then, of course, Bambu Handy no longer works, so….?
I’ll post a link to this topic in this mega thread as well, in case anyone wants to discuss it or read up on it.
TLDR: Independent software developer Pawel Jarczak has voluntarily shuttered his popular “OrcaSlicer-BambuLab” project following legal threats from Bambu Lab, ending one man’s fight to restore direct control to the popular third-party slicer.
I read that as soon as the developer wrote it in their github.
If everything is as he states, Bambu has no power over his fork. He stated that he did not reverse engineered the “proprietary” plugin and that he only used what was open at the time. That also makes me wonder if the “proprietary” plugin is that secure (we know it’s not since the beginning).
I hope that someone can continue where that developer left and give it to the community once more. I wish that i was more knowledgeable to continue where he left. I would not give in to Bambu in any circumstances if i knew that what i had done was legal and correct. Some day someone will have to start a legal fight so that this does not precede, like it has happened and still happens with Nintendo.
The EU is a good point to start said legal actions and i doubt that Bambu would win, if everything is as he states. Outside the EU i don’t have a clue but from what i have seen from other entitled companies, it does not work so well due to the lack of consumer protection overall.
This creates a state in where developers will be afraid to do more for the community. I just wonder if that wouldn’t be a good thing because if the community stops developing and perfecting, what will these companies do with their software afterwards?
I suspect that may be their primary concern: having open source code that demonstrates how to defeat their security. On the other hand, if it were, then why not just fix their security? Otherwise, the vulnerability persists. So, something doesn’t quite add up.
Exactly that. There is something that does not add up. I feel the urge to try and contact the developer and see if he wants to follow on what he said and even see if he could try and explain the methodology behind it.
The problem is that Bambu hasn’t been able to finish programming the system for a year now. Furthermore, nothing has been released for Linux yet. The security vulnerabilities have existed for months - to the point where they’re common knowledge on the GitHub projects.
It’s not really “defeated”, more like: It’s like a door that’s open, and Bambu asks you not to go through it, but leaves still the door open anyway. That’s not hacking or any special programming - it’s just open.
Ironically, Bambu has actually documented how it’s done. Of course, it doesn’t say, “Here’s how to get around it,” but rather, “Please use it this way!” and if a developer decides against it, well…
I want to express my support for this.
I understand that Bambu Lab needs to care about security, authentication, and protecting their cloud infrastructure. But the right solution should not be to make printer access depend on Bambu’s cloud or on closed middleware.
What many of us want is simple: a documented, open, local API for accessing and controlling the printer on our own network. Sending jobs, reading status, managing AMS/filament data, pausing, stopping, changing settings, and integrating with tools like OrcaSlicer, Home Assistant, monitoring systems, and farm management should not require cloud access.
Cloud features are fine as an option, but local ownership and local control should be a first-class supported use case. These are machines we bought and operate on our own networks.
Bambu Lab makes excellent hardware, but locking down access risks damaging the trust and community goodwill that helped make these printers popular in the first place. A secure, documented local API would be a much better path forward than forcing everything through proprietary cloud-dependent workflows.
I’m jumping back into this thread to send this picture:
“Please send help.” - My PC
//only three of those aren’t orcaslicer
///only one of those aren’t slic3r
Right now, cloud access is not necessary for any of this. Just place your printers in LAN mode, and enable Develop mode if the firmware requires authorization.
Doing all this remotely is the issue. Bambu is saying that if you want to use the Bambu cloud, you have to use Bambu software. You are free to develop your own cloud or enable secure remote access to your LAN.
MY complaint has always been that Bambu sold the printer to me with the ability to use third-party software and then added restrictions on the advertised features. Call it bait-and-switch or just plain lying, it is a dishonorable way to treat customers.
Agree. My Artillery X2 is fully controlled in house and also outside, using only Octoprint and my phone. No cloud needed and also as easy as any Bambu printer. Just click print and leave it be… No calibrations, no tuning, no tinkering.
this has been my sticking point too, but as time goes on, this will be true for less and less people since they closed it down so early in their history. Humans dont generally care at all about unknown unknowns but if you show us something we can do, and take it away….
I’m technically now a hypocrite since I bought an x2d with that knowledge, but whatever, I dont see corpos changing, I can do all three of: accept it; not like it; and remain vocal about it being a bad direction.
Definitely me too. I have 15 of these things, and I will start looking into another ecosystem if they do this.
Rossmann steps up…
Louis Rossman pledges $10000.00 to teach Bambu Labs a lesson.