X1C Chamber fan sets at 100

I have 3 X1C’s and 1 P1S. One of my X1C’s, my oldest, after one of the last firmware updates, sets the chamber fan at 100%. I have looked through the Gcode and it is the same on all 3 X1C’s with the exception of the m1005 commands at the end. I am using the same filament profiles on all the printers, so I can’t figure out why it does this. When the print starts I can manually set it to 70% and it gets much quieter, however when a color change happens it automatically goes back to 100%. All my printers are on the latest release, 1.08.02.

I think I reversed the firmware update and it went away, but it came right back after I updated again. I have also tried resetting the printer back to factory and that did nothing. Does anyone know if Bamboo support helps with printers out of warranty? They kind of dropped the ball on my last support ticket about their filament with the tape keeps coming off the spools. I haven’t heard a response in weeks, lol.

Downgrade the firmware to the previous working version. See how it goes.

It is not a firmware thing. It is a gcode controlled operation.there is a section in the gcode that litterally tells you

;=============turn on fans to prevent PLA jamming=================
{if filament_type[initial_no_support_extruder]=="PLA"}
    {if (bed_temperature[initial_no_support_extruder] >45)||(bed_temperature_initial_layer[initial_no_support_extruder] >45)}
    M106 P3 S180
    {endif};Prevent PLA from jamming
    M142 P1 R35 S40
{endif}

Line 56 and 241. Remove that block entirely if you want to remove it.

M106 P3 

Is the gcode to control the chamber fan.

1 Like

But the gcode is the same on all three of my X1C printers and only one of the printers has this behavior.

I am downgrading the firmware again to a 1.07.04. This was the last firmware that it didn’t do this. But I was hoping there was a different fix, and not one where the gcode is inconsistent from printer to printer.

And I don’t want the chamber fan to not work at all, I just want it to go back to what is was previously.

Downgrading the firmware fixes the issue. Kind of stupid… Hopefully with the next release it will work correctly.