Jump to content
Corsair Community

Commander PRO 3-Pin


Tomas143

Recommended Posts

Howdy,

 

I posted my problem on the german Corsair Forum but they cant really help, maybe someone here has an idea.

 

My problem:

I am using a Commander Pro with 8 Thermaltake Riing SP Fans and two Corsair AF. The fans are connected via Y-Cables. I tried different configurations with and without Y-Cables and different Fans but always have the same Problem.

The Commander Pro just recognizes one or two ports as 3-Pin Fans, the other ones are recognized as 4-Pin. All fans are 3-Pin fans.

Every reboot the Port changes and sometimes one is working sometimes two ports.

I used SysView to find the error and tried some methods mentioned in the german forum like uninstalling the whole link software and other stuff but nothing worked out.

The problem appeared after I upgraded the firmware. Out of the box the Commander Pro was working fine and I could control all Fans.

 

 

Sorry for the grammar and thanks in advance.

Link to comment
Share on other sites

maybe someone here has an idea.

 

It's possible to tell the CLCP 0.2.136 firmware all the CLCP ports are either 3-pin voltage or 4-pin PWM, but AFAIK CL 4.8.0.82 can't do this and all the fan ports can only be set to be the same.

 

My SIV utility 5.21 can, but currently you need to do this manually every time the system is booted, see http://forum.corsair.com/forums/showthread.php?p=911579 + http://forum.corsair.com/forums/showthread.php?p=911568.

 

If you post [Link Fans] + [Link Status] I will PM you how to enable SIV to do this, but you must accept you do this at your own risk and this may not be possible with a future CLCP firmware release.

 

I feel Corsair should implement support for similar to what I specified in http://forum.corsair.com/forums/showthread.php?p=912207 and suggest you request this via https://support.corsair.com/

Link to comment
Share on other sites

I kinda hoped that you would read this post. Your Program is great, good job on this.

I think setting all to DC would be great. Just like in the link you posted its greyed out. Corsair should have this function in its Link Software.

LinkFans.thumb.jpg.625533593565fced4752bcab5ec4a427.jpg

LinkStatus.thumb.jpg.b0578a07afed6ebc1caaffae91fd9440.jpg

Link to comment
Share on other sites

attachment.php?attachmentid=30480&d=1501498834

attachment.php?attachmentid=30479&d=1501498825

 

  1. I kinda hoped that you would read this post.
  2. Corsair should have this function in its Link Software.

 

  1. I suspected as much. After checking all the version information I think SIV can help so will PM you the incantation. This will only work for the 0.2.136 firmware and a new SIV will be needed once the CLCP firmware is updated.
  2. Have you requested they add this and http://forum.corsair.com/forums/showthread.php?p=912207 via https://support.corsair.com/?
  3. I feel I need to check the above screen shots before telling members how to enable this, so please don't pass on how to do this.
  4. The green blobs should update a few seconds after making the change, do they?
  5. Please let us know if this helps.

 

The problem appeared after I upgraded the firmware. Out of the box the Commander Pro was working fine and I could control all Fans.

 

Looking at http://forum.corsair.com/forums/showthread.php?p=911538 it specifies Noctua fans fixed in v4.8.0.82 with firmware 0.2.136 so I suspect this fix is what triggered your issue with the Thermaltake Riing SP Fans and two Corsair AF fans.

 

I find it rather surprising the Corsair CLCP can't correctly detect Corsair AF fans and advise you to also raise this with Corsair support.

Link to comment
Share on other sites

It worked perfectly!!! :biggrin::biggrin::biggrin: Youre a genius. They should let you work on the Link Software.

 

To your points:

2. I didnt yet, but I will. I told a Corsair Member in the german Corsair Forum.

3. No prob.

4.Worked

 

 

Corsair Support is weird, I couldt find a Subject related to the CLCP :mad: so I tried my luck at the german Corsair User Forum but they just told me that its hardware related since all problems should have been fixed with the last firmware...but just like you suspected, it triggered the problem.

 

 

So, thank you very much! Now I can use the CLCP for what it is supposed to:sunglasse

Link to comment
Share on other sites

It worked perfectly!!! :biggrin::biggrin::biggrin:

 

Good, I suspected it would :nodding:. With luck the next CLCP firmware will do better and if not I suspect there will be a SIV beta that does much the same as 5.21 does for the new firmware :rolleyes:.

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...