Jump to content
Corsair Community

H100i clashing with Commander Mini since update


Jbonnett

Recommended Posts

Hi All,

Since updating to v4.2.1.42 I haven't been able to change the colour of the H100i led due to it clashing with the Commander Mini, everytime I try the led strip changes colour instead... If I try to change the led strip it also changes the led strip colour.

 

I also tried this http://forum.corsair.com/v3/showthread.php?t=128345 due to other problems I've had where the H100i geen rgb doesnt work on restart (unless I leave my computer unplugged for hours), when I tried this fix it seemed like it was trying to update the firmware on the Commander Mini due to the led strip changing colour... I also still can't change the H100i colour on the earlier version of the Link software. So I could do with a link to the Commander mini's firmware if someone doesn't mind? I couldn't find it myself.

 

I updated back to v4.2.1.42 and the Commander Mini is missing with the H100i showing as the Commander Mini in the devices tab.

 

Just to note I have the H100i plugged into the Commander Mini via a Link cable.

 

Anyone have any ideas?

 

Update: I have the H100i on the correct firmware now, although the Commander Mini is still showing as the H100i and ideas how to add back the old firmware? I tried manually updating it but had an error with Link software v3.2.5742 and don't have the .s19 for v2.4.5110. In the image the Commander Mini is showing as H100i, I have the H100i unplugged.

 

http://s27.postimg.org/9x9baf2cj/Link.png

 

Attempting to Update:

 

http://s17.postimg.org/bvlpyvyan/Link_H100i.png

 

http://s27.postimg.org/gwxh40exv/Link_Commander.png

Link to comment
Share on other sites

What version of CL is this screen shot from? I suspect a very old version that does not support your hardware.

 

You seem to be trying to load the old Link Commander firmware into a H100i which is rather silly. The H100i firmware is CLink_H100i_v1.1.3.s19.gz.

 

I was just emailing you, yeah this was the version that I can manually update firmware... The thing is the first time I tried updating the H100i, and that H100i was connected to the Commander even though I selected to update the H100i it pushed it to the Commander.

 

I tried unplugging the H100i (I have that on the firmware I want, that's working fine now that I can tell), even though the H100i is unplugged the Link software shows that there is a H100i plugged in and even SIV does.

 

I have tried using newer versions of the software but it still shows as a H100i, I can't do a manual update to the Commander firmware because it's apparently the wrong device or up to date. You can see in the last two screenshots I posted.

Link to comment
Share on other sites

I suspect you used a very old version of CL that does not support the CLCC. You are not the first to do this and I recall posting about how to recover this before, but can’t find the post. From memory to recover this do exactly as follows:
  1. Install CL 3.2.5742.
  2. Closedown CL.
  3. Open an explorer window and navigate to C:\Program Files (x86)\CorsairLink\Firmware\
  4. Copy CorsairLinkChassisFW_1.1.6.s19.gz to CLink_H100i_v1.2.0.s19.gz
  5. Start CL and update the pseudo H100i firmware from 1.1.3 to 1.2.0
  6. Closedown CL.
  7. Delete CLink_H100i_v1.2.0.s19.gz
  8. Power cycle the system/CLCC.
  9. With luck the CLCC should now have the CLCC firmware

 

Good luck :bigeyes:

 

Just tried that, It's still showing as the H100i after power cycle. It seems like the update is too quick, and it's not updating because it's still on 1.1.3.

Link to comment
Share on other sites

Just saying it did not work is next to useless, post the screen shot of CL 3.2.5742 doing the firmware update. How many seconds did this take?

 

Pretty much after I click... That is all I can tell you.

 

http://s27.postimg.org/8gd9j1uoz/Links.png

Link to comment
Share on other sites

For some reason CL is not updating the firmware. I assume you are pressing [start Update] rather than [ OK ].

 

I managed to find http://forum.corsair.com/forums/showthread.php?p=754175 + http://forum.corsair.com/forums/showthread.php?t=137337 so you could try using CL 2.7.5361, maybe it will do better.

 

Ok I got it to work in the end... Any idea why the H100i wouldn't get recognized now? It's plugged back into the Commander.

Link to comment
Share on other sites

  • 3 weeks later...

I also get "AirFlow" device now, I have no idea where that has come from... The H100i shows is I plug it into a USB header separately, but not via the commander.

 

http://s30.postimg.org/4j3tmsedd/status.png

 

http://s23.postimg.org/iqt2m3dtn/devices.png

 

http://s30.postimg.org/8ahzmuhfl/bus.png

Link to comment
Share on other sites

In that case it's probably the H100i, but as usual you have not provided enough information for my to know what may cause this.

 

I don't know what info to give, it doesn't make sense to me seen as the H100i works plugged into the usb header...

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...