CL 3.2.5695 + 3.2.5676 and the old Link Commander

With the releases of CL 3.2.5695 + 3.2.5676 there seems to be some confusion about the old Link Commander support. I have tried to gather what I have found in this post.

1. http://forum.corsair.com/forums/showthread.php?p=792094 states The Commander unit will no longer be recognized by the system! See below for instructions on how to manually fix this. I take this me mean it will work if you do the work-a-round. :biggrin:
   
2. http://forum.corsair.com/forums/showthread.php?p=793775 contains The last Link version to support our legacy Commander is 2.7.xxxx. :!:
   
3. http://forum.corsair.com/forums/showthread.php?p=790530 shows CL 3.1.5667 reporting my old Commander :confused::biggrin:
   
4. http://forum.corsair.com/forums/showthread.php?p=792930 was unable to get CL 3.2.5676 to report his old Commander :mad:
   
5. http://forum.corsair.com/forums/showthread.php?p=792300 was unable to get CL 3.2.5676 to report his old Commander :mad:
   
6. http://forum.corsair.com/forums/showthread.php?p=792086 was unable to get CL 3.2.5676 to report his old Commander (this is me) :mad:
   
7. There are many other similar posts.
   
8. http://forum.corsair.com/forums/showthread.php?p=793533 says customer support will help :biggrin:.
   
9. http://forum.corsair.com/forums/showthread.php?p=793614 is what happened when I contacted customer support :cool:.
   
10. http://forum.corsair.com/forums/showthread.php?p=793775 had a different outcome :evil:
    
11. CL 3.2.5695 + 3.2.5676 are the only CL releases supported for Windows 10 ;):.
    
12. AFAIK no one has managed to get CL 3.2.5695 or 3.2.5676 to report an old Commander I expect the code within CL for the old Commander is totally broken :p:.
    

Corsair, please can you clarify what the exact situation is?

If your have issues and need help post to this thread including the SIV [Link Devices] and [Link Status] screen shots. Before starting SIV exit CL. It is also worth checking what the Windows Devices and Printers panel reports.

If the old Commander is connecting/disconnecting constantly see http://forum.corsair.com/forums/showthread.php?p=777371 for how to update the driver.

I have a post 3.2.5695 beta release of CL which reported all of my 4 x CLCC + 1 x old Link Commander :bigeyes:

After installing and launching v3.2.5676 in a system that has the older Corsair Link Commander unit, if the Commander unit is missing from C-Link software, you can follow the instructions listed below to fix this problem:

Exit C-link software from the C-Link ICON on system tray.

Open Windows device manager and find the problematic “Corsair Hydro Series 7289 USB Device” on the USB device list.

Right click and select Update Driver Software.

Select Browse My Computer for Device Software Manually and hit Next.

Select Let Me Pick from list of device drivers on My computer and hit Next.

Select USB Input Device and hit Next. After that, Windows will successfully update driver back to correct one.

Restart C-Link software and Commander unit should appear back into C-Link software.

I tried to follow this but Corsair Hydro Series 7289 USB Device is not even showing up in the Device manager. I think I found it as a hide item but couldn't understand what I was meant to do next. Can anyone help with picture if possible.

So, after installing Windows 10, the Commander started to connect/disconnect constantly (The sound of USB disconnecting told me that). Disconnected it from the Mother Board and no more sounds.

For a workaround connected the Cooling Node to my H100i (yes, it's working) and my AX1200i trough the USB Dongle.

I've managed to run v 3.1.5570 but it did not detect any link device.

Forgot to tell that I did all the USB's changes

1. As I read here the CL 3.2.5695 doesn't recognize the old commander and as I haven't been able to do it manually
   
2. I guess the only solution is to buy a Commander Mini to have the fans and the H80 pump under control
   
3. My only control is to check the temperatures of every device that thankfully are shown.
   
4. Is H80 supported by the new Commander?

1. AFAIK the old Commander does not work at all with CL 3.2 and I get the same issue. The part numbers you quoted are correct.
   
2. When I raised a ticket about this issue Corsair did an RMA of an old Commander to a CL Mini, though others have had less luck.
   
3. My SIV utility can report and control an H80 via an old commander on all of W2K to W10.
   
4. I have just checked and CL 3.2.5695 reported my CL mini attached H80. I have asked Corsair for the specification of what CL supports many times and this has not been provided.

As I've said before, users with the original Corsair Link Commander that are having issues with it specifically are strongly encouraged to contact customer service.

I did and I'm not sure how it helped.

The answer I got is if you are within the 1yr warranty for the old module they will swap you to a Mini but if you aren't then you are out of luck because the the old module doesn't support Windows 10. That makes me a little sad, but I understand it.

Where you expecting them to give some other answer?

an impending release of Link

I am looking forward to this release, any indications on the expected release date? Any beta we could test to help you as a community?

Initially we were going to push for swapping Minis for old Commanders, but an impending release of Link restores functionality to the old Commander units.

That's great news - too bad your customer support doesn't know that. Can you tell them? I've ordered a new Mini because of their response but that's OK - it will likely work better than the old module.

My example is my CS ticket that was updated this week as follows:

Comment

Created By: Zack TS (8/30/2015 6:18 PM)

Hello,

We're sorry to inform you the older Corsair Link device below is not compatible with Win 10 system, we can replace them with our new commander mini if you're still withing it's warranty.

Corsair Link Cooling Kit

Corsair Link GPU Node

Corsair Link Cooling Node

Please attach a photo/screenshot/PDF of the receipt/invoice to the ticket so that we can validate the warranty. The attachment area is at the bottom of this screen. Afterwards respond back with a ticket comment so that we know it's been attached, thanks.

Created By: Scott (8/28/2015 8:03 PM)

So you are saying that because I upgraded to Win10 I should connect the H100i directly and give up on using all my other Link gear? I'm just checking because on the forums there are some Corsair employee (Dustin) suggesting this isn't the company line and that I should contact customer service again.

Just a reminder, I have the following equipment which, after upgrading, will no longer work with the CL software? I need to buy a whole new fan controller for this? Either Corsair Commander Mini or another brand?

Corsair Link Cooling Kit

Corsair Link GPU Node

Corsair Link Cooling Node

Corsair AX1200i

Corsair Dominator Platinum with Corsair Link Connector

Corsair H100i (I guess this works with the direct connect)

Created By: Zack TS (8/18/2015 7:25 PM)

Hello,

H100i does not require Commander Mini, just plug in the provided USB cable to the pump, the other head to internal USB connector on your motherboard. Please let us know if you have other questions regard to LINK software. Thanks.

Created By: Scott (8/18/2015 6:50 AM)

How can I get the H100i to work with Windows 10 without the Corsair Commander?

The H100i has a 5 year warranty and I purchased it in mid-2013.

Created By: Zack TS (8/18/2015 12:07 AM)

Hello,

We're sorry to inform you the old cooling kit and lighting node is not compatible with Win 10, or link version after 2.7. We can replace them with new commander mini if they're still within warranty.

Please make sure you're using PWM/Manual fan mode in BIOS instead of DC/Auto fan mode, use the latest BIOS and USB port driver in your system, disable USB selective suspend (found in the Power Options of Control Panel, Advanced Power settings), try another USB header. If it still does not detect the cooler, grab a mini usb cable to a regular usb cable and plug the cooler to the back of the usb ports on the mobo (trying to identify if the cable provided is faulty)

I don't have a date for it yet. I'm working with red-ray to test it on his rig.

I have 4 x CLCC + 1 x old Link Commander and I also have the a beta release of CL. Dustin has just given me the OK to post:

The post CL 3.2.5695 beta reported all of my 4 x CLCC + 1 x old Link Commander :bigeyes: