iCUE Problems with Commander Pro

I am new in this Forum so I don't know if this Thread fits here.

 

I have an Obsidian 1000D case for almost a year and with it came a integrated Commander Pro. This Commander Pro is connected to the PSU and the USB Connector on the Motherboard. I Connected 13 Fans with Y-Connectors together so that 5 of 6 Fan slots are used.

 

iCUE had some Problems with it which are irrelevant now because I have a bigger Problem now.

 

As i was fixing a previous Problem iCUE detects the Case but if I click the symbol it normally would show the Fan-Speed Options and the LED settings.

Now it only shows the Device settings.

After updating the Firmware (which only goes to 99% and opens a second 1000D device) and aborting it, iCUE shows the Options for some Ligthing, but no Fan-Speed or Fan LED Options.

 

Should I change the Commander Pro from the Case?

First, that many fans with Y connectors is likely to give you problems. We typically don't recommend more than 9 or 10. We've seen a number of issues with users having 3 fans on a single port via splitter.

 

It sounds like your firmware may not have finished updating, tbh.

 

Are you running any other monitoring tools?

Oh and also now some fans won't spin at all. :mad:

Yesterday everything was fine. But when I came home today suddenly it didn't work anymore. If Y Splitters are not working then I can understand it but why aren't the LED's not working either? They have a different Connector as compared to the Power Connector of the Fans.

Oh and also now some fans won't spin at all. :mad:

You might want to try and reset your Commander Pro and reduce the number of fans connected to it (no more than 10 and don't use anything greater than a 2-way splitter on an individual fan port).

 

To perform the factory reset:

 

• Shut down ICUE.
  
• Locate and press the reset button inside the Commander Pro (you'll see a small hole in the Commander Pro's case) with a paper clip or something suitable. It's momentary so you have to keep it pushed it.
  
• While holding the reset button in, disconnect the SATA power to the Commander Pro for a few seconds and then plug it back in. The LED on the Commander Pro with flash. Release the reset button - it can be a struggle to do this step and it might help if you have a friend or grow a third hand to complete it. The Commander Pro should reboot.
  
• Start ICUE and let it detect the Commander Pro.
  
• If required; perform a firmware update (on the setting tab for the Commander Pro).
  

You might want to try and reset your Commander Pro and reduce the number of fans connected to it (no more than 10 and don't use anything greater than a 2-way splitter on an individual fan port).

 

To perform the factory reset:

 

• Shut down ICUE.
  
• Locate and press the reset button inside the Commander Pro (you'll see a small hole in the Commander Pro's case) with a paper clip or something suitable. It's momentary so you have to keep it pushed it.
  
• While holding the reset button in, disconnect the SATA power to the Commander Pro for a few seconds and then plug it back in. The LED on the Commander Pro with flash. Release the reset button - it can be a struggle to do this step and it might help if you have a friend or grow a third hand to complete it. The Commander Pro should reboot.
  
• Start ICUE and let it detect the Commander Pro.
  
• If required; perform a firmware update (on the setting tab for the Commander Pro).
  

 

Tomorrow I am getting a second Commander Pro. So hopefully this is going to solve the Problem. After work I am going to to test, if the reset will work today.

So after the reset the LED's should work again right?:confused:

It sounds like your firmware may not have finished updating, tbh.

 

The funny thing is: I have reinstalled iCUE once, then went to the device settings where the information for Obsidian 1000D was set to "Firmware v?".

 

I tried to update it -> it went to 99% and it stopped forever. Instead it opened Obsidian 1000D (1) with the newest firmware version.

 

I cancelled the old update as it stayed on 99% for 2 solid hours. And went to force update the firmware for Obsidian 1000D (1) as this was my only device after cancelling the old update.

This time the update went through without Problems and Obsidian 1000D (1) went to be Obsidian 1000D as it schould be with all the right settings. Only missing the Fan-Speed controll and the LED setting didn't work too.

So I tested the reset and it does not help. RGB doesn't work, no Fan Speed. No Options in general.

 

I also have RGB LED Hubs connected to the Commander Pro. If I try to use them alone they doesn't work neither.

 

I am going to ty to disassemble and assemble everything concerning the Fans.

Hopefully that will solve my problem:sigh!:

 

Edit:

I have tested the RGB LED Hubs. They do still work but I think the Commander Pro doesn't work as it should be. It still gives Power for the Fans, but I think the USB Connector is defective.

It is hard to describe in English because my mother tongue is german...

 

iCUE recognizes the Obsidian 1000D Commander Pro but not as it should be. If I connect the RGB LED Hubs to the Commander Pro I cannot customize the Fan LED in iCUE as some days ago.

Because of a previous answer I have now only 8 Fans connected, but only the 2., 3. and 4. Power Slots are giving Power to the Fans.

Should I replace the Commander Pro with a new one?

Edited February 13, 2020 by Qelmar

So I've tested if the Fans can't get Power anymore or if I have detroyed the Commander Pro with too many Fans. I think it's the latter. Because I have tried to connect the Fans with the integrated motherboard Fanslots and they are working fine. Now only 1 Slot does work on the Commander Pro.

 

But I have seen cases where a person connected less Fans to a Commander Pro, like 5 or 6, and the Commander Pro stopped working after half a year.

 

in my case I bought two knew Commander Pro which are arriving tomorrow and on Monday. Hopefully it will solve my problem.

So I've tested if the Fans can't get Power anymore or if I have detroyed the Commander Pro with too many Fans. I think it's the latter. Because I have tried to connect the Fans with the integrated motherboard Fanslots and they are working fine. Now only 1 Slot does work on the Commander Pro.

 

But I have seen cases where a person connected less Fans to a Commander Pro, like 5 or 6, and the Commander Pro stopped working after half a year.

 

in my case I bought two knew Commander Pro which are arriving tomorrow and on Monday. Hopefully it will solve my problem.

 

I had a CoPro that worked fine for many months with just 3 fans.

Then suddenly one port stopped to give power... it was replaced by Corsair.

Actually the new one is working with 7 LL120 RGB, this weekend I’m gonna plug the fan number 8.

 

Baio

So I've tested if the Fans can't get Power anymore or if I have detroyed the Commander Pro with too many Fans. I think it's the latter. Because I have tried to connect the Fans with the integrated motherboard Fanslots and they are working fine. Now only 1 Slot does work on the Commander Pro.

 

But I have seen cases where a person connected less Fans to a Commander Pro, like 5 or 6, and the Commander Pro stopped working after half a year.

 

in my case I bought two knew Commander Pro which are arriving tomorrow and on Monday. Hopefully it will solve my problem.

 

Yes, there are time when it's stopped working with fewer fans.

But there are many more times where folks overload the CoPro (as you have). When they stop working, it's not a surprise.

Our recommendation here to keep it to 10 or less and only 2 way splitters is based on seeing issues when folks go outside of those guidelines. So don't go outside the guidelines. And if you have issues after going outside those guidelines, that's why.

Yes, there are time when it's stopped working with fewer fans.

But there are many more times where folks overload the CoPro (as you have). When they stop working, it's not a surprise.

Our recommendation here to keep it to 10 or less and only 2 way splitters is based on seeing issues when folks go outside of those guidelines. So don't go outside the guidelines. And if you have issues after going outside those guidelines, that's why.

 

Yeah and because of your previous reply and some research on this topic I've decided to buy 2 new CoPros. 1 to replace my old CoPro and a second to daisychain it to the replacement CoPro.

Hopefully this will solve the Problem with Fan detection, Fan Speed settings and RGB settings in iCUE.:thinking:

You will also likely have to contact support to see about getting the firmware for one of your new CoPros because the 1000d has unique firmware for chassis lighting that you might restore functionality for.

 

-usna92

Good Day Guys.

I too have a Corsair 1000D with the pre-installed Custom(Specifically for 1000D-I Believe?) CommanderPro. I have 3x be quiet! Silent Wings 3 140mm BL071 Fans connected to ports 1-3 on the CommanderPro.

I installed iCue and then updated both the Obsidian D Lighting Node to 0.9.212 and Icue to 4.11.274. See below.

ICue picks up the Obsidian 1000D and HX1200 PSU. It does not show any commander pro. When I try go to the Obsidian 1000D option, then cooling, it shows 12V, 5V, 3.3V; no fan speed or adjustment.

 

I am completely confused. I cannot adjust fan speeds? I have the usb header connected to my motherboard. I also have the temperature sensors connected, which only seem to be picked up in HWInfo(Shows temperature, then zeros, then shows temp, then zeros, repeat)

I tried to reset the CommanderPro (hole below the Corsair Logo), but there seems to be no button. There is also a LED at the top, that is not on ever.

 

So the Fans are running full speed and temperature sensors reading, but no configuration in ICue?

 

Any advice.

 

PS-I have tried different USB headers in the motherboard with same results

Quit HWiNFO and then restart the CUE service. The two programs are fighting over access to the Commander. Before you launch HWiNFO the next time, go to settings (small launch window) -> Safety and uncheck the Corsair Link/Asetek Support. That should disable monitoring of the internal Corsair devices. You can do this manually as well.