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

So I updated this morning and all of my personal filament profiles, along with all of the built in presets (Generic PLA, Bambu Basic PLA, Generic PLA Silk, etc.) have all been reset with the auxillary fan at 70%.

I sent to prints off to my X1C’s and the whole room sounded like a hurricane.

Come on Bambu Lab. This is a major screwup. I have like 60 or 70 custom filament profiles and the worst part…

You CAN’T edit the built ins. They are burned in with the 70% chamber fan.

This is very inconvenient and I wish I didn’t have to upload 100 log files to put in a support ticket. (Absolutely horrible to always force this.)

Another thing, the AMS filaments are no longer an option when picking slot 1, 2, 3, 4, etc in Bambu Studio. They just aren’t there anymore.

I personally think the whole connection between the AMS and Bambu Studio is trash. There needs to be the same interface and selection in both. When I create a preset in Bambu Studio, and I have about 60 or 70, that should be pickable in the Device area when loading up filaments. It is not. Sure I can go and double my work and create custom filaments. But I do mine by color… like Polymaker Pastel Peanut, and it has the exact color code of the filament and that it is PolyTerra filament.

Really bad design and implementation for those who have more than 10 printers. I’ve spent all morning re-adjusting my user presets and was pretty pissed off that they edited my “copies” of Generic PLA" and such. They should have been left alone.

Total mess for production’s sake. Not a big deal for those that have one printer and just mess around a little. But if they want people to use these to make money, they can’t go changing things around like that. (And they didn’t even say they did in the update, which is worse.)

You might try logging out of Studio and then logging back in to force a re-sync of your presets.

The built-in presets, in Windows, are at C:\Users\%username%\AppData\Roaming\BambuStudio\system\BBL\filament
All of the PLA filaments inherit their settings from fdm_filament_pla.json, which is where you can find
"additional_cooling_fan_speed": [ "70" ],

and change it in any text editor. Changes made here WILL be overwritten if these presets or Studio are again updated by Bambu.

Looking at my backups from as a long ago as July '23, this default fan speed has always been set at 70% for PLA.

I also updated to Studio 1.9.1.66 this morning. None of my User Presets have been changed.

4 Likes

Works fine for me - change over the filaments in device tab for AMS, drop down the Prepare filament screen - its all populated. image

and my custom filaments havevnt been changed, 30% aus cooling etc here as example

I know you said you dont want to do custom filament profiles? so when you say Presets - I think we have similar, I have both linked to a Custom Filament (SUNLU)

Or from my list…

but also other simple presets, including named with colour , colour pallete and cooling are show in the Device\Preparae\Filamentgs drop downs? Even if NOT tied to a custom filament, but a simple filament colour and preset saved for a bigger included\default brand avaialble in Studio eg Polymaker (Or Generic for that matter)

image

Hi DruiD,

I figured out this part… I tried out the new “Multi-Device Management”. The AMS Filaments came back when I went back into preferences and turned it off. Unfortunately, its not ready for prime time as it only does simple AMS mapping at the moment.

I don’t know. I’ve never had my auxillary fans go on and they went to 100% this morning after the update on two different machines. Then when I changed the 70% back to 0%, it went away. So something must have been screwy if you say they always are at 70%. My auxillary fan just doesn’t come on. I could have missed that I had the wrong plate set or something because everything seemed to have changed and I may have missed it.

Yes, that is what I mean. I had all these filaments… my complaint was that I create all these filaments in Prepare, Filament, User presets but…

none of them are connected to “Device” here unless I’m just not smart enough yet to figure out how to add the new “custom filament” and connect it to an actual RGB color code

Ok umm - So in this drop down - the AMS colours are from the Device Section - it only lists the FILAMENT profile, not prests etc See here i its SUNLU CHERRY RED - as below in my User Preset- but shows the AMS understands and thats Filament ID (associated with SUNLU PLA+ - my custom filament) and the oclour I choose in Device Screen.

image

for example … if i just colour here and change it to say “green” for the RED filament


NOTE ** This is photoshoped in green as during the print I cant actually chaange color with the filaments active in the AMS

  • it will be “Green” in the top drop down - as thats what i set in the AMS and AMS just sees a that not the “preset” info.
    image
    NOTE ** This is photoshoped in green as during the print I cant actually chaange color with the filaments active in the AMS

The reason your filaments say Generic, Bambu is like mine just says SUNLU PLA, SUNLU META… its the parent filament that the PRESET (eg Cherry Red in my case) was created off
image

and the inverse is true as well. This SUNLU BLACK filament, for the purposes of this, I have modified the filament PRESET colour to yellow, but in the AMS box (like above) its still black … so in the Prepare-Filament screen … you get this effect once selected and not in the drop down menu - you see the AMS Device colour (DEFINED as black) and the filament PRESET colour (yellow).
image

Per AMS slot\filament - The Left hand colour swatch is what we told the AMS\what the AMS thinks it has until its changed. The RIGHT side is what is saved in the FIlament PRESET.

[quote=“SneakySmurf, post:6, topic:75406”]
none of them are connected to “Device” [/quote]

Edit one, and find the Parent Filament, thats where you need to look in Device Screen.


So in this example, I select Polymaker PLA Lite - then the the K value if I havvec calibrated it , but I also need to manually select a colour here…
image

So in summary, what you think your adding (other filaments, like Amolen PLA GLOW - Green) in the PREPARE are NOT FILAMENTS but a PRESET as far as the DEVICE SCREEN goes - but instead a sub-preset linked hat parent filament and the PRESET shows in PREPARE screen, and once K Calibrated is just the k value against the PARENT in the device screen. To be 100% honest - its a wierd concept I struggled with as well.

So now, you can either create ever single “colour tweak” as a full custom filament with a single set of paramaters, eg colour ,cooling, type etc … and you will then be able to DIRECTLY do it in the DEVICE screen -as its its own FILAMENT

  • or-
    …as Bambu intended. FILAMENT is a grouping by vendor\product\type -eg AMOLEN \ PLA \ GLOW … and presets are the extra tweaks … like colour, cooling. - ALL still linked back to that PARENT - AMOLEN \ PLA \ GLOW (and btw it does this i the background via a Filament ID within the JSON files).

That’s a TLDR from me, but hopefully I have understood your problem and helped.

PRESETS -
https://wiki.bambulab.com/en/software/bambu-studio/preset
vs FILAMENTS
https://wiki.bambulab.com/en/bambu-studio/create-filament
and some known facts
https://wiki.bambulab.com/en/software/bambu-studio/custom-filament-issue

And amoungst many other similar threadds on this forum , my own journery of discovery and isssue with this system of ccreating and custominsing “filaments” in the way we think of them … eg PINK TRI-SILK POLYMAKER… not - POLYMAKER - PLA LITE - SILK - TRI COLOUR - PINK etc :stuck_out_tongue:

https://forum.bambulab.com/t/custom-filament-issues/36350/9

I now think you are not hearing the auxiliary fan, but the chamber fan at 100%.

The filament presets did not change, but Bambu fixed a logic error in the printer start code.

https://github.com/bambulab/BambuStudio/issues/4054

So it’s not a bug, but a feature, correcting a problem I’ve never encountered.

2 Likes

@SneakySmurf @lkraus I just got a config update?

I updated the software to the 5/10 update on Monday morning and ever since Bambu Studio immediately crashes upon opening. I have tried uninstalling and reinstalling and still same problem. I can’t even submit a ticket to technical support because they require that you send the logs…I can’t access the logs because I can’t get into studio.

That’s confusing, because it says it reduces the fan speed as bed temperature rises.
Are you using Studio 1.9.0 or 1.9.1?

Update again, they’ve supposedly fixed the problem with a new version 1.9.1.67 just for Mac.

[quote=“lkraus, post:12, topic:75406, full:true”]
That’s confusing, because it says it reduces the fan speed as bed temperature rises.
Are you using Studio 1.9.0 or 1.9.1?[/quote]

On Windows, V.1.9.1.66
image

It makes sense because they INCREASED IT, with a fix in v1.9.1 actually, to 100% from above 50 degress to fix the PLA jamming issue, so they have just dropped it back to 45 degrees,reduning to stay at 70% oncce over 45 degrees, 45 degrees might only kick in AFTER the initial start that was jumping straight 100% for most people since the update - I think its a balance between temps and fan kicking in to stop the PLA jamming they are trying to get right.

Or … the config “reduce” is a typo lol, but I dont think so… see below.

Old Code from v1.9.1 was this … Greater than 50 , push it to 100%, but then if greater than 45, but less than the previous statement 50 value, set it to 70% - so for cool plate, it was like 70% , Textured \ hot plate - straight to 100%

Now - everything is 70% fan above 45, less than 45 assume 0 and no setting for 50 and above.
Git hub picture, you can see the change in your own machine start code for PLA etc.

GitHub link and for sources Chamber fan goes to 100% when warming bed at begining of print job · Issue #4054 · bambulab/BambuStudio · GitHub

I’m windows not mac unfortunately

Is this another one of those “tester” threads that spilled over into the Forum? Because according to BL, the most current OTA software release is version 01.08.00.00 (20240507). What gives here and where can I find what’s really going on with software updates?

I don’t want to be part of trial software or firmware for the printer. I want them to work together when they come out. :roll_eyes:

It’s not a tester thread. We are discussing the newest update:

Which “newest update”. I see two that are two different sizes. The one you show didn’t show up until this morning. This is exactly why I don’t update software as soon as it hits the “interweb”. I’m holding back on firmware for the X1 too.

1 Like

Well where did you get these from and what was the latest you downloaded and what day and time?

I mean we posted when ti was released publically v1.9.1.66, I posted 10-12hrs later that a config package went out (maybe in another thread, not sure) toadjust the chamber noise fan, but maybe since then and you checking Bambu updated the v1.9.01 with that package update and its so minor it doesnt need are revision change, OR … somehow compression changed the “size on disk” as the origianal download size, above what you highlighted is the same…

Offcourse no one has to update if they dont want to, day 0 or day 365 after an update. I have been guilty of cross posting from BETA (for which I apologised a few times and now very careful) - my only recommendation is always get the latest version off Github or direct bambu stable link and that will be the “latest”.

I dont work for Bambu but I love this stuff and maybe overly invested but thats my cross :stuck_out_tongue:

I think I downloaded it from the BL link at 10:18am on 5/14 as the created date shows. I thought the name seemed strange because it didn’t match the naming convention of the previous files. (I keep all the files.) As you can see in the name that file was named by BL with a date of 5/11.

When I went back to Studio in the afternoon, it said there’s an update available. I’m still on version 01.08.02.56. The file on the right is the one that was downloaded at 1:09pm.

It’s clear to me the BL is not keeping files in sync, and this is what scares me about implementing a new version now. Between the firmware fiascos and intermediate program files being released willy-nilly, I’m afraid to update. It should be done by one department with firmware and program files in sync. Period.