The Corsair User Forums  

Go Back   The Corsair User Forums > Corsair Product Discussion > Corsair Link

Reply
 
Thread Tools Search this Thread Rating: Thread Rating: 8 votes, 5.00 average. Display Modes
  #61  
Old 11-22-2015, 08:08 AM
red-ray red-ray is offline
Banned
red-ray's PC Specs
 
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,152
POST ID # = 821445
red-ray Reputation: 81
Default

Yes, you should be able to do all you wish once you get a CL Mini.

Last edited by red-ray; 11-22-2015 at 08:41 AM.
Reply With Quote


  #62  
Old 12-20-2015, 04:59 AM
red-ray red-ray is offline
Banned
red-ray's PC Specs
 
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,152
POST ID # = 826532
red-ray Reputation: 81
Thumbs down 13 months and still no fix

Quote:
Originally Posted by Corsair Dustin View Post
We're more or less at the mercy of the original hardware/firmware vendor, which is why this hasn't been updated. We're keeping on them.
I feel no fix after 13 months is not acceptable. On what date will there be a fix?

http://forum.corsair.com/forums/showthread.php?t=137364 also needs fixing.

What actions are Corsair planning to ensure there are firmware fixes in sensible timescales?

Last edited by red-ray; 12-22-2015 at 03:17 AM.
Reply With Quote


1 members found this post helpful.
  #63  
Old 01-10-2016, 11:29 PM
k3mist's Avatar
k3mist k3mist is offline
Registered User
k3mist's PC Specs
 
Join Date: Jan 2016
Posts: 19
POST ID # = 830318
k3mist Reputation: 13
Question

Quote:
Originally Posted by red-ray View Post
I feel no fix after 13 months is not acceptable. On what date will there be a fix?

http://forum.corsair.com/forums/showthread.php?t=137364 also needs fixing.

What actions are Corsair planning to ensure there are firmware fixes in sensible timescales?
Hi Ray,

I have the Corsair Commander and I wish I would have found these forums prior to purchase. However, water under the bridge.

I am using SIV at this point because of the issues in CL. Hardware detection issues and it constantly resetting and adding all the devices over and over again with previous devices being inactive/blank not reporting anything. Which you then have to go through and delete. Plus other issues, like LED flicker, etc.

I'm guessing I really don't need to explain any of this.

Anyway, my question, is it possible to control the fan curve from different temp sensors using SIV? For example, the internal temp of my CPU to control the speed of the rad fans?

I see SIV easily detects all temps, devices, fans, etc but I can not figure out how to "bind" these two separate controls, if its even possible. I read the directions on your site, etc, but can not find anything. Please let me know.

Anyway, I really appreciate your work on SIV, its a life savor at the moment.
Reply With Quote


1 members found this post helpful.
  #64  
Old 01-11-2016, 03:34 AM
red-ray red-ray is offline
Banned
red-ray's PC Specs
 
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,152
POST ID # = 830339
red-ray Reputation: 81
Arrow press the pink blob and select the temperature

Quote:
Originally Posted by k3mist View Post
Anyway, my question, is it possible to control the fan curve from different temp sensors using SIV?
This is really a SIV question so see http://forum.corsair.com/forums/showthread.php?p=830342
Attached Images
File Type: png [Link Fans].png (74.6 KB, 674 views)

Last edited by red-ray; 01-11-2016 at 03:51 AM.
Reply With Quote


  #65  
Old 02-16-2016, 03:44 PM
red-ray red-ray is offline
Banned
red-ray's PC Specs
 
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,152
POST ID # = 837452
red-ray Reputation: 81
Arrow Adding 0 RPM and < 40% PWM support will require a CLCC firmware change

Quote:
Originally Posted by Corsair Chris View Post
We're looking into this for future versions, at this time we don't have an ETA on when it will be implemented.
Adding 0 RPM and < 40% PWM support will require CLCC + H110i + H110iGT + H100i + H80i firmware changes. If firmware changes were not required I would have implemented support for this a long time ago.

The Asetek cooler firmware can't be updated how do you propose to do this for Asekek based coolers?

Quote:
Originally Posted by red-ray View Post
I feel no fix after 12 months is not acceptable. On what date will there be a fix?

What actions are Corsair planning to ensure there are firmware fixes in sensible timescales?
The firmware bugs specified in this thread have been outstanding for well over 12 months I feel these should have been fixed by now and need to be fixed first.

Last edited by red-ray; 02-16-2016 at 04:08 PM.
Reply With Quote


  #66  
Old 04-01-2016, 06:35 AM
red-ray red-ray is offline
Banned
red-ray's PC Specs
 
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,152
POST ID # = 845056
red-ray Reputation: 81
Unhappy When might this be fixed?

The CL 4.2.2.27 release has failed to fix this issue. When might this be fixed?

It was first reported on 20-Nov-2014 and it not being fixed 16 months later is to say the least rather poor.
Reply With Quote


1 members found this post helpful.
  #67  
Old 05-13-2016, 11:01 AM
red-ray red-ray is offline
Banned
red-ray's PC Specs
 
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,152
POST ID # = 852004
red-ray Reputation: 81
Unhappy When might this be fixed?

The CL 4.2.3.41 release has failed to fix this issue. When might this be fixed?

It was first reported on 20-Nov-2014 and it not being fixed 17 months later is to say the least rather poor.

I wonder does the Corsair CEO Andy Paul knows this has not been fixed after 17 months? It's about time he made a similar post to http://forum.corsair.com/v3/showthread.php?p=763184 about Corsair Link bugs that are not fixed in a timely manor.

Last edited by red-ray; 05-16-2016 at 05:33 PM.
Reply With Quote


  #68  
Old 06-04-2016, 02:51 AM
Starkinsaur Starkinsaur is offline
Registered User
Starkinsaur's PC Specs
 
Join Date: Jun 2016
Posts: 1
POST ID # = 856318
Starkinsaur Reputation: 10
Default

Red-Ray, thanks for your efforts on this issue. It's nice to see there is someone who cares about this when the manufacturer clearly doesn't.

I am having the same problem which renders this device a complete waste of money.

Unfortunately Link version 4.2.3.41 fails to be able to communicate with the commander mini at all so I'm stuck using an old version (3.2.5742) where the fans can't be controlled...

Corsair, the fact that you continue to market and sell this garbage is a disgrace. I used to regard Corsair as a quality brand, that is clearly no longer the case.

For anyone who is thinking about buying any of this hardware; save yourself the time, expense and heart ache - buy from a respectable manufacturer instead. The advertising is false; the hardware does not provide the functionality they tell you it does because it's so very broken.
Reply With Quote


1 members found this post helpful.
  #69  
Old 06-04-2016, 03:07 AM
red-ray red-ray is offline
Banned
red-ray's PC Specs
 
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,152
POST ID # = 856319
red-ray Reputation: 81
Arrow CL3 should work for the temp 4 input

Quote:
Originally Posted by Starkinsaur View Post
Unfortunately Link version 4.2.3.41 fails to be able to communicate with the commander mini at all so I'm stuck using an old version (3.2.5742) where the fans can't be controlled...
CL3 should work for the temp 4 input, see http://forum.corsair.com/forums/showthread.php?p=810730

CL 4.2.3.41 talks OK to my 4 x CLCC, but I obviously don't use CL4 to control them as I use my SIV utility. Have you checked the CL4 log file that is in C:\Users\All Users\CLink4\ to find out why it does not report your CLCC?

It took be a couple of days to work-a-round the firmware bugs in SIV on 04-Feb-2015, but it would be far better if Corsair fixed the CLCC firmware bugs.

Last edited by red-ray; 06-04-2016 at 03:13 AM.
Reply With Quote


  #70  
Old 07-22-2016, 03:34 PM
mcr1878 mcr1878 is offline
Registered User
mcr1878's PC Specs
 
Join Date: Oct 2013
Posts: 42
POST ID # = 863633
mcr1878 Reputation: 10
Default

Quote:
Originally Posted by red-ray View Post
The CL 4.2.3.41 release has failed to fix this issue. When might this be fixed?

It was first reported on 20-Nov-2014 and it not being fixed 17 months later is to say the least rather poor.

I wonder does the Corsair CEO Andy Paul knows this has not been fixed after 17 months? It's about time he made a similar post to http://forum.corsair.com/v3/showthread.php?p=763184 about Corsair Link bugs that are not fixed in a timely manor.

Consumer protection law would tend to say that if the device is not working as advertised and is not going to be fixed (2 years) almost after that bug being reported

Then theres an argument that its not performing as advertised.

There's such a thing in the EU as the Unfair Commercial Practices Directive 2005/29/EC

This device is advertised as:

http://www.corsair.com/en-gb/corsair-commander-mini

A New Level of Control
Manage fan speeds individually, set up customized cooling profiles, or program fans to respond to changes in ambient temperature – the choice is yours. You can program lighting to relay critical system information, change the look of your system to provide an instant visual indicator of your selected cooling profile, or just have fun. And with Corsair Link Dashboard, you can do it all without opening your PC’s case.




These fans are not obviously able to be controlled based on ambient temperatures; temperature probes attached to the device.

That is clearly misleading advertising.


I'm having problems with my CPU cooler H110i blinking every now and again when cycling. Not working as intended.
Reply With Quote


1 members found this post helpful.
  #71  
Old 10-20-2016, 05:10 PM
Thatualle1970's Avatar
Thatualle1970 Thatualle1970 is offline
Registered User
Thatualle1970's PC Specs
 
Join Date: Sep 2013
Location: Dorchester, ON
Posts: 17
POST ID # = 876267
Thatualle1970 Reputation: 13
Default

Quote:
Originally Posted by red-ray View Post
I have been doing some more testing and I think I have a handle on what is happening. I have noted the following:

1) When I write 0xFF to the mode register it reads back as 0x8F, so my code thought the command had failed to enable manual feedback mode. This happens for the H100i/H110iGT/CL Mini, but the old Cooling node/H100/H80 which read back as the 0x00FF that I wrote.
2) If I ignore the unexpected returned mode and update the feedback temperature anyway then the fan speeds change.
3) SIV only writes the temperature feedback when the temperature changes. I have noticed that the firmware changes the feedback temperature I set to the internal temperature.

The net effect is that I think there are two firmware bugs:

1) The mode is not returned correctly.
2) The feedback temperature gets overwritten when it should not be.

Please will you pass this onto the development manager and provide feedback to me?
1 -- you're correct, the returned fan mode is omitting the temperature channel bits (bits 6~4); note that bits 7 and 0 are read-only, so writing 0xFF to a fan that's not detected will never return 0xFF.

2 -- feedback temperature is whatever you wrote to it last, regardless of channel, it's a "write only" register.
Reply With Quote


  #72  
Old 10-20-2016, 05:42 PM
red-ray red-ray is offline
Banned
red-ray's PC Specs
 
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,152
POST ID # = 876271
red-ray Reputation: 81
Sigh.. I am unclear what point you are making

Quote:
Originally Posted by Thatualle1970 View Post
1 -- you're correct, the returned fan mode is omitting the temperature channel bits (bits 6~4); note that bits 7 and 0 are read-only, so writing 0xFF to a fan that's not detected will never return 0xFF.

2 -- feedback temperature is whatever you wrote to it last, regardless of channel, it's a "write only" register.
  1. Yes, but it's the none RO bits that are incorrect. With the Cooling Node it works as it should.
  2. Maybe, but unless I keep writing the same temperature the fan speeds change when they should not, so I think a timeout is coming into play. What is the URL where Corsair specify what should happen.
  3. Note the issue has not been visibly addressed after 23 months which shows Corsair totally lack professional diligence
Reply With Quote


  #73  
Old 11-22-2016, 04:02 AM
red-ray red-ray is offline
Banned
red-ray's PC Specs
 
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,152
POST ID # = 879806
red-ray Reputation: 81
Thumbs down 24 months and still no fix

Quote:
Originally Posted by red-ray View Post
I feel no fix after 12 months is not acceptable. On what date will there be a fix?

What actions are Corsair planning to ensure there are firmware fixes in sensible timescales?
No fix after 12 months was rather poor and no fix after 24 months is even worse.

Do Corsair totally lack professional diligence or are they just incompetent?

Last edited by red-ray; 12-08-2016 at 12:15 PM.
Reply With Quote


  #74  
Old 03-03-2017, 07:02 AM
red-ray red-ray is offline
Banned
red-ray's PC Specs
 
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,152
POST ID # = 893630
red-ray Reputation: 81
Thumbs down H110iGT + H110i Pump Custom mode does not work

I received a report that SIV failed to change the pump speed on a H110i and when I double checked I see the same issue on my H110iGT.

Below you can see that in the SIV 5.17 Beta-10 screen shots the fan speeds changed, but the pump did not.

Corsair, please will you fix the H110iGT 1.1.08 + H110i 2.0.00 firmware? You should also implement pump custom curves in CL4 for both Asetek and CoolIT coolers.

As I suspect Corsair will fail to do this in a timely manor, if at all, I added a work around for SIV 5.17 Beta-11 which as you can see below does what the firmware should do.

Quote:
Attached Images
File Type: png H110iGT Pump Custom Mode before and after work around.png (238.1 KB, 504 views)

Last edited by red-ray; 03-03-2017 at 07:48 AM. Reason: Typo
Reply With Quote


1 members found this post helpful.
  #75  
Old 03-03-2017, 07:32 PM
Bob Pilette Bob Pilette is offline
Disabled Veteran
Bob Pilette's PC Specs
 
Join Date: Jan 2017
Location: Cecilia KY
Posts: 25
POST ID # = 893727
Bob Pilette Reputation: 10
Default 2 Bad Corsair Link Commander Minis So Far

My first Commander Mini quit sensing FAN 2 after a couple of months.

My second (replacement) Commander Mini stops responding after approx less than 30 mins shortly after I got it. After stopping, it shows Channel IDs of 1F 00 00 00 00 00 00 00 instead of 05 00 00 00 01 00 00 00 on the Link Devices page of SIV. Only a Power Cycle of the CM resets it.

Awaiting reply from Corsair on second ticket.

Last edited by Bob Pilette; 03-03-2017 at 07:36 PM.
Reply With Quote


Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 06:50 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.