HD120 lighting issue

[cifelli]

I bought a total of 6 hd120, a 3 pack with controller and 3 individual fans, and a commander pro. I have everything hooked up and only the 1st three fans on the hub let me change the leds with LINK software. ALL 6 i can control speeds and they all spin but i cant get #4-6 on the hub to light up. I tested all the fans and they will all work 3 at a time in any configuration in the ports #1-3. I think the led hub may be bad or am I overlooking something. Please help

[red-ray]

Assuming you have pressed [ + ] enough times so that CL4 knowns there are six sets of 12 LEDs then it could well be the LED hub, but I have never seen a post about one with this issue.

 

Do you have a multi-meter you could use to check the LED hub voltages and connectivity?

 

Pin-1 is ground, pin-4 should be +5 volts and port N pin-3 should be connected to port N + 1 pin-2.

[cifelli]

I did press the + so the LINK software knows there are 6 fans. Good idea with the multi meter but i don't think i have one. ill check and update if I do.

[r3db]

I have a similar problem, i have just 4 of my 6 fans light up.

 

One no lightning and the other bright but there is one green led (that's weird)

[wildfire99]

I had a similar problem with mine but quickly realized I had the drop-down selection for type of RGB to something other than "HD120 fan".

 

Another issue I had was not hooking them up sequentially on the hub (I had plugged into ports 1-3 and then port 6), because nothing anywhere I saw mentions having to ensure they are hooked up in order. A little silkscreen on the hub with some arrows to each port number would likely resolve this.

 

The other issue I had when setting up my fans was that I hooked up SP120 and HD120's on the same hub, because I didn't know they were incompatible. But once I figured out the secret "Corsair Code" for how all this hooks up I no longer have any issues, thankfully.

 

One caveat is that before I hooked up any fans I hooked up the fan commander pro I use and allowed Link to update it's firmware, which similar to Windows Update, needed to do this twice. So if you update the firmware, keep trying until it's officially "done." I don't know if firmware plays into some of these problems, but I would not be surprised.