Jump to content
Corsair Community

H115i Elite Capellix 280MM Liquid Cooling problem detecting and controlling in iCue... something up with CoCore + CoPro? Fan detection and control works, and pump is powered including LEDs stuck in default state.


Recommended Posts

I have the following build:

  • CPU: AMD RYZEN 9 5950X 3.40 GHz (4.90 GHz Max Boost), 16-Core 32-Thread
  • GPU: EVGA GeForce RTX 3080 Ti FTW3 Ultra Gaming 12GB
  • Motherboard: Gigabyte X570 AORUS Master ATX Motherboard (WIFI)
  • RAM: Corsair Vengeance RGB 32GB DDR4 3600MHz (4x8GB)
  • SSD: 2TB Intel 660P M.2 NVMe SSD
  • CPU Cooler: CORSAIR Hydro Series H115i Elite Capellix 280MM Liquid Cooling
  • PSU: CORSAIR RM850x 80 Plus Gold PSU
  • Case: CORSAIR Obsidian Series 500D RGB SE Mid Tower Case, LL120 Fans, Commander PRO

My problem right now is with the  H115i Liquid Cooling pump RGB. It's stuck in a default rainbow state and I want to control it to match it with my fan lighting scheme, which is successfully detected and controllable by Commander Pro in iCue.

The confusion I see seems to involve Commander Pro + Commander Core. It seems I have the pump RGB powered into the Core unit. The Core has a loose USB coming out of the other end, which from my reading, should be put into the motherboard OR Commander Pro. It cannot reach the motherboard's internal USB2.0 ports. So I had it in one of the Commander Pro's USB ports. But whether it is plugged into the CoPro USB port or left completely disconnected, it does not register at all in iCue, and thus cannot be controlled. I cannot control the pump, nor the LEDs on it.

The pump itself is working, and the LEDs do work in their default rainbow state. But I would like to be able to do what is advertised, and change the LED theme. It would be nice to have some control over the pump itself in iCue.

I have poured over many troubleshooting threads and the next thing I will try is taking that loose CoCore USB which does not reach the motherboard, and does nothing when plugged into CoPro, and buying a USB extension cable for it. The options are slim here. Best I can find is a 9-pin male-to-female USB2.0 for internal motherboard connection. Not sure if this will work at all, but have no other ideas on what to do.

iCue is updated fully and works well with the 6-fan RGB control and speed control. It just lacks any communication whatsoever with the pump itself.

 

Any obvious ideas that I'm missing? Thank you

Link to comment
Share on other sites

if in the latest version of icue software there are problems with the H100i , namely that it is no longer shown , I have a solution = on your pump there is a CPU Cooler Pump Speed USB cable USB Interface , take it out and back, what I did is open icue, put the cable out and back and suddenly I saw my cpu cooler at device

Link to comment
Share on other sites

2 hours ago, sammmm said:

The Core has a loose USB coming out of the other end, which from my reading, should be put into the motherboard OR Commander Pro.

No USB connection, no communication between the device and software.  You cannot control it without the software.

 

You may have issues piggy backing other devices into the Commander Pro USB passthrough ports on recent AMD motherboards.  They don't handle multiple connections sharing the same line very well.  Most AMD users needs a SATA powered USB hub to handle multiple devices.  

 

Do you need the Commander Pro?  From your description and case it seems unlikely you have more than 6 fans.  The Commander Core can do both PWM and RGB control for 6.  Is the Commander Pro on lighting channel duties for other devices (strips, more fans, etc.)?

Link to comment
Share on other sites

I think you're right c-attack, I could do this all without CoPro. I will consider that but I do want to try one thing first. I don't have my machine in front of me right now, but off memory I was thinking of trying this in my current situation:

Taking that free USB2.0 coming out of the Commander Core, and extending that so it can reach the motherboard USB2.0 port, without doing anything to the CommanderPro, which as you said does not work as a passthrough for the Commander Core if it is already itself plugged into a motherboard USB2.0.

So basically I'd have the CoPro feeding a USB into the motherboard, and then the CoCore would also feed its own USB directly into the motherboard. I do have the extra motherboard USB2.0 available, it's just that with the pitifully short length of the USB line coming out of the CoCore, it doesn't quite reach far enough from where I have the CoCore to the motherboard.

Is that potentially workable, or am I way off still? Another idea might be to feed the loose CoCore USB into a SATA-powered USB hub like you suggested, which then would feed the hub's USB into the motherboard. Not sure what the effective difference there is besides gaining even more free USB ports with the hub besides the one that would be used by CoCore, which is a bonus.

 

Link to comment
Share on other sites

It seems like the best course of action for the moment is to get a USB 2 extension (internal).  If I understand correctly, you still need it with or without the Commander Core because it is fixed in a location too far to reach.  Any generic USB extension should work and I have used one from time to time.  

 

If all of your fans are on the Commander Pro for speed control, then they may not be using the native coolant temp data from the Commander Core.  You can assign that to the Commander Pro, but it must get the data from the Commander Core -> MB -> software -> Commander Pro chain and thus is will only work when the software is running.  Since the Commander Core is necessary to provide power to the pump, it has to stay.  From what you've described, it alone can handle all your fans for speed and RGB.  However, be aware that when you move the fans over to the Commander Core, you will need to re-create your lighting patterns in any existing profile.  Those are device specific in the profile data.  Right now the Commander Core is a blank.  

Link to comment
Share on other sites

Thanks again, this did the trick. It is unfortunate that simply connecting the Core's USB to the Commander Pro does not work (apparently an AMD problem as you mentioned) but having both directly going into the motherboard works now. 

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...