How stay out of date and away from forced authentication

Despite so much water passing under that bridge it seems users still struggle with the concept of Bambu being in full control of their printer and workflow.
I am a P1S user and I stopped updating and caring about it with the 1.07 firmware.
It shall allow for offline firmware update, which might come handy one day in the far future.
So what’s the deal with this useless topic you wonder?

I am not a fan of this modern way of consumer binding at all costs.
Especially when it comes to tools and a printer is just a tool…
I want to provide a general idea/workflow for those wanting to stick with the old stuff, that’s all.
And for obvious reasons I won’t post any links as this probably makes the Bambu bots take the topic down within minutes - speaking from past experience here…

I stick with my printer but the the idea is the same for the other Bambu machines, H2D excluded…

The 1.07 firmware for the P1 series and those without the forced authentication for the other models shall be the base of operations.
I already posted something in regards to getting the older network drivers and Studio versions but using the right keywords you can find this info with any good search engine in minutes.
Studio should match the firmware in terms of firmware requirements.
So 1.9 something is probably as high as we can go here.
Orca is always an option though :wink:

The biggest hurdle here is Lan Only mode and the resulting downsides one just has to accept.
Ok, shall we try to begin ?

Firmware downgrade if required…
Handy lets you downgrade the firmware but there is a catch…
You need to be logged into your account to get the firmware and install it.
Right now Bambu has not fully closed the backsupport door, meaning if you grab an older Handy version from places like APKMirror or APKPure you should still be able to downgrade even if the newest Handy version refuses to do so.
Check the firmware release notes though!!!
If it says you can’t downgrade to an earlier version than you might have a problem, so best to not update the firmware based on blind faith alone.
Ok, I assume you somehow found the right links and managed to go back a firmware version that does not include the new auth system…

Orca is the way to go…
If you need to stick to Studio for whatever reasons it is best to learn how to use and configure a VM, a Virtual Machine.
In there you can have as many machines as you like and install whatever Studio version you can get your hands on.
Plus it is quite easy to prevent Studio from calling home unwanted.
You could slice and dice with the latest Studio version and as long as printer firmware and the older Studio version won’t complain can print (almost) as usual.

How to make Lan Only mode stick and ensure custom profiles and filaments work ?
Tricky one…
For (very) obvious reason the OFFLINE ways to bind your printer fail more often than what they work.
Double check that all version are matching close enough!!!
Studio gets updates and to get started here it is best to use the Studio version that was current with the installed firmware.
If all fails just bite the bullet and do the Bambu online binding through your account and all.
If you have a working Studio version where the printer works just copy the Config file over :wink: Well, at least copy the part into the other config file that has binding code and such…
Once you can access and use the printer reboot the lot and confirm it still works !!!
Now and only now is the time to pull the plug.
Use a an old router to just cater for the printer that has no internet access, configure your firewall to block Studio, restrict access for Studio and printer through your router’s firewall and network settings - whatever fits the bill and your knowledge level.
All you really need is printer, Handy and Studio in the same Wifi network.
Worked it out and and it still works? Well done!!!

SD access…
There is apps for Windows and Mac that allow you to use your account details to start a secure FTP connection to the printer - giving you full access to the SD card.
You can delete old files, add new print files and all that but from there you can’t start any jobs or access the printer itself.
There are some apps that give access to most things you might need but it seems they all stalled and there is no current progress to report.
But those that worked before the auth stuff came around still work on the old firmwares as advertised.

Camera feed…
Bambu uses a third party system to provide the video feed, which comes with rather annoying security features Bambu utilises to the fullest.
While there is few options to access those feeds if unsecured there is none I know of that works as a standalone option on a mobile phone or computer.
You would have to extract the codes used by the API or find one that is hacked to get around those limitations.
For now just accept that without handy or studio you won’t get a camera feed without a lot of nightmares.

Lost code - help needed!
There was a repository about 2 years ago that aimed to replace the standard P1 screen with a Raspberry based option that simulates whatever the original offers.
Added benefit was that it came with BT and Wifi to allow for a companion app to act as the screen and input.
Was only for Linux but still.
Sadly the entire project seemed to have vanished as there is no website any more and the Google Drive links it had can’t be found through a search these days either.
None of my search engines produce a result :frowning :frowning:
I know that chance are next to minus 4 but if you downloaded the repo or just the Rapberry Pi files then please let me know if they include anything to find or contact the author!

As always > feel free to ask here if you want more details or need specific help on the above…

1 Like

What about those custom profiles ???

Well. what do you want me to say?
IF you have working print or filament profiles then please export them into a folder you find later on.
It also helps to copy the corresponding folders on your drive, those in the user folders.

Like with so many things it is not always easy to transfer things from one Studio version to a much later one.
It can and might happen that you exported your profiles and that the import in the same Studio version works fine but trying the same with a Studio version a few levels up can mean prints fail or that profiles fail to show up.
Sometimes you can force this to somewhat work by corrupting the installed Studio version (like by deleting a few vital files) and installing over that version.
When the installer (or if) find the error log it should always aim to import whatever was present in the old installation.
If you ever watched the install closely you probably notice that the installer just deletes all files in all folders.
I don’t know it the same still works on Studio versions above 1.9x but you can always try…
Before closing the installer check if your custom profiles are still present in their folders - if not copy them over again!
You get a 50-50 chance that Studio will honour your hard work by having your custom filaments and print setting show up.

What are the downfalls here?
Lets say you had enough but way to late in time …
Means you have profiles for a much later firmware and Studio version that what you intent to downgrade to.
Or in lame words it means you have settings and file structures the old version might not be able to handle (correctly).
Sometimes it works and if it does then be grateful and also export those profiles!
Chances are though that once you double check with older 3MF you have and never ones you create before the downgrade that the prints fail to impress.
If this happens then PLEASE don’t start screaming and swearing like I did for few hours as it won’t help - trust me I know…
And I also know you will hate me for the solutions as it involves a lot of manual labour…

If you exported WORKING profiles you can access them through Notepad++, binary editors and more.
Helps though if you took screenshots of your custom settings, profiles and such.
Trust me when I say that starting from pure scratch after a complete downgrade IS your best option to provide working outcome.
Ok, but what IS the best way to get custom filaments working on the 1.07 firmware and matching Studio version if you don’t use Orca?
Check the Bambu Wiki.
Create a custom profile as the Wiki says but with some minor changes >
Lets say you main filament supplier is ‘AAFilaments’ or in short AA.
You might have 20 different colours of PLA and several types of filaments from AA but you WILL keep things dead simple!
Take a pen and some paper and start writing down notes based on the exported working profiles you had.
For example: AA PLA of the standard kind prints fine at 218ºC a bed temp of 52 and …
Unless you actually have massive fluctuation for different colours just define a single PLA profile for AA that has no colour assigned.
The colour you set in Studio after an AMS sync in the AMS settings.
Similar story for the K-Factors >
Calibrate the filament from scratch if there is any flaws you should not have and save the profile with the number in the filename!
E.g.: AA PLA 0.015, AA PLA 0.22, …
The befit of this approach is that you can use those k-factor setting no matter the filament colour and that you only need one filament profile unless colour like black actually require slight adjustments you don’t want to do on the fly when needed.
For PLA matte, silk or other plastics you use the same approach.
You will quickly get used to this and see the benefit of the simplicity.

Ok, id did all the above, even created the filaments profiles from scratch and in the simple form…
But you ruined it all for me and my 3MF files won’t produce proper prints - damn you!!!
I know… It really sucks if you wasted all the time reading my nonsense only to find out you can’t use your print files…
My apologies but please direct your frustration towards Bambu instead :wink:
Use logic here!
Studio versions change, with that standard setting and we can also find new features.
How would a Studio version know what to do if there is lines it can’t interpret?
Or how could a newer Studio version know that you compensated for flaws in your settings that are now fixed in completely different settings?
You hopefully see the real issue now :wink:
So again, try logic >
The model printed fine with the firmware and Studio version it was created with.
So why not just import the model geometry and trust that your current machine and other settings a proper ? :wink:
The only thing that really gets lost here is the support setting but that is good if you ask me…
Calibrate your filaments and settings and just import the model geometry - make that a habit for downloaded files.
Custom supports can be a pain but I still find this hassle preferable over importing a file that fails to print no matter what I try.
I downloaded less than 10 3MF until I got fed up with the hassles of syncing the AMS trying to get the filament to match and all that…
Import the geometry, define things as needed and Bob’s your aunty.
I know, it is not what Bambu promises in terms of being easy and hassle free but it beats wasting hours and filament to watch prints fail again and again…

1 Like