c-attack

Expansion of device capability to 24 per hub. That may not benefit you. It does benefit others. Yes, the lighting wizard should be able to re-write a new configuration, but apparently it can’t. This is the critical reason why most people will need to clean install and remove the old configuration data. There also are multiple other fan specific associations like dashboard info, lighting, and control curves all of which use the same fan tagging data. As for why the Wizard can’t over-write, that’s likely a very technical reason and probably not something anyone is going to explain. Since they had a full page guide up for clean installing prior to the release of the new FW, it seems fairly certain it just wasn’t possible versus unintended consequence. No, export all your profiles prior to the clean install. Then reimport them. You only run into issues when you try and take a short cut and delete the config file without removing the all the other CUE associations.

They usually do mention a specific version because that is the one they tested. Asus and most other board vendors don't keep a running list. In this instance you can be pretty sure it will be the same version or an otherwise identical Hynix kit. That is the only bin for any 2x16 7200 kit right now. So while it is possible you might get ver 5.43.20 or ver 5.44.xx, that only means the RAM came from a later production run of Hynix IC. There is no reason to suspect it won't work unless you mix it with other Hynix from different versions.

I'd hold off on the reinstalling Windows for the moment unless you have another reason. From my end, the drop back to 4.33 and immediate detection resolution proves this is an issue with the new 5.14 release. I am not sure why, but it likely is tied to the implementation of the new Device Memory Mode. Now that the fans are detected, go to "8 series LED fans" and Pump Cap and use the yellow + to add a new lighting effect. That should turn the lights on. I don't know what to tell you on the motherboard support. I stopped trying to troubleshoot or use it a long time ago and prefer the board to stay off and Armory Crate uninstalled. Your MB is clearly detected, but if all it shows is the two 12v RGB headers, it is of no value to you. Might as well turn off the Asus plugin and use AC when needed to change motherboard lighting.

This should be straight forward. Go to "Assignments" in CUE for your K70. Yellow + to create a new one. Then select "keyboard" for the assignment type (purple). A keyboard should appear on the lower right side. There select W (green). Then in the larger image of your KB above click on Arrow Up (yellow). Repeat for each of the ASD and directional keys.

If it was HWinfo, you should see the difference pretty quickly. HWinfo can be run at the same time, as long you disable monitoring of the Commander Core, pump, and any other Corsair internal devices. RAM is usually OK. Also the portable version HWinfo is easy to use and only deploys its driver when launched, simplifying this kind of thing.

Color wave is one of several patterns that may have a different hardware lighting appearance compared to it's software appearance with full system resources. If you run hardware color wave across a series of LL, QL, or XX-Elite fans you will see one color wave per device. It waits until the wave is completed across the fan array before sending the next. This is contrary to software color wave where each fan has it's own color wave at the same time -- 4 fans, 4 waves moving in progression. Other devices with higher onboard memory like newer high end KBs or CUE Link QX/RX fans can run the software version of color wave and it looks the same between modes. Can you explain which hardware you see this on? *Apologies. I did not intend to link your post in the earlier quote. I grabbed the wrong one scrolling down.

A RGB port on the Commander XT. Those are the 6 fan RGB headers on the other side of the device. Don't use motherboard RGB ports. The connectors are not made for each other.

That was a typing error on my phone. I intended to write 5.14 -- that is the debut of this new User Interface. I saw one or two people mention some trouble with their Commander Core/XT lighting, but there were not any details to even categorize it. I also am not sure why this would affect those devices as changes to their main lighting setup were not part of the change. The big change is renaming "Hardware Mode" to Device Memory Mode and making it a separate operating state within the CUE app via the toggle switch. That put a lot of older devices that auto-saved data into a different category. A Commander Core/XT should not have trouble with this, but it's the only string left to pull on. I'll keep an eye for others. However, where I was leading to with this question is if you only set this up on 5.14 and never used it prior to that version, there may be a workaround if this problem is setup based only. 1) Uninstall CUE 5. You do not need to check the box to "erase all settings", but if you haven't put a lot of effort into your profiles yet, I would delete the settings so you can start over clean after. 2) Download and install CUE 4.33 from the Corsair website. https://www.corsair.com/us/en/s/downloads 3) Set-up your devices. You don't need to do much beyond checking everything works, including the Commander XT. Set a few lighting effects to verify. If it works here, we have removed hardware or circuit types of defects and it almost surely means this is a CUE 5.14 error. 4) Go back to the CUE website and download install CUE 5. It will pick up the CUE 4 configuration and you should load into CUE 5 already set up for 4 fans and pump. I can't guarantee this will work, but it should help determine whether this is software or hardware. If it doesn't work on CUE 4, then there likely is some very unusual issue. No meaningful differences for CUE between Win 10 and 11. Anything like that would cause problems on the installation, registry, or general app behavior, not very specific device issues like this. Don't spend too much time chasing the motherboard lighting. Motherboard 5v ARGB headers are not controllable through CUE. It is a competing pathway for gear not made by Corsair. 12v RGB headers are, but not too many things using that anymore. Motherboard IO shield lighting may or may not be controllable. Some of the newer boards with complex Polymo lighting (or whatever Asus is calling it) are complex addressable arrays and not controllable through CUE. Also, when testing devices or lighting make sure you use "Lighting Effects" from the main device tab in CUE. Don't use Murals for testing. It adds a layer of complexity for testing and not all devices are Murals capable.

I don’t know what to suggest at this point. The Commander XT has independent rgb channels, unlike the older series circuit controllers. If one of the fans were bad on the rgb side, only that fan would be affected. I would not expect any controller to have a simultaneous 6 port fail without some type total power delivery problem affecting everything. These H100x Elite RGB models have been tricky with their rgb integration into CUE, but nothing tricky about the SP-Elite fans. You connect it to any RGB port and it should be auto-detected as 8 LED fan. I am not sure where that leaves you. It might be time to contact Corsair Support, but I’m not confident they will come to a resolution either. However, I am curious about the new CUE version. Did you update to CUE 5.14 with this new UI before you hooked up the Commander XT to the fans and pump?

Will it let you set up manually? It’s “8 LED fan series” for the SP-Elite. For the pump it needs 16 LEDs. Not sure if it will offer H100x as a choice but Hydro X -> XC7 will generate 16 LEDs too.

Don’t let the Commander Pro run from its presets. They are not really functional and use cpu temp on a curve designed for water temp. This keeps the fans at 1500 rpm all the time. You definitely need to use a custom curve.

I am using a Commander Pro for the same purpose and have not seen any deviant behavior on the current release, although there have been lingering control issues elsewhere the last several months. 25-27C is a normal idle coolant values, but be aware your maximum is going to be somewhere in the 35-40C range, so that curve may not be what you want. I can’t see the sensor choice under the graph, but the yellow line indicates the current value is 50-something and thus the fan speed is higher. When you create a new fan curve on the Commander Pro it always defaults to cpu temp. You need to get off that as it’s is not an appropriate or necessary control variable for water cooling. Click the drop down menu under “Sensor” and find Commander Pro Temp 1. It’s probably all the way at the bottom. Then in the lower right corner of the graph are 4 shape tools. Click the one in the left. This will give you a decent starting point for a water cooling curve. there are no automatic rules for this. Everyone’s normal idle temp will be based mostly on room and case temp. This also means you will see shifts based on condition changes. However, I am going to assume you are running 2x360mm rads and both cpu and gpu in the loop, thus a +10C increase during long term gaming (highest wattage) is probably about right.

You still must set CPU fan to 100% or Full Speed (Q-Fan) for the H80i GT as that is a power supplying connection unlike most other models. It will work with the current CUE software, although I am concerned the Device Memory Mode is going to cause problems on these older devices. My recommendation is to use the CUE 4 download (prior generation) to manage these older devices when there is no other Corsair hardware present. You also can skip cue entirely by putting the pump power on W_ Pump and the two fans on cpu/opt. Then in the BIOS set the fan delays to maximum for cpu fan (8.5 seconds). They will run cpu temp and I spend a lot of time explaining why that’s inefficient, but in these circumstances it’s a viable means of control.

Commander Pro Temp # is the data coming from the 4 temp sensors on the end of the device. A connected 10K thermistor for air temp or specialized one for water temp in custom loops is the normal purpose. What is connected to your Commander Pro temp register(s)?

W_Pump or AIO_Pump have no special properties on most Asus boards aside from a higher current capacity on premium boards. There are a CHAssis fan header preset to 100%. Most of the time this is wasted as nearly all AIO units these days use a SATA connector for power. The H80i GT was one of the last units not to do that and does take power directly from the motherboard. That 3 pin connector needs to connect to either AIO Fan, W Pump, or the CPU Fan connector set to “Full Speed” or 100% in the bios. If you use W pump or AIO pump, then you must disable the cpu boot protection system. Go to the Advanced BIOS (F7) -> Monitoring -> CPU fan RPM. Hit enter and then change it to Ignore to disable the boot protection. No matter which MB fan port you choose, that 3 pin must be connected for power. It will slide onto any 4 pin header in the correct orientation. The motherboard has an auto-detect for DC vs PWM or you can manually set it in the bios. The AIO should always be set to PWM and is meant to use a full 12v with speed adjustments handled by the internal controller.