Asked about opinion for bambu vs Prusa Core  

RE: Asked about opinion for bambu vs Prusa Core

Prusa provides API spec to the PrusaLink that is on the printers, you can interact with the printer over local network.

RE: Asked about opinion for bambu vs Prusa Core

It appears the reaction is growing over on the Bambu forum.  Unless Bambu changes course, this move will represent a significant moment in their business and reputation.  The "option" to simply not update firmware is not comforting to many people because it will be unavoidable with new printers, and nobody wants to run two separate workflows in a farm setting.  Claims are often different from reality, but multiple users there are already stating that they will sell their Bambus, stop recommending them, and replace with a different brand.

-J

RE: Asked about opinion for bambu vs Prusa Core

Thats really good from prusa's side. But this is not a plugin its something helpfull if you want to write a plugin.  Its what is said in my post. For the end user that will not bother writing plugins or going on an alternative route for its workflow this development doesn't matter. Of course the ethical approach would be since BL "borrows" code from Prusaslicer to keep open their code too for others to build on.

Posted by: @_kaszpir_

Prusa provides API spec to the PrusaLink that is on the printers, you can interact with the printer over local network.

RE:

I think you need to also look at the rational for this closing of their firmware and don't assume a non-competitive stance. With the rise of hacking it is possible that machines connected to the cloud could be hacked and someone could turn on your hotend, causing a fire. It's why Apple's HomeKit is so locked down. And as they build in more features between their slicer, cloud and printers it wouldn't be possible for them to support all others.. and publishing their work would bypass the security they are intending to provide. Prusa has less advanced cloud services with less conveniences, but it is more open. Users will choose their philosophy. I really like the simplicity of my MK3S+, but the lack of sophistication in their new platform for IP connectivity is a negative in my view. Also the problems people have had in going from version 3.11 firmware in their MK3S keeps me from updating my firmware as Prusa has caused many, many problems with thermal runaway issues. So keeping my firmware up-to-date is not an issue. I use OctoPrint on my MK3S+ and it is more robust and performs faster than Prusa's current IP features without requiring any USB drives for buffering.. another point of failure. But it doesn't have all the features it could because Prusa still controls their own firmware and they only support Octoprint so far.. (they don't officially support its operation). So even Prusa has some aspects of a walled garden.. and as they also offer more features between their Printables/PrusaLink/PrusaConnect I suspect it will become less easy to use non Prusa Slicers.

My biggest concern with all these complex security "fixes" is that, as a Network and Electronic engineer, I see too many instances of these features just not working. It is so complicated it is not possible for people to write error-free code. And I use Apple's new "Theft" security setting that gets auto-turned on in an update, can only be disabled by biometric (not passcode) authentication. However, the finger-print ID is prone to failing over time, and their feature of not requiring it if you are home doesn't seem to work in the 2 iPhone cases I've worked on, requiring users to take their phones to an Apple Store to be totally reset (3.5 hour drive).

RE: Asked about opinion for bambu vs Prusa Core

It will be determined by how successful they are in writing their firmware. And as I indicated with firmware for Prusa's MK3S+ ... if they have this type of success, or lack of it, it will hurt their sales. Fortunately for Prusa users you can just choose to downgrade.. But with Bambu, there may be so many features you need in new updates, you are virtually forced to keep your firmware current.

Posted by: @teamd3dp

It appears the reaction is growing over on the Bambu forum.  Unless Bambu changes course, this move will represent a significant moment in their business and reputation.  

RE:

Well if you have both systems (like I do), or a larger print farm with multiple makes/models of printer, then it's easier to use something like OrcaSlicer as your one overall software solution that has profiles for various printers. Now, with BL's move, it means OrcaSlicer can no longer be used. You're stuck with using Bambu's own slicer and nothing else. It has  lot of people riled up on the BL forum.....

I see the other side as well and see why BL are following this path. I only run locally with no network services other then on my local LAN, so not bothered as much, but it is a strong stance by BL and interesting to see how it will play out.....

Posted by: @tsamisa

 

Posted by: @iftibashir

Here's another reason to avoid BambuLab going forward : https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/

Seems like they are going to start restricting users to their way or no way - so no more 3rd party software like OrcaSlicer etc.

I already use my A1 in LAN only mode - I do not care for or want to use cloud services - and I certainly won't be updating my firmware any time soon. 

Another tick for Prusa and their open source nature. 

Does Prusa provide network or any plugins for slicers other than prusaslicer? Genuine question and NOT a sarcastic comment. Also not to be the devils advocate usually people that DO NOT want to tinker with their 3d printers (the majority of BL customers i recon) tend to keep using the "official" workflow software open source or not. If im not mistaken BL was already working as a rather closed ecosystem and their users were mostly ok with it. Im not sure if dropping plugins for 3rd party slicer will make a difference in their customer base.

RE:

I've run jobs through OrcaSlicer for my Mk4S, and it works perfectly, and iirc, the esp32 camera feed was working in OrcaSlicer perhaps even before they had a tab for it in PrusaSlicer.  The point here is that LOTS of people use OrcaSlicer as their central control hub for printers of different brands. You can't do that with Bambu studio, which means folks will have to split their workflows up.  Bambu must have some significant reason for wanting to push this, because the alternative is that they genuinely don't understand many of their customers.  The fear that they fully control your printer has been the prominent argument against Bambu, and this move is likely going to be perceived as them forcing users to relinquish even more control.  If it was just a philosophical, under the hood change, people would likely ignore it.  But force them to use a lesser workflow and remove efficiency from their day to day operations and folks are going to get upset.  We will see how it goes.

Interestingly,  isn't it common to release "bad press" news on Fridays so that the sting will be softened by the time everyone gets caught back up on Monday?  Let's not forget they didn't want to allow the X1 plus firmware either.  I suspect they have a clearly planned roadmap that includes all this and perhaps more, and they want it badly enough to go through the firestorm for it.

-J

RE: Asked about opinion for bambu vs Prusa Core

Prusa already has their own workflow with PrusaSlicer and PrusaConnect, they just keep certain things in slow development mode so it does not break a lot of existing setups - especially when they are using their own machines in the farms.

Bambu wants to have their own workflow as well, first creating their own slicer fork, and now they started to move more aggressively by breaking existing integrations of connecting other software to the printers. Who knows, maybe Prusa some day will do the same. But more important question is if they want to stay available for other integrations or not. AFAIR PrusaConnect does not have a publicly available API spec, so their product is also limited but from the platform side.

All in all people will rant, some will just get along with the change and will adjust, for the others it will be major change which will make them work to adjust to it, and some will surely abandon given products in the near future. I am sure that Bambu move was well calculated and they know the risks.

Posted by: @tsamisa

Thats really good from prusa's side. But this is not a plugin its something helpfull if you want to write a plugin.  Its what is said in my post. For the end user that will not bother writing plugins or going on an alternative route for its workflow this development doesn't matter. Of course the ethical approach would be since BL "borrows" code from Prusaslicer to keep open their code too for others to build on.