Jump to content
Corsair Community

Discuss Link v4.2.4.25 here


Technobeard

Recommended Posts

  • Administrators

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.

 

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

Link to comment
Share on other sites

  • Replies 68
  • Created
  • Last Reply
  • 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 :mad:.

 

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.

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:

 

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 :(:.

 

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.

 

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.

Link to comment
Share on other sites

  • 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 :biggrin:.
  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 :biggrin:.
  5. With all of AIDA64, HWiNFO and SIV active CL 4.2.4.25 totally failed to report any of my DIMMs :eek:.
  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 :asskick:.
  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 :sigh!:.

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 :o:.
  3. I contacted the CPUID SDK developers and worked with them to look into why :cool:.
  4. We figured out the root cause of the issue and fixed it :biggrin:.
  5. I expect this issue will be fixed once Corsair release a new CL4 with the corrected CPUID SDK :nodding:.
  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 :laughcry:.

attachment.php?attachmentid=25964&stc=1&d=1469511766

attachment.php?attachmentid=25966&stc=1&d=1469514014

attachment.php?attachmentid=25967&stc=1&d=1469515687

1255154559_OnlytwoofeightDIMMsreported.thumb.png.9b18d63069f06f07e2376b9913b269ca.png

793065290_AIDA64reportedeightofeight.thumb.png.2ec5007652c29d0bab6e839410cc0be0.png

1117808750_CL4.2.4.25failedtoreportanyDIMMs!.thumb.png.4a742d115968208f9287920162cdcc12.png

Link to comment
Share on other sites

  • 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.

 

attachment.php?attachmentid=25969&stc=1&d=1469518045

181499850_CL4.2.4.25highDPClatencies.thumb.png.f9ea49b5df384a283bbf56411f5a578c.png

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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 :eek:

 

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

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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 :eek:

 

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...

Link to comment
Share on other sites

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!

Link to comment
Share on other sites

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?

 

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 :(:.
Link to comment
Share on other sites

The response was>

 

Some Corsair responses don't seem to add up and I wonder how accurate they are ;):.

 

I logged the http://forum.corsair.com/forums/showthread.php?t=134621 firmware issue as ticket #6560108 and one response is:

 

Created By: J**** TS (5/27/2015 2:06 PM)

 

There is a new firmware in the works that is currently undergoing testing.

 

Why has not been released after 14 months?

Link to comment
Share on other sites

Two things you really must get into the next release (and I'm boycotting any further Corsair hardware purchases until you at least promise to do them at some point in the not too distant future!):

 

1. The ability to switch fans off as well as to control their speed. It is completely ridiculous that this feature is missing as anybody buying a fan speed controller would expect to be able to switch a fan off with it! Furthermore are you artificially limiting the control range? I bought a pair of ML120 fans which are specified to have a control range of 2000RPM, but the range I actually get with Corsair Link is only 750-2320RPM (1570RPM range).

 

2. Proper support for the RMi series PSUs. Why can we see power in and power out, voltage and current on each DC rail and calculated efficiency, but ONLY on the specific device display off the home page? It is just idiotic that only the fan speed and the temperature are implemented on the integrated Configure display, when all this wealth of information is already available within the program. How much effort can it be to implement the rest of the virtual indicators?

 

Corsair makes great hardware and the ability of Corsair Link to display live indicators over a picture of the user's system is brilliant. But these are continually being let down by stupid limitations and slow pace of development in Corsair Link, and this is getting to the point were a trades descriptions act prosecution would be in order - you cannot go on advertising features when the user cannot actually use them since they've not been implemented in the software!

Link to comment
Share on other sites

Two things you really must get into the next release (and I'm boycotting any further Corsair hardware purchases until you at least promise to do them at some point in the not too distant future!):

 

1. The ability to switch fans off as well as to control their speed. It is completely ridiculous that this feature is missing as anybody buying a fan speed controller would expect to be able to switch a fan off with it! Furthermore are you artificially limiting the control range? I bought a pair of ML120 fans which are specified to have a control range of 2000RPM, but the range I actually get with Corsair Link is only 750-2320RPM (1570RPM range).

 

2. Proper support for the RMi series PSUs. Why can we see power in and power out, voltage and current on each DC rail and calculated efficiency, but ONLY on the specific device display off the home page? It is just idiotic that only the fan speed and the temperature are implemented on the integrated Configure display, when all this wealth of information is already available within the program. How much effort can it be to implement the rest of the virtual indicators?

 

Corsair makes great hardware and the ability of Corsair Link to display live indicators over a picture of the user's system is brilliant. But these are continually being let down by stupid limitations and slow pace of development in Corsair Link, and this is getting to the point were a trades descriptions act prosecution would be in order - you cannot go on advertising features when the user cannot actually use them since they've not been implemented in the software!

 

i am not defending corsair, just check my post, even i got bad experience with their H80i cooler, but

 

1. there only few people, if not only you that wanting the fan off feature

did you ever know how the RPM fan works ?

what they marketing is 2000RPM fan-speed not feature that you can control any rpm in 2000range

 

i am curious why you wanting to turn off fan, if for noise reason, at the lowest step (750rpm?) you should barely hear it

and for fan lifespan, like other motorize device, most said it better to keep spinning rather than on/off.

 

 

2. i am not really sure what you mean, but you want those power out, voltage in home/main screen?

its just one click away to see those right ?

but for this, i think, its would be great if corsair support API for their corsair link service, not sure if they already did or not

with that, we can pull off data to own made program or desktop custom software like rainmeter

Link to comment
Share on other sites

i am not defending corsair, just check my post, even i got bad experience with their H80i cooler, but

 

  1. there only few people, if not only you that wanting the fan off feature did you ever know how the RPM fan works ?
  2. i am not really sure what you mean, but you want those power out, voltage in home/main screen?
  3. its just one click away to see those right ?
  4. it would be great if corsair support API for their corsair link service, not sure if they already did or not

 

Yes you are, your post lacks structure and I can't check your post as you failed to link to it. To reply at all I needed to give it structure and in general you need to include links or quotes to justify your opinions.

 

  1. Had you checked you would have found there are lots who would like CL Mini zero RPM support and they would also like all the existing CL Mini firmware issues addressed. Corsair say they will release firmware corrections then fail to do this, see http://forum.corsair.com/forums/showthread.php?p=864676, the firmware section in http://forum.corsair.com/forums/showthread.php?p=864149 and follow the links. Some firmware issues have been outstanding since 20-Nov-2014 which is appalling.
  2. It's obvious. All the values that are available on the PSU details screen should be available on the [Configure] tab. CL4 should have had this from day one and I am at a loss as to why it did not. Corsair have also failed to respond to my post asking for this.
  3. Incorrect. From the [Configure] tab it's two clicks, further to get back to [Configure] is also two clicks and on this system it takes over 15 seconds to go from the [Home] to [Configure] tab which is way too long. Corsair have also failed to respond to my post about this.
  4. There is currently no Corsair Link API that provides sensor information.
  5. PSUs have zero RPM support so clearly zero RPM is sensible.
  6. There is no way for you to know this, but the posts requesting zero RPM support are just the tip of the iceberg and I have lost count of the number of requests I have had to add CL Mini zero RPM support to SIV. Obviously I can't do this as the CL Mini firmware fails to support it.

 

48. Only my AX1500i + AX760i PSU Temp and fan speed are available on [Configure]. All the PSU information should be, epically so for the Power and Efficiency.

6. When I switch from [Home] to [Configure] it takes about 15 seconds when I have all my CL hardware connected. This is far longer than is acceptable.

Zero RPM Fan Mode for silent operation at low and medium loads

http://www.corsair.com/en-gb/~/media/113E9E77EFE1446EB8BD9444165E3A7F.ashx?w=240

Link to comment
Share on other sites

Just built new system and it died .... but have reinstalled Win10 and link software and noticed that it doesnt display the M.2 Samsung 950 drive. Just put my SSD's back on and it shows them....funny thing is it shows my Corsair SSD at 30C but my Samsung 850 at 19C

Its not a worry or anything just thought I would post it here

Link to comment
Share on other sites

noticed that it doesnt display the M.2 Samsung 950 drive.

 

Basically CL4 uses the CPUID SDK to get disk temperatures and it did not support NVMe drives such as your Samsung 950 'till yesterday.

 

I know this as I was working with Franck to resolve CPUID SDK HWM issues I had on my system, mentioned NVMe to him and gave him some of the SIV NVMe code. I have a test version of HWM that reports my NVMe disk drive temperature.

 

The net effect should be that the next CL4 release should have NVMe support without Corsair needing to do anything at all to the CL4 code, so should actually happen :biggrin:.

 

If Corsair released the latest build of C:\Program Files (x86)\CorsairLink4\cpuidsdk.dll NVMe reporting would work for all existing CL4 releases.

Link to comment
Share on other sites

 

1. there only few people, if not only you that wanting the fan off feature

did you ever know how the RPM fan works ?

what they marketing is 2000RPM fan-speed not feature that you can control any rpm in 2000range

 

i am curious why you wanting to turn off fan, if for noise reason, at the lowest step (750rpm?) you should barely hear it

and for fan lifespan, like other motorize device, most said it better to keep spinning rather than on/off.

 

 

2. i am not really sure what you mean, but you want those power out, voltage in home/main screen?

its just one click away to see those right ?

but for this, i think, its would be great if corsair support API for their corsair link service, not sure if they already did or not

with that, we can pull off data to own made program or desktop custom software like rainmeter

 

@red-ray has already answered most points better than I could, but a few additional points and amplifications:

 

1. It does not make sense to frequently switch fans on and off, but with a modern PC it does make sense to have fans that are off most of the time and only come on when the PC is really stressed like doing a render. Ideally there'd be a hysteresis or minimum on time setting, but lets walk before we climb.

 

Check out the ML spec: ML120 PRO. Quote: "Extensive Control Range. A 2,000 RPM control range gives you total control between low noise and absolute performance". Clearly implies a 2000 RPM difference between the stall speed and the maximum speed.

 

I am controlling my fans from an H80i Liquid Cooler with an extra cable to allow control of 4 fans. I do not have a CL mini, so if zero-speed is a firmware limitation it is in multiple products. I suspect that CL software takes a least-common-denominator approach and none of us will get this feature until all can use it.

 

2 The good feature in CL, which keeps me using it rather than experimenting with alternatives, is the Configure (SIC) view which enables you to monitor all relevant parameters together on on display overlaid on a picture of your actual system so you can place virtual indicators in the relevant location. It is completely stupid that FOR CORSAIR's OWN HARDWARE it does not allow display of all the measurements that the hardware offers. I appreciate it is difficult to get data into the program, particularly from third-party hardware, but for goodness sakes when you've done the hard part why place artificial restrictions on what can be done with the data?

 

Here's mine:

 

attachment.php?attachmentid=26037&stc=1&d=1469880397

 

(Picture taken before I substituted ML fans above and below the radiator)

 

Now how much nicer and more useful would that be if I could overlay the total Watts (a good proxy for how much heat will be generated, so an excellent fan control input), Efficiency and Amps for each output voltage?

PCB_028.thumb.png.011b695a6a321697df6fce3bdd0a3240.png

Link to comment
Share on other sites

Now how much nicer and more useful would that be if I could overlay the total Watts (a good proxy for how much heat will be generated, so an excellent fan control input), Efficiency and Amps for each output voltage?

 

I just don't get how Corsair did not do this from day one. When I added LCD support to SIV it would have been harder not to have all the PSU information available!

 

CL4 should also have different user specified colours for low, medium and high values just as SIV does.

 

attachment.php?attachmentid=26038&stc=1&d=1469882879attachment.php?attachmentid=26039&stc=1&d=1469883347

1755853371_AX1500iPSUInformation.png.6be1e6132481eda3fa631154b6a26add.png

24073857_AX1500iPSULCDSetup.png.cf05f62a5c48d2446f04871f2a363009.png

Link to comment
Share on other sites

Am i suppose to see my ram(s) temperature through CL link?

 

I do not get RAM temperature despite having Corsair memory (type CMY16GX3M2A1600C9). I guess it depends on having a temperature sensor on the RAM stick. I do not see that for these memory chips in other software either.

Link to comment
Share on other sites

Archived

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


×
×
  • Create New...