3DQue announced compatibility with Bambu Lab’s new “Developer Mode”.
There’s a lot going on here, so let’s take this apart.
Bambu Lab made a major change to their firmware recently, following up on announcements from several months ago. The software and network configuration as originally deployed by Bambu Lab allowed third-party applications to directly access and control the 3D printers.
This feature was used by several third-party slicers, farm software, and others to add functionality to the Bambu Lab environment. In particular, many Bambu Lab operators preferred using OrcaSlicer instead of Bambu Lab’s BambuStudio, as that software had a few more interesting features.
However, Bambu Lab became increasingly concerned about future security incidents. Allowing anyone to control the printer took away their ability to ensure safe operations. This isn’t an issue if everyone using the devices is well-behaved.
But that’s something Bambu Lab cannot guarantee, and I suspect they expected gigantic lawsuits if someone took advantage of the open nature of the original configuration.
Imagine, for example, if a bad actor created a program that would damage a 3D printer by playing with thermal or motion settings. Then imagine that software targeting a large print farm with hundreds of Bambu Lab devices. When the smoke cleared, I’m sure the farm operator would then launch a lawsuit against Bambu Lab to recover from the damage that Bambu Lab’s configuration allowed to happen.
To solve this legal dilemma, Bambu Lab introduced new firmware (which just landed on most Bambu Lab machines) that prevents third-party access. Instead, third-party software must interact with the 3D printers through a new component, Bambu Connect.
This change did not affect the vast majority of Bambu Lab 3D printer operators, who simply continued using BambuStudio software, which still connects directly to the printers. There was, however, a vocal minority of Bambu Lab operators that were directly affected by the changes. Not only were third-party slicers unable to directly access the machines, but more importantly, any print farm management software was also blocked.
That’s critical because there are many large-scale print farms using Bambu Lab 3D printers.
As a result of their pressure, Bambu Lab introduced something called “Developer Mode”.
Basically, Developer Mode changes the nature of the device to open up access to third-party controls, much as before. However, in doing so, the operator must tick off a form accepting responsibility for any activity on the system. In fact, the waiver states:
“Developer Mode Important Notice
If you enable LAN Only mode and turn on Developer Mode on your printer, it’s important to understand the risks involved:
Developer Mode allows third-party software to control the printer, which means it can manage print jobs and process data. This can lead to potential problems such as print failures, irreversible printer damage, or data privacy issues.
Bambu Lab cannot oversee or verify actions performed by third-party software. By using this Developer Mode, you accept full responsibility for any risks or consequences.
Bambu Lab may provide updates to Developer Mode from time to time. We encourage you to check the wiki regularly for updates.”
Now that Developer Mode has been released, it’s now up to third-party developers to make use of it.
One of the first to do so is 3DQue, who produce print farm management software for Bambu Lab devices. Their AutoFarm3D system provides “seamless, automated print farm management on Bambu’s industry-leading printer line, including the P1, X1, and A1 series.”
3DQue said the new integration includes:
- Farm-wide job routing and smart queue management
- AMS-aware filament routing (with AutoFarm3D’s own mapping tools)
- Compatibility with Auto Ejection and Door Opener hardware
- Scalable print farm support—from 5 to 500+ printers
This will be incredibly welcome by anyone operating a large-scale 3D print farm using Bambu Lab equipment. Bambu Lab does not provide any form of print farm management software, so without this integration, I’m not sure what managers would have done.
Via 3DQue
