The native sensors for the Commander Pro are the temp probes on that specific Commander Pro. C-Pro 2 cannot use C-Pro 1's temp sensors as a native source. So you should be getting either full speed max from C-Pro 2 on boot or you do have at least one temp probe from C-Pro 2 in place and if so, is that the control source for those fans? Here’s how: Make sure iCUE is closed. You can press Ctrl+Shift+Esc to bring up Task Manager to verify. On your keyboard, press Win+R (the Windows logo key and the R key). In the popped up Run box, type or paste %appdata% and click OK. Cut the Corsair folder and paste it on your Desktop as a backup. In this video I show you how to run a Commander Pro without the iCue software. Many fan and RGB controllers require buggy and bloated software like Corsair i Commander Core (XT/ST) - HWiNFO64 HWiNFO64 added monitoring support for the Commander Core line in version 7.42 which has made it incompatible with SignalRGB. When this monitoring is enabled HWiNFO64 will put the Commander Core back into hardware mode after each update which stops SignalRGB from being able to control the RGB OR fan speeds of Commander pro was detected and no issues. But even connected to the commander pro USB header, the node core is still not being detected. I think I will be contacting Corsair to send me a new node core as you cannot just buy them individually, but I wanted to see if anyone has some advice for me. Commander Pro USB hub not working; Random disconnect sound; Random disconnect and reconnect of Commander Pro; H100i freakout when reading sensor data with HWInfo64 The issue that is really bothering me is the random disconnect and reconnect of the Commander Pro. During gameplay this results in the entire system hanging for a second. My system CPAQf7. 17 hours ago, DevBiker said: 1) Yes, you can use either your motherboard or the Commander Core XT. Either will work. It's standard PWM to control the pump speeds. 2) The temp sensor would need to have a temp sensor header on your motherboard. It's a standard temp sensor so if your motherboard has one, it'll work. In order to keep it on one device you would need a RGB lighting hub (effectively a mini lighting mode core) to supply the 5v for the fan lighting. They should be about $10 USD but are very hard to find at the moment. The other option is as you stated, Commander Pro for speed, lighting mode core for RGB. Edited December 27, 2021 by c-attack. LL Fans/Commander Pro Not Working Correctly. I have (6) LL fans connected to an RGB LED/Fan hub that is connected to a Commander Pro. Fan operation is fine. Issue is the LED function on fans 4-6. No matter what profile, sometimes fans 4 through 6 will not show the correct pattern. It is like they are not getting all the information. I have my brand new H150i Pro RGB XT and have just installed it, it is working (the temps are slightly higher than I expected but I'm hoping with some help I can control the fans) I have 9 fans in my O11 Dynamic XL case, I run 2 lighting node cores (the ones that came with my 3 packs of QL120s) to control the RGB on all 9 (3 are mounted on the First things i would try would be reseating the commander pros usb cable to the motherboard, check for firmware updates for commander Pro, try alternate usb cable if you have one. Check all sata power connectors and maybe try different combos of which devices are powered by what sata power wire. Reply. king_harold1 •. The 5 fans are plugged into Commander Pro, ports 1-5 in order, no open spaces between. Also connected is a USB slot connected to the RGB controller as well as 1 LED strip connection. The connection from the Commander Pro to the motherboard is on a USB hub, also connected to power via SATA.

corsair commander pro not working