I’m pretty sure I was successful with putting both my Bambu printers on LAN mode and setting up my router to block their connection to the internet before potentially unknowingly updating to this garbage firmware version. We’ll see, definitely not buying another Bambu for the foreseeable future. I bet Prusa is pretty happy about this decision from Bambu.
I tried switching to LAN, it took multiple attempts and half a day to get my mini to show up as a choice for LAN mode in Bambu Studio. And then when shut off for the night, it was gone again in the morning. As in it couldn’t be found. And now it’s back to Studio not connecting to it.
I’m not sure what I can do besides using the sneaker net to run it.
I’m going to save your comment for now. I have a script that I use at work that helps with printer detection because we have a very similar issue. I’ll try to post it here if I remember.
Running the script after launching Bambu studio helps with detection of the printer. Only caveat is that you have to run it every time you launch Bambu studio.
It’s nothing malicious, I’ll just post the code for you with the important bits that need to be changed noted.
Take note of line 4. It is looking for a separate file called discover_printer.ini to retrieve printer information from. You can name the ini file whatever you want, just make sure to update the name within the powershell script.
Here’s the link to the ini file. Not sure why I even bothered to put it there since it’s so short lol.
PRINTER1_DEV_NAME= The name you want the printer to show up as in Bambu Studio
PRINTER1_USN= Serial number of the printer
PRINTER1_IP= Local IP address of the printer
PRINTER1_CODE= The access code for the printer that is in lan mode
You can do multiple printers in one ini, just change the number at the end of “PRINTER” to the next number.
We use this for X1E models, but the script looks to be generic so I don’t think it will matter which one you have.
I have only seen one person have an issue out of the 50 or so that use this script. It will connect from his machine but consistently fails to send files to the printer.
I just put the powershell script and the ini in the root directory of the Bambu Studio installation and make a shortcut to the ps1 script on the desktop. If you have powershell scripts locked down you may need to add a key at the bottom to allow it to run.
To use the script, open Bambu Studio first then run the script and browse to the device tab and click the + in the left hand menu to bring up discovered printers.
I bet Prusa is pretty happy about this decision from Bambu.
Maybe they are happy, but does this help them ? Maybe a little bit in the short term, but Prusa offers are on a different price range. Higher prices where justified in the past by delivering a better quality, better out off the box experience and innovative features compared to competitors until Bambu reshaped the market.
The team at Prusa shouldn’t feel happy, they should feel comforted in their strategy of supporting open-source and community efforts. But, above all, they should see an opening to gain back the front stage if they are able to provide a printer at the right price and the right features
Now, given they just launched the CORE One, priced at 1350€ assembled, I doubt they have anything ready to reveal right now to amaze us.
I’m pretty sure I was successful with putting both my Bambu printers on LAN mode and setting up my router to block their connection to the internet before potentially unknowingly updating to this garbage firmware version. We’ll see, definitely not buying another Bambu for the foreseeable future. I bet Prusa is pretty happy about this decision from Bambu.
I tried switching to LAN, it took multiple attempts and half a day to get my mini to show up as a choice for LAN mode in Bambu Studio. And then when shut off for the night, it was gone again in the morning. As in it couldn’t be found. And now it’s back to Studio not connecting to it.
I’m not sure what I can do besides using the sneaker net to run it.
I’m going to save your comment for now. I have a script that I use at work that helps with printer detection because we have a very similar issue. I’ll try to post it here if I remember.
Running the script after launching Bambu studio helps with detection of the printer. Only caveat is that you have to run it every time you launch Bambu studio.
It’s nothing malicious, I’ll just post the code for you with the important bits that need to be changed noted.
Ok, I will look forward to looking at it.
Sorry for the delay, I’ve been quite busy.
Here’s a link to the powershell script.
https://pastebin.com/RFtfLQNq
Take note of line 4. It is looking for a separate file called discover_printer.ini to retrieve printer information from. You can name the ini file whatever you want, just make sure to update the name within the powershell script.
Here’s the link to the ini file. Not sure why I even bothered to put it there since it’s so short lol.
https://pastebin.com/138TnASY
PRINTER1_DEV_NAME= The name you want the printer to show up as in Bambu Studio
PRINTER1_USN= Serial number of the printer
PRINTER1_IP= Local IP address of the printer
PRINTER1_CODE= The access code for the printer that is in lan mode
You can do multiple printers in one ini, just change the number at the end of “PRINTER” to the next number.
We use this for X1E models, but the script looks to be generic so I don’t think it will matter which one you have.
I have only seen one person have an issue out of the 50 or so that use this script. It will connect from his machine but consistently fails to send files to the printer.
I just put the powershell script and the ini in the root directory of the Bambu Studio installation and make a shortcut to the ps1 script on the desktop. If you have powershell scripts locked down you may need to add a key at the bottom to allow it to run.
To use the script, open Bambu Studio first then run the script and browse to the device tab and click the + in the left hand menu to bring up discovered printers.
I hope it works for you.
I’m not yet in a hurry. ;) Thank you for sharing!
Did you just block the device by mac? Or only specific endpoints?
I blocked it using my router’s GUI, I imagine it goes by the MAC address but I’m not sure.
Maybe they are happy, but does this help them ? Maybe a little bit in the short term, but Prusa offers are on a different price range. Higher prices where justified in the past by delivering a better quality, better out off the box experience and innovative features compared to competitors until Bambu reshaped the market.
The team at Prusa shouldn’t feel happy, they should feel comforted in their strategy of supporting open-source and community efforts. But, above all, they should see an opening to gain back the front stage if they are able to provide a printer at the right price and the right features
Now, given they just launched the CORE One, priced at 1350€ assembled, I doubt they have anything ready to reveal right now to amaze us.
If you did update, you should be able to rollback
Someone on youtube (possibly Louis Rossman) said that they made it so you couldn’t revert back but I don’t know whether or not that’s true.
I don’t think anyone does at this point.
Maybe not easily, but I’m not aware of a way to prevent people from manually flashing a new firmware replacing what’s there.