evanmulawski / fancontrol.corsairlink Goto Github PK

Hello,

I just added the plugin to fancontrol for my corsair system utilizing a commander pro, H115i Platinum cpu cooler, and a HX1000i PSU.

I am new to fancontrol and was able to use your plugin to control the case fans that are connected to the commander pro however I am not seeing anything come up for the H115i or HX1000i.

Any support would be appreciated. Thanks

From #76, #78, #127, #130

When a Hydro Platinum device read fails multiple times, iCUE reboots the device:

https://forum.corsair.com/forums/topic/176494-corsair-h100i-platinum-se-randomly-stops-and-restarts/
https://forum.corsair.com/forums/topic/171275-hydro-h100i-connectingdisconnecting/

Implement reboot logic when a read fails by sending the reboot packet.

Notes:

• Based on an observation in #78, the device accepts writes and adjusts pump/fan speeds accordingly even when this issue occurs (implies only reads fail).

I'm geting this warning in the log file using the [v1.3.0-beta.4] version.

2023-07-31T22:06:59.3157235Z [WRN] Device Enumeration: Failed to enumerate SiUsbXpress devices.
2023-07-31T22:07:32.0381218Z [INF] HID Device Manager: Found 0 Corsair HID device(s)

I have the H115i Platinum AIO and NO corsair services installed and running, also, i'm using the .net 4.8 version of fancontrol.

Therefore, any sensors are loaded into Fancontrol

I've tried a few different version of the release versions but can not find a file called 'FanControl.CorsairLink.dll'. Closest I can find is 'FanControl.CorsairLink.csproj' or 'FanControl.CorsairLink.sln'.

OpenRGB needs to implement the well-known Corsair mutex that provides compatibility with other software. This was added for Commander CORE devices in commit 6c8da3a0.

I have opened a merge request that improves it and updates existing Corsair RGB controllers to use it.

If you want to use OpenRGB with the CorsairLink Fan Control plugin, please upvote and comment on the merge request!

Now Available

See the comment below.

Your readme says that this plugin is compatible with SingalRGB v 2.2.29+. In my experience that is not the case. As soon as I start SingnalRGB v2.2.32 my COmmander Pro temperature sensors go haywire, the reading will alternate between something that seems to be the correct temperature, 0 C, and NaN. I'm attaching the log but it doesn't say anything as nothing is logged when this is happening.

My temperature sensors recover as soon as I stop SignalRGB, so no reboot was needed.

log.txt

Followed all the installation instructions on a fresh install of Fan Control. Closed iCUE and terminated all services in task manager before starting Fan Control.

usbdeview entry for my setup

CORSAIR iCUE Commander CORE USB Composite Device Unknown Yes Yes No No 630f0001801ccabae51f2af52091005f 2023-01-15 1:18:31 PM 2023-01-12 6:31:57 PM 1b1c 0c1c 1.00 00 00 00 JAMIE-PC 6&26eb1bce&0 usbccgp @usb.inf,%GenericParent.SvcDesc%;Microsoft USB Generic Parent Driver usbccgp.sys (Standard USB Host Controller) 100 mA 2.00 USB Composite Device 10.0.25276.1000 Composite.Dev.NT usb.inf USB\VID_1B1C&PID_0C1C\630f0001801ccabae51f2af52091005f Removable, UniqueID, SurpriseRemovalOK

device-variant
Corsair Hydro Series H115i Extreme
USB\VID_1B1C&PID_0C0A\7289_2.0

Support for AXi-series PSUs is currently in progress. If you would like to help test development builds, please leave a comment with your AXi model (e.g. AX1600i) and the hardware product ID (PID) (e.g. 1c11). To find your hardware product ID, ensure your device is connected via USB and use Device Manager or USBDeview.

/cc @Superino45 @EduardoPimentel

Sometimes PUMP and FAN on Corsair H115i Pro stuck at average speed and not going below them. After a while, only restarting FanControl can fix this.

2023-08-18T19:26:29.3478316Z [INF] HID Device Manager: Found 0 Corsair HID device(s)

2023-08-18T19:26:29.3493176Z [INF] HID Device Manager: Found 0 supported Corsair HID device(s)

2023-08-18T19:26:29.3632017Z [INF] SiUsbXpress Device Manager: Found 1 Corsair SiUsbXpress device(s)
  name=Corsair H115i Pro, devicePath=\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}

2023-08-18T19:26:29.3637024Z [INF] SiUsbXpress Device Manager: Found 1 supported Corsair SiUsbXpress device(s)
  name=Corsair H115i Pro, devicePath=\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}

2023-08-18T19:26:29.3862451Z [INF] Device Initialization: \\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}
2023-08-18T19:26:29.3876693Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Firmware Version: 1.0.4.0
2023-08-18T19:26:29.3881908Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Sensor: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/SpeedSensor/-1
2023-08-18T19:26:29.3881908Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Sensor: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/SpeedSensor/0
2023-08-18T19:26:29.3881908Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Sensor: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/SpeedSensor/1
2023-08-18T19:26:29.3891830Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Sensor: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/TemperatureSensor/-1
2023-08-18T19:26:29.3896829Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Controller: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/SpeedController/-1
2023-08-18T19:26:29.3896829Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Controller: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/SpeedController/0
2023-08-18T19:26:29.3896829Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Controller: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/SpeedController/1
2023-08-18T19:30:00.3106075Z [INF] HID Device Manager: Found 0 Corsair HID device(s)

2023-08-18T19:30:00.3125890Z [INF] HID Device Manager: Found 0 supported Corsair HID device(s)

2023-08-18T19:30:00.3249880Z [INF] SiUsbXpress Device Manager: Found 1 Corsair SiUsbXpress device(s)
  name=Corsair H115i Pro, devicePath=\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}

2023-08-18T19:30:00.3254839Z [INF] SiUsbXpress Device Manager: Found 1 supported Corsair SiUsbXpress device(s)
  name=Corsair H115i Pro, devicePath=\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}

2023-08-18T19:30:00.3490707Z [INF] Device Initialization: \\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}
2023-08-18T19:30:00.3500372Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Firmware Version: 1.0.4.0
2023-08-18T19:30:00.3510574Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Sensor: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/SpeedSensor/-1
2023-08-18T19:30:00.3510574Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Sensor: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/SpeedSensor/0
2023-08-18T19:30:00.3510574Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Sensor: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/SpeedSensor/1
2023-08-18T19:30:00.3515489Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Sensor: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/TemperatureSensor/-1
2023-08-18T19:30:00.3525479Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Controller: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/SpeedController/-1
2023-08-18T19:30:00.3525479Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Controller: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/SpeedController/0
2023-08-18T19:30:00.3525479Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Controller: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/SpeedController/1

Normal

Stuck

Describe the bug
My configuration uses a temperature sensor connected to a Commander Pro to report loop coolant temperature, and controls fan speed based on that temp. Every few seconds, all temperature readings from the Commander Pro either shift to 0C or NaN. As it does this, the fans ramp down as it thinks the temp is 0C. The sensor reading returns but then shifts back a few seconds later. Video of the phenomena is linked below. I've tried downgrading to V158 as well as replacing the Corsair Link DLL. I normally don't have iCue installed, but shutting down Fan Control and installing Corsair iCue yields constant temperature readings without issue.

Is there a log.txt file next to FanControl.exe with recent date entries?
log.txt

Relevant hardware specs and setup
Intel Core I7 13700KF
ASUS Prime Z790M-Plus D4
32 GB Oloy 3200 MTs
RTX 3080 Vector FTW3

Video: https://github.com/Rem0o/FanControl.Releases/assets/136206652/8f79af9e-a515-48b1-b4bb-1cdba772a3f2

I use the CorsairLink plugin, but I sometimes get this error:

Where do I set that variable? I have looked in all editable files in my FanControl directory but I cannot find anywhere to add it.

Even with the error, all my fans are still detected and respond to my fan curves, I just don't want the errors disturbing me.

Im running a Hydro H100i GT V2 (0c09) AOI and using the 1.4.0-Beta-1 version of the plugin. It is able to detect my RM750i, but not my AOI. It's using non-stock fans (Noctua), but i can't see pumps speed, temperatures of fan speeds at all. I'v added the CorsairLink.log file to the issue. In the logs there's no mention of my cooler at all

CorsairLink.zip

Any idea's why this might be the case?

I have a Commander Pro and I've tried multiple releases and none of them work as the plugin fails to initialize and load any sensors. I'm still stuck having to use the original and now abandoned CommanderPro plugin, which has also started to act up to the point I need to restart the main app over and over until it finally works. I'm attaching the log, if you need anything else let me know so we can get this choo-chooing along!

Using version: Latest 1.1
FanControl: 1.47 Framework

iCue has been kicked the curb so there is no way this should be interfering.

log.txt

Unfortunately it's not working for me. Here's a bit of logging:

20-1-2023 14:48:51: [CorsairLink] DeviceManager: Found 3 Corsair device(s)
  name=LCD Cap for Elite Capellix coolers, devicePath=\\?\hid#vid_1b1c&pid_0c39#7&2544036e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
  name=CORSAIR iCUE COMMANDER Core, devicePath=\\?\hid#vid_1b1c&pid_0c32&mi_00#8&12b9ba96&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
  name=CORSAIR iCUE COMMANDER Core, devicePath=\\?\hid#vid_1b1c&pid_0c32&mi_01#8&2a7d46db&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

20-1-2023 14:48:51: [CorsairLink] DeviceManager: Found 1 supported Corsair device(s)
  name=CORSAIR iCUE COMMANDER Core, devicePath=\\?\hid#vid_1b1c&pid_0c32&mi_00#8&12b9ba96&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

20-1-2023 14:48:51: [CorsairLink] An exception occurred attempting to initialize device 'CORSAIR iCUE COMMANDER Core (205537824242)' (\\?\hid#vid_1b1c&pid_0c32&mi_00#8&12b9ba96&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}):
20-1-2023 14:48:51: [CorsairLink] System.IO.IOException: Operation failed early: The parameter is incorrect ---> System.ComponentModel.Win32Exception: The parameter is incorrect
   --- End of inner exception stack trace ---
   at HidSharp.Platform.Windows.NativeMethods.OverlappedOperation(IntPtr ioHandle, IntPtr eventHandle, Int32 eventTimeout, IntPtr closeEventHandle, Boolean overlapResult, NativeOverlapped* overlapped, UInt32& bytesTransferred)
   at HidSharp.Platform.Windows.WinHidStream.Write(Byte[] buffer, Int32 offset, Int32 count)
   at CorsairLink.CommanderCoreDevice.SendCommand(ReadOnlySpan`1 command, ReadOnlySpan`1 data)
   at CorsairLink.CommanderCoreDevice.Initialize()
   at CorsairLink.CommanderCoreDevice.Connect()
   at FanControl.CorsairLink.CorsairLinkPlugin.FanControl.Plugins.IPlugin.Initialize()

AC V143, and the beta-4 release
It's the commander that came with the H170i and one that came with the 7000d case.

Maybe I'm doing something wrong? If you need more info, feel free to msg me. Thanks for making this!

Originally posted by @bjongbloed in #1 (reply in thread)

I commented on a similar bug on the github repo of FanControl, but looking at the logs it seems to be totally a CorsairLink issue, do you have a clue what is causing FanControl to fully stop after these states? Makes the application totally useless unless I want to restart each time one of these states happens

log_12.txt
log_14.txt

Hi,

I am using the Version 159 (Net 4.8) from Fan Control. In my setup, I have a Corsair elite lcd xt with the included commander core, where I connected 6 fans (both the speed & lightning cables).

After putting the plugin in the folder and starting FanControl, the hardware lightning from the 6 fans connected to the commander core turns off, but I am able to control the pump and the fans:

The Corsair service is not running (I tried this even before installing iCue).

I also tried both with the version 1.1.2 and the 1.2.0-beta.2 from this plugin, but same result.

I checked the error log, but it does not seem helpful:

12/06/2023 20:24:00: [CorsairLink] DeviceManager: Found 17 Corsair device(s)
name=, devicePath=\?\hid#virtualdevice&10&col01#2&d21ad2d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col03#8&3a46e5c5&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col04#8&3a46e5c5&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col05#8&3a46e5c5&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=, devicePath=\?\hid#virtualdevice&10&col02#2&d21ad2d&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
name=, devicePath=\?\hid#virtualdevice&10&col04#2&d21ad2d&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col01#8&3a46e5c5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
name=, devicePath=\?\hid#virtualdevice&10&col03#2&d21ad2d&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
name=Corsair ST100 Headset Outpu�t, devicePath=\?\hid#vid_1b1c&pid_0a32&mi_03#c&1a5a5122&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=, devicePath=\?\hid#virtualdevice&10&col05#2&d21ad2d&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=Lighting Node PRO, devicePath=\?\hid#vid_1b1c&pid_0c0b#b&1fbbda6b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col02#8&3a46e5c5&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=LCD Cap for Elite Capellix coolers, devicePath=\?\hid#vid_1b1c&pid_0c33#b&2be4c9b1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_01#8&22835980&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=Corsair ST100 LED Driver, devicePath=\?\hid#vid_1b1c&pid_0a34#b&31d24af4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR iCUE COMMANDER Core, devicePath=\?\hid#vid_1b1c&pid_0c32&mi_01#c&1169e095&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR iCUE COMMANDER Core, devicePath=\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

12/06/2023 20:24:00: [CorsairLink] DeviceManager: Found 1 supported Corsair device(s)
name=CORSAIR iCUE COMMANDER Core, devicePath=\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

12/06/2023 20:24:00: [CorsairLink] Device 'CORSAIR iCUE COMMANDER Core (207F33A7534B)' (\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, FW: 2.0.19):
12/06/2023 20:24:00: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/0
12/06/2023 20:24:00: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/1
12/06/2023 20:24:00: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/2
12/06/2023 20:24:00: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/3
12/06/2023 20:24:00: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/4
12/06/2023 20:24:00: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/5
12/06/2023 20:24:00: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/6
12/06/2023 20:24:00: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/0
12/06/2023 20:24:00: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/1
12/06/2023 20:24:00: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/2
12/06/2023 20:24:00: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/3
12/06/2023 20:24:00: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/4
12/06/2023 20:24:00: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/5
12/06/2023 20:24:00: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/6
12/06/2023 20:24:00: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/TemperatureSensor/0
12/06/2023 20:24:00: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/TemperatureSensor/1
12/06/2023 20:25:15: [CorsairLink] DeviceManager: Found 17 Corsair device(s)
name=, devicePath=\?\hid#virtualdevice&10&col01#2&d21ad2d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col03#8&3a46e5c5&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col04#8&3a46e5c5&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col05#8&3a46e5c5&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=, devicePath=\?\hid#virtualdevice&10&col02#2&d21ad2d&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
name=, devicePath=\?\hid#virtualdevice&10&col04#2&d21ad2d&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col01#8&3a46e5c5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
name=, devicePath=\?\hid#virtualdevice&10&col03#2&d21ad2d&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
name=Corsair ST100 Headset Outpu�t, devicePath=\?\hid#vid_1b1c&pid_0a32&mi_03#c&1a5a5122&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=, devicePath=\?\hid#virtualdevice&10&col05#2&d21ad2d&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=Lighting Node PRO, devicePath=\?\hid#vid_1b1c&pid_0c0b#b&1fbbda6b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col02#8&3a46e5c5&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=LCD Cap for Elite Capellix coolers, devicePath=\?\hid#vid_1b1c&pid_0c33#b&2be4c9b1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_01#8&22835980&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=Corsair ST100 LED Driver, devicePath=\?\hid#vid_1b1c&pid_0a34#b&31d24af4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR iCUE COMMANDER Core, devicePath=\?\hid#vid_1b1c&pid_0c32&mi_01#c&1169e095&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR iCUE COMMANDER Core, devicePath=\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

12/06/2023 20:25:15: [CorsairLink] DeviceManager: Found 1 supported Corsair device(s)
name=CORSAIR iCUE COMMANDER Core, devicePath=\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

12/06/2023 20:25:15: [CorsairLink] Device 'CORSAIR iCUE COMMANDER Core (207F33A7534B)' (\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, FW: 2.0.19):
12/06/2023 20:25:15: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/0
12/06/2023 20:25:15: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/1
12/06/2023 20:25:15: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/2
12/06/2023 20:25:15: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/3
12/06/2023 20:25:15: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/4
12/06/2023 20:25:15: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/5
12/06/2023 20:25:15: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/6
12/06/2023 20:25:15: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/0
12/06/2023 20:25:15: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/1
12/06/2023 20:25:15: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/2
12/06/2023 20:25:15: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/3
12/06/2023 20:25:15: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/4
12/06/2023 20:25:15: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/5
12/06/2023 20:25:15: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/6
12/06/2023 20:25:15: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/TemperatureSensor/0
12/06/2023 20:25:15: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/TemperatureSensor/1
12/06/2023 20:25:22: [CorsairLink] DeviceManager: Found 17 Corsair device(s)
name=, devicePath=\?\hid#virtualdevice&10&col01#2&d21ad2d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col03#8&3a46e5c5&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col04#8&3a46e5c5&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col05#8&3a46e5c5&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=, devicePath=\?\hid#virtualdevice&10&col02#2&d21ad2d&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
name=, devicePath=\?\hid#virtualdevice&10&col04#2&d21ad2d&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col01#8&3a46e5c5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
name=, devicePath=\?\hid#virtualdevice&10&col03#2&d21ad2d&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
name=Corsair ST100 Headset Outpu�t, devicePath=\?\hid#vid_1b1c&pid_0a32&mi_03#c&1a5a5122&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=, devicePath=\?\hid#virtualdevice&10&col05#2&d21ad2d&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=Lighting Node PRO, devicePath=\?\hid#vid_1b1c&pid_0c0b#b&1fbbda6b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col02#8&3a46e5c5&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=LCD Cap for Elite Capellix coolers, devicePath=\?\hid#vid_1b1c&pid_0c33#b&2be4c9b1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_01#8&22835980&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=Corsair ST100 LED Driver, devicePath=\?\hid#vid_1b1c&pid_0a34#b&31d24af4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR iCUE COMMANDER Core, devicePath=\?\hid#vid_1b1c&pid_0c32&mi_01#c&1169e095&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR iCUE COMMANDER Core, devicePath=\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

12/06/2023 20:25:22: [CorsairLink] DeviceManager: Found 1 supported Corsair device(s)
name=CORSAIR iCUE COMMANDER Core, devicePath=\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

12/06/2023 20:25:22: [CorsairLink] Device 'CORSAIR iCUE COMMANDER Core (207F33A7534B)' (\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, FW: 2.0.19):
12/06/2023 20:25:22: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/0
12/06/2023 20:25:22: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/1
12/06/2023 20:25:22: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/2
12/06/2023 20:25:22: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/3
12/06/2023 20:25:22: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/4
12/06/2023 20:25:22: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/5
12/06/2023 20:25:22: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/6
12/06/2023 20:25:22: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/0
12/06/2023 20:25:22: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/1
12/06/2023 20:25:22: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/2
12/06/2023 20:25:22: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/3
12/06/2023 20:25:22: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/4
12/06/2023 20:25:22: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/5
12/06/2023 20:25:22: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/6
12/06/2023 20:25:22: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/TemperatureSensor/0
12/06/2023 20:25:22: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/TemperatureSensor/1
12/06/2023 20:28:21: [CorsairLink] DeviceManager: Found 17 Corsair device(s)
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col02#8&3a46e5c5&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col03#8&3a46e5c5&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=Lighting Node PRO, devicePath=\?\hid#vid_1b1c&pid_0c0b#b&1fbbda6b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=, devicePath=\?\hid#virtualdevice&10&col03#2&d21ad2d&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col04#8&3a46e5c5&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col05#8&3a46e5c5&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=LCD Cap for Elite Capellix coolers, devicePath=\?\hid#vid_1b1c&pid_0c33#b&2be4c9b1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=, devicePath=\?\hid#virtualdevice&10&col04#2&d21ad2d&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=, devicePath=\?\hid#virtualdevice&10&col02#2&d21ad2d&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
name=Corsair ST100 Headset Outpu�t, devicePath=\?\hid#vid_1b1c&pid_0a32&mi_03#c&1a5a5122&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=Corsair ST100 LED Driver, devicePath=\?\hid#vid_1b1c&pid_0a34#b&31d24af4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=, devicePath=\?\hid#virtualdevice&10&col05#2&d21ad2d&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_01#8&22835980&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=, devicePath=\?\hid#virtualdevice&10&col01#2&d21ad2d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col01#8&3a46e5c5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
name=CORSAIR iCUE COMMANDER Core, devicePath=\?\hid#vid_1b1c&pid_0c32&mi_01#c&1169e095&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR iCUE COMMANDER Core, devicePath=\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

12/06/2023 20:28:21: [CorsairLink] DeviceManager: Found 1 supported Corsair device(s)
name=CORSAIR iCUE COMMANDER Core, devicePath=\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

12/06/2023 20:28:21: [CorsairLink] Device 'CORSAIR iCUE COMMANDER Core (207F33A7534B)' (\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, FW: 2.0.19):
12/06/2023 20:28:21: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/0
12/06/2023 20:28:21: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/1
12/06/2023 20:28:21: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/2
12/06/2023 20:28:21: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/3
12/06/2023 20:28:21: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/4
12/06/2023 20:28:21: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/5
12/06/2023 20:28:21: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/6
12/06/2023 20:28:21: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/0
12/06/2023 20:28:21: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/1
12/06/2023 20:28:21: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/2
12/06/2023 20:28:21: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/3
12/06/2023 20:28:21: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/4
12/06/2023 20:28:21: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/5
12/06/2023 20:28:21: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/6
12/06/2023 20:28:21: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/TemperatureSensor/0
12/06/2023 20:28:21: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/TemperatureSensor/1
12/06/2023 20:30:51: [CorsairLink] DeviceManager: Found 17 Corsair device(s)
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col02#8&3a46e5c5&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col01#8&3a46e5c5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
name=, devicePath=\?\hid#virtualdevice&10&col03#2&d21ad2d&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col03#8&3a46e5c5&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col05#8&3a46e5c5&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_00&col04#8&3a46e5c5&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=, devicePath=\?\hid#virtualdevice&10&col04#2&d21ad2d&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=LCD Cap for Elite Capellix coolers, devicePath=\?\hid#vid_1b1c&pid_0c33#b&2be4c9b1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=, devicePath=\?\hid#virtualdevice&10&col02#2&d21ad2d&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
name=, devicePath=\?\hid#virtualdevice&10&col05#2&d21ad2d&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=Corsair ST100 Headset Outpu�t, devicePath=\?\hid#vid_1b1c&pid_0a32&mi_03#c&1a5a5122&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=Lighting Node PRO, devicePath=\?\hid#vid_1b1c&pid_0c0b#b&1fbbda6b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=Corsair ST100 LED Driver, devicePath=\?\hid#vid_1b1c&pid_0a34#b&31d24af4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard, devicePath=\?\hid#vid_1b1c&pid_1b49&mi_01#8&22835980&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=, devicePath=\?\hid#virtualdevice&10&col01#2&d21ad2d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR iCUE COMMANDER Core, devicePath=\?\hid#vid_1b1c&pid_0c32&mi_01#c&1169e095&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
name=CORSAIR iCUE COMMANDER Core, devicePath=\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

12/06/2023 20:30:51: [CorsairLink] DeviceManager: Found 1 supported Corsair device(s)
name=CORSAIR iCUE COMMANDER Core, devicePath=\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

12/06/2023 20:30:51: [CorsairLink] Device 'CORSAIR iCUE COMMANDER Core (207F33A7534B)' (\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, FW: 2.0.19):
12/06/2023 20:30:51: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/0
12/06/2023 20:30:51: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/1
12/06/2023 20:30:51: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/2
12/06/2023 20:30:51: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/3
12/06/2023 20:30:51: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/4
12/06/2023 20:30:51: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/5
12/06/2023 20:30:51: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedSensor/6
12/06/2023 20:30:51: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/0
12/06/2023 20:30:51: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/1
12/06/2023 20:30:51: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/2
12/06/2023 20:30:51: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/3
12/06/2023 20:30:51: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/4
12/06/2023 20:30:51: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/5
12/06/2023 20:30:51: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/SpeedController/6
12/06/2023 20:30:51: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/TemperatureSensor/0
12/06/2023 20:30:51: [CorsairLink] added CorsairLink/\?\hid#vid_1b1c&pid_0c32&mi_00#c&35411e57&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}/TemperatureSensor/1

Just left my system running for a few hours with v1.4.0-beta.4, I've now noticed the cooler's fans are running as slow as they possibly can. Totally ignoring my fan curves.

I've restarted FanControl and they ramp up to the correct speeds set in my curves, but then they slowly fall down to ~600rpm.

New log:
Log & Desktop Capture.zip

I've also attached a screen capture of what happens when I load FanControl with v1.4.0-beta.4. You can see the front fans ramp up to their correct speeds, then they slowly go back down to ~600rpm as described above.

I have reverted back to the build you sent above (called v20230831r001.zip) and all fans respond perfectly.

Originally posted by @Meh7991 in #47 (comment)

Hi there.

I do not know what or who to blame here. I'm entirely clueless.

I have a H100i Platinum, a 680X Case with a Commander and its 3 fans + 3 QL and its Commander.
They failed to show up anymore in FanControl. I have issues for a few weeks now since it started to throw an error reading like "CorsairLink failed to initialize or has no sensor". Then, FanControl just wouldn't be able to detect or use any of my fans except my GPU. "Expected 14x sensors, found 3x". Using v147 as it seems to be the only version that, somehow, keeps my CPU cool.

If dev is active, I'm willing to elaborate or share all the old logs I have since the last couple of weeks. (500MB+)
Cheers.

Hey there,

I am having the same behaviour as in issue (#2), though I believe it's a different exception:

I've attached the logs.
I've tried the latest Release (v 1.0.0) as well as the latest beta release.

I have ensured both zip's and dll's are unblocked as per the instructions. Please let me know if I can help in any way.

Corsair Commander PRO could not initialize or has no sensors.
2/26/2023 12:10:12 PM: [CorsairLink] DeviceManager: Found 2 Corsair device(s)
  name=CORSAIR iCUE Commander CORE, devicePath=\\?\hid#vid_1b1c&pid_0c1c&mi_01#7&26ae1e37&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
  name=CORSAIR iCUE Commander CORE, devicePath=\\?\hid#vid_1b1c&pid_0c1c&mi_00#7&2d6e075&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

2/26/2023 12:10:12 PM: [CorsairLink] DeviceManager: Found 1 supported Corsair device(s)
  name=CORSAIR iCUE Commander CORE, devicePath=\\?\hid#vid_1b1c&pid_0c1c&mi_00#7&2d6e075&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

2/26/2023 12:10:12 PM: [CorsairLink] An exception occurred attempting to initialize device 'CORSAIR iCUE Commander CORE (e20f10a0948871aa8559c2063091005f)' (\\?\hid#vid_1b1c&pid_0c1c&mi_00#7&2d6e075&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}):
2/26/2023 12:10:12 PM: [CorsairLink] System.TypeInitializationException: The type initializer for 'CorsairLink.Synchronization.CorsairDevicesGuard' threw an exception.
 ---> System.MissingMethodException: Method not found: 'Void System.Threading.Mutex.SetAccessControl(System.Security.AccessControl.MutexSecurity)'.
   at CorsairLink.Synchronization.CorsairDevicesGuard.CreateMutex()
   at CorsairLink.Synchronization.CorsairDevicesGuard..cctor()
   --- End of inner exception stack trace ---
   at CorsairLink.Synchronization.CorsairDevicesGuard.Acquire()
   at CorsairLink.Synchronization.CorsairDevicesGuardLock..ctor()
   at CorsairLink.Synchronization.CorsairDevicesGuardManager.AwaitExclusiveAccess()
   at CorsairLink.CommanderCoreDevice.RefreshImpl(Boolean initialize)
   at CorsairLink.CommanderCoreDevice.Connect()
   at FanControl.CorsairLink.CorsairLinkPlugin.FanControl.Plugins.IPlugin.Initialize()
2/26/2023 12:10:14 PM: [CorsairLink] DeviceManager: Found 2 Corsair device(s)
  name=CORSAIR iCUE Commander CORE, devicePath=\\?\hid#vid_1b1c&pid_0c1c&mi_01#7&26ae1e37&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
  name=CORSAIR iCUE Commander CORE, devicePath=\\?\hid#vid_1b1c&pid_0c1c&mi_00#7&2d6e075&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}```

Hi Evan

I think I found a bug/ unwanted behavior with the corsair PSU control you added in the latest BETA.

When switching between 2 FanControl profiles that have a different % for the PSU fan, the PSU looses its ability to control it properly.

As an example, if profile 1 is set to 30% (560rpm) and profile 2 is set to 40% (740rpm), the initial load of profile 1 goes as expected (0rpm to 560rpm). If I switch to profile 2 (expected 740rpm), the fan ramp up to 880rpm (equivalent to 50%) despite showing 40% in FanControl.

Changing back to profile 1, the fan still stay at 880rpm (50%). At this point, it seems like the scaling of % vs rpm is completely off (ex 100% is now 1300rpm instead of 1500rpm, the unit will refuse to go below 880rpm). Also, turning the fan off will work, but will not fix the issue... The unit will go back to the same behavior if set from 1-100%. Only closing FanControl and starting it again will make the control go back to normal.

From my testing, I think you initialize the software control of the unit at 50% right? I noticed because when starting FanControl with a 30% value (550rpm), the fan goes from 0 to 880rpm then goes back to the set 30% (560rpm). Would it be possible to initialize at duty cycle value (30%)?

Another problem has occurred, device does not respond after PC wakes up from sleep mode, tried running iCUE, no response either, only works after reboot PC.

2023-08-28T00:16:40.4182978Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower -1 30%
2023-08-28T00:16:40.4182978Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower 0 30%
2023-08-28T00:16:40.4182978Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower 1 30%
2023-08-28T00:16:41.4278733Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WriteRequestedSpeeds
2023-08-28T00:16:41.4278733Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): GetLiquidTemperature
2023-08-28T00:16:41.4278733Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: A9
2023-08-28T00:16:41.4278733Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  A901002304
2023-08-28T00:16:41.4278733Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): GetPumpRpm
2023-08-28T00:16:41.4278733Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: 31
2023-08-28T00:16:41.4288705Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  3101000564
2023-08-28T00:16:41.4288705Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): GetFanRpm 0
2023-08-28T00:16:41.4288705Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: 4100
2023-08-28T00:16:41.4288705Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  410100000130
2023-08-28T00:16:41.4288705Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): GetFanRpm 1
2023-08-28T00:16:41.4288705Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: 4101
2023-08-28T00:16:41.4288705Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  410100010136
2023-08-28T00:16:41.4298681Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): STATE
Requested power for channel -1: 30 %
Requested power for channel 0: 30 %
Requested power for channel 1: 30 %
Pump (channel: -1, controllable: True): 1380 RPM
Fan #1 (channel: 0, controllable: True): 304 RPM
Fan #2 (channel: 1, controllable: True): 310 RPM
Liquid Temp (channel: -1): 35,4 C

2023-08-28T00:16:41.4458252Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower -1 30%
2023-08-28T00:16:41.4458252Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower 0 30%
2023-08-28T00:16:41.4458252Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower 1 30%
2023-08-28T00:16:42.4435017Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WriteRequestedSpeeds
2023-08-28T00:16:42.4435017Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetPumpPower 30%
2023-08-28T00:16:42.4435017Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: 301E
2023-08-28T00:16:42.4573736Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower -1 30%
2023-08-28T00:16:42.4573736Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower 0 30%
2023-08-28T00:16:42.4573736Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower 1 30%
2023-08-28T09:08:42.9066459Z [WRN] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): An error occurred refreshing device 'Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3)' (\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}):
2023-08-28T09:08:42.9814451Z [ERR] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): 
Type: CorsairLink.SiUsbXpress.Driver.SiUsbXpressDriverException
Message: Driver operation failed.
Source: FanControl.CorsairLink
Stack Trace:
   в CorsairLink.SiUsbXpress.Driver.SiUsbXpressDevice.WriteInternal(Byte[] data)
   в CorsairLink.SiUsbXpress.Driver.SiUsbXpressDevice.WriteAndRead(Byte[] buffer)
   в CorsairLink.Devices.HydroAsetekProDevice.WriteAndRead(Byte[] buffer)
   в CorsairLink.Devices.HydroAsetekProDevice.SetPumpPower(Byte percent)
   в CorsairLink.Devices.HydroAsetekProDevice.WriteRequestedSpeeds()
   в CorsairLink.Devices.HydroAsetekProDevice.Refresh()
   в FanControl.CorsairLink.CorsairLinkPlugin.Refresh()
Data:
    driverStatus: SI_WRITE_ERROR

2023-08-28T09:08:42.9814451Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WriteRequestedSpeeds
2023-08-28T09:08:42.9814451Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): GetLiquidTemperature
2023-08-28T09:08:42.9814451Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: A9
2023-08-28T09:08:42.9814451Z [WRN] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): An error occurred refreshing device 'Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3)' (\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}):
2023-08-28T09:08:42.9814451Z [ERR] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): 
Type: CorsairLink.SiUsbXpress.Driver.SiUsbXpressDriverException
Message: Driver operation failed.
Source: FanControl.CorsairLink
Stack Trace:
   в CorsairLink.SiUsbXpress.Driver.SiUsbXpressDevice.WriteInternal(Byte[] data)
   в CorsairLink.SiUsbXpress.Driver.SiUsbXpressDevice.WriteAndRead(Byte[] buffer)
   в CorsairLink.Devices.HydroAsetekProDevice.WriteAndRead(Byte[] buffer)
   в CorsairLink.Devices.HydroAsetekProDevice.GetLiquidTemperature()
   в CorsairLink.Devices.HydroAsetekProDevice.RefreshTemperatures()
   в CorsairLink.Devices.HydroAsetekProDevice.Refresh()
   в FanControl.CorsairLink.CorsairLinkPlugin.Refresh()
Data:
    driverStatus: SI_WRITE_ERROR

2023-08-28T09:08:43.2228019Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower -1 30%
2023-08-28T09:08:43.2228019Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower 0 30%
2023-08-28T09:08:43.2228019Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower 1 30%
2023-08-28T09:08:43.6110651Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WriteRequestedSpeeds
2023-08-28T09:08:43.6110651Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): GetLiquidTemperature
2023-08-28T09:08:43.6110651Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: A9
2023-08-28T09:08:43.6110651Z [WRN] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): An error occurred refreshing device 'Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3)' (\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}):
2023-08-28T09:08:43.6110651Z [ERR] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): 
Type: CorsairLink.SiUsbXpress.Driver.SiUsbXpressDriverException
Message: Driver operation failed.
Source: FanControl.CorsairLink
Stack Trace:
   в CorsairLink.SiUsbXpress.Driver.SiUsbXpressDevice.WriteInternal(Byte[] data)
   в CorsairLink.SiUsbXpress.Driver.SiUsbXpressDevice.WriteAndRead(Byte[] buffer)
   в CorsairLink.Devices.HydroAsetekProDevice.WriteAndRead(Byte[] buffer)
   в CorsairLink.Devices.HydroAsetekProDevice.GetLiquidTemperature()
   в CorsairLink.Devices.HydroAsetekProDevice.RefreshTemperatures()
   в CorsairLink.Devices.HydroAsetekProDevice.Refresh()
   в FanControl.CorsairLink.CorsairLinkPlugin.Refresh()
Data:
    driverStatus: SI_SYSTEM_ERROR_CODE

2023-08-28T09:08:43.6320076Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower -1 30%
2023-08-28T09:08:43.6320076Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower 0 30%
2023-08-28T09:08:43.6320076Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower 1 30%
2023-08-28T09:08:43.9691066Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower -1 50%
2023-08-28T09:08:43.9691066Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower 0 50%
2023-08-28T09:08:43.9691066Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower 1 50%
2023-08-28T09:08:44.0050111Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower -1 50%
2023-08-28T09:08:44.0050111Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower 0 50%
2023-08-28T09:08:44.0050111Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower 1 50%
2023-08-28T09:08:44.0060076Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Disconnect

2023-08-28T09:18:18.2344656Z [DBG] Plugin: Runtime: .NET Framework 4.8.4645.0
2023-08-28T09:18:18.2564079Z [INF] HID Device Manager: Found 0 Corsair HID device(s)

2023-08-28T09:18:18.2584021Z [INF] HID Device Manager: Found 0 supported Corsair HID device(s)

2023-08-28T09:18:18.2713677Z [INF] SiUsbXpress Device Manager: Found 1 Corsair SiUsbXpress device(s)
  name=Corsair H115i Pro, devicePath=\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}

2023-08-28T09:18:18.2713677Z [INF] SiUsbXpress Device Manager: Found 1 supported Corsair SiUsbXpress device(s)
  name=Corsair H115i Pro, devicePath=\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}

2023-08-28T09:18:18.2743626Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Connect
2023-08-28T09:18:18.2743626Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Disconnect
2023-08-28T09:18:18.2811836Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): OverrideSafetyProfile
2023-08-28T09:18:18.2811836Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): OverrideSafetyProfile (test='temp_100_speed_100')
2023-08-28T09:18:18.2841744Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: 4A64636261646464646464646464646464646464C59C
2023-08-28T09:18:18.2870115Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  8F0100
2023-08-28T09:18:18.2870115Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: 4B
2023-08-28T09:18:18.2870115Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  4B01003C3B3A39643C643C643C643C643C643C643C64
2023-08-28T09:18:18.2870115Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): OverrideSafetyProfile (test='temp_60_speed_100')
2023-08-28T09:18:18.2870115Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: 4A3C3B3A39643C643C643C643C643C643C643C647B4A
2023-08-28T09:18:18.3355792Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  4A0100
2023-08-28T09:18:18.3355792Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: 4B
2023-08-28T09:18:18.3363914Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  4B01003C3B3A39643C643C643C643C643C643C643C64
2023-08-28T09:18:18.3363914Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): InitializeSpeedChannelStores
2023-08-28T09:18:18.3373902Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower -1 50%
2023-08-28T09:18:18.3373902Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower 0 50%
2023-08-28T09:18:18.3373902Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower 1 50%
2023-08-28T09:18:18.3383876Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WriteRequestedSpeeds
2023-08-28T09:18:18.3393849Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetPumpPower 50%
2023-08-28T09:18:18.3393849Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: 3032
2023-08-28T09:18:18.3396481Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  300100
2023-08-28T09:18:18.3406370Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetFanPower 0 50%
2023-08-28T09:18:18.3406370Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: 420032
2023-08-28T09:18:18.3414335Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  420100
2023-08-28T09:18:18.3414335Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetFanPower 1 50%
2023-08-28T09:18:18.3414335Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: 420132
2023-08-28T09:18:18.3414335Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  420100
2023-08-28T09:18:18.3423254Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): GetLiquidTemperature
2023-08-28T09:18:18.3423254Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: A9
2023-08-28T09:18:18.3433249Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  A901001A06
2023-08-28T09:18:18.3433249Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): GetPumpRpm
2023-08-28T09:18:18.3433249Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: 31
2023-08-28T09:18:18.3447543Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  3101000546
2023-08-28T09:18:18.3447543Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): GetFanRpm 0
2023-08-28T09:18:18.3447543Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: 4100
2023-08-28T09:18:18.3460940Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  41010000011A
2023-08-28T09:18:18.3460940Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): GetFanRpm 1
2023-08-28T09:18:18.3460940Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: 4101
2023-08-28T09:18:18.3467559Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  41010001012C
2023-08-28T09:18:18.3477719Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): STATE
Requested power for channel -1: 50 %
Requested power for channel 0: 50 %
Requested power for channel 1: 50 %
Pump (channel: -1, controllable: True): 1350 RPM
Fan #1 (channel: 0, controllable: True): 282 RPM
Fan #2 (channel: 1, controllable: True): 300 RPM
Liquid Temp (channel: -1): 26,6 C

2023-08-28T09:18:18.3498025Z [INF] Device Initialization: \\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}
2023-08-28T09:18:18.3498025Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: AA
2023-08-28T09:18:18.3507660Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  AA010001000400
2023-08-28T09:18:18.3507660Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Firmware Version: 1.0.4.0
2023-08-28T09:18:18.3517915Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Sensor: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/SpeedSensor/-1
2023-08-28T09:18:18.3517915Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Sensor: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/SpeedSensor/0
2023-08-28T09:18:18.3517915Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Sensor: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/SpeedSensor/1
2023-08-28T09:18:18.3517915Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Sensor: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/TemperatureSensor/-1
2023-08-28T09:18:18.3527918Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Controller: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/SpeedController/-1
2023-08-28T09:18:18.3527918Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Controller: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/SpeedController/0
2023-08-28T09:18:18.3527918Z [INF] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): Controller: CorsairLink/\\?\usb#vid_1b1c&pid_0c13#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}/SpeedController/1
2023-08-28T09:18:19.3009605Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower -1 50%
2023-08-28T09:18:19.3009605Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower 0 50%
2023-08-28T09:18:19.3009605Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): SetChannelPower 1 50%
2023-08-28T09:18:19.3598036Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WriteRequestedSpeeds
2023-08-28T09:18:19.3598036Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): GetLiquidTemperature
2023-08-28T09:18:19.3598036Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: A9
2023-08-28T09:18:19.3607734Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  A901001A06
2023-08-28T09:18:19.3607734Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): GetPumpRpm
2023-08-28T09:18:19.3607734Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: 31
2023-08-28T09:18:19.3607734Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  3101000726
2023-08-28T09:18:19.3607734Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): GetFanRpm 0
2023-08-28T09:18:19.3607734Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: 4100
2023-08-28T09:18:19.3617977Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  41010000011C
2023-08-28T09:18:19.3617977Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): GetFanRpm 1
2023-08-28T09:18:19.3617977Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): WRITE: 4101
2023-08-28T09:18:19.3617977Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): READ:  41010001012C
2023-08-28T09:18:19.3617977Z [DBG] Corsair H115i Pro (86FAED6661FACCA561FB790C8B97A7F3): STATE
Requested power for channel -1: 50 %
Requested power for channel 0: 50 %
Requested power for channel 1: 50 %
Pump (channel: -1, controllable: True): 1830 RPM
Fan #1 (channel: 0, controllable: True): 284 RPM
Fan #2 (channel: 1, controllable: True): 300 RPM
Liquid Temp (channel: -1): 26,6 C

I need to test this again, maybe it's because start delay 1 sec, trying to increase

Originally posted by @XJIOP in #79 (comment)

I initially could not get the plugin to load at all, then it was working perfectly for a brief time, and is now giving me this error on startup.

CorsairLink.log
log.txt

Hey, I have a Corsair iCUE H115i Elite Capellix and an Asus Z590 Gaming E Motherboard.

I had my FanControl all setup perfectly. Today I was messing around in my BIOS and when I rebooted I got the ["CorsairLink could not initialize or has no sensors" error]. I had changed my Asus Aura setting in my BIOS from "ALL ON" to "STEALTH ONLY". Switching back to "ALL ON" allowed this Plugin to properly read the sensors again! Unsure if this is helpful, but thought I'd chime in.

Log attached just in case.

log.txt

Originally posted by @xTSwizzle in #15 (comment)

I'm having issues with the Temperature sensor readouts, I know that you needed to manually set the fans and that worked great but when adding a temperature sensor to the Commander Pro it displays the temp and it turns on and off every 1 second.

I installed this but seems it doesnt detect any sensors for my Corsair Commander Mini

Was wondering how to go about requesting support for the H150i Pro AIO Cooler from Corsair?

I love using this plugin to manage my fan behaviors (I'm running an ITX system that uses the AIO as an exhaust) but I'm having a strange bug where my H100i Pro XT disconnects randomly. I'm trying to make the switch from iCUE because of how I need the fans to respond to different sensors.

Hardware:
Ryzen 7 3700x
ASUS X570-I Strix
ASUS RTX 3090 TUF
and I have two Corsair devices connected: the H100i Pro XT (0c20) and a K70 LUX keyboard. None of them have any hardware/software RGB lighting profiles (and their default is set to be off). The H100i is set to the Quiet preset, and there are no custom fan curves set. Within Fan Control, the H100i is set at a fixed 30%.

Software/Potential Conflicts:
Windows 10

SignalRGB

• I matched the speed setting to Quiet.

HWinfo64 (installed) v7.60

• I disabled Corsair/Asetek support.

Fan Control v165 .NET 4.8

• I use the CorsairLink plugin (v1.3.0) and the HWinfo plugin (v1.3). I configured Fan Control to be the last software started after all monitoring programs.

I've attached a CorsairLink.log for reference but most of it is full of detection errors despite the device still being shown as connected. For whatever reason, this bug doesn't seem to pop up on any logs since Windows doesn't make the USB disconnection sound, but software reports a timeout when trying to communicate with the AIO. When undetected by CorsairLink, the pump will still run and go to its default settings.

For troubleshooting, I've gone through most possibilities without any success. All of these were tried without iCUE installed.

• Disabled USB selective suspend
• Replugged SATA power
• Replugged microUSB/USB2.0 cable at both ends
• Reinstalled USB drivers
• Reinstalled chipset drivers
• Restarted and reinstalled H100i via Control Panel devices (Control Panel > Hardware and Sound > Devices and Printers)
• Restarted H100i via Device Manager through Human-Interface Devices
• Unchecked the box for "Allow the computer to turn off this device to save power"
  The H100i has a HID-compliant vendor-defined device and a USB Input Device component. I've tried configuring them with no success.
• Uninstalled and restarted USB hubs
• Updated and reinstalled H100i firmware
• Using my PC with and without SignalRGB installed
• Using my PC with and without HWinfo
• Having only FanControl with CorsairLink open
  I would try having none of these programs installed, but Windows wouldn't notify me that the AIO wasn't detected. There would be no way to know if the issue was still happening.

I've considered this being an unsolvable X570 USB dropout issue, but nothing else in the system suffers a performance hit or has stutter during the disconnect. The internal USB 2.0 header has no visible damage and the H100i is isolated on its own USB root hub. Unfortunately, I don't have another internal USB2.0 header/device to isolate the issue.

Right now, I'm running a very janky solution to keep the H100i responding without restarting the whole system. Despite the incompatibilities, I installed iCUE and run it alongside all the previous software (Fan Control with CorsairLink/HWinfo plugins, HWinfo64, SignalRGB). For whatever reason, there aren't any disconnects when only using iCUE and it is the only program that has been able to keep the H100i detected after the disconnect notification from other software. If I have iCUE and everything else open, the disconnects still occur. However, after refreshing the sensor detection with iCUE open, Fan Control picks up the H100i again and everything works normally (RGB responds to effects and pump responds to Fan Control). However, it eventually disconnects and I have to refresh sensor detection.

I'm not sure what else I can do to get this working, but I'm not yet convinced that the whole AIO is defective since iCUE somehow manages to circumvent the entire problem.

Hi there.

I was wondering if it was possible to control my fans via a Commander Core XT. I recently installed new Corsair fans to the front of my case and hooked them up to a Commander Core XT. I also have 3 Corsair fans on my radiator which I've also connected to the XT.

In assisted setup I've ticked Commander Core XT and the fans are appearing with their RPM but aren't responding. I was wondering if it's possible to control them via an XT as I've noticed people controlling them with a Commander Core Pro. Weirdly enough the 6 fans increase in speed when I open FanControl so I'm not sure if there's a background process going on.

It's no biggie if I can't directly control them directly, the XT was more of an experiment on my part and I can hook them back up to their old fan headers.

Thanks.

First off, thank you so much for working on this plugin, I've been wanting a plugin that lets me move away from iCUE for a while and this looks like it'll probably be it. However, I just downloaded your latest release to test with my Commander CORE and whenever I launch FanControl I get the message: CorsairLink could not initialize or has no sensors. This message also shows up in the log.txt file, but with no further details.

I've already checked to make sure that all the Corsair and iCUE services on my PC are stopped, so that shouldn't be the issue. If you need any more information from me please feel free to ask, I really would like to see this work properly.

Request for support added for Hydro H100i GTX | AIO | 0c03 please

Dear Development Team,

I would like to request the addition of support for the Corsair HX850i power supply in the Fan Control plugin. It would be greatly beneficial to be able to control the fans of the power supply, monitor its temperatures, and view the current fan speed.

As a user of Fan Control, I believe this addition would enhance the overall experience for users who have this specific power supply.

Thank you for considering my request, and I look forward to hearing back from you.

Best regards,
Haruki_

Add support for the following devices:

• Hydro H80i GT (0c02)
• Hydro H80i GT V2 (0c08)
• Hydro H80i Pro (0c16)
• Hydro H100i GT V2 (0c09)
• Hydro H100i GTX (0c03)
• Hydro H100i Pro (0c15)
• Hydro H110i GT V2 (0c0a)
• Hydro H110i GTX (0c07)
• Hydro H115i Pro (0c13)
• Hydro H150i Pro (0c12)

The Asetek Hydro AIOs use the same SI USB Xpress driver as the Flex USB PSU devices added in v1.3.0.

Progress:

• Pro variants
• V1 variants
• V2 variants

I am trying to use the commander core link plugin and receive the following for all my fans when using auto setup: no sped control reacted to sensor for fanXX. Only the pump, which is connected to the CPU fan header on the MB, and my GPU fans are detected. All other fans are connected to the commander core. I am using a gigabyte aorus 570s MB. Any ideas? TIA

Discussed in #92

I can confirm that the "SendCommand CRC mismatch" happens even when OpenRGB is totally disabled, and every time my system wakes up from sleep.

Originally posted by @chjohans in #45 (comment)

22/5/2023 06:10:31: [CorsairLink] An exception occurred refreshing device 'H115iRGBPROXT (D288920C757645790248E957911BA8A2)' (\\?\hid#vid_1b1c&pid_0c21#b&1240a30f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}):
22/5/2023 06:10:31: [CorsairLink] CorsairLink.CorsairLinkDeviceException: SendCommand CRC mismatch (device=H115iRGBPROXT (D288920C757645790248E957911BA8A2), data=1400FF05FFFFFFFFFF03FFFFFFFF5703FFFFFFFF5701FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, writeBuf=003FC01400FF05FFFFFFFFFF03FFFFFFFF5703FFFFFFFF5701FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFC8, readBuf=00C120112000AC02F51B14035EE8035EA602035EE8035E060201BF0000BF07090000000000000000000000000000000000000000000000000000000000000000F7, readCrcByte=F7, readBufCrcResult=9B)
   at CorsairLink.HydroDevice.SendCommand(Byte command, ReadOnlySpan`1 data)
   at CorsairLink.HydroDevice.WriteCooling()
   at CorsairLink.HydroDevice.Refresh()
   at FanControl.CorsairLink.CorsairLinkPlugin.OnTimerTick(Object sender, ElapsedEventArgs e)

There's no DLL file for the corsair plugin available to download and extract. Please upload corsair fan control plugin.

CorsairLink.log

Using a H150i Elite RGB AIO.
Occasionally getting a popup window notifying there are errors

I am aware that it's not possible to use this together with Corsair's own iCUE, Corsair simply refuses to "play ball" with others.

But, it is possible to get this to "play nice" with certain other monitoring software that is probably frequently being used by the target group for this plugin.

HWiNFO (https://www.hwinfo.com/) and SIV (http://rh-software.com/) have both implemented a named Mutex locking mechanism that makes sure that only one program will access Corsair devices at any given time. Please consider implementing this, there is some info re this on the SIV board here: https://siv.boards.net/thread/14/running-same-time-corsair-icue, and I know that Ray, the author of SIV, has more info and he's willing to share. At least I know that he has helped others to implement this. Corsair used to use this in their own Link software a few years ago, but dropped it and never implemented it in iCUE. But that didn't stop others from using this.

Please consider this, as it is now HWiNFO will stop reporting values for any Corsair devices that are accessed by this plugin. And, this plugin will stop getting updated data from these devices as well. It would be really useful to be able to run HWiNFO together with FanControl and this otherwise excellent plugin.

I just got home from work and tried the latest build, unfortunately I'm still getting errors. Here is my log.txt. Maybe I'm running a different firmware version.

2023-01-16 7:09:18 PM: [CorsairLink] DeviceManager: Found 7 Corsair device(s)
  name=, devicePath=\\?\hid#virtualdevice&10&col01#2&3b8f46cf&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
  name=, devicePath=\\?\hid#virtualdevice&10&col05#2&3b8f46cf&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}
  name=, devicePath=\\?\hid#virtualdevice&10&col02#2&3b8f46cf&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
  name=, devicePath=\\?\hid#virtualdevice&10&col03#2&3b8f46cf&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
  name=, devicePath=\\?\hid#virtualdevice&10&col04#2&3b8f46cf&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
  name=CORSAIR iCUE Commander CORE, devicePath=\\?\hid#vid_1b1c&pid_0c1c&mi_01#7&387a1dd5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
  name=CORSAIR iCUE Commander CORE, devicePath=\\?\hid#vid_1b1c&pid_0c1c&mi_00#7&20b69190&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

2023-01-16 7:09:18 PM: [CorsairLink] DeviceManager: Found 1 supported Corsair device(s)
  name=CORSAIR iCUE Commander CORE, devicePath=\\?\hid#vid_1b1c&pid_0c1c&mi_00#7&20b69190&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

2023-01-16 7:09:18 PM: [CorsairLink] An exception occurred attempting to initialize device 'CORSAIR iCUE Commander CORE (630f0001801ccabae51f2af52091005f)' (\\?\hid#vid_1b1c&pid_0c1c&mi_00#7&20b69190&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}):
2023-01-16 7:09:18 PM: [CorsairLink] System.FormatException: The response was not valid.
   at CorsairLink.CommanderCoreDevice.EndpointResponse.ThrowIfInvalid()
   at CorsairLink.CommanderCoreDevice.InitializeSpeedChannels(EndpointResponse hardwareFixedSpeedPercentResponse)
   at CorsairLink.CommanderCoreDevice.Initialize()
   at CorsairLink.CommanderCoreDevice.Connect()
   at FanControl.CorsairLink.CorsairLinkPlugin.FanControl.Plugins.IPlugin.Initialize()
2023-01-16 7:09:20 PM: [CorsairLink] DeviceManager: Found 7 Corsair device(s)
  name=, devicePath=\\?\hid#virtualdevice&10&col01#2&3b8f46cf&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
  name=, devicePath=\\?\hid#virtualdevice&10&col05#2&3b8f46cf&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}
  name=, devicePath=\\?\hid#virtualdevice&10&col02#2&3b8f46cf&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
  name=, devicePath=\\?\hid#virtualdevice&10&col03#2&3b8f46cf&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
  name=, devicePath=\\?\hid#virtualdevice&10&col04#2&3b8f46cf&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
  name=CORSAIR iCUE Commander CORE, devicePath=\\?\hid#vid_1b1c&pid_0c1c&mi_01#7&387a1dd5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
  name=CORSAIR iCUE Commander CORE, devicePath=\\?\hid#vid_1b1c&pid_0c1c&mi_00#7&20b69190&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

2023-01-16 7:09:20 PM: [CorsairLink] DeviceManager: Found 1 supported Corsair device(s)
  name=CORSAIR iCUE Commander CORE, devicePath=\\?\hid#vid_1b1c&pid_0c1c&mi_00#7&20b69190&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

2023-01-16 7:09:20 PM: [CorsairLink] An exception occurred attempting to initialize device 'CORSAIR iCUE Commander CORE (630f0001801ccabae51f2af52091005f)' (\\?\hid#vid_1b1c&pid_0c1c&mi_00#7&20b69190&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}):
2023-01-16 7:09:20 PM: [CorsairLink] System.FormatException: The response was not valid.
   at CorsairLink.CommanderCoreDevice.EndpointResponse.ThrowIfInvalid()
   at CorsairLink.CommanderCoreDevice.InitializeSpeedChannels(EndpointResponse hardwareFixedSpeedPercentResponse)
   at CorsairLink.CommanderCoreDevice.Initialize()
   at CorsairLink.CommanderCoreDevice.Connect()
   at FanControl.CorsairLink.CorsairLinkPlugin.FanControl.Plugins.IPlugin.Initialize()
2023-01-16 7:09:22 PM: CorsairLink could not initialize or has no sensors.

Originally posted by @Lithradus in #2 (comment)

In HWiNFO64, I get tenths of a degree of temperature, but in FanControl + CorsairLilnk, I'm only getting whole degrees. It matters a bit more for coolant than CPUs because the range is smaller. Is this a FanControl issue or CorsairLink issue?

Originally posted by @CalculonPrime in #24 (comment)

Is it possible to add Fan/Pump Control for the H60iRGBPROXT ?

The Pump has two fan connectors, one three pin fan connector for the pump speed (no control) and a USB connector for RGB and pump Control.

If you need more information i will try to support you.

Thanks and Cheers
Corsair H60iRGBPROXT.txt

I have a Commander Pro and have a water temp sensor connected to it to monitor the temp of the water in my cooling loop. The sensor is supported in Fan Control but does not show a constant reading, It will show NaN or 0° most of the time and randomly show the actual temp reading every few seconds.

Hi again,

The latest 1.4.0-beta.5 release has mostly solved the disconnection issues that I posted in #76 with my H100i Pro XT. I've been able to uninstall iCUE and have everything running mostly stable. However, I've been able to narrow down the last bit of disconnection to be caused by SignalRGB. Whenever it is open (regardless if the H100i is enabled or disabled via Devices), the CorsairLink plugin still spits out the same "Multiple errors detected" message and the H100i becomes unresponsive until I do a cold boot. It's the same error I posted in #76.

I saw that the compatibility section was updated, but I was confused with what was meant by the "Commander only" note. I don't mean to add a redundant issue if SignalRGB is already known to be causing problems with the new builds, but I wanted to make sure this was known.

When I use iCue to set some Hardware RGB setting to the 3pin RGB on the Core XT (the default behaviour that should run when iCue is not open), and then close iCue and shut down all iCue and corsair background processes the Hardware RGB setting is fine.

However, when I open Fan Control it shuts down the RGB completely. Is this expected behavior? Am I missing something obvious? It seems pretty basic but I couldn't find the same issue mentioned.

Running NET4.8 v147 of FanControl software, with version 1.0.0 of CorsairLink. Log:

3/10/2023 2:40:45 AM: [CorsairLink] DeviceManager: Found 1 Corsair device(s)
name=H115iRGBPROXT, devicePath=\?\hid#vid_1b1c&pid_0c21#7&37184169&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
3/10/2023 2:40:45 AM: [CorsairLink] DeviceManager: Found 0 supported Corsair device(s)
3/10/2023 2:40:46 AM: [CorsairLink] DeviceManager: Found 1 Corsair device(s)
name=H115iRGBPROXT, devicePath=\?\hid#vid_1b1c&pid_0c21#7&37184169&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
3/10/2023 2:40:46 AM: [CorsairLink] DeviceManager: Found 0 supported Corsair device(s)
3/10/2023 2:40:46 AM: CorsairLink could not initialize or has no sensors.

I don't have the bloated iCUE software installed, but the pump is connected to a motherboard USB header. Speed of the pump is at its factory default, and the radiator fans are plugged into the motherboard (and so controllable via Fan Control without CorsairLink). Pump RPM is also fed into the motherboard via a 1-wire fan header connector (though that RPM is reported by FanControl as twice its actual value.) What I need from CorsairLink is the coolant temperature sensor.

Note that I have HWiNFO64 (which was not running at the same time as FanControl), and it does show two sensors for the H115i - the coolant temperature, and the true (un-doubled) water pump rpm. So i can read them there, but I need FanControl to have access to them.

Type: CorsairLink.CorsairLinkDeviceException
Message: Checksum failure.
Source: FanControl.CorsairLink
Stack Trace:
in CorsairLink.Devices.HydroPlatinumDevice.SendCommand(Byte command, ReadOnlySpan`1 data)
in CorsairLink.Devices.HydroPlatinumDevice.ReadState()
in CorsairLink.Devices.HydroPlatinumDevice.Refresh()
in FanControl.CorsairLink.CorsairLinkPlugin.Refresh()
Data:
writeBuffer: 003F08FF00FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF32
readBuffer: 00C1C01207008E266D2413034FE8034F3D02034FE8034F3D0201BF0000BFCC0900000000000000034FFFFF4F530201F25000052D3237417124000000000000001F

CorsairLink.log

Using beta 6 from yesterday - h150i elite

Hello,
So I've tried installing the last release - v1.4.0-beta.3 and this issue comes more often than before (in beta 1)
What is happening is that FanControl loses control over my Corsair H150i Pro AiO.
Commands and speeds doesn't update anymore. If I force manual to 100% nothing is happening.
In the logs, at the time I'm getting the issue, I start getting this message :
2023-08-31T15:27:46.7239708Z [WRN] Plugin: Refresh skipped - refresh already in progress.
CorsairLink.log
If I close FC and open it again, it will work again for about 20 minutes.
Icue is installed but service is set to manual and Icue doesn't start with windows.

Thank you for the plugin! I've noticed when using the plugin with FanControl, it is cause a stutter with the lighting in SignalRGB. When I remove the plugin, the stutter goes away. Any way to fix it?

It recognizes all of my fans and sensors fine now, but it's causing my RGB in the fans to flicker off every half a second or so. Interesting.

Originally posted by @rumpleforeskin83 in #2 (comment)