Closed EvanMulawski closed 1 year ago
@zenosisalive @cmoore-mayesh Can you run Fan Control with version v1.3.0-beta.4 of this plugin after installing the included driver and provide the CorsairLink.log
file? Need to see if it already detects your devices.
Log attached. CorsairLink.log
@cmoore-mayesh Please try the attached build with debug logging enabled. To enable debug logging, set the FANCONTROL_CORSAIRLINK_DEBUG_LOGGING_ENABLED
environment variable to 1
and restart Fan Control. Please provide the CorsairLink.log
file after testing.
This build adds support for Asetek Pro AIOs only.
Appears to be having problems enumerating the device properly. The SiUSBXp.dll is in the plugins folder properly and the env variable is properly set. Attached is the log file as requested.
2023-07-30T19:42:13.3253375Z [DBG] Corsair H150i Pro (1C2C03043D1712AB799502138DEE93AD): Connect 2023-07-30T19:42:13.3253375Z [DBG] Corsair H150i Pro (1C2C03043D1712AB799502138DEE93AD): Disconnect 2023-07-30T19:42:13.3308870Z [DBG] Corsair H150i Pro (1C2C03043D1712AB799502138DEE93AD): InitializeSpeedChannelStores 2023-07-30T19:42:13.3319126Z [DBG] Corsair H150i Pro (1C2C03043D1712AB799502138DEE93AD): SetChannelPower -1 50% 2023-07-30T19:42:13.3324345Z [DBG] Corsair H150i Pro (1C2C03043D1712AB799502138DEE93AD): SetChannelPower 0 50% 2023-07-30T19:42:13.3324345Z [DBG] Corsair H150i Pro (1C2C03043D1712AB799502138DEE93AD): SetChannelPower 1 50% 2023-07-30T19:42:13.3324345Z [DBG] Corsair H150i Pro (1C2C03043D1712AB799502138DEE93AD): SetChannelPower 2 50% 2023-07-30T19:42:13.3329623Z [DBG] Corsair H150i Pro (1C2C03043D1712AB799502138DEE93AD): WriteRequestedSpeeds 2023-07-30T19:42:13.3340303Z [DBG] Corsair H150i Pro (1C2C03043D1712AB799502138DEE93AD): SetPumpPower 50% 2023-07-30T19:42:13.3345561Z [DBG] Corsair H150i Pro (1C2C03043D1712AB799502138DEE93AD): WRITE: 3032 2023-07-30T19:42:13.3382088Z [WRN] Device Initialization: An error occurred initializing device 'Corsair H150i Pro (1C2C03043D1712AB799502138DEE93AD)' (\\?\usb#vid_1b1c&pid_0c12#7289_2.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}): 2023-07-30T19:42:13.3382088Z [ERR] Device Initialization: Type: CorsairLink.SiUsbXpress.SiUsbXpressException Message: Failed to read - data error. Source: FanControl.CorsairLink Stack Trace: at CorsairLink.SiUsbXpress.Driver.SiUsbXpressDevice.Read() at CorsairLink.Devices.HydroAsetekProDevice.WriteAndRead(Byte[] buffer) at CorsairLink.Devices.HydroAsetekProDevice.SetPumpPower(Byte percent) at CorsairLink.Devices.HydroAsetekProDevice.WriteRequestedSpeeds() at CorsairLink.Devices.HydroAsetekProDevice.Refresh() at CorsairLink.Devices.HydroAsetekProDevice.Connect() at FanControl.CorsairLink.CorsairLinkPlugin.FanControl.Plugins.IPlugin.Initialize()
This is in the log.txt file from FanControl itself.
7/30/2023 3:33:50 PM: CorsairLink could not initialize or has no sensors. 7/30/2023 3:38:32 PM: CorsairLink could not initialize or has no sensors.
@cmoore-mayesh New build.
Appears to be somewhat functional.
The fan and pump tachs are WILD though.
Log file attached.
@cmoore-mayesh This should fix the RPM readings.
Oh -- this is working so VERY nicely now. RPM is accurate and responding as expected on pump and fan. Curves applied are working as expected as well.
Many MANY thanks to you. Now I can truly lose the bloated iCue software in its entirety.
@cmoore-mayesh Glad to hear it! Let me know if you experience any issues. This will be in v1.4.0-beta.1 after v1.3.0 is officially released.
Hope that's ok
@zenosisalive That's expected. Only the Pro models are supported in the posted build - still working on the others.
@zenosisalive Please try the attached build with debug logging enabled. To enable debug logging, set the FANCONTROL_CORSAIRLINK_DEBUG_LOGGING_ENABLED
environment variable to 1
and restart Fan Control. Please provide the CorsairLink.log
file after testing.
Sorry, I've looked but don't know where that setting/file is located
That's all I can find
@zenosisalive The downloaded ZIP file needs to be unblocked first - follow Installation.
To enable debug logging, run the following in a Command Prompt window:
setx FANCONTROL_CORSAIRLINK_DEBUG_LOGGING_ENABLED 1
or use Windows search to launch the UI:
and click New to add or Edit to change the selected environment variable.
@zenosisalive New build - this should fix the RPM readings. Let me know if you can control the fan and pump speeds.
The RPM looks right and I seem to have pump control but not fan control CorsairLink.log
Sets fan to max RPM on launch and doesn't respond to RPM slider
@zenosisalive New build.
Still no Fan control CorsairLink.log
@zenosisalive Are you using the fan(s) that came with the device?
i cannot duplicate zeno's issue -- I have a SLIGHT revision of the same cooler on another PC. Attached is the log -- not sure if this helpful or not.
@cmoore-mayesh Thanks - unfortunately that's a completely different device with a different communication protocol, even though the model name is similar.
Damn. Was afraid of that.. I know this one is ancient but was hoping they didn't modify it too hard. Good luck finding the issue.
@zenosisalive New build.
There is only one fan plugged in but it is original. Behaviour was same under Corsair software and the fans are connected via a simple splitter. Sorry if that caused trouble :/
I have tested the latest build and all seems to be working correctly. The sensor nametext is also different to the prev builds.
@zenosisalive No problem at all, was just trying to get as much information as possible. Thanks for testing - going to release v1.4.0-beta.1 soon.
Completed in v1.4.0-beta.1
Add support for the following devices:
0c02
)0c08
)0c16
)0c09
)0c03
)0c15
)0c0a
)0c07
)0c13
)0c12
)The Asetek Hydro AIOs use the same SI USB Xpress driver as the Flex USB PSU devices added in v1.3.0.
Progress: