@Sebo3D1 Does this also disable the auto part cooling fan?
I am new to this forum. I have wasted lots of LW PLA on my X2D. The darn fans keep coming on strong. I have no issues printing the same filament on my X1C.
It is absurd what BambuLab has done. It doesn’t have to be this complex and dificult. It is sad that BambuLab is not even participating in this thread or trying to resolve this issue.
No wonder Prusa is known as the Cadilac of 3D printers. They have live chat 24/7 and help you resolve issues quickly and efficently. I would gladly pay their higher prices just so I don’t have to pull my hair out (not much left) dealing with these type of stupid and preventable issues.
Easy fix for cooling, put a piece of paper on the fan suction, as it will not be able to suck air, it will not be able also to blow air 
. Maybe gave it some support with piece of tape …
I can imagine people start ripping of the fans from the walls inside and leaving them to blow next to the printer in the free air … As most probably if you fully disconnect it it will fail the print.
And next level would be fan rpm emulator…
FYI it will help a lot if you open your lid and front door to keep the temp low while the fans are off.
I’m battling the Aux fan control at the moment. I thought I commented everything out that controls the aux fans (P2 and P10). Now P2 works as intended and takes exactly the values I set in the PETG filament cooling tab. P10 however is stuck on the value that I set in the machine start code. I let AI check the gcode and it also couldn’t find the part where P2 gets set but P10 not.
Anyone have an idea what’s going on? Some firmware mumbojumbo I don’t have control over with the gcode?
These are the first lines on the first layer
";======== X2D layer_change gcode ==========
;===== 2026/07/01 =====
M106 P2 S25.5
M106 P10 S25.5"
And it literally only changes the fan speed of the left auxillary fan. This has got to be a bug or what?
It is kind of known that Bambu does things inside the firmware that can not be seen or set outside, or at least not so easy. So it is most probably not bug but some underlying scripts.
I wonder why the gcode would have the second M106 line then if it is being ignored, but the first line for the other aux fan works.
Maybe if you look in the final code you will some other $values or ros in the code are using it somehow. As there could be separate functions and values in the start/stop, filament and the slicer G code. Just a suggestion.
Hi guys, for anyone that is interested - I believe I have found the reason why the right aux fan does not respond to the M106 commands… The issue seems to be simply that any commands targeted at the right aux fan (P10) are tab intended; this causes the parser to fail and those commands just get ignored. Removing the tab indentation fixes the issue for me.
Update:
I updated to the latest X2D 1.02.00 firmware and Bambu Studio (BS) 2.9.1.70.
Bambu has indeed changed quite a bit, so I had to rewrite my modifications.
I’m attaching a 3MF file with the necessary changes.
I print PETG with PLA as the support interface. My models are half-circle objects, and with the AUX fans running at 70–80%, they were constantly detaching from the build plate.
The attached settings set both fans to 30% and the exhaust fan to 70%. Once printing starts, you can manually adjust any fan speed, and it will stay at that level without changing between layers or filament changes.
I can also hardcode any fan speed so it remains constant, regardless of temperature, layer changes, or filament changes.
Bambu Lab X2D 0.4 nozzle - Manual Fans Hold.3mf (28.0 KB)