Jump to content
AIDA64 Discussion Forum
leon_123

Corsair Link conflict with AIDA64 (Corsair H115i)

Recommended Posts

I'm using Corsair H115i AIO Liquid Cooler come with Corsair Link (CL) software to controll the cooler, when I open AIDA64, it report that the fans in the cooler rotate in 900RPM, which is incorrect number because I set fan on Corsair Link always at 1500RPM, and I noticed that its lower 2 fans in the cooler to 900 RPM too, I can't use Corsair Link to change, and the LED on the pump is reset to white too. If only I close it, CL will return to normal and I can gain control the H115i, but sadly everything is reset to default. mad.gif

I think there's some sort of conflict between Corsair Link and the other monitoring software, the two don't play well. How can I fix that?

 

CL version: 4.2.3.41
AIDA64 version: 5.75.3900.

Share this post


Link to post
Share on other sites

We've already implemented the necessary synchronization techniques to make sure AIDA64 can work together with Corsair Link Software. If it still doesn't work as expected, then you can do the following:

1) Disable Asetek sensor support in AIDA64 / main menu / File / Preferences / Stability. That way however you will lose the sensor readings coming from H115i.

2) You can try tweaking the Asetek fan speed value in AIDA64 / main menu / File / Preferences / Hardware Monitoring. You only need to adjust the first percentage value in case you have a single water cooler. You may find a setting that would produce the same RPM output that you've configured in CL Software.

Regards,

Fiery

Share this post


Link to post
Share on other sites

confirmed, Asustek LC sensor support cause complete loss of fan control and disabling of all fan curves through consair link.

 

closing corsair link does not return normal behavior.

 

H80i.

 

so, either no sensors, or no fan control  not much of a choice there.

 

if enabled, fan rpms drop to 780 and stays there, and coolant temp quickly rises over 45c (red zone) under load.

 

what is the corsair link sensor support for if it doesn't do anything?

Share this post


Link to post
Share on other sites

Corsair Link Software keeps evolving, and we're adjusting AIDA64 to suit the latest CL Software version. If you install the latest CL Software and the latest AIDA64, they should be able to work together, without a collision. The next version of CL Software will be even more secure about avoiding collisions.

Corsair Link sensor support refers to the CL Framework. It's when you have a CL Commander central unit and you hook your devices onto it -- rather than hooking up the same devices via direct USB connection. When you have devices connected via USB, the CL Framework is not utilized at all, and so altering the Corsair Link sensor support option does nothing. I know, it's quite confusing that both the CL Software and the CL Framework are called CL, but that's Corsair's choice on the technical term.

Share this post


Link to post
Share on other sites

gotcha, i dont have a commander module, so i guess i can disable it.

 

I am using both the latest Corsait link (4.2.3.41) and the latest aida64 beta (3908).

 

The behavior persists.  I cannot monitor the CL sensors in aida64 without completely disabling all automated and manual fan control within CL.

 

perhaps i need to downgrade the version on one or both?

 

Do you happen to know approx when the next version of CL is due? their forums are awful and rarely have any offical replies. 

Share this post


Link to post
Share on other sites

Have you tried fixing the fan duty cycle (%) value in CL Software, and set the same percentage value as Asetek fan speed value in AIDA64 / main menu / File / Preferences / Hardware Monitoring?

Downgrading is not necessary. I suppose this is a different issue than the "classic" hardware collision. We'll contact Corsair and try to find a solution with them.

Share this post


Link to post
Share on other sites

ill try when i get home. but im trying to use the default or custom fan curves supplied by CL, not a dedicated duty cycle.

 

After re-reading my post, i wanted to clarify.

 

having the aida64 asetek monitor enabled is what disables fan control, not me disabling it to get the sensors to work.  The sensors themself work fine.

Share this post


Link to post
Share on other sites

unfortunately, all setting the fan% in aida64 does is raise the rpm.

 

its still locked in place and wont use the fan curves in CL.

 

im not interested in a static RPM, i want the fan curves to increase and decrease the rpm as needed based on the coolant temp.

Share this post


Link to post
Share on other sites

unfortunately, all setting the fan% in aida64 does is raise the rpm.

 

its still locked in place and wont use the fan curves in CL.

 

im not interested in a static RPM, i want the fan curves to increase and decrease the rpm as needed based on the coolant temp.

Okay, I think I understand the issue now. Currently, due to hardware limitations, AIDA64 can only work with an Asetek based water cooler if you use a fixed duty cycle (%) value. If you use dynamic fan control via CL Software, AIDA64 cannot work with your hardware, since there will be a constant collision between the hardware polling done by CL Software and AIDA64. The synchronization technique that the latest CL Software and the latest AIDA64 use help in every other case but this one. We've already dropped an email to Corsair, explaining this issue. There are multiple solutions fortunately, and hopefully we can pick the one that is suitable for all users. I will keep you posted in this topic, although things may go a bit slow since we're in the middle of summer right now.

Until then, you need to either use a fixed duty cycle value, or disable Asetek LC sensor support in AIDA64 / main menu / File / Preferences / Stability.

Share this post


Link to post
Share on other sites

understood.

 

based on corsair's track record of fixing their own program, im not going to hold my breath.  

 

How hard can it be to expose an interface for an external program to passively read values?  Their own damn software does it.

 

They make outstanding hardware, but they need to hire some real software engineers, not that group of muppets they have coding for them currently.

 

in the mean time, no monitoring for me.

Share this post


Link to post
Share on other sites

understood.

 

based on corsair's track record of fixing their own program, im not going to hold my breath.

We do have a very good relationship with Corsair, so you can definitely expect a resolution for this issue.

 

How hard can it be to expose an interface for an external program to passively read values?  Their own damn software does it.

What you're saying applies to most sensor devices, but Asetek LC based water coolers are the exception from the rule. You cannot just passively read values from them. You have to alter the fan duty cycle (%) value in order for the device to pass back the current fan RPM and pump RPM measurements. It's a very bad design for sure, one of those that are very hard to work with. But we've come up with an idea that we've proposed to Corsair. If they accept it, then there will be a very convenient solution to this issue that would enable any 3rd party software to talk to Asetek based Corsair water coolers without altering the duty cycle setting or even talking to the device directly.

The only problem is -- although this doesn't affect your case -- that such a fix would only help with Asetek LC based water coolers made by Corsair. Competitors making water coolers based on the same Asetek LC hardware (for example: NZXT Kraken) would still suffer from the same issue with their respective manufacturer made software (e.g. NZXT CAM). But that's a case for another day ;)

 

They make outstanding hardware, but they need to hire some real software engineers, not that group of muppets they have coding for them currently.

I know quite a bit about the background of those software development issues that Corsair has been facing in the past few years, and I can tell you one thing for sure: recently they (Corsair management) have made huge strides to fix that. So you can expect their software to greatly improve as time goes by.

Share this post


Link to post
Share on other sites

well, thats certainly good to hear.

 

im guessing you solution involves the corsair driver abstraction layer passing the info rather than trying to read the sensor directly which would obviously only be useful for corsair products..

Share this post


Link to post
Share on other sites

well, thats certainly good to hear.

 

im guessing you solution involves the corsair driver abstraction layer passing the info rather than trying to read the sensor directly which would obviously only be useful for corsair products..

Our idea is to alter Corsair Link Software in a way that it would export the measured values using shared memory or Windows Registry. It would work quite similarly to our existing module in AIDA64 called External Applications. That way only Corsair Link Software would need to talk to Corsair water coolers and other CL compliant Corsair hardware, and 3rd party applications could only talk to Corsair Link Software and wouldn't have to access hardware at all. Very convenient, since that completely eliminates the issues about hardware access collisions. The only problem is: implementing such a feature in Corsair Link Software may be a bit tricky and would require certain development and QA resources on Corsair's part that they may or may not be able to allocate in the short run. We'll of course pester them hard enough to push them over the fence ;)

Share this post


Link to post
Share on other sites

i see the latest beta has "improved support"

 

what does that mean exactly?

 

edit:  looks like you guys fixed the static duty cycle issue.  sweet.  

 

Thanx!

 

This kind of support is why i gladly open my wallet every year to you guys...

Share this post


Link to post
Share on other sites

i see the latest beta has "improved support"

 

what does that mean exactly?

 

edit:  looks like you guys fixed the static duty cycle issue.  sweet.  

 

Thanx!

 

This kind of support is why i gladly open my wallet every year to you guys...

Yes, we've found a way to measure readings on Corsair Hydro water coolers, without having to alter the duty cycle value The only problem is that it only works with the recent versions of Hydro.

Thank you for the feedback and your kind words ;) I'm glad it works on your device.

Share this post


Link to post
Share on other sites

I almost forget about this topic since I was very busy, sorry.

 

Looks like you guy have this issue fixed, glad to here that, I will update AIDA to lasted version and see if the issue solved.

 

I will update the result here.

Share this post


Link to post
Share on other sites

I almost forget about this topic since I was very busy, sorry.

 

Looks like you guy have this issue fixed, glad to here that, I will update AIDA to lasted version and see if the issue solved.

 

I will update the result here.

Make sure to update Corsair Link Software to its latest version too.

Share this post


Link to post
Share on other sites

Got it, I have to manualy download the beta version, because I'm using the latest stable version. But are there any diffenrences between stable and beta version?

 

Anyway, issue resolved, good work. ;)

 

G5Z1Jt8.png

Share this post


Link to post
Share on other sites

Yes, the beta version is the best one for Corsair water coolers :) And if you prefer to use the latest beta over the latest stable version, then you can enable it in AIDA64 / main menu / File / Preferences / General / NetUpdate.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...