Corsair Link Support

[Fiery]

Hmm, so it is not the power that PSU draws from the wall.

Corsair Link shows two different powers - incoming (draw from outlet) and outgoing (what computer is using) and difference between these two (efficiency). 

Can you make Aida64 do the same ?

PSU efficiency is calculated using a proprietary (and not public) formula by manufacturers' software like Corsair Link Software, Enermax Digifanless Software, Thermaltake DPSApp, etc. Since it's not actually measured, we believe it's not an accurate and scientific way of providing incoming power draw measurement. That's why we're not pursuing finding out how those formulas work. Especially since the formula is not only specific to a certain series of PSUs (like Corsair AXi), but also different across PSU models inside a series. So for example, there's a formula for AX760i, and a different one has to be used for AX1500i.

[ANUBIS]

Ok, thanks for explaining.

There is another thing - Aida64 reports two different temperature readings from my PSU (RM1000i) According to manufacturer there should be only one temperature sensor - Corsair Link also shows one temperature. What are the two temperatures, and which one is the right one ?

(Power Supply #1, Power Suply #2)

[Fiery]

Both temperatures are right and valid. I don't know what they refer to exactly, but they are both valid.

[ANUBIS]

Ok, thanks. No more questions for now. I just have to wait until Corsair Link sortware is made compatible with Aida64.

Everything else regarding PSU (RM1000i) and Aida64 is working well for me.

[Fiery]

Thank you Now the fanspeed appears in the sensor page when the fan is active and the entry is removed when the fanspeed is 0rpm. But the readings are now correct. But there is still a small problem if you want to map the sensor reading to a Logitech LCD display you have to push the button when its not active.

So it would be great if AIDA64 can show the fanspeed for the PSU in the sensor-page even when the fan is stopped.

We've fixed that issue in the latest AIDA64 beta update:

http://www.aida64.com/downloads/latesta64xebeta

Please let me know how it works

[Steven77nl]

I can also report that my AX1200i is not able to provide the current (A) and power (W) usage for the 5v supply (also not in the Corsair Link Software). I understood its a firmware issue and that is something Corsair will need to fix.

But still I would like to be able to see the total power usage of my AX1200i, so that I can feed it to my Logitech keyboard LCD screen. And reading this topic this seems to be a challenge to get this working, but still I would like to try to give my input to this.

 

SIV is able to show this information and also if I run a Corsair Link Dump from AIDA64 I can see these values back in the dump that was created. I have done the debug and the screenshot at the same time, so values can be compared.

I have added the debug dump and screenshot to this post.

 

These values are for sure my Output W and Supply W:

Bank #0 / Pkt #96 = 8B 08 42 FF = 278.000 W

Bank #0 / Pkt #97 = 4B 10 F1 FF = 300.000 W

 

Anything you can do with this information to get these sensors work ?

 

Also I got a AX860i in another computer and that one reads out fine with AIDA64 btw

(Voltage, Current, Power for all voltages including the total)

I connected that one in the same computer, connected to the same Corsair Link Commander Mini.

So its not a conflict with other software that the AX1200i is not working

 

Hope this will help getting it working

DebugCorsairLink.txt

[Fiery]

Pkt #96 is simply the rail power, not the total power of the PSU. Bank #0 / Pkt #96 is the +12V power, Bank #1 / Pkt #96 is the +5V power, and Bank #2 / Pkt #96 is the +3.3V power. Those power values however are less accurate than when you take the rail voltage and rail current, and multiply them to get the calculated rail power. That's why AIDA64 ignores Pkt #96 values.

And BTW, when current cannot be measured due to firmware issues, Pkt #96 also indicates zero Watts. So when it comes to total PSU power measurement, it wouldn't help to switch to using Pkt #96

[Steven77nl]

Thanks, that cleared some things up for me.

Every bank is for a different rail, so bank #3 is for the -12v rail.

 

But now... I don't give up  ... sorry

 

If I put all 4 bank next to each other and compare them, then most Pkt#'s are nearly the same.

I would say they are the same, but just because of of the short time in between reading those 4 banks you get small differences.

Presume these must have the global values for the PSU.

 

So what about Pkt #88 and #89 ?

These are voltage and current... can't you calculate the correct PSU's power input from this ?

 

Also I can connect my AX860i as well again (with a power meter between the wall socket and the PSU) and do some more comparison if you like.

[Steven77nl]

This weekend I have been playing a bit more with the software.

I bought the software last week because I wanted it to feed sensor information to my Aquaero 6 and my logitech Keyboard LCD screen.

So far I still think its a great piece of software and I would like to have it completely replace any other sensor software that I am using.

Though there are still a few things that I am missing,

 

- As mentioned in my previous post, I don't see the current belonging to PSU input voltage (#89 ?)

 

- When connecting 2 PSU's, I would expect to see a 'Power Supply #1' and a 'Power Supply #2', for all sensor types, but I only see one.

SIV shows information of both of them.

 

- Sensor information given for the Power Supply input voltage can not be selected to be used for external applications and as LCD sensor input.

Its available in the sensor page, but not in the list that you can select for your LCD or external applications.

 

- And this might be more a feature request, but it would be nice that we can add a few virtual sensors on which you can do configurable calculations on selected existing sensors.  Free for anyone to configure as they wish.

For example:

vSensor #1 = difference between 'Temperature #2' and 'Temperature #5'

(for example to show the delta-T of watercooled systems)

vSensor #2 = average of 'Temperature #4' and 'Temperature #6' and optional 'Temperature #7'

​(for example to show a average of the internal temperature)

vSensor #3 = total of 'GPU1: GPU VRM Power' + GPU2: GPU VRM Power' + GPU3: GPU VRM Power'

(for example to show the total power usage of all GPU's)

 

Screenshots and CorsairLinkDump are attached again.

 

corsairlinkdump.txt

[Fiery]

So what about Pkt #88 and #89 ?

These are voltage and current... can't you calculate the correct PSU's power input from this ?

No, since by multiplying those values the resulting Wattage amount is constantly lower than if you add up the power draw amounts for the individual voltage rails. In your case for example, Pkt#88 x Pkt#89 is around 310 Watts, but the sum amount of power drawn by the voltage rails is cca. 318 Watts.

[Fiery]

When connecting 2 PSU's, I would expect to see a 'Power Supply #1' and a 'Power Supply #2', for all sensor types, but I only see one.

AIDA64 supports one PSU. We don't plan to support multiple PSUs, since it is a very-very rare usage scenario among AIDA64 users.

 

Sensor information given for the Power Supply input voltage can not be selected to be used for external applications and as LCD sensor input.

Its available in the sensor page, but not in the list that you can select for your LCD or external applications.

We've fixed that in the latest AIDA64 beta update available at:

http://www.aida64.com/downloads/latesta64xebeta

 

And this might be more a feature request, but it would be nice that we can add a few virtual sensors [...]

That's certainly an interesting idea, but it is just as challenging and complicated to make happen as it sounds intruiging We may implement it, but definitely not in the near future.

[Steven77nl]

No, since by multiplying those values the resulting Wattage amount is constantly lower than if you add up the power draw amounts for the individual voltage rails. In your case for example, Pkt#88 x Pkt#89 is around 310 Watts, but the sum amount of power drawn by the voltage rails is cca. 318 Watts.

 

Then I am happy to say that my PSU is very power efficient.

It's giving move power than it takes 

 

AIDA64 supports one PSU. We don't plan to support multiple PSUs, since it is a very-very rare usage scenario among AIDA64 users.

 

Unfortunately, but understandable.

I only got 2 PSU's connected to my Corsair Link Commander Mini because I got 2 computers build in a stack-able case. I will disconnect the second one again.

 

We've fixed that in the latest AIDA64 beta update available at:

 

Great  Thanks !!

I have tested it and it works for me.

 

I do noticed that the sensor screen is refreshing a lot now.

I counted and its not the same time in between every refresh, but at least less than 10 seconds.

It makes the 'Sensor' window scroll back to the top every time, thus it makes reading values lower in the list almost impossible.

 

Still would like to see the power Supply 'current' as well 

 

That's certainly an interesting idea, but it is just as challenging and complicated to make happen as it sounds intruiging We may implement it, but definitely not in the near future.

 

I work in the IT as well, so I know you love a challenge. 

I will bug you about the progress later this year 

[Fiery]

I do noticed that the sensor screen is refreshing a lot now.

I counted and its not the same time in between every refresh, but at least less than 10 seconds.

It makes the 'Sensor' window scroll back to the top every time, thus it makes reading values lower in the list almost impossible.

Such issue usually comes up when a value disappears and then reappears in the list of sensor items. Can you see which value is the culprit on your system?

[Steven77nl]

Such issue usually comes up when a value disappears and then reappears in the list of sensor items. Can you see which value is the culprit on your system?

 

Today it doesn't seem to be doing it. 

If it does happen again, then I will find out which sensor and will let you know.

 

[edit]

 

It started again, but I have found the bugger that is bugging me.

It was a fan set to run at a certain water temperature, but the controller curve was too sensitive and the water stayed exactly at that temperature, so my fan power kept pulsing.

I changed the controller curve and now its fine.

 

Thanks for the support !

It made me find the issue real quick.

[Steven77nl]

No, since by multiplying those values the resulting Wattage amount is constantly lower than if you add up the power draw amounts for the individual voltage rails. In your case for example, Pkt#88 x Pkt#89 is around 310 Watts, but the sum amount of power drawn by the voltage rails is cca. 318 Watts.

 

Sorry for being so persistent, but still I would like to be able to see more sensor information about my Corsair link devices. Seeing what the sensor debug dump is giving, so much more are possible to show to us.

 

Yes I understand now that if you would calculated up all sensor information from all devices/sources that you don't end up with the total that the Corsair Link sensors are giving, but I don's think that's an reason to leave out those sensors in a program like yours. In the end, its still hardware sensor information.

You are now able to read out all Corsair hardware sensor information from the Corsair Link devices, so why not show them ? In the end, it's sensor information.

 

And if its really a problem that you only want to show(in your eyes) correct information, then just make an option where people can tick a check box saying:

"I understand that not all hardware sensor are showing me accurate information, but I agree that I know this and won't sue you" 

 

There are enough people mentioning that also temperature differences are noticed between a hardware sensor against using a temperature gun and your not leaving those temperatures out either.

 

My reason for testing and basically buying your product within days was that it was able to read the the Corsair Link hardware sensors, sending the information to my Aquaero 6 and showing it on my Logitech keyboard.

I was under the impression it just read all hardware sensors, but now it seems that you are not showing/sending it when you don't trust a sensor output.

 

So again, please leave the decisions to trust the output (or not) to us (the users) and just show them all when we confirm that we agree on this.

As you are already able to read the information, I don't see to much of a problem to also show it when we wish.

SIV does the same and I know its not right, but I don't care and its better than nothing. I rather see a approach to reality than nothing.

 

Thx !

[Fiery]

Even if there are exceptions from the rule, it's still a rule. We simply don't want to show such information to users that obviously doesn't add up, that looks wrong or incorrect from the get-go. From day one we wanted to design AIDA64 to make it as user-friendly as possible. Not to overwhelm users with endless amount of information, not to show ridiculous or hard-to-understand readings. That's why we keep working hard to implement motherboard-specific sensor adjustments for example. In that process we remove those readings that look suspicious, that are obviously due to a non-connected sensor rail, etc. You could bring up a case on that too, like why don't we show a 128 Celsius reading for the 3rd motherboard temperature sensor input. Afterall, it is a sensor reading...

Back to the actual issue. Let's say we implement the readings that don't add up. Why would you trust a reading that doesn't add up? Why would you want to monitor such a reading? It's like keeping a close eye on an obviously wrong +12V voltage rail reading that shows a fluctuating value between +7.2V and +8.5V. Why would you want to monitor that?

As for the screenshot... Do you think it's possible that the +5V rail draws 0 Ampers? If you think it can be correct, then the whole calculation of adding up +3.3V, +5V, +12V and -12V power can be implemented in AIDA64 even if one of the rails indicate 0 Ampers. We don't do that right now simply because it doesn't seem to be correct, even if Corsair's own software shows it. If there's a firmware issue of measuring +5V rail current, and Corsair's own software is not prepared to properly handle it, then even CL Software can show nonsense But we here at FinalWire don't like showing nonsense.

[red-ray]

I expect the AXi powers not adding up is an issue with either the firmware or hardware within the PSU. I have posted on the Corsair forum about this several times and finally for a reply, see http://forum.corsair.com/forums/showthread.php?p=845107.

 

There are also limitations in the PWM power controllers and any +3.3 / +5.0 / +12.0 / PCIe currents < 4.5 amps (AX1500i+AX1200i) or < 3.0 amps (AX860i+AX760i) get reported as zero.

[MasterJochen]

Hi im new to AIDA64, 

i got my brand new corsair 1500i today and it runs fine its connected to a internal usb hub in my pc wich is connected directly to my rog asus Maximus VI Formula. Now here is my problem i dont know where to find the values of the PSU . I didnt installl the software offered by corsair since i read it could conflict with AIDA64 but in AIDA64 i cant find any values. HEre is the dump file:

------[ AIDA64 Extreme v5.75.3900 ]------

------[ Microsoft Windows 10 Home 10.0.10586.494 (64-bit) ]------

------[ Motherboard Info ]------

Motherboard ID      : 63-0100-000001-00101111-041312-Chipset$1AQQW031_BIOS DATE: 08/15/14 17:22:17 VER: 16.03
Motherboard Model   : Asus Maximus VI Formula
Motherboard Chipset : Intel Lynx Point Z87, Intel Haswell

DMI MB Manufacturer : ASUSTeK COMPUTER INC.
DMI MB Product      : MAXIMUS VI FORMULA
DMI MB Version      : Rev 1.xx
DMI MB Serial       : 131118281400097
DMI SYS Manufacturer: ASUS
DMI SYS Product     : All Series
DMI SYS Version     : System Version
DMI SYS Serial      : System Serial Number
DMI BIOS Version    : 1603


------[ DevClass / Human Interface Devices ]------

<DESC>HID-konformes Benutzersteuergerät</DESC><DEVPATH>\\?\hid#vid_046d&pid_c32b&mi_01&col02#7&61c1938&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C32B&MI_01&COL02\7&61C1938&0&0001</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>00000006</ADDR><REV>9202</REV>
<DESC>HID-konformes, vom Hersteller definiertes Gerät</DESC><DEVPATH>\\?\hid#vid_046d&pid_c32b&mi_01&col03#7&61c1938&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C32B&MI_01&COL03\7&61C1938&0&0002</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>00000006</ADDR><REV>9202</REV>
<DESC>HID-konformes Benutzersteuergerät</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_01&col01#8&d31f35b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_01&COL01\8&D31F35B&0&0000</INSTANCE><BUSNUM>00000004</BUSNUM><ADDR>00000003</ADDR><REV>0002</REV>
<DESC>HID-konformes, vom Hersteller definiertes Gerät</DESC><DEVPATH>\\?\hid#vid_046d&pid_c32b&mi_01&col04#7&61c1938&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C32B&MI_01&COL04\7&61C1938&0&0003</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>00000006</ADDR><REV>9202</REV>
<DESC>HID-konformer Systemcontroller</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_01&col02#8&d31f35b&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_01&COL02\8&D31F35B&0&0001</INSTANCE><BUSNUM>00000004</BUSNUM><ADDR>00000003</ADDR><REV>0002</REV>
<DESC>HID-Tastatur</DESC><DEVPATH>\\?\hid#vid_1e7d&pid_2e22&mi_01#8&356a11ef&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1E7D&PID_2E22&MI_01\8&356A11EF&0&0000</INSTANCE><BUSNUM>00000008</BUSNUM><ADDR>00000002</ADDR><REV>0101</REV>
<DESC>HID-Tastatur</DESC><DEVPATH>\\?\hid#vid_046d&pid_c232#2&6bacd57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C232\2&6BACD57&0&0000</INSTANCE><BUSNUM>0000000A</BUSNUM>
<DESC>HID-konformes Gerät</DESC><DEVPATH>\\?\hid#vid_1d34&pid_0004#7&2fe3733d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1D34&PID_0004\7&2FE3733D&0&0000</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000004</ADDR><REV>0002</REV>
<DESC>HID-konforme Maus</DESC><DEVPATH>\\?\hid#vid_046d&pid_c231#2&e9c483e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C231\2&E9C483E&0&0000</INSTANCE><BUSNUM>0000000B</BUSNUM>
<DESC>HID-Tastatur</DESC><DEVPATH>\\?\hid#vid_046d&pid_c32b&mi_00#7&2e86c701&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C32B&MI_00\7&2E86C701&0&0000</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000005</ADDR><REV>9202</REV>
<DESC>HID-konformes, vom Hersteller definiertes Gerät</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f00a#7&4e53038&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F00A\7&4E53038&0&0000</INSTANCE><BUSNUM>00000002</BUSNUM><ADDR>00000004</ADDR><REV>0002</REV>
<DESC>HID-konforme Maus</DESC><DEVPATH>\\?\hid#vid_1e7d&pid_2e22&mi_00&col01#8&1192d42d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1E7D&PID_2E22&MI_00&COL01\8&1192D42D&0&0000</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR>00000001</ADDR><REV>0101</REV>
<DESC>HID-Tastatur</DESC><DEVPATH>\\?\hid#vid_046d&pid_c32b&mi_01&col01#7&61c1938&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C32B&MI_01&COL01\7&61C1938&0&0000</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>00000006</ADDR><REV>9202</REV>
<DESC>HID-konformes Benutzersteuergerät</DESC><DEVPATH>\\?\hid#vid_1e7d&pid_2e22&mi_00&col02#8&1192d42d&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1E7D&PID_2E22&MI_00&COL02\8&1192D42D&0&0001</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR>00000001</ADDR><REV>0101</REV>
<DESC>HID-Tastatur</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_00&col01#8&20620f99&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_00&COL01\8&20620F99&0&0000</INSTANCE><BUSNUM>00000003</BUSNUM><ADDR>00000002</ADDR><REV>0002</REV>
<DESC>HID-konformes Benutzersteuergerät</DESC><DEVPATH>\\?\hid#vid_12ba&pid_00ff&mi_02#7&2ca8588f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_12BA&PID_00FF&MI_02\7&2CA8588F&0&0000</INSTANCE><BUSNUM>00000009</BUSNUM><ADDR>0000000F</ADDR><REV>0100</REV>
<DESC>HID-konformes Gerät</DESC><DEVPATH>\\?\hid#vid_1e7d&pid_2e22&mi_00&col03#8&1192d42d&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1E7D&PID_2E22&MI_00&COL03\8&1192D42D&0&0002</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR>00000001</ADDR><REV>0101</REV>
<DESC>HID-konforme Maus</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_00&col02#8&20620f99&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_00&COL02\8&20620F99&0&0001</INSTANCE><BUSNUM>00000003</BUSNUM><ADDR>00000002</ADDR><REV>0002</REV>
<DESC>HID-konformes, vom Hersteller definiertes Gerät</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_02#8&359ca124&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_02\8&359CA124&0&0000</INSTANCE><BUSNUM>00000005</BUSNUM><ADDR>00000004</ADDR><REV>0002</REV>
<DESC>HID-konformes Gerät</DESC><DEVPATH>\\?\hid#vid_1e7d&pid_2e22&mi_00&col04#8&1192d42d&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1E7D&PID_2E22&MI_00&COL04\8&1192D42D&0&0003</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR>00000001</ADDR><REV>0101</REV>

------[ DevClass / USBXpress Devices ]------

< No USBXpress Device Found >

< No Corsair Link Device Found >

Could the usb hub be the problem? What else could i check for? 

[Fiery]

Hi im new to AIDA64, 

i got my brand new corsair 1500i today and it runs fine its connected to a internal usb hub in my pc wich is connected directly to my rog asus Maximus VI Formula. Now here is my problem i dont know where to find the values of the PSU . I didnt installl the software offered by corsair since i read it could conflict with AIDA64 but in AIDA64 i cant find any values. HEre is the dump file:

...

Could the usb hub be the problem? What else could i check for?

If it's an AX1500i PSU, then you need to install its driver, which is part of Corsair Link Software. Feel free to install Corsair Link, it's now synchronized with AIDA64 You only need to make sure to use the latest version of both AIDA64 and Corsair Link Software. You need to install:

- AIDA64 v5.75.3930 (latest beta build)

- Corsair Link Software v4.2.4.25 (latest build)

They will not collide on your system anymore.

[MasterJochen]

thanks man

[namuk]

There is a new link build out now i.e 4.5.0.55 and it solves bugs on the corsair side 

[Fiery]

17 hours ago, namuk said:

There is a new link build out now i.e 4.5.0.55 and it solves bugs on the corsair side 

Thank you, I'm glad things are going in the right direction