DevBiker

The CoPro is limited to 4.5A for fans overall (this is based on the SATA power connector, not the CoPro itself). Splitters do work with the CoPro, even if they aren't "officially supported". However, there have been numerous reports of issues with 3-way splitters, in particular. I do have several 2-way splitters on both of my CoPros and they are both working just fine. At any rate, limit it to 1.0A per header at most. LED power is supplied by the Fan Hub, not the CoPro. 6 LL Fans on a single fan hub will be just fine; it's less then the 4.5A 5V limit of the SATA power connection. Do make sure that both the CoPro and the NoPro have full SATA power connectors. Both devices have an internal microcontroller that uses 3.3V power. The fan hub does not require this - it only uses the 5V rail so, if necessary, you can use a molex-to-sata adapter with that.

Is that just on startup? Or when you lock the workstation? Or all the time? As I mentioned before, I've seen it do this when you unlock ... but it's only for a couple of seconds.

It should flash rainbow for a second or two but, once unlocked, revert to your selected profile. Next time, before flashing, try switching profiles. Sometimes that resets things.

IF this is implemented (and I doubt that it's high on the priority list right now as they have a bunch of other, higher-priority issues to sort out), it'll be a while.

So ... the CoPro needs a SATA power connection. It only has one power connection ... so it can only be connected to a single PSU. If you have one system on and not the other, only one PSU would be supplying power. If the system that's on is different from the PSU that the CoPro is connected to, you won't have power to the CoPro. The solution would be something that connects to both PSUs and supplies power to one SATA connection, automatically switching between the two (based on what's on). Such a thing, AFAIK, doesn't exist.

Have you check to make sure that you added all of the fans to the channel? How many fans are we talking about here? Have you rearranged them on the hub?

If the Link UI is running, yes, it's normal for it to start back up. The Link UI actually starts the service - and stops it when you shut down the Link UI.

I think your biggest challenge would be power - you'll have two power supplies and only one of them may be supplying power. Assuming it's powered, the CoPro could do that as long as your temperature sources for your fan curves is based on one of the CoPro's built-in thermistors (though the lighting effects would only be rainbow). But the problem is powering it ... you'd really need to have some kind of SATA switched power - the SATA power connected is attached to both PSUs but only one actually provides the power - whichever one is powered first. I've not seen such a thing though, technically, it should be possible to create.

You'd have to check your manual or contact Gigabyte for what that means.

A couple of things to look at ... and somethings that you may need to rewire as it doesn't sound like it's installed correctly ... something that we've seen before in cases like this. First, your cooler will have a single fan header cable coming off of the header. This will be a standard, 3-pin fan header. Where is that plugged in to your motherboard? It should plugged in to the CPU_FAN header on your motherboard. Once it is, you'll also need to go into the BIOS and make sure that the CPU_FAN header is set to 100%/Full Power. You can also set it to PWM mode. Second ... the 2 fans for the radiator should be plugged in to the Y-splitter that comes off of the pump header. This will allow the fans to be controlled by the pump. Once that's done, go into Corsair Link and set the fans on "Balanced" mode and make sure that the temperature source for the fan curve is set to "H100i V2".

Can you check your BIOS to see if you have Fast Start enabled (disable it). XHCI Handoff should also be enabled.

Static colors on the NoPro is an issue with the current release of iCue. It's been explained in multiple posts ... to work around the issue, use Color Shift and have the colors just barely off ... for example, for all red, all the time, shift between 255,0,0 and 254,0,0.

Just out of curiousity, is anyone having this issue using any adapters (molex to SATA, for example)?

Yes, this is a known issue. It appears to be relatively random. It should, however, be fixed in the next build.

I have not seen this but it sounds like an initialization problem. Do you have Fast Boot enabled in your BIOS? How about Fast Start in Windows? One or both of them may be the root cause.

Link has been released for a couple of years. So they are not selling hardware with the required software in beta. iCUE is the next generation that is currently in beta. Link is still available. And your lighting control issues are completely due to being mis-configured. The behavior that you described is exactly the behavior that I would expect to see when you configure ML fans on the lighting channel as LL fans.

Impressive! Nicely done!

Uh, no, I don't. I don't read minds. I can only read what you wrote. You have ML fans configured as LL fans in iCue. That's the problem. So ... it's what we like to call an EBChAK error. That's an Error Between Chair and Keyboard, not a software error or bug.

Call it what you will. It's reality, dude. So ... with iCue, how can you not control the individual LEDs? You absolutely can. You've said what you have ... but nothing that you've complained about makes any sense. If you have a CoPro, there's no need for a Lighting Node Pro in your configuration. This statement: makes no sense at all. The first two what? The next four what? LEDs? Fans? Strips? How do you have the channel configured? Have you looked at the videos linked in my profile? As for software ... it's out and has been out. If iCue isn't working for you, you can always use Link.

I would disagree with this. They are working as quickly as they can. The reality is that software development is hard and this is a large project. It can only go so quickly. I know this is a news flash to many but devs don't just wave a magic wand over the screen and the code suddenly works. So ... you have some issues but you're providing some very general, high level complaints that don't give us the information that we need to actually work through what's going on. Which fans are you having difficulty controlling and what are they connected to? What lights are you talking about and what are they connected to?

You could restart Link. Link also has a corresponding service however it shuts down the service when you exit Link.

Try restarting the Corsair Service. You may need to shut down iCue first (not always).

For the cooler, you can save the settings to the device - this way, your fan curve will be applied regardless of whether iCue is active or not. To do this, select the cooler. Then, in the hamburger menu for "Profiles", select "Save Static Lighting, DPI, Performance to Device"

What effect do y'all have configured on the lighting nodes? NoPro or CoPro? I'm looking for similarities across all of y'all that are reporting the same issue.

Do you have OSD enabled? I wonder if the OSD settings may be conflicting with Riva?