RedRover

Holy cow, you guys need to advertise this more!!! So many more uses than just RGB bling. I'm turning my previous PC with an ax1500i into an all-flash DAS/NAS for my new workstation and was about to plug in 48 SSDs when I finally thought to double check the Amps available on the 5V rail. Glad I did, because the PSU "only" has 30A on the 5V; I need almost 100A, 475 watts to be exact. Add in two more SSDs for boot drives, plus 5 HDDs that need 5V for startup, that's a lot of 5V. I've been googling for days trying to figure out what kind of PSU can support that much power on the 5V, but they're all heavily weighted to 12V, even in big (and very expensive) redundant server PSUs. These little guys are a life saver. Each of my 3 backplanes have 4 SATA power connectors, supporting 16 SSDs a piece, so I'll just put two of these on each backplane and I'll still have plenty of headroom on the ax1500i, and plenty left on each load balance unit. Put the remaining SSDs and HDDs on the PSU and all will be good. And you're including SATA power cables with the caps, so I can trim these down to a single SATA connector each and make them the perfect length. It's a win-win-win. You guys need to get your marketing guys to look into the DIY homelab and NAS market, these things would sell like crazy.

That is a really neat trick. Seems to me the iCUE team could easily implement some kind of export/import library function since this trick works. They could expand on this in a number of places and dramatically improve it's usability. Thanks for the tip. Red

Well, that controller is in another PC, which is still in service. Taking it apart would take too long and would be pretty disruptive. Too bad I can't export the library. Actually, I'm surprised iCUE doesn't have the ability to import/export via a library. It would make so many things easier.

I have older profiles I want to use on my new PC with QX fans. The previous system had QL fans. I believe they are identical as far as RGB layout goes. Is there a way to pull out, or simply change the xml to make the QL RGB settings a QX instead? Thanks, Red

One of the things I like to do is see what other people have created in iCUE and try them out on my own PC. Unfortunately, there still does not seem to be a way to merge profile information. Sure, I can download a profile and import all those awesome lighting effects somebody worked really hard on, but then I have to recreate a pump curve, two fan curves, keyboard and mouse assignments, Nexus profiles, and so on. It's quite a lot of work. Conversely, some of those lighting effect creations are pretty awesome, and could similarly take a very long time to replicate. But wait, import and export functions already exist and will let us choose what to import/export. Would it be possible to include a merge function. If the same functions/curve names/etc exist, just ask which profile wins. This could turn an hour or many hours of work into something that takes a minute or two. Even if we still need to tweak a few things, it would save a tremendous amount of time and make iCUE even more awesome.

Also, please give the Nexus some love. That thing is great and it really deserves some attention.

Just built a new system using the all new iCUE Link Hub ecosystem, and it is very cool. A few suggestions based on the issues I've identified so far. I'm sure some have already been mentioned, but you get to see them again :). Multiple Link Hubs: Due to some ongoing overcurrent alarm issues, I was not able to use a single hub. I know this is being worked on, but for now this caused a few issues I believe can be fixed by the software team. My physical set-up is as follows: Hub 1 Port 1: DX5 w/ LCD screen Hub 1 Port 2: 3 - QX140 fans Hub 2 Port 1: 3 - QX140 fans, XG7 GPU block via Link Hub adapter cable Hub 2 Port 2: 3 - QX140 fans, 1 - QX120 fan Issue 1: When setting up fans for Hydro X profile (which badly needs review), only the 3 fans on the same hub are included. Possible Solution: The fans should be global, seen by devices regardless of the Link Hub they are plugged in to. Issue 2: Alarms are only available for sensors on the same hub. Possible Solution: Similar to issue 1, sensors should be global, not just the sensors attached to that hub. Issue 3: Effects run simultaneously on hub devices "per slot", as setup in the Link System Hub's Lighting Setup screen. Moving the devices around on the Lighting Setup screen will change which devices mirror each other. e.g. Visor effect is supposed to run through each device, one at a time, and in order. But devices on each hub will mirror each other simultaneously instead. This is true for all Linked Lighting effects but is most visible in effects light Visor or Type Lighting. e.g. Device 1 on Hub1 will display the same effect as Device 1 on Hub 2. (This isn't exactly right, I've tried changing the device order, but I'm not sure what the logic is as to which ones get mirrored. It might be the color marker that determines which ones are mirrored or some other random thing.) Possible Solution: Also, like issue 1, the fans/devices should be global, and given unique identifiers. Issue 4: Because of the lack of unique names, identifying the correct component in the Mural setup screen can be difficult, or at least a minor annoyance. I also have a Lighting Node Pro and the light strips still get duplicate names, just as they did in my last setup several years ago. This issue has carried over to the new iCUE Link ecosystem; when you have multiple hubs, like components end up with duplicate names. Possible Solution: Same as above, make the devices global and assign unique identifiers. Also, let us rename the devices and enforce uniqueness, same as we can already do with sensors and fan/pump curves. It would be great if we could rename fans/light strips/etc. based on their location in the case, or if I wanted to name them after the players on my favorite sports team, or just Bob1 Bob2 Bob3, whatever. Fan Setup I know this has been requested many times over the past few years, but fan orientation is still a missing feature. The lighting setup screen, and the mural setup screen assume the fans are facing toward the user, in a push/exhaust configuration. This is obviously not the only way fans are installed. The side fans in 5000 and 7000 series cases are commonly installed with the back of the fan facing the user, in a pull/intake configuration, especially in custom water cooling setups. Nobody wants to hide those fancy, expensive fans behind a radiator. While it's possible toget either the vertical or horizontal setup correct for effects or murals, you can never get both if there is no mirror/flip/orientation option; lights on the fan/device will always be backwards in some way. Then when you change the effect it will be off for something else. Solution: Provide a mirror/flip/orientation option. Please, please, please. Please? Custom ARGB Light Strips Everyone knows your light strips use the same format as every other major vendor, you just don't use the same connector. Adapters to use non-Corsair light strips are available at every major retailer and webstore. Please let us officially setup non-corsair 5V ARGB light strips that adhere to the same standard, ASUS, MSI, ASROCK, GigaByte, and just about every other 5V ARGB light strip available. It seems to me, all you need to do is let the user input how many lights/pixels are on each strip, and bam, it would work. I know it's not that hard to hack it by either choosing the RGB LED Strip with 10 lights per strip, or the LS100's with various light counts per length. We can get pretty close that way. But really, if you just let the end user choose the number of lights per strip it would make the iCUE ecosystem even more enticing to people. You could cap it at whatever power level you need; per channel it's currently 60 for RGB LED Strip and138 for LS100, and I know the Lighting Node Pro will do 138 per channel if you ask it to. (not sure how long it would last, though) Solution: Expose the hard-coded light count as a user defined variable. Thank you for continuing to improve iCUE and the ecosystems involved. I hope you will consider these suggestions.

I know this has been posted before, but I didn't see anything recently, and with a new version (4 is new to me), I thought I'd check again. I simply want to copy a portion of a profile from one to another. Their is the import and export option, and they both let you choose what part to export/import, but the import always seems to add a whole new profile. I just want to copy the key assignments, or the lighting profile, or the cooling profile from one existing profile into another existing profile. It's a real hassle when I start up a new profile and get the key and cooling profile done, then decide, oh yeah, I want some cool lighting effects I've already spent 20 million hours on from another profile. Or copy, start with copying a lighting profile, and now I have to remap 20 keyboard and mouse buttons, and fix all the fan curves and pump profiles. It seems like they are 99% of the way there, just give the import function an option to overwrite/replace when copying to an existing profile. Heck, just giving it the option to copy to an existing profile would be a huge deal. Maybe I'm missing something really obvious and I need to be kicked off my soapbox. If so, please start kicking, but do me a favor and let me know what I'm missing while you're giving me the beatdown. Red