Jump to content
Corsair Community

Link doesnt adjust fan speed


Jupitersock

Recommended Posts

When I boot up link just doesn't adjust fan speed with temp, I have to close it, restart mess about with groups, run inteltest burn to check if its adjusting speeds, if not do it all again, I have to do this every time I boot up or reboot. I had the 3 pins fans at first, corsair sent the 4 pin and I have tried all my fans yet the problem still persists. Does anyone else get this? is there a fix for this its driving me mad?

 

Windows 7 64

Link to comment
Share on other sites

your having problems with it ramping your fans up and dowm,correct?

what are you using [group] to control them?

cpu temp or h80i temp?

ive found using the h80i temp [hydro water temp] to control fan speeds works best.

Link to comment
Share on other sites

When I first boot corsair link doesn't adjust fan speeds, the CPU temp will go up to 60oC and the fans will stay at 650 rpm, they do not change no matter how long I wait. To get it to work I have to close link then restart it, test again, if that doesn't work close link restart test again, it will start changing the fan speed eventually, here are some screen shots.

 

I have tried reinstalling the software several times.

 

Boot as you can see fan speeds do not change.

 

http://s17.postimg.org/at2042nfz/Untitled_1.jpg

 

Now its working after I closed and restarted link 3 times.

 

http://s16.postimg.org/grrre04hx/Untitled_2.jpg

Link to comment
Share on other sites

Well, first thing I see there is that you have the fans grouped with the Pump AND the CPU. Not recommended and no wonder it gets confused with two temperature feeds trying to tell the fans how fast to run at the same time. It is recommended to group the fans with the Pump only; not the CPU.

 

CPU temperatures fluctuate almost instantaneously. The water temperature is what you should be concerned about. It rises and falls at a slower rate and through a narrower range.

 

The fans are cooling the water that is in the radiator.

The cooled water cools the water block.

The cooled water block cools the CPU.

 

Having the fans attempt to sense and cool the CPU directly is a disconnect. If the water temperature is monitored and controlled properly, it will take care of the CPU temperature.

 

If it is not clear how the dynamics are designed to work, consider this object example: If you group the fans to the CPU, and it jumps in temperature under load, the fans spin up. However, when the load on the CPU suddenly drops, the CPU temperature immediately drops. This shuts down the fans prematurely; leaving the water still hot. When the CPU receives another load, there is no thermal reserve available in the form of cool water. The fans were not allowed to bring it back to low temperature after the load had dropped.

 

Note: When you remove the CPU from group 1, you will have to reconfigure the temperature range for the two radiator fans. It will now be far narrower and a lot lower. Mine are set to 27, 29, 30, 31, 32, 34 covering the fan speed range.

Link to comment
Share on other sites

I see the logic there.

 

I will try setting it up by H100i temps to see if CL works properly.

 

Speed, do you have CL set up to run at startup? Is it minimized?

 

you probably should delete that profile and make a whole new one.

Link to comment
Share on other sites

Well, first thing I see there is that you have the fans grouped with the Pump AND the CPU. Not recommended and no wonder it gets confused with two temperature feeds trying to tell the fans how fast to run at the same time. It is recommended to group the fans with the Pump only; not the CPU.

 

CPU temperatures fluctuate almost instantaneously. The water temperature is what you should be concerned about. It rises and falls at a slower rate and through a narrower range.

 

The fans are cooling the water that is in the radiator.

The cooled water cools the water block.

The cooled water block cools the CPU.

 

Having the fans attempt to sense and cool the CPU directly is a disconnect. If the water temperature is monitored and controlled properly, it will take care of the CPU temperature.

 

If it is not clear how the dynamics are designed to work, consider this object example: If you group the fans to the CPU, and it jumps in temperature under load, the fans spin up. However, when the load on the CPU suddenly drops, the CPU temperature immediately drops. This shuts down the fans prematurely; leaving the water still hot. When the CPU receives another load, there is no thermal reserve available in the form of cool water. The fans were not allowed to bring it back to low temperature after the load had dropped.

 

Note: When you remove the CPU from group 1, you will have to reconfigure the temperature range for the two radiator fans. It will now be far narrower and a lot lower. Mine are set to 27, 29, 30, 31, 32, 34 covering the fan speed range.

 

This is wrong it works fine with the CPU temp as the measure for the curv, it just doesn't work when you first boot, you have to restart the software several times to get it to work.

 

I haven't grouped the CPU and pump temps as you can see pump temp is group 0.

 

You can make a curv for any temp sensor link detects.

 

The H100I temp doesn't fluctuate enough to make a curv for it, in fact mine hardly moves after 1 hour of Prime95.

 

I think this is a conflict with some motherboards and link as further testing I have discovered that my motherboard PWM headers stop adjusting fan speed when link does work.

Link to comment
Share on other sites

Well I personally tried grouping them with the h100i temp instead of my cpu temp both with custom fan profiles and it appears that when done this way the settings do persist correctly. I didn't have to play with Corsair link or even set it to run at startup.

 

Now Im not saying that everything is working correctly since the same effects should be had grouping the fans and basing their speed curve with the cpu.

 

 

Personally im not a fan of having them this way since my case fans aren't running this way and it makes the fans on the h100i rum at full speed for a while until the coolant temp drops.

Its a very narrow band but it seems to be a workaround for now.

 

 

I set my temperature points at 31, 32, 33, 34, 35. Seems to work fairly well for now as my H100i temperature rarely passes 35 degrees and usually hovers at around 28-30c in a 25-26c home.

 

Will report back with further findings.

Link to comment
Share on other sites

good to see your having some success,i was a fan of using cpu temp myself and tried using h100 temp and was sold on using it now,to me it makes better sense as it is the water that needs to be controlled and you dont have to set it to go on max at the first point,,my 2nd point is just 1000 and if that doesnt cool it down then 1 degree higher it goes to 1500 and hasnt ever went above that but its there if needed
Link to comment
Share on other sites

I got it working first time every boot now, I disabled the automatic CPU fan control in the bios, just set it to manual or full on, this stops the PWM on the CPU header, for some reason this works, I suspect a conflict somewhere between the motherboard and Link.

 

I had some fans running of it so I just connected them to link with a Akasa PWM splitter - smart fan cable so I can run all my PWM fans from link.

Link to comment
Share on other sites

This is wrong it works fine with the CPU temp as the measure for the curv,

 

It isn't "wrong". You just think it is. Yes, you can group the fans with the CPU. That doesn't make it the best way to do it. I tried them grouped with the CPU, just to see what it does, and went back to how it should be done. That said, grouping the fans to TWO temperature sources is not the way to do it.

 

it just doesn't work when you first boot, you have to restart the software several times to get it to work.

 

And that it just one of the things that is "wrong" with how you're doing it.

 

I got it working first time every boot now, I disabled the automatic CPU fan control in the bios, just set it to manual or full on, this stops the PWM on the CPU header, for some reason this works, I suspect a conflict somewhere between the motherboard and Link.

 

I had some fans running of it so I just connected them to link with a Akasa PWM splitter - smart fan cable so I can run all my PWM fans from link.

 

Glad you got it sorted.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...