jwilds1

https://imgur.com/a/dRJTRkt Finally, success. After scrounging an old PS from my now non-functioning old NAS, and then confirming what I thought was a dead spare Commander Pro, I was able to get things running with a brand-new Commander Pro.

Well, I ended up getting this - https://www.amazon.com/gp/product/B07RRZ5LRD And it still doesn't work. I have the power supply connected to a 12v, 3.3A wall converter. I'm about ready to throw all this stuff in the fire pit *edit - now I realize it's missing the 3.3v wiring*

Something like this - https://www.amazon.com/RGEEK-Switch-24pin-Power-Supply/dp/B071P3HMNK ?

Getting closer, but still didn't work. I cleaned out a lot of junk in USBDeView, and I can now actively see the hub portion connect and disconnect as I plug in the USB connector. However, I cannot get the other row to work. The cable I purchased is a 5-pin, so I just pulled the last "no-connection" pin from the Molex and installed both possible ways into the "bottom" row. I get no connect/disconnect sound when keeping the same orientation on the plug but just moving to the bottom row. When I rotate the plug 180 degrees (which I figured wouldn't work but had to try it), I get a "USB Device Not Recognized" from Windows.

Has anyone done this? I purchased these: https://smile.amazon.com/gp/product/B000V6WD8A - USB single row header to USB-A Male adapter https://smile.amazon.com/gp/product/B00MVRS38G - External SATA Power Supply I'm hearing the USB connection sound when I plug it in, but iCUE is not finding it. I've restarted the PC while connected and it's still not appearing in iCUE. The internal Commander Pro is recognized and functioning fine. USBDeview - https://imgur.com/a/yLak0bH

Yes, by wrong pinout I mean I had the 5v and ground reversed. All I know is that the new Commander worked. Thanks a lot for your help! Here's what the end result looks like - 2 strips on each PC, each with 60 LEDs per. I set my PC up with Wall paper Engine and an iCUE audio responsive wallpaper. I then sent audio and video via NDI over to the other rig, with the same wallpaper. The result is a disco. That's not how I usually have it set up, just wanted to see how far it could go.

SUCCESS but only partial. I think I figured out why, and I'm hoping my hunch is true - These LEDs are directional. In that, if you solder the leads on the "end" of the string and attempt to plug them in, it won't work. The only string that works is the one from the start of the spool. The other 3 sections don't, but the common thing among the 3 is the cables/Molex connectors I added or modified (end of the spool was modified to turn a female connector into a male) were all against the direction noted on the strips. Back downstairs to the soldering iron

OK, replacing the CoPro got me back to square 1 (no DIY RGB strips, but everything is now showing up in iCUE. Do you think I fried the RGB Strip with the wrong pinout, or can I correct the pinout on the Molex and shorten and try again with the same (yet shorter) strip?

1) Both the Commander Pro and h150i show as "not connected" in USBDeView. 2) Pinout on my Molex was wrong. 3) Between the time the Commander Pro/everything connected to it was working and now, nothing has changed regarding which USB header I plugged into on the mobo or the SATA power connector. Pretty sure it's the Commander Pro. Will replace and report back.

As far as the Lighting Channels not recognizing anything, I could have been a little more clear. Nothing was lighting up when plugged into them. And as far as configuring it in iCUE, I can't - nothing connected to the Commander Pro is showing up in iCUE with the new configuration. In addition, the CoPro isn't showing in iCUE either I can cut that strip in half and just put one half on CoPro LED channel 1 and another half on channel 2, but that doesn't solve my problem of iCUE not finding the CoPro. Any other words of advice? Thanks in advance!

Could use some assistance - I'm fairly sure I fried my CoPro. Current setup: Commander Pro connected to motherboard h150i pro (pump connected to USB on CoPro) Lighting Node Pro (connected to USB on CoPro) RGB Fan hub connected via 2-conductor wire to Lighting Node Pro 3x LL120 fans connected to RGB hub (channels 1-3) Was working great up to this point. Using some of DevBiker's invaluable how-to's (and a little overeagerness on my part), I attempted to modify & connect approximately 58" (87 LEDs) of this - https://smile.amazon.com/gp/product/B07FVR6W71 - by modifying the plug end to 3-pin Molex and connecting to an LED channel on the CoPro. Now, everything connected to the Commander Pro does not show up in iCUE. When adding the Molex connector to the RGB strip, I just kept the configuration the same from a Corsair strip (see attached image). I've attempted plugging in just one standard Corsair strip into LED port 1 and 2 (individually) and still nothing is being recognized. Any guidance? I have no issue going and getting another CoPro, aside from the fact that the closest MicroCenter is like an hour away.

My configuration is very similar, and experiencing the exact same issues with nearly the exact same timeframe. (3) LL120s plugged into a Fan hub which (I believe) is plugged into a Commander Pro. This is by memory, as the PC is wall-mounted and I'd have to take it down to confirm. 2 of the 3 fans flickering constantly. Currently using "Arc" Lighting style with white/black. When flicker occurs, small segment of lights on each fan (2 or 3 LEDs) change to a random color then back to white. Choosing a "Temperature" setup makes everything crazy. iCue has been updated to latest and greatest, and firmware confirmed to be latest.