No Automatic Fan Speed Adjustment

[nul7]

I created a support ticket, but haven't heard anything back so I figured I might as well post in the forum.

 

System Specs are on my profile and I have a total of 11 140mm PWM fans, 7 of which I want to control via the CL software. I am attempting to group 4 with the first graphics card temp and 3 with the second graphics card temp.

 

Cooling Link Software: 2.4.5110

Commander Firmware: 2.06

Both Cooling Node Firmware: 1.2.11

Lighting Node Firmware: 1.1.9

 

I bought a Cooling and Lighting Kit and a Cooling Kit so I could have 2 cooling nodes. Everything installed smoothly and all my fans and components are properly detected by the software. I cannot get the software to automatically adjust fan speed.

 

I can adjust speeds manually (Setting %, Maximum, etc) in CL and it works, but selecting any of the premade curves (quiet, balanced, or performance) or a custom curve does nothing. The temperature line moves properly in the curve grid, but the fans always stay at the same speed.

 

I've tried swapping Commander units, replaced all fans (from NZXT FX Enthusiast RF-FX14L-OP to Rosewill Hyperborea), using a different USB header, uninstalling/reinstalling, program from the system tab vs the groups tab, fresh install of Windows... no luck.

 

What am I missing to get this thing to work?

[wytnyt]

what are you using to trigger your fan curve

post a screenshot of your fan curve

[wa3pnt]

It sounds like you do not have the fans in the group of the device (CPU temp, H100i, etc.) that you want to control the fans.

 

Can you post a screenshot of either the System screen or the Group screen?

 

RodeoGeorge

[nul7]

While running FurMark:

http://s17.postimg.org/jdn5ng2az/Screenshot_1.png

 

Temps still climbing, still no increase in fan speed:

http://s17.postimg.org/maa6nq84r/Screenshot_2.png

 

Temps go off the chart after this, fans don't speed up at all:

http://s17.postimg.org/v6kyrnyqz/Screenshot_3.png

 

After setting all fans to maximum speed to cool everything back down, then back to custom curve:

http://s17.postimg.org/eg9l2c0bv/Screenshot_4.png

 

Top, Rear, Inner Top, and Front Top are grouped to Graphics Card 1 Temp.

Bottom, Inner Bottom, and Front Bottom are grouped to Graphics Card 2 Temp.

 

EDIT:

 

And here is my Group page:

http://s14.postimg.org/v355qrya5/Screenshot_5.png

 

and my Devices page:

http://s14.postimg.org/jfb3w8959/Screenshot_6.png

[wytnyt]

you have your fans linked to your video card,you may try going into your video setting and see if the video has control of its fans,if it does the link cant use the gtx to curve the fans,link has to have control

graphic cards are set to use its own control by default

i have same brand card and had to change its settings

since you have win8 trigger options are limited till an update is released.i didnt see a hydro water temp[mebbe missed it] but thats your best trigger to use

if that isnt a option then you have 4 thermals,you can place one on the cpu or video and use that as a trigger,not quite as accurate but itll work ok.

you really need to get everything working together and familarise yourself with things,then itll all come together for you.

[nul7]

Thanks for the response.

 

I'm not trying to control the fans on the graphics cards. I'm simply trying to have CL control case fans based on the temperature of the graphics cards. It doesn't make sense that it would be able to read the temperature properly and not control the fans independently. The software should just read what the temp is, match that on the curve, and set the appropriate fan speed. It shouldn't matter what sensor it is, or what it's attached to... just read the temp and adjust the fans.

 

I'm not using a Corsair cooler, so CL can't read my water temps.

 

I'll move some things around tomorrow and try grouping with one of the thermal sensors from the kit.

[wa3pnt]

Just to see if there is a problem with Corsair LINK reading the temperatures of the GPUs in such a way as to control the fans, try grouping the fans with the CPU temperature and if they then increase as the CPU temp increases.

 

RodeoGeorge

[nul7]

This is the worst product I purchased for my new build. Whoever is in charge of this should be ashamed of themselves. It has SO much potential, but has been so poorly implemented it's not worth the materials it's built from.

 

I moved a probe to the graphics card, booted up, grouped everything to it and it worked great... until I restarted. From then on, the sensor would only read 0 (as reported here: http://forum.corsair.com/v3/showthread.php?t=123192). Swapping sensor ports made no difference. Based on the suggestions in that thread, I uninstalled 2.4.5110 and installed 2.4.5065.

 

First thing I notice is that I, of course, lost my CPU temp (it seemed to read about 10 degrees too high in 5110, anyway). I reconfigured everything and fired up FurMark. Only the fans that were connected to the same node as the probe would automatically adjust. I took the computer apart for the millionth time, moved a probe from the other node to the other graphics card. Readjusted, and it works. Reboot, and my LEDs reset to white and the fans ramp up... open the software and it settles in and starts working again.

 

So I got it to work just enough to be somewhat useful by reverting the software, losing CPU temp, only grouping fans to a temp probe instead of something accurate/useful, the probe has to be on the same node as the fans, and having to open the software on every reboot. Yippee.

[wytnyt]

This is the worst product I purchased for my new build. Whoever is in charge of this should be ashamed of themselves. It has SO much potential, but has been so poorly implemented it's not worth the materials it's built from.

 

I moved a probe to the graphics card, booted up, grouped everything to it and it worked great... until I restarted. From then on, the sensor would only read 0 (as reported here: http://forum.corsair.com/v3/showthread.php?t=123192). Swapping sensor ports made no difference. Based on the suggestions in that thread, I uninstalled 2.4.5110 and installed 2.4.5065.

 

First thing I notice is that I, of course, lost my CPU temp (it seemed to read about 10 degrees too high in 5110, anyway). I reconfigured everything and fired up FurMark. Only the fans that were connected to the same node as the probe would automatically adjust. I took the computer apart for the millionth time, moved a probe from the other node to the other graphics card. Readjusted, and it works. Reboot, and my LEDs reset to white and the fans ramp up... open the software and it settles in and starts working again.

 

So I got it to work just enough to be somewhat useful by reverting the software, losing CPU temp, only grouping fans to a temp probe instead of something accurate/useful, the probe has to be on the same node as the fans, and having to open the software on every reboot. Yippee.

 

it isnt the corsair products,it win 8 which is typical with new OS's

corsair is working on a new software release as noted in a win8 sticky thread

[nul7]

it isnt the corsair products,it win 8 which is typical with new OS's

corsair is working on a new software release as noted in a win8 sticky thread

 

Windows 8 has been out for more than a year, it is hardly new. If they're giving that as an excuse as to why their product doesn't work properly, they're being insincere.

[wytnyt]

im not getting a pointless non ending debate,things works well in win7 so obviously its in the OS

i dont fault corsair,if i were them id wait till microsoft is finished changing things before even considering working on the software

first it was win8 then 8.1 then 8.2,where will it get finished and how many times would corsair be expected to redo it.

the fault is in microsoft plain and simple

plenty nuff said...

and sadly enough,its the customers who always gets left holding the bag,,

[nul7]

im not getting a pointless non ending debate,things works well in win7 so obviously its in the OS

i dont fault corsair,if i were them id wait till microsoft is finished changing things before even considering working on the software

first it was win8 then 8.1 then 8.2,where will it get finished and how many times would corsair be expected to redo it.

the fault is in microsoft plain and simple

plenty nuff said...

and sadly enough,its the customers who always gets left holding the bag,,

 

You're obviously not a software developer and not familiar with how things work in this field. I am. You're absolutely delusional if you think it's Microsoft's fault. If software companies waited for the OS developer to stop making changes, there would be no third-party software. OS's are under constant development. It is the responsibility of the developers to keep up with those changes. More than a year has passed since the release of W8... that is more than enough time to fix any bugs related to the new OS. They could have rewritten this software from scratch multiple times in that amount of time.

 

Worse yet, this is a .NET app. The entire purpose of the .NET framework is to provide interoperability and the CLR/CLI. It's Microsoft's version of a WORA framework for Windows. If coded properly a .NET app will run on any version of Windows that supports that version of .NET... they'll even run on Linux and OSX with Mono.

 

Anyway... I'm not here to argue. It's working just enough to say that it's working. Hopefully they'll get their act together on this and bring out the potential in this product. I was excited when I discovered it, which is why I'm so disappointed now that I have it. Thanks for the replies.

[AlC0]

I'll have to agree with nul7. I have had issues with this product since I first bought it, back in march. The one thing that amazes me the most, is how Corsair, a brand known for their flawless PSU's, good RAM, cases, and so much more good stuff, let their Brand get dragged through the mud like this.

 

To those of you who read my last thread: I got my temp readings to work, but the custom curve fan speed does not. Hopefully I can get both some day.

 

I am no expert, but I know basic electronics, and a thing or two about programming. A fan-controller is not a very complex unit. Not even the LINK. The important things are the sensors, and the PWM/voltage regulators, and readings form sensors not directly connected to the LINK. All the BS about "only corsair fans is guaranteed to work" is really low. Most motherboard fan controllers is capable of using both PWM and voltage regulators to adjust fan speeds. One would expect more from a dedicated unit for that purpose. In the early versions of the node firmware, it didn't even support PWM fans. Any idiot would see that popping up as an issue when the product was to be released. They have fixed that, and a lot of other issues, but still, there is all these little bugs that takes a brilliant concept, and make it to a source of frustration for the customer.

 

The hardware itself seems to be good, it is just everything that has anything to do with software has a million bugs. The quality of the programming work that has been done in this case is sub-standard.

 

I really like Corsair as a brand. I have a good PSU from them, memory that has never failed me, really nice fans at very compete able prices, great customer support and so much more. I am still going to buy their products, but I really hope they will hire some competent software developers to solve this mud pile piece of software.