icue keeps resetting the temperature source

[AntiMatterDyna]

i want my fan curve to depend on cpu temperature, i set up a custom curve and made sure the cpu package was selected as the sensor , but after every reboot the sensor goes back to being the liquid temperature... lucky that i even figured out what was happening because i was stress testing my cpu and the temps suddenly spiked way higher... this could have ended VERY badly... how do i get the sensor to always be cpu temp???

[DevBiker]

First, it's a bug that should be fixed shortly (hopefully next release).

 

Second ... I'd actually argue that it's a bug to allow you to set the CPU temperature as the temperature source. It's not the proper way to do it - the fan speed for the cooler should be based on the temperature of the coolant.

 

Now ... before you hit reply and start flaming, consider: What do the fans actually cool? Is it the CPU? NO! They blow air through the radiator to cool the liquid coolant. It's the liquid coolant that cools the CPU. For the best CPU temperatures, you want to keep the coolant cool; this will directly translate to better CPU temperatures. See more detail - including some useful tips for setting the fan curve appropriately - in the Liquid Cooler FAQ linked in my signature.

[BlaiseP]

And to add to DevBiker's argument for basing the temperature source off the coolant; fluctuations in CPU temperature (which happen with monotonous regularity) will see your fans ramping up and down often (noise) if you base your temperatures off the CPU.

[AntiMatterDyna]

maybe for every day use, but when im stress testing a cpu with aida64 i'd rather get the immediate response of the actual cpu heat.... lesson here is i guess dont trust icue at all and set it manually to 100%...

[tristanb]

I'm noticing the same issue, in addition on every reboot all commander pro fan speed related profiles, default to quiet. It's becoming ridiculous, especially since the only way to get them off quiet is to create another profile, which works sometimes.

[c-attack]

maybe for every day use, but when im stress testing a cpu with aida64 i'd rather get the immediate response of the actual cpu heat.... lesson here is i guess dont trust icue at all and set it manually to 100%...

 

If you are going to run benchmarks, you should be setting the fans to a fixed speed of your choosing to maintain consistency between runs today, tomorrow, or 6 months from now. Coolant temp will shift with the room temp, so day to day actual coolant temps and thus fan speed will vary. For your normal use with dynamic curves, you should use coolant temp as stated above and the fans "response" to the initial CPU voltage thump has no impact on end CPU temperature. However, I think we all agree it should not reset on you on boot each time.

 

 

 

I'm noticing the same issue, in addition on every reboot all commander pro fan speed related profiles, default to quiet. It's becoming ridiculous, especially since the only way to get them off quiet is to create another profile, which works sometimes.

 

That is different than what happening above and was a very annoying glitch on early versions of iCUE. What version are you on? I haven't heard about this in quite a while.

[DevBiker]

maybe for every day use, but when im stress testing a cpu with aida64 i'd rather get the immediate response of the actual cpu heat.... lesson here is i guess dont trust icue at all and set it manually to 100%...

 

You do realize that doing this will do absolutely, positively nothing to impact the CPU temperature, right? For stress testing, as c-attack mentioned, use a static profile. Or stick with the liquid temperature and have it increase at a lower temperature. The coolant is what is cooled by the fans, not the CPU. And the coolant take a good deal longer to warm up than the CPU does. And cool down, too.

 

CPU is everyone's default because that's all we've had to go on for a long time. That's not the case any longer. Even motherboards come with additional temperature sensors and headers for thermistors because CPU temp just isn't an appropriate control variable for a liquid cooled system.

 

Argue all you want ... the good thing about physics is that it's true whether you believe in it or not.

[MikeC1064]

Sorry to hijack, but for us inexperienced users when you say use the coolant temperature, what option are you talking about and where? If you don't use custom fan curves is coolant temp used by default in the supplied performance settings?

 

Thanks.

[tristanb]

That is different than what happening above and was a very annoying glitch on early versions of iCUE. What version are you on? I haven't heard about this in quite a while.

 

c-attack, I'm using iCUE v3.9.93, this is my first installation/experience with any of the link/iCUE software. I'll see what I can find on this glitch, I started another thread with my debug logs, if you want to take a look, so I don't take over someone else's issue.

[c-attack]

Sorry to hijack, but for us inexperienced users when you say use the coolant temperature, what option are you talking about and where? If you don't use custom fan curves is coolant temp used by default in the supplied performance settings?

 

The various cooler models will use coolant/liquid temperature as the default control variable. This is sometimes referred to as H1xx Temp (insert your cooler model name). iCUE has cleaned the naming up a bit and when you click on the cooler tab, it is the one to the right of the pump and labeled CPU Coolant Temperature (with some of the label cut off of course). This is how the cooler really works. CPU heat originates in the pins as voltage. The heat is then conducted out of the CPU through the cold plate of the cooler. No matter if you are using an air cooler or water, your CPU temps is voltage temperature - less whatever heat you can conduct out in that moment in time. The cooler is really a waste removal system. It takes the heat and transports it elsewhere. However, the conductive path across the cold plate and CPU runs both ways, so if you don't take out the waste heat in the cooler, it adds back to the CPU temp. You can see this when you run a 100% stress test with a graph, like AIDA64. You start the test and see the huge voltage based temp jump. That value is determined on your CPU model and voltage and stays pretty constant at specific settings. So you jump from 30C to 75C. Over the next block of time, you can see the CPU temp creep up slowly, maybe +1C per minute. That is the waste heat building up faster than it can be disposed of. No cooler is perfect. Most AIO models will stop around +6C-8C depending on size. It will match your coolant temp rise. That is the number you are trying to shrink with your pump and fan settings. That original +45C on 100% power on can't be reduced, but the coolant temp can. The fans and pump affect the coolant temp only, so when the CPU takes a big jump opening a program, you don't need the fans to ramp up since the coolant temp hasn't changed. The CPU temp did spike because the voltage and load did, but you can't stop that. As long as you keep your fans moving at a slow to steady moderate pace, most of the waste heat gets removed. Very few people need to run high or aggressive fan curves to keep things in check.

 

On the Commander Pro, the default presets correspond to CPU temperature and that is usually a poor choice for anything except an air tower. With the C-Pro you have a lot of other choices, most of which are better than CPU temp. GPU temp, coolant temp, and the temp probes that come with it are all better choices, making the preset curves not something you need at all.

[c-attack]

c-attack, I'm using iCUE v3.9.93, this is my first installation/experience with any of the link/iCUE software. I'll see what I can find on this glitch, I started another thread with my debug logs, if you want to take a look, so I don't take over someone else's issue.

 

I've read your other posts and I was hoping someone would take a look a the logs. They don't mean much to me and I am not a programmer. However, the specific C-Pro/iCUE bug I was referring to would wipe all your assigned fan curves and put you back to Quiet-Quiet-Quiet all the way down your fan settings. Having read your other post, this seems like something different. I have used ML-RGB (low range) and Pro (high range), in both 120 and 140mm sizes through all the iCUE versions. I have never seen it refuse to follow an assigned command regarding maximum or any fixed speed. When you were using the custom curve to do this, were you using fixed % or fixed RPM? If one, try the other. I have had a few other fan models hesitate with a fixed %, but they all seem to work when you tell it to run a specific rpm.

[MikeC1064]

On the Commander Pro, the default presets correspond to CPU temperature and that is usually a poor choice for anything except an air tower. With the C-Pro you have a lot of other choices, most of which are better than CPU temp. GPU temp, coolant temp, and the temp probes that come with it are all better choices, making the preset curves not something you need at all.

 

So as I don't have a C-Pro (as far as I am aware - just the lighting node pro that came with the fans), what options do I have? From what I can see, all I am able to change are the options that affect the RPM settings for the pump and two fans within the Device page for the AIO? I currently have the Fans set to Quiet and the Pump set to Balanced.