Jump to content
Corsair Community

Can iCUE control case fan ML120's connected to mobo Fan Headers and/or base their fan profile off of GPU and AIO Temp sensor data if connected to Commander Core, XT or Pro??


Ca1ibos
 Share

Recommended Posts

I'm building a PC for my brother with a 5900x and RTX3070 and am trying to decide between an Elite Capellix H150i or a H150i RGB Pro XT. While the latter is only slightly cheaper (€13), it does also save me having to purchase 3x ML120 fans (for reasons too convoluted to explain) so effectively its another €38 cheaper so €38+€13=€51 cheaper.

However, as well as the 3x ML120 360mm Radiator fans I have another 2x ML120 side intake fans feeding the GPU cool outside air and 4x case roof mounted ML120fans as exhaust that I would like to control. So for example when the GPUis in use and heats up and its own fans start up and gradually spin faster, I would like the case intake fans feeding the GPU cool outside air to also start spinning up etc. Similarly when the PC is under low load I would like those case roof exhaust fans at low rpm's but when the case interior starts heating up under load I'd want those fans to spin up faster. The reason for wanting this kind of fan control is that this PC is in a small HTPC formfactor case (Thermaltake Core G3 used on its side) and will be on the shelf of an IKEA TV unit with about 2cm clearance at the side and above. On the one hand this PC in the Living room needs to be quiet when not under too much load but because of the constrained size of the case and the constrained space it will be sitting in, I want to maximise cooling potential when it is under heavy load when my brother is 4K60 Flat Gaming or PCVR gaming or using his Adobe Suite of Software for his Photography/videography hobby.

While I did have something similar set up on my current PC with the fans connected to motherboard headers and using Speedfan to control the case fans based on GPU temperature, it was a pain to setup, it sometimes didn't work/crashed and importantly for my Brothers PC scenario, I won't be there to fix it when it does.

Hence I was thinking that if iCUE is able to do this even with the case fans just connected to motherboard Fan headers and it can do it based off the GPU sensor data, (I know iCUE detects GPU's but can is that only in terms of RGB control or can iCUE base a fan profile of off GPU temp?) well in this scenario all I need is a H150i RGB Pro XT,

However if iCUE can only control those 2x intake for GPU and 4x Exhaust fans connected to something like a Commander Core, Commander Core XT or a Commander Pro will I be able to connect all fans including the 3x AIO fans (9 in total but none will be RGB)  with the aid of fan splitter cables, and can I create 2 fan groups within iCUE with the 2 intake fans RPM's based off GPU sensor Data and the 4 roof case exhaust and the 3x AIO Radiator intake fans based off of the AIO temp sensor data. In this scenario it makes more sense to buy an Elite Capellix H150i that already comes with a Commander Core.

However, the final potential scenario is if iCUE can only control those fans connected to a Commander Device and if it CANNOT control those intake and exhaust Case fans RPM's based off of GPU and AIO's own integrated temp sensors and can only do it based off of Core XT or Commander Pro Temperature probes. In this scenario where a Commander Core that came with an Elite Capellix H150i doesn't have temperature probes, well then it would make sense to buy the H150i RGB PRO XT AIO and a Commander Core XT or Commander Pro that both have at least 2 Temperature probes.

Final question....Assuming some or all of the above is possible, can those fan profiles set for all those fans whether they be based on integrated GPU or AIO sensor data or CoCoXT or CoPro Temp probe data, can those be set as a default profile stored on the memory module of a CoCo, CoCoXT or CoPro and remain active when the iCUE Software itself is disabled. (Ideally this would be the case, as I am also installing an Aida64 Sensor panel on the front of this case and Aida64 and iCUE don't play nice together)

 

 

Link to comment
Share on other sites

Forum Edit function still not working right Mods!!

Kinda answered my last question just now. 

If I want to install iCUE to create the Hardware Fan profiles and then uninstall/disable it so that it doesn't interfere with my Aida64 Sensor Panel software, then I can't rely on iCUE software to base fan profiles off of integrated temp sensor data because it will no longer be installed to do the monitoring of that temp sensor data. Thats even if that scenario were possible in the first place. Whereas I imagine that a CoCoXT and CoPro can still control fans connected to it based off its own Temperature Probe Data once a hardware Fan profile has been set with iCUE Software before its un-installation.

So I think that means that I should buy a H150i RGB Pro XT AIO and a Commander Core XT or a Commander Pro? Seeing as I don't think I need more than 2 Temperature Probes and a CoCoXT has 2, is there any other reason I should choose a CoPro over a CoCoXT??

Link to comment
Share on other sites

Edit still Borked!! This is annoying!!

Given the small HTPC case will never have RGB enabled Fans so the RGB Fan headers on an CoCoXT are moot, whereas I might in the future buy my brother some LS100 RGB Strips for behind his 50" LGTV while he is 4K60 Flat Gaming, perhaps the CoPro that is only about €6 dearer than a CoCoXT, is the better buy with its 4 temp probes, 2 USB Header Passthroughs and importantly given what I just said, 2x Lighting Channels for the LS100 Strips??

Link to comment
Share on other sites

  • Corsair Employees

The iCUE software does not have the ability to control fans plugged into your motherboard header so if you wish for iCUE control over all of your fans they will have to be plugged into the Commander Core that comes with the cooler. As for the curves, the default curves are based on the liquid temperature of the loop, but you can set custom curves and utilize a SINGLE temperature sensor for those curves to ramp up and down on.

Link to comment
Share on other sites

3 minutes ago, Corsair Notepad said:

The iCUE software does not have the ability to control fans plugged into your motherboard header so if you wish for iCUE control over all of your fans they will have to be plugged into the Commander Core that comes with the cooler. As for the curves, the default curves are based on the liquid temperature of the loop, but you can set custom curves and utilize a SINGLE temperature sensor for those curves to ramp up and down on.

Right, so if I buy the H150i RGB Pro XT thats the 3 Radiator fans controlled by the Hardware profile (based on water temp) I've set for the pump unit controller.

Then my 2 intake and 4 exhaust case fans connected to the CoCoXT or CoPro can be controlled by a hardware Profile I've set up but I can't split them into independent intake and exhaust groups based off of different sensors?? All 6 fans connected to the CoCoXT or CoPro can only be in one group and all based off of one sensor??....and by 'sensor' do you mean the integrated temp sensor Data coming from the GPU or do you mean from one of the CoCoXT/CoPro Temp probes??

Unless I am misinterpreting what you said, why does a CoCoXT/CoPro have 2 and 4 Temp probes respectively if you can only control all the connected fans as one group and based off of only one of the temp probe sensors??

Link to comment
Share on other sites

Given Corsair Notepad is busy and couldn't come back to clarify, I think I understand now after a bit of googling.

Yes, Fans connected to a CoCo can be grouped and with some based of AIO water temp and some based of GPU Temp sensor data. I think what Notepad was saying was that other than the Rad fans being based of water temp, you can have other fans based off of no more than one more Temp sensor. At least I think thats what Notepad means. ie. You can split your fans into groups and you have 2 choices for any given fan group. Either Water temp or the SINGLE Sensor of your choice. So for example I could have 3 groups. Rad fans based off of Water temp. INtake fans based off of GPU Temp Sensor but the third fan group of the exhaust fans can only be based off of water temp or my chosen GPU temp. I could not base my exhaust off of motherboard or RAM temp sensors for example because my SINGLE temp sensor preference was GPU.

I also learned that the Aida64/iCue conflicts are when both are trying to communicate with one instance of the CPUID protocol at the same time for Data on any of Corsairs 'i' products. Seeing as all I want displayed on my Aida64 sensor panel is CPU, Ram, GPU, Storage Temperature, Freq. Load, FPS, free space kind of data and don;t want/need to display Corsair 'i' PSU info or pump or AIO water temp data etc, well then I can tell Aida64 to stop monitoring the Corsair 'i' stuff and then there is no more conflict.

So, now that I have no need to disable iCUE after setting hardware profiles because the risk of conflict with Aida64 is gone and thus I can leave it running all the time,  and I don't need to base grouped fan profiles off of Temp Probe readings because I can indeed base a groups fan profile off of the actual on-die GPU temp sensor, well it confirms that I don't actually need a CoCoXT or CoPro. and a Commander Core will do....which means the obvious AIO choice for this build is an Elite Capellix H150i that only costs €13 more than a H150i RGB Pro XT but importantly already includes a Commander Core.

So my particular setup would be as follows:

3 of the CoCo RGB ports occupied by the AIO ML120 RGB cables

3 of the CoCo Fan ports populated by the AIO ML120 PWM cables. These grouped together in an 'AIO Group' and RPM's based off of AIO Water temp.

1 of the CoCO Fan ports populated with a PWM Y Splitter cable and the 2 ML120 intake Fans connected. These are the 'Intake' Group and RPM's based off of GPU Temp Sensor data and with 'Zero RPM mode activated' so they can be turned off when the GPU is not under load and even its own fans aren't spinning.

The Last 2 of the CoCo Fan ports both populated with PWM Y Splitter cables and the 4 Exhaust Fans connected. These are the 'Exhaust' Group and RPM's based off of AIO Water temp. Zero RPM mode not activated but running minimum RPM along with the AIO Rad fans until a sustained CPU load is applied and the water temp starts to rise, then the Exhaust fans increase RPM's in concert with the RAD fans.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...