When Side Fan kicks on, Nozzle temp drops quickly and printer stops due to nozzle temp error

dbw5 · February 14, 2025, 12:24am

Nozzle temp will be rock solid, until the side fan kicks on at >50%. then it drops from 220 to about 112 and then bounces around a bit until it steadies.
However, many times, the printer will error out claiming nozzle issue.
If I manually watch he side fan and “ramp” it up slowly, the temp stays fine and no printing errors.

PIA… any ideas anyone?

For_Ward · February 14, 2025, 1:01am

Try to set your fan percentages per layer for the side fan.

There are a couple options for setting up your fan strength percentages in the GUI.

dbw5 · February 14, 2025, 3:47am

I saw those settings, but none of them say Side fan… so which is the fan… is it the part cooling fan? thanks.

For_Ward · February 14, 2025, 4:15am

It is under that Cooling section called: Auxiliary Part Cooling Fan. There should be three fans.

Part
Auxiliary
Exhaust

Enjoy!

dbw5 · February 14, 2025, 8:38pm

My fan labels are completely different. I am printing right now so I cant show them. I do see I am a few versions behind in my creality print software, so will update it .

Here is an example.

dbw5 · February 14, 2025, 8:44pm

This time when it rebooted and I Resumed, I turned the fan on immediately so that it could stabilize at the right temp with the fan running, instead of the fan starting up later.

But as the head moves close to the side fan, the temp starts to fluctuate again.

this is ridiculous!.

dbw5 · February 14, 2025, 8:50pm

Watching the temp bounce around from 205 to 230 with a target at 220.

Just dropped to 187, and printing quit.
I had dropped the fan speeds.

this time I am starting with them all up high… Seems to be stable for now.

dbw5 · February 14, 2025, 8:56pm

spoke too soon…

You can see the variations in temperature in this graph. The big dip in hte middle is when it quit.

You can then see that it starts out very stable, then starts to bounce around again.

I dont have this problem when I print small items and place them far up front on the table, away from the fans.

I sure hope hte new software fixes this. As this is a PoS right now.

dbw5 · February 14, 2025, 9:11pm

Am at a total loss…

Look how stable it was and then bam. it quits.

Radical_Data · February 14, 2025, 9:20pm

Hello dbw5,

I don’t have the same printer so this is “just a shot at it” kind of question.

I take it that the Silicone Cover Sock is in place and intact ?
If not, that may cause the temperature fluctuations.

Cheers.

dbw5 · February 14, 2025, 10:37pm

Thanks. I am not sure what that is.

I have never run across it

This is a K1
Currently have all fans at 100% and made sure the cover was snug. Had been stable for about 2 hours now.

For_Ward · February 14, 2025, 11:05pm

Okay. You are using Mainsail with the K1. I was mistaken. I thought without further questioning you that you had a K1C with the GUI from Creality. A-Okay…

There was also some talk about people doing a calibration for the heater. Maybe something to look into…

So, with Klipper and Mainsail, one would and this is for boards I am familiar with currently and not the K1 board for Mainsail, I would follow along in Klipper ideals…

I know nothing about the K1 and using Mainsail with it
PID_CALIBRATE HEATER=heater TARGET=230
That should calibrate your hotend heater if it is available on the K1 at 230 degrees C

If that is not available on the K1 and/or your HEATER=heater is called something different, do not try number 2.

If and when your GUI from Creality (I am guessing here) allows for it, calibrate the heater element so that the heater knows where it should gravitate towards.

For_Ward · February 14, 2025, 11:29pm

Also @dbw5 ,

I remember using Mainsail a bit with another controller. If things are properly set up in the config and if things were Open Source with Creality alongside Klipper, one could easily tune the machine to a working order…

Klipper uses some type of Macros:

github.com/Klipper3d/klipper

config/sample-macros.cfg

master

# This file provides examples of Klipper G-Code macros.  The snippets
# in this file may be copied into the main printer.cfg file and
# customized.

# See docs/Config_Reference.md for a description of parameters.


######################################################################
# Start Print and End Print
######################################################################

# Replace the slicer's custom start and end g-code scripts with
# START_PRINT and END_PRINT. See docs/Slicers.md for more information on using these macros.

[gcode_macro START_PRINT]
gcode:
    {% set BED_TEMP = params.BED_TEMP|default(60)|float %}
    {% set EXTRUDER_TEMP = params.EXTRUDER_TEMP|default(190)|float %}
    # Start bed heating
    M140 S{BED_TEMP}

This file has been truncated. show original

You can view how some of their buildings are put together and how to incorporate that into your build. Will it work? No clue. Time will tell…

But…

I say if it is broke, fix it. I cannot guide you 100% of the way but I will say these ideas…

K1C uses Klipper (I think). I have not researched the ideas in about two months.
K1C adaptations have changed and quickly. For instance, from 4.x.x to 6.x.x in about two months time.
So, someone is purchasing these machines and making them work and well.

I have the K1C. I got tired of waiting for prints to finish and I splurged. I saw their other series but I cannot afford to handle the price tag. So anyway, I hope you can configure your board firmware so that your GUI does as expected, i.e. not as shown. If you need other ideas, please just jump on in and let me know what exactly is available on the Mainsail screens or I may just interpret them incorrectly.

For instance, read the klipper docs on specifics. I know the, or knew, older 4.x.x version had klipper but their flavor of klipper installed on the machines and that is as far as I made it…

I took the entire machine apart, acted like it did not work, and then just went with what they offered. I made a simple workaround useless because I quit. I flashed the machine and then barreled over and just upgraded to their OTA firmware(s) available. I work with it and with them now instead of going against their build process.