Ca1ibos

Thanks folks. Yeah, I'll probably try and sell the spare AIO instead. Not worth the risk or potential modding headaches.

Bought a load of gear for a build last year but 'life' got in the way and the system remains un-built. Would have been able to buy the parts a lot cheaper at todays prices but thats water under the bridge now and Visa card already cleared of the expense. Learnt my lesson not to get ahead of myself and order parts before I am sure I'll have the time to build and use the system. Anywho.... Should be able to put the system together shortly. 5900X on Strix X570, 4x8gb Corsair Vengeance RGB 3600CL18, Strix RTX3090, Corsair Elite Cappellix 360mm AIO with Elite LCD add-on, Commander Core, Commander Pro. I have a 360mm H150i RGB Pro XT AIO I bought for my brothers build that it turns out I can't use on his system. I happened to come across a post on r/pcmods on reddit where someone modded their Palit 3080 with a spare eVGA AIO. It fit under the Fan shroud with the Heatsink removed. They added small heatsinks to the memory etc. No mention of software conflicts but they are probably using a different manufacturers AIO. I'm not stupid enough to assume that this mod is even physically possible with a Strix RTX3090 and a Corsair H150i Pro XT, but before I even go to the effort of dismantling the card and/or AIO Pump Head, I'd like to know if its even possible from a software standpoint. ie. Will iCUE be able to run 2 Corsair AIO's in the same system concurrently or will their be conflicts. https://old.reddit.com/r/pcmods/comments/wnm3ji/i_just_aiod_my_grafics_card_installed_evga_hybrid/

Any idea when this will be available on the EU Website. In fact, does anyone at Corsair have any idea when ANYTHING will be available on the Corsair EU website?? There is literally NOTHING in stock on that website!! Are you closing the EU Web-shop down?? Ironically, I actually don't want that kit for the LGA1700 brackets, not that anyone with a new Alderlake system needs it anyway (They actually just need the shorter Stand-0ff Kit). No I actually want this kit for the new 4 Point AM4 retention brackets. Ideally, I'd order 2 if they were available now and use one on the 5900x based system with a H150i RGB Pro XT AIO for a build for my brother, but that one I'll 'settle' for the supplied 2 point AM4 bracket if I have to build and can wait no longer for the new 4 point brackets. However, I really don't want to build my 6900x 3D V-Cache based system in January/February with my Elite Capellix H150i and Elite LCD Upgrade kit using the 2 point brackets and absolutely want to wait till I have the new 4 point AM4 brackets for that. The thick unyielding cable loom from the Elite LCD exits the module straight into the ThumbNut of the 2 point AM4 bracket putting undue pressure and torque on it which is probably why so many people have issues with Elite LCD modules losing connection and throwing up errors and red triangles on the Display. I also wouldn't be surprised if the pump noise many Elite Capellix H150i units suffer is due to resonances/vibrations allowed to propagate to the point of audibility due to the 2 point AM4 mounting system allowing poorly lapped CPU Heatspreaders and Cooler baseplates from effectively rocking by fractions of a millimeter with the pump vibrations leading to the buzzing noise. The 4 point AM4 brackets should rule that possible cause for the pump noise out. I can wait for the bracket till January/February as the 3D V-Cache 6900x won't be out till than at the earliest anyway but honestly, how long does it take for Corsair to restock some non electronic parts these days!! Its not the 'Great Covid Silicon shortage' thats for sure. Just how slow is the proverbial 'Slow Boat from China' to Europe these days!!

Have to say, I’ve had nothing but good experiences from their European Webstore. Perhaps I’ve been lucky and always happened to order items with plenty of stock and before the Christmas courier rush started to begin its ramp up.

Time to get a vertical GPU mount I think. Show off your GPU better and your AIO tubes can run in a straight line behind the GPU to the bottom of the rad on the front.

I might take you up on that kind offer some day if I run into any issues I can't resolve myself.

Sounds to me that these 'Small Little Yellow Envelopes' should have been sent via regular Postal services who are setup to automatically handle and sort.....small little envelopes. If I had to guess, the delayed 'Small Little Yellow Envelopes' sent via DHL have fallen between the rollers in the Netherlands DHL Parcel centres automated sorting/moving conveyors and are are on the floor under the machines!!

I've got 3 sensor panels planned for 3 builds all running iCUE.. Its frustrating that the AIDA64 forums are a deadzone. The only active thread related to sensor panels is the Layout thread but it seems literally every Sensor panel user couldn't be bothered helping out new users. I am hoping I'll be able to figure everything out myself eventually but certainly don't expect any help from the AIDA64 forums or its users. What I have read on the subject is that nearly all conflicts between AIDA64 and iCUE are resolved by de-selecting all Corsair devices in the AIDA64 settings. ie. Anything sensor that both iCUE and AIDA64 are trying to connect to at the same time. This is hopefully fine for me as long as I can access RAM data even if its corsair Ram whilst not affecting iCUE's ability to control the RGB of the RAM. You might be out of luck if Corsair refuse to reverse whatever change they made to iCUE 4.x because if sounds like you want AIDA64 Sensor panel to access an actual Corsair Water Temp sensor. In my case I don't care and I don't think iCUE cares if RAM data is deselected in iCUE but selected for monitoring in AIDA64, but in your case, you can't deselect Water temp monitoring in iCUE because iCUE needs it for its fan curve control of your radiator fans and pump speed. Post back here if you find a solution!

Already owned a 5900X/Strix-F X570/4x8GB 3600C18 Corsair Vengeance RGB Pro/RTX3090. Got caught up in the Alderlake Hype and rather than buying my brother a 12600K and mid/low (if you can call them that) Z690 board as planned I decided to order myself a 12900K/Asus Maximus Hero/and the DDR5 we've just been talking about. Actually ordered the 5200C38 from the same vendor as the CPU and board but found the C36 FE kit on the Corsair site for about €40 cheaper so promptly cancelled the other kit from the Vendor. However, because of the Z690 Launch day stock issues I was able to read and watch reviews before my order had shipped and had time to talk some sense into myself! LOL. The performance jump and lead over Ryzen 9 was just not worth the massive platform change cost to me. Had to keep my promise to my brother and give him my 5900x though. I'll pick myself up a 6900x 3D V-Cache early next year and handicap my RTX3090 with my old 6700K/Z170-A in the mean-time. LOL. So the cost to me now is a more suitable Strix mITX B550 board and 2x16GB 3600C18 Vengeance LPX for the brothers build and the 6900X V-Cache. Presume prices will be similar to the 5900X so I expect to have spent about €800 which is about €700 cheaper than what the €1500 switch to Alderlake was going to cost me. Once I get the 6900x out comes the 6700K/Z170-A and back in will go my Strix-F X570/4x8GB 3600C18 Corsair Vengeance RGB Pro to join my RTX3090 in my O11 Dynamic XL Case again.

........or for people who want that nice new more secure and easy to mount 4 mounting Point AM4 bracket......with no centre position Thumbnuts that strains our Elite LCD module cables...

Arrrghhh. Theres the 'Gotcha' I was kinda expecting. RIght so. I'll forget about a Commander device for the Media Server for now and go back to the idea of the Fan PWM's into mobo headers and the QL120 RGB cables -> Lighting Node Core-> USB Header to USB A Adapters -> Power USB Hub -> Main Rig (I'm right about the Lighting Node Core needed for the QL120's. I think I mis-remembered earlier when I said RGB Hub needed and bought. That might have been back when I was going to use RGB ML120's for the Media Server but I actually think I switched my plan to QL120's before I got around to buying an RGB hub for the RGB ML120's.

Cool!! So effectively the only thing I talked about that you haven't tested is plugging your spare Elite Capellix LED Module into the second Commander Core that had no pump connected to see what happens!! Yeah, I have already bought the required powered USB hub and USB Header to Type A converter cables. IIRC my original plan was to run the Media Server fans PWM's off the motherboard headers and the RGB of the fans into an RGB Hub and a Lighting Node Pro which I already have on hand too. It was the idea to re-use the Spare Capellix LED Module inset into the front of my Media Server case that brought a Commander Core XT for the Media Server into the frame. My main concern is that when iCUE on the main Rig detects the Elite LCD H150i AIO via the CoCo in the main Rig....BUT ALSO.... detects the LED Module via the CoCoXT in the Media Server, it may think there are two EC H150i's AIO's connected to the system which may cause conflicts or issues.

I was a very lucky boy and got probably the last 2x16GB 5200/CL36 Dominator Platinum RGB FE Kit from Corsair Europe. (Disappeared off the site straight after) Ended up cancelling my Alderlake order but my DDR5 had already shipped and been delivered to me in Wicklow in Ireland. There was a very lucky boy in Donegal Ireland who got probably the last available 2x16GB 5200/CL36 Dominator Platinum RGB FE Kit..... Yeah, another Lucky Sod dug deep into Google search results looking for any Corsair Dom Plat RGB DDR5 and found ME. DM'd me on Reddit and we did a deal. Sent him the Ram from the other side of the country and he had it in his hands less than 24 hours later. Very happy chappy he was! Unlike so many other unfortunate Alderlake buyers he certainly won't be waiting on Ram and can build his system straight away. Luck of the Irish I guess!! LOL.

Asked in Zotty's RGB Master thread but he nor any of the other iCUE experts replied. Hoping for more visibility here out in the open so to speak. LOL. I'll try not to create my usual context providing but invariably TLDR inducing wall of text this time. Main Rig with an Elite Capellix H150i with Elite LCD Upgrade Kit with its Commander Core. Commander Pro also in this rig for the rest of the 10x QL120 fans and strips in this rig. Comprehensive Desk LS100 and RGB Pro Strip setup run off a seperate PSU (On/Off Alexa etc) not unlike Zotty's setup. The Lighting Node Pro's for the Desk strips going back to a USB hub which is plugged into this Rig. All controlled by iCUE on this main rig. In my Media Server on the other side of the long desk, Can I run 6x QL120's and some strips off of a Commander Core XT.....AND.....the now spare LED Module of the Elite Capellix H150i, have the Commander Core XT Sata Powered by the Media Server PSU, have a Hardware/Default Fan Profile set based off the two XT Temp Probes......BUT......have this Commander Core XT's USB Header cable.....NOT.....plugged into the Media servers Motherboard.....BUT INSTEAD..... be plugged into the main Rigs motherboard Header. The reason is that I only want the 24/7's Media Servers RGB LED's lit up when the Main rig is switched ON. I don't need iCUE on the Media Server once I've set the fan profiles and Hardware Lighting Profile to OFF. When the Main Rig is switched ON I want the iCUE install on the main rig to control all the RGB in the Media Server Case (as well as its own Fans and Strips and the Desk RGB Strips) Will the iCUE install on the main rig be able to handle that without crashing or conflicts? Will it work but only if I don't add the extra complication of the Spare EC H150i RGB LED Module freed up by my Elite LCD purchase. My fear is that iCUE on the main rig detects the main rigs CoCo and its CoPro but because I'll have wired the CoCoXT in the media server back over to the main rig too, the main rig iCUE install will also detect the CoCoXT and its connected EC LED Module. Will the main rig iCUE think I actually have 2 Elite Capellix AIO installs on this main rig and crap out on me? Help me iCUE Jedi Masters Zotty, C-Attack and Dev-Biker. You're my only hope!! LOL.

I assume you meant to say Com Pro rather than Com Core. A Commander Core doesn't have any temp probes does it? I think I have it straight in my head now. I was actually only asking about Temp Probes because I also intend to use an Aida64 Sensor panel on this build and I heard iCUE and Aida64 conflict and don't play nice. Turns out the conflicts are caused by them both trying to use the same instance of the CPUID protocol and its only for the Corsair 'i' products. Given I don't want to display data about my AIO water temps or a Corsair 'i' PSU or Commander devices etc on my sensor panel, well apparently I can de-select them from monitoring in the Aida64 preferences and the conflicts are erased and iCUE and Aida64 co-exist peacefully. from then on. Certainly don't need to worry about the CPU overhead of iCUE running with a 5900X with 12c16t and turning down the iCUE Hardware monitoring Polling rate should deal with any stutters if they occur. So I actually am happy to leave iCUE always running straight from startup and thus don't need to base fan profiles off of CoCoXT or CoPRO temp probes in order to maintain temp fan control in Hardware mode with iCUE off. Instead I can base my group profiles off of my AIO Water temp for my Radiator fans and 4 exhaust fans and GPU on-die Temp sensor for my 2 case Intake fans. This means I can choose the Elite Capellix H150i as my AIO instead of the other option which was the €13 cheaper H150i RGB Pro XT, because the EC H150i already comes with a CoCo so I don't have to buy one.

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.

Can a CoCoXT or CoPRO have connected fans in separate groups controlled by different Temp Probes? So Say I had 2 case intake fans and 4 case exhaust fans connected to a CoCoXT or a CoPRO, could I have the two Case intake fans feeding my GPU cool air be controlled by the Temp Probe I would place on the GPU heatsink independently of the 4 exhaust fans controlled by the Temp Probe I would place on the 'Hot' side of my 360mm Radiator? Ideally the Case fans feeding the GPU Cool air would be stopped and only come on when the GPU heated up and its own fans started spinning under load. Similarily, the exhaust fans would be low RPM until such time as there was load on the CPU and the Radiator started dumping more hot air into the case whereupon the case exhaust fans would increase RPM's.

Same.

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

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

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

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)

Forum is acting up! …..or will the main rigs Commander Pro and Commander Core for my Eilte Cappelix in the main rig, conflict with the Core XT connected via usb extension from over in the media server? In other words, can one in effect run a Commander Pro, a Commander Core and a Commander Core XT all from a single instance of iCUE running on the main rig. (Remember though, the Core XT is actually getting 24/7 power via sata over on the Server.)

Sorry, forum will no longer let me edit my post. if I don’t connect the Media Servers Commander Core XT to the servers motherboard USB header at all but connect it to the servers Sata power, can a default profile be set for the Core XT running in the server that still allows temp based fan control by the XT via its temp sensors and a default RGB Fan and strip profile including for the Capellix LED module connected to it…… …..but with the Core XT’s USB header cable actually connected to the main gaming rig on the other side of the desk via a header to usb A convertor and usb A extension cable, iCUE on the main rig see’s it and can take control of all the RGB in the Servers Core XT when the main rig is on?

My original master plan was similar to Zottys’ with a comprehensive Desk and two PC RGB FAn/Strip setup, with all the strips on a dedicated PSU on an Alexa Plug controlled by an Alexa Show 5. A USB cable run from the Showcase Media Server rig back to the main gaming rig with iCUE. A default RGB profile configured but when my main rig is on, iCUE in that rig would take over control of all the RGB. The spark of an idea that might change part of that plan was really wanting to use the now spare Elite Cappellix LED module freed up with the purchase of an Elite LCD upgrade kit for the H150i EC in my main rig. It would make a cool LED Corsair Logo mounted to the front of my Media Server case. I Realised I’d need a Commander Core for that, which then made me think I could simplify the fan control and RGB fans and strips and assosciated lighting cores and Lighting pro’s and cables back to the main rig etc, if I actually bought a Commander Core XT for the Media Server. That could handle the Case and A500 air cooler fan control and their RGB via the temp probes and fan and fan rgb ports of the XT, the strips on the lighting channel and….yes….the spare Capellix LED module. So far so good….however I could still like iCUE on the main rig to take control of all the RGB in the media server case especially with a music visuallizer. So I guess the question is whether I can have an independently running iCUE software install and Commander Core XT on the 24/7 Media Server, but with a single USB connection back to the main rig which when on, the iCUE install of the main rig could take over control of the Media Servers Commander Core XT RGB?