The Corsair User Forums  

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

Closed Thread
 
Thread Tools Search this Thread Rate Thread Display Modes
  #1  
Old 07-25-2016, 07:24 PM
Technobeard's Avatar
Technobeard Technobeard is offline
Bearded Corsair Employee
 
Join Date: Oct 2012
Posts: 4,302
POST ID # = 864130
Technobeard Reputation: 68
Default Discuss Link v4.2.4.25 here

This will be the official discussion thread for Link v4.2.4.25.

If you'd like to report a bug, please respond to this thread in this format:
  1. Version of your Link software. NOTE: If you're not using v4.2.4.25, please install it and see if the bug has been fixed.
  2. What version of Windows you're using.
  3. Summary - One line / sentence explaining the issue
  4. Detailed description of the issue - This part can be as long as you want. It should be detailed enough so that we can clearly identify the issue and attempt to replicate it.
  5. Attach photos of the issue to the post that help #4.

Quote:
07/20/2016 - Corsair Link Software Update Version 4.2.4.25

Changelog:
  • Addressed instances where the DRAM modules were not updating temperature readouts in UI
  • Addressed issue with DPC Latency
  • HXi and RMi PSU Multi-Rail mode terminology update
  • Resolved several device connection issues
  • Updated EULA
  • Fixed interlocking of access to Corsair devices for third-party applications
  • Some visual improvements of charts

Last edited by Technobeard; 07-25-2016 at 07:27 PM.


  #2  
Old 07-26-2016, 12:47 AM
red-ray red-ray is offline
Banned
red-ray's PC Specs
 
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,148
POST ID # = 864149
red-ray Reputation: 81
Unhappy SIV 5.12 or later needed

Quote:
Originally Posted by Technobeard View Post
  • Fixed interlocking of access to Corsair devices for third-party applications
The interlocking has been fixed, but the fix was poorly designed as it failed to take released third-party applications into account . I was told of this change < 24 hours before CL 4.2.4.25 was released which meant it was too late to remedy the poor decision Corsair made .

The Global\CorsairLinkReadWriteGuard semaphore was changed to the Global\CorsairLinkReadWriteGuardMutex mutex rather than the Global\Access_CorsairLink mutex I requested on 22-Sep-2014. Because a different name was used this broke the SIV V5.11 interlocking which worked with all earlier CL4 releases, but not CL 4.2.4.25 so I needed to change SIV to use the different name, see http://forum.corsair.com/forums/showthread.php?p=863330. That said Corsair are finally using a mutex is a correct implementation which resolves all the issues with the semaphore, but I am at a loss as to why Corsair did not use the name I proposed as had they done this SIV 5.11 (actually SIV 4.47 and later) would have interlocked correctly with CL 4.2.4.25 as would the released versions of AIDA64 and HWiNFO.

On 08-Aug-2016 I discovered that CL 4.2.4.25 probably fails to correctly implement the defined locking semantics, see http://forum.corsair.com/forums/showthread.php?p=866159. Using SIV 5.12 Beta-24 it reported the issue in < 2 seconds, so I am at a loss as to how the Corsair CL4 interoperability testing passed.

How do I download new firmware into my CL Minis + H100i + H110iGT?

Have any of the following firmware bugs been addressed some of which have now been outstanding since 20-Nov-2014? If not on what date are they scheduled to be addressed please?
  1. http://forum.corsair.com/forums/showthread.php?t=134621 - Commander Mini will not control fans based on temp sensors
  2. http://forum.corsair.com/forums/showthread.php?p=757703 - Commander Mini + H100i + H80i fan mode register is not returned correctly.
  3. http://forum.corsair.com/forums/showthread.php?t=137364 - Commander Mini + RGB LEDs - Blinking Issue.
  4. http://forum.corsair.com/forums/showthread.php?p=754023 - 10,000 RPM Fans #1 - Corsair suspect it's a firmware bug of 16-Jan-2015.
  5. http://forum.corsair.com/forums/showthread.php?p=709734 - H100i + H80i incorrect colour if you use zero, use 255,1,1 rather than 255,0,0.
  6. http://forum.corsair.com/forums/showthread.php?p=855427 - H100i + H80i you can't use 1,1,1 rather than 0,0,0 as this is not black.
  7. http://forum.corsair.com/forums/showthread.php?p=837226 - CLCC support for 0% PWM or 0 RPM to stop the fans.
Some fixes appear to get promised, but then never seem to be released.
Quote:
Originally Posted by Corsair Dustin View Post
This is a known issue with a fix coming.
This was posted over 17 months ago on 02-Feb-2015 so I would have expected it to be fixed by now. On what date is the fix expected? On 03-Feb-2015 Corsair stated:

Quote:
Originally Posted by Corsair Dustin View Post
I believe it requires a firmware update to be corrected. It should be in the next Corsair Link drop, or the one after.
There have been at least 7 CL drops since then .

Quote:
Originally Posted by Corsair Dustin View Post
So just so you guys know, we're aware of this bug, but because of the issues we've seen with H100i/H80i and the current version of C-Link, this has been backburnered to get more pressing problems fixed.
Posted on 03-Nov-2014, over 20 months ago.

Quote:
Originally Posted by Technobeard View Post
If you'd like to report a bug, please respond to this thread.
I have done this for all the CL4 releases and Corsair have not responded to most of these posts. Why is this and why should I bother to report issues?

Here is an itemised list of issues which Corsair failed to respond to or address in a timely manor.
  1. http://forum.corsair.com/forums/showthread.php?p=851701 - CL 4.2.3.41 issues
  2. http://forum.corsair.com/forums/showthread.php?p=844974 - CL 4.2.2.27 issues - How do I change the TCP port
  3. http://forum.corsair.com/forums/showthread.php?p=841278 - CL 4.2.1.42 issues
  4. http://forum.corsair.com/forums/showthread.php?p=833499 - CL 4.2.0.162 issues
  5. http://forum.corsair.com/forums/showthread.php?p=833532 - CL asking for a reboot when it should not
  6. http://forum.corsair.com/forums/showthread.php?p=837724 - CL4 using a massive amount of TCP transfers
  7. http://forum.corsair.com/forums/showthread.php?p=833695 - Silly driver package name
  8. http://forum.corsair.com/forums/showthread.php?p=833699 - Issues with > 32 CPUs
  9. http://forum.corsair.com/forums/showthread.php?p=834459 - CL4 does not support CSMI RAID
  10. http://forum.corsair.com/forums/showthread.php?p=836506 - CL4 does not support EC Sensors
  11. http://forum.corsair.com/forums/showthread.php?p=836736 - NVMe Disks are not Reported
  12. http://forum.corsair.com/forums/showthread.php?p=837364 - No support for the original Commander.
  13. http://forum.corsair.com/forums/showthread.php?p=845182 - BSOD caused by Corsair supplied AXi PSU/Asetek Cooler kernel mode driver
  14. http://forum.corsair.com/forums/showthread.php?p=845092 - 10,000 RPM Fans #2 - no reply
  15. http://forum.corsair.com/forums/showthread.php?p=853869 - 10,000 RPM Fans #3 - no reply
  16. http://forum.corsair.com/forums/showthread.php?p=854759 - To fix -ve X and fail to fix -ve Y is incompetent
  17. http://forum.corsair.com/forums/showthread.php?p=839550 - H100iV2 and H100iGTX have different firmware
  18. http://forum.corsair.com/forums/showthread.php?p=850509 - CL4 causing high DPC latencies.
  19. http://forum.corsair.com/forums/showthread.php?p=864164 - CL4 causing high DPC latencies after Corsair claim to have fixed it.
  20. http://forum.corsair.com/forums/showthread.php?p=837228 - CLCC support for 0% PWM or 0 RPM to stop the fans.
Note that some of the entries itemise up to 52 issues and I expect I reported other issues I could add to the list.

Last edited by red-ray; 09-15-2016 at 09:52 AM.


2 members found this post helpful.
  #3  
Old 07-26-2016, 01:46 AM
red-ray red-ray is offline
Banned
red-ray's PC Specs
 
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,148
POST ID # = 864155
red-ray Reputation: 81
Thumbs down CL 4.2.4.25 only reported two of my eight DIMMs

Quote:
Originally Posted by Technobeard View Post
  • Addressed instances where the DRAM modules were not updating temperature readouts in UI
  1. I suspect this change may have introduced a new bug as CL 4.2.4.25 only reported two of my eight DIMMs .
  2. Below you can see SIV reported all eight DIMMs and updated their values 13,950 times .
  3. I was wondering if the issue could have been caused by SIV, so I started up AIDA64 which reported eight of eight which means AIDA64 and SIV must interlock access to the SMBus correctly, so this must be an issue with CL 4.2.4.25 rather than AIDA64 or SIV.
  4. Some time later I got the HWiNFO Beta that uses Global\CorsairLinkReadWriteGuardMutex and it also reports all eight of my DIMMs .
  5. With all of AIDA64, HWiNFO and SIV active CL 4.2.4.25 totally failed to report any of my DIMMs .
  6. I am at a loss as to how the CL 4.2.4.25 interoperability testing failed to find this issue and feel CL4 needs to be better tested before Corsair release a new version .
  7. CL4 is also still reporting them as PC3-10700H when they are PC3-14900H .
  8. AIDA64 + HWiNFO also reported my CSMI RAID + USB attached disks and CL4 totally fails to report any of my disks .
On 12-Feb-2016 I reported what I suspected was the same issue in CL 4.2.0.162, see http://forum.corsair.com/forums/showthread.php?p=836736, so maybe it's been around for a while. Given this I decided to do some checking so I did as follows:
  1. I tried the CPUID SDK HWM utility.
  2. It also failed to report all my DIMMs .
  3. I contacted the CPUID SDK developers and worked with them to look into why .
  4. We figured out the root cause of the issue and fixed it .
  5. I expect this issue will be fixed once Corsair release a new CL4 with the corrected CPUID SDK .
  6. I suspect this is the root cause of the issues in http://forum.corsair.com/forums/showthread.php?t=155914.
  7. Please can you explain why the Corsair CL4 Development Team failed to address these issues after 5 months given it took me < 24 hours to do this? I suspect some, probably the managers, need to be RMAed .
Quote:


Attached Images
File Type: png Only two of eight DIMMs reported.png (226.7 KB, 4396 views)
File Type: png AIDA64 reported eight of eight.png (239.7 KB, 4391 views)
File Type: png CL 4.2.4.25 failed to report any DIMMs!.png (487.5 KB, 4409 views)

Last edited by red-ray; 08-05-2016 at 03:45 PM. Reason: Add AIDA64 + HWiNFO information + figured out why and how to fix this


  #4  
Old 07-26-2016, 03:28 AM
red-ray red-ray is offline
Banned
red-ray's PC Specs
 
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,148
POST ID # = 864164
red-ray Reputation: 81
Thumbs down CL4 still causes high DPC latancies on my system

Quote:
Originally Posted by Technobeard View Post
  • Addressed issue with DPC Latency
Below you can see CL 4.2.4.25 still causes high DPC latencies on my system.

Note I did not have SIV running and soon as I closed down CL 4.2.4.25 these stopped.

The two RM PSUs should be PSU #1 and PSU #2.

Quote:
Attached Images
File Type: png CL 4.2.4.25 high DPC latencies.png (273.1 KB, 4399 views)

Last edited by red-ray; 07-26-2016 at 03:32 AM. Reason: Add note about RM PSUs


  #5  
Old 07-26-2016, 09:20 AM
gnewtzie gnewtzie is offline
Registered User
 
Join Date: Jul 2016
Posts: 3
POST ID # = 864207
gnewtzie Reputation: 10
Default More than 2 monitors.. nogo

If you try to move the CL4 window onto the 3rd and 4th monitor... it just moves back to where it was. It might be different if you have all your monitor's horizontal... but mine are in a 2 x 2 configuration.
Like this. 0's work, x's don't
x x
0 0


1 members found this post helpful.
  #6  
Old 07-26-2016, 09:33 AM
red-ray red-ray is offline
Banned
red-ray's PC Specs
 
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,148
POST ID # = 864209
red-ray Reputation: 81
Arrow I reported this as a CL 4.2.3.41 bug

Quote:
Originally Posted by gnewtzie View Post
If you try to move the CL4 window onto the 3rd and 4th monitor... it just moves back to where it was. It might be different if you have all your monitor's horizontal... but mine are in a 2 x 2 configuration.
Like this. 0's work, x's don't
x x
0 0
I reported this as a CL 4.2.3.41 bug and Corsair failed to fix it, see http://forum.corsair.com/forums/showthread.php?p=854759.

They fixed -ve X, but not -ve Y

Corsair should publish a list of known outstanding issues and this has been requested on many occasions. Corsair failing to provide this is unprofessional.

Last edited by red-ray; 07-26-2016 at 09:50 AM.


  #7  
Old 07-27-2016, 09:06 AM
Specter's Avatar
Specter Specter is offline
Registered User
Specter's PC Specs
 
Join Date: Feb 2013
Posts: 376
POST ID # = 864350
Specter Reputation: 22
Default

Reading all these issues I am surprised that these is still a fan base on Corsair Link products. My LEDs still blinks when the fan speed changes, there is still no easy way to maximize the corsair link window in one click or double click the title bar. It does not even respect Windows 7, 8 or 10 window snapping to make maximizing easier. Who in their right mind thought it would be great to drag bottom right corner in order to resize the window?!!!!!!!!!!!

I thought the Maglev fans would bring my interest back but it failed so bad when I saw the maglev fans were not RGB

Honestly, all these add on corsair products are becoming irrelevant. For instance, 2016 motherboards are now coming with built in RGB headers and GPUs are starting to implement 4 pin PWM fan headers with better fan control options so that eliminates the need for a Commander mini or NZXT Hue + Grid v2.

I know for a fact my next build will have zero Corsair products for the simple fact they are more focused on pushing out new products riddled with bugs rather than fix the existing products on the market.

So for me, it will be EK Predator with a predator GPU and a motherboard with RGB headers.


1 members found this post helpful.
  #8  
Old 07-27-2016, 09:23 AM
panos7 panos7 is offline
Registered User
panos7's PC Specs
 
Join Date: Jul 2016
Posts: 7
POST ID # = 864355
panos7 Reputation: 10
Default



uhmm...sry..why CL4 v4.2.4.25 is dead..?It does completely nothing...
can't install it....gg corsair for the software and... the bugs...


1 members found this post helpful.
  #9  
Old 07-27-2016, 12:54 PM
ACP ACP is offline
Registered User
ACP's PC Specs
 
Join Date: Nov 2012
Posts: 79
POST ID # = 864388
ACP Reputation: 10
Default

So does HWinfo and Aida64 now play nice with CL4? or will I still experience both applications conflicting with eachother?


  #10  
Old 07-27-2016, 04:31 PM
DelBoyJamie DelBoyJamie is offline
Registered User
DelBoyJamie's PC Specs
 
Join Date: Mar 2016
Location: Under Your Bed
Posts: 27
POST ID # = 864414
DelBoyJamie Reputation: 16
Thumbs down

Quote:
Originally Posted by red-ray View Post
I reported this as a CL 4.2.3.41 bug and Corsair failed to fix it, see http://forum.corsair.com/forums/showthread.php?p=854759.

They fixed -ve X, but not -ve Y

Corsair should publish a list of known outstanding issues and this has been requested on many occasions. Corsair failing to provide this is unprofessional.
I'll be really honest with you I've been watching what you do for a long time Ray and we would love to have someone like you helping out with issues. Its getting ridiculous and I find it disgusting that they don't respond to you. Corsair (I know you more than likely will not care) I WILL NOT BE PURCHASING ANY FURTHER CORSAIR PRODUCTS OR RECOMMENDING THEM TO CUSTOMERS. I find is terrible the amount of work this guy does and goes out of his way to help. It says to me as a long time customer I'm 36 years old and I have spent £1000's and £1000's on corsair products. I will no longer be purchasing or recommending products to any of our customers from now on. Why would I when you wont take this guys comments why would you a customer who has no idea and needs help. Or is it because the "generic" reply's "reboot PC or Uninstall and re-install" is the only reply's your good at. When someone like this so complex and descriptive in his reports you guys dont reply?, is this because you don't know how... Maybe.. People may think I'm being stupid. Its the principle. Look back years and years of Red Rays reports and tell me how would you feel. I personally am disgusted. This guy should be applauded, maybe even hired as a technical adviser good knows I think you guys need it...

Last edited by DelBoyJamie; 07-27-2016 at 04:33 PM.


2 members found this post helpful.
  #11  
Old 07-27-2016, 06:28 PM
CircuitWizardry CircuitWizardry is offline
Registered User
 
Join Date: Jun 2014
Posts: 107
POST ID # = 864434
CircuitWizardry Reputation: 21
Default

I bought a H100i many moons ago, mainly because of Corsair Link, and wanted to add some other Link enabled devices. Luckily the other items were out of stock, and shortly after I got the cooler and discovered how well Link worked, I was able to cancel my order for the other items. I would still be waiting for fixes, as many of the issues I saw still remain, while new problems have been introduced.

I suggest that people let their friends know about Corsair Link, so that they are not subjected to the buggy mess that is Corsair Link!


  #12  
Old 07-28-2016, 12:35 PM
ACP ACP is offline
Registered User
ACP's PC Specs
 
Join Date: Nov 2012
Posts: 79
POST ID # = 864570
ACP Reputation: 10
Default

just to add that yes CL4 does with with the latest beta of HWinfo64....I can now monitor my H110i gt and Hx850i temps on my OSD when gaming. Absolutely awesome!


  #13  
Old 07-29-2016, 04:38 AM
RaithK RaithK is offline
Registered User
RaithK's PC Specs
 
Join Date: Mar 2016
Posts: 7
POST ID # = 864667
RaithK Reputation: 10
Default

There still is the bug regarding LEDs blinking when fan speed is not set to constant RPM or percentage.


1 members found this post helpful.
  #14  
Old 07-29-2016, 04:50 AM
red-ray red-ray is offline
Banned
red-ray's PC Specs
 
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,148
POST ID # = 864669
red-ray Reputation: 81
Arrow A link would be good

Quote:
Originally Posted by RaithK View Post
There still is the bug regarding LEDs blinking when fan speed is not set to constant RPM or percentage.
A link would be good. Do you mean the one Corsair specified they would fix on 03-Feb-2015?

Quote:
Originally Posted by Corsair Dustin View Post
I believe it requires a firmware update to be corrected. It should be in the next Corsair Link drop, or the one after.
Quote:
Originally Posted by red-ray View Post
There have been at least 7 CL drops since then .

Last edited by red-ray; 07-29-2016 at 05:17 AM.


  #15  
Old 07-29-2016, 04:55 AM
RaithK RaithK is offline
Registered User
RaithK's PC Specs
 
Join Date: Mar 2016
Posts: 7
POST ID # = 864670
RaithK Reputation: 10
Default

The link to the post is http://forum.corsair.com/forums/showthread.php?t=137364

The response was>
Quote:
Originally Posted by Corsair Dustin View Post
This is a known issue with a fix coming.
and

Quote:
Originally Posted by Corsair Dustin View Post
It's unfortunately a firmware issue with the Commander Mini and the firmware has been difficult for us to fix.


Closed Thread

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 09:45 PM.


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