DevBiker

One stop-gap would be to take a standard mini-USB cable and run it outside the case to plug into a USB port on the back of the system. It's a little Frankenstein and not what we should have to do but, honestly, the problem may be with the AsMedia hub also (not saying it is, just a possibility). If that's the case, Corsair won't be able to do much about it. I and others have also used NZXT's internal USB hub. I can confirm that using that with a Commander Pro that has a Lighting Node Pro and a H100iV2 connected does work.

No ... what Corsair Dustin has been alluding to is that the RPM control is a limitation of the IC itself. Like I said, my guess is that the commands specifically to set a custom fan curve actually take, as input, target RPM and the device controls the PWM to hit that target fan curve. Working with these little devices is sometimes weirder than a normal person would think. They are designed by electrical engineers, who also tend to be a little weird. Mostly it's due to the very limited processing and memory available on those devices. Now, I've not opened it up to see what chip they are using but I have done device programming like this before and for there to be a wonky crazy limitation on the actual controller doesn't come as something that's out of the realm of believability. In fact, once you've programmed a couple of these devices, it's pretty darn believable.

I have it. Played it a couple of times. Gorgeous game. Still hasn't gotten much into my Overwatch time tho. My son, however, is a different story. Maybe I'm too old.

Bug fixes are awesome! Definitely prioritize that over new features; totally get it. But ... it'd be really cool if you could also do control based on temperature deltas. Simple deltas between two values might even be feasible in the firmware (not sure how capable it is but I think it could be done with an Arduino ... I'm using that as my baseline which may not be fair).

My guess is that the hardware controller on the Commander Pro takes a target RPM and then adjusts the PWM signal to keep the target RPM ... and it may specifically be in the part of the command set that allows you to set a fan curve with an alternate command that does allow you to set a fixed percentage (but no curve). What would, IMHO, be ideal is if Link tested the fans for their min/max speeds and then remembered it (tools like Asus' FanXpert do this). The software could then display the fan curve as percentages and then, through a wee bit of math, abstract the commands that require RPMs at the controller level. After all, there's no problem that cannot be solved with another layer of abstraction. ;-) Perhaps a stop along the path to this panacea would be to allow the user to specify the max RPM for the fan (we'd have to test it ourselves or enter based on the spec sheet) and then it'd do the math - the active fan testing would be a bit more involved to implement. But setting those fan curves by RPM is paaaaaaainful. Especially when the fan maxes at 1500 RPM ... so you have 2500 RPM worth of emptiness. And then moving them 1 degree at a time. The arrows make it better but patience is not one of my virtues.

Go to your BIOS and either set the CPU fan to PWM or set it to constant 100%. The problem is that your pump wasn't getting the 12V from the CPU fan header that it was expecting because it was in non-PWM mode and varying voltage to control CPU fan speed. That does Very Bad Things to your pump.