Bambu Studio Update sets all profiles to 70% Chamber/Auxillary Fan

I am not sure how thats happening, I also keep the files, and multiple versions of BETA and STABLE going back months and months almost a year when I got my printer. I dont get or see diffferent versions of the latest V1.9.1.66 for windows - I frequent the links and do fresh downloads when I am validating a bug in a VM and have done this multiple times over thje last, 4 days ago, 2 days ago, today, the file is the same. (for windows)

For me…
Git hub link hasnt been updated in days…
Software download page hasnt been updated in days…

Downloading from here - Software | Bambu Lab

Or downloading from here - Releases · bambulab/BambuStudio · GitHub

The files are the same, dated approx 3 days ago, same time, same security seal, and do not change the date, time or filename (BL???) when I download them from those two trusted sources across multiple times different days (to verify the fan issue etc).

Windows Filename :- Bambu_Studio_win_public-v01.09.01.66-20240511203248.exe

I am not trying to convice you to upgrade or debate if Bambu have \ have not got file sync issues, although my experience clearly differs from yours and find no evidence of changing versions (apart from MAC which did get a minor release increase for a change, to v.67 - but I am talking Windows)

All the best, I hope you find your way forward with this.

Yep, that’s where I got the “win-public” version you show. That may have been the first time I used that link. I usually wait for Bambu Studio to let me know there’s a new version. I’m just saying there shouldn’t be different names from two different places.

Here’s a screen grab of my files followed by the notice BS gives with a download button. It downloads a “different” file and it shouldn’t. They should stick with one naming convention so it doesn’t confuse people. :smirk:

My apologies to the OP @SneakySmurf for high jacking the thread. I didn’t mean to. Honest.

I havent updated the new Bambu Studio yet but I did for my X1C and has been running fine.

1 Like

Its all learning. I actually never see that "notification\wiki link’ you just shared, and if thats a different file name yet again, abit wierd - agreed. Does that prompt you from within Studio itself like that?

Yes. That pops up and overlays Bambu Studio. Here’s a full screen image.

Thanks. I haven’t updated the X1C firmware yet. I was waiting for BS v1.9.1 to be “finalized”. :roll_eyes:

1 Like

I wanted to print with ASA the last couple of days and all my prints warped at the corners. I thought there was something wrong with the filament so i dried it for 8 hours.

The same problem again. Changed brand… Guess the result?

I then went on the search for a cause for this. So i started with the usual 101 step. Look at it.

Peepers applied and off to the races again. I jumped when the fan kicked in and stayed on at 70%!

I then turned the exhaust fan off manually and would you believe it… the print did not warp off the plate in the corners.
(and I print on a better sticking plate than standard bambus, never needs glue and does 110c as sweetspot for abs and asa. at least up until this happened.)

I then went upstairs again started to check the fan settings for my custom made filament profile only to find that BL has had the audacity to make changes to my personal files on my personal pc without my authorization or consent.

I live in Norway and im pretty sure that BL has broken some law here when they change data in a personal file on a remote computer. Im not gonna dive into that though as that does not alliviate my situation. Just thought I should be a bit informative around my motivations for posting this.

The mere fact that it is widely ageed upon that fans should be off or max at 20-30% for ASA. This includes drawing in fresh air when the exhaust fan kicks in.
(not versed in ABS but I checked the abs profiles and they are indeed also now corrupted with 70% chamber exhaust fan)

Even at 10% that thing WILL create a draft in the chamber that causes warping and adhesion issues.

It puzzles me that BL would push such a detrimental “update” when EVERYONE knows that ASA and ABS are very touchy about drafts. For me i dont have that many profiles to correct, but i do see you issue if you are used to their way of cataloguing.

I did check ALL my profiles just to be sure that they changed no more, and i found that they did not corrupt two of my custom filaments for some reason… then i check the rest and no pla profiles are changed. They also corrupted all the PA profiles with this 70% horse manure… imagine printing pa with 70% fan sucking all out all the heat and draft cooling your model in 3,2,1.

What a disaster this “update” was? think they are safe guarding themself against rma claims from stale belts and temp worn hardware. plus i found that a user had issues with loss of steps when chamber temp was at max. (50c)

BL moneygrabbers are now in “panic mode” as the possible cost to service all the claims would make them have to sell their yahts.

i was a sucker and pressed the button… had to manually scrub their filth off everything. No wonder ppl are going over to x1plus firmware?

Good luck proving that, because is unlikely that Bambu changed your "personal " file.

The .json file that holds your filament settings likely includes a line like this:

“inherits”: “Generic ASA”,

That “inherits” means that your User preset uses the values in the System preset for Generic ASA unless you have changed a particular value to something different. The user preset only contains the modified values. If the old default fan speed was satisfactory before, it’s unlikely that your user preset specifies any fan speed at all.

Bambu replaces the System presets every time you update Studio, sometimes with changes, sometimes without changes. So when they changed fan speed in the system preset, your user preset did not specify anything different than the default, and the fan speed went to 70%.

1 Like

FWIW, I have received a “config” update since installing 1.9.1.66. My ASA presets all show Aux fan speed at 0%.

Edit: I may have implied that Bambu changed fan speeds for ASA filament by changing the value in the Generic ASA preest. I don’t really know where they changed it, it could have been done in several places as there are several levels of inheritance.

Generic ASA inherits from Generic ASA@base, which inherits from fdm_filament_asa, which inherits from fdm_filament_common.

1 Like

Prooving? What are u talking about sir? The profiles i use on a regular basis suddenly turns on the exhaust fan for all asa and abs filaments. This warps these filaments as the chambertemp is baaaarely enough as is of 50c. All my prints warped off the bed.

Regarding the wear claim, the producer of the belt states operation temps uptil 60c under optimal contitions, optimal. This is far from that.

I suspect u print mainly pla and have little to no experience with high temp polymers, as is you do not understand the effect of a chamber from above mentioned filaments.

Why yours are different from mine could many factors including and not limited to zone, to country, to hardware revision.

I can make screenshot to proove all pa,abs and asa profiles are now with 70% exhaust fan.
Which is one of two… either a huge blunder or a security measure.

If you ever did ht materials you would know that draft is your enemy. Are you suggesting i magically changed all the profiles of pa/abs/asa to 100% certainly loosen from the plate and warp?

And the file I made in visual studio as a profile for the asa filament i regularly print with and have several custom made profiles for. Which i then imported to BS, that got changed by BL to ruin four cosecutive prints costing me only time, filament and headache.

I dont know how you dont understand this.

Do check pa/asa/abs filament profiles on your own install and see that they turned on the exhaust for them.

For PLA exhaustfan is only needed if chamertemp exceeds jamtemp for the poorly heatinsulated extruder and its path, but when you have a chambertemp of 50c, for a duration of time i would accept the exhaust to keep the temp ±2c.

Any sooner or any higher speed than (pulling number out the air) say 50% would create a draft that would be detrimental to an pa/asa/abs print. Even catastrophic failure is possible since these materials love to warp at the slightest draft. The fan is quite powerful and creates at least in my x1c a hefty draft enough to warp corners on a 30x30x0.2 square. So i think 50% is more than generous an assuption on BLs behalf.

I have not bothered to edit the native profiles as i just use a few types of filament, i just turned it off from the slicer and that was that. Exported and safely out of BLs reach…

I umderstand you have little to no knowledge of personal rights in other countries let alone your own? To alter a persons data is considered an punishable offence in many countries…

Like i said… im not getting into that. And you did still didnt you? Sigh…

The whole point is that 70% exhaust is bad for those filaments and i did not change it… if you doht understand now i cant help u. And liking ur own posts is lame…

Lets not hijack this fellas thread. I make a new one.

@lkraus was explaining that Bambu changed the generic profile, but since you didn’t change the fan in your user profiles, the profiles inherit the fan setting from the generic profile, so any changes Bambu makes to the generic profile will also be inherited by your profiles. If you change the fan speed on your user profiles to something else, you will no longer have any changes to your fans when Bambu changes the generic profile.

1 Like

I get that. That was not problem sir. What is the issue is like the op said.
The exhaust now turns on for my asa/abs/pa prints making them fail due to warping off the plate.

All these profiles was 100% functional before this update, also they turned off the same fan for petg which needs the same fan.

Someone dropped the ball on this at BL, clearly failed prints from known good settings sure is an issue imo.

I guess if one prints mostly PLA one does even notice this change, but I mainly print the three ones above and they all suffered from this update.

I wish that this community would be more focused on the issue and not semantics faults and such. English is not my native language so there will be translation challenges😕

Thank you for your answer sir.
Im sure that BL will come with a remedy soon, dont u think so too? I dont want failed prints and i think that BL does not want that either😇