Hydro Asetek devices stop responding #79
Assignees
Labels
bug
Something isn't working or functioning as expected
fixed
Fix available in official release
in-prerelease
Available or fixed in a pre-release
Comments
|
@XJIOP When it gets stuck, does the fan/pump respond to manual control? |
Yes, it respond to manual and curve, but not below the stuck speed. I checked again, after some random time it works again without restarting app, but not for long, stuck happens often. |
|
Can you enable debug logging and upload the |
|
Pump idling 30% is about 1380 RPM. The logs show that the pump speed rises to 2130 rpm by 40%, then it reaches normal speed. Pump and Fan speed stuck at the end of logs.
Turning off the hysteresis nothing changes. |
|
@XJIOP Please try the attached build with debug logging enabled and upload the full CorsairLink.log file after testing. (You can delete/move the current log file.) |
|
New log with your attached plugin dll. Here the speed immediately gets stuck and does not decrease. I use a stress test from Intel Extreme Tuning Utility. It looks like the controller switches to Balanced mode, pump speed is the same. The same problem was in ICUE but in the latest versions, this has been fixed. |
|
@XJIOP Do you know if it was fixed in iCUE 4 or 5? Not seeing anything in Corsair's patch notes. |
|
@EvanMulawski I use iCUE 5, did an update a few days ago, and noticed that this problem was gone. |
|
What's it? There is always the same pump speed. 
|
The circled sensor is the speed reported by the plugin/device. The other is the speed reported by the motherboard. The device only reports speed in increments of 30 RPM. |
|
@XJIOP Just to confirm, is iCUE completely closed when you are running Fan Control? |
|
@EvanMulawski Yes, I completely close iCUE and stop CorsairService before starting FanControl. Had the same problem in the old CorsairLink app. |
|
@EvanMulawski Pump and Fan speed is still stuck Maybe under some events, reset the pump mode? |
|
That command sets the pump to one of the preset speeds. It seems like something is taking over when the liquid temperature reaches 40 degrees. |
|
@XJIOP I think I found it - it's the fan safety profile. It activates at 40C by default. I'll have to override that. |
|
@XJIOP New build. |
|
@EvanMulawski With this build, Corsair device is not recognized |
|
@XJIOP New build - this will attempt to write several different safety profiles for testing. |
|
@EvanMulawski Build 20230822r001 still activated at 40C, but not understand when it is deactivated, at 32C still high RPM. For test, I created PUMP and FAN curves starting at 41°C, without hysteresis. |
|
@XJIOP New build. Not sure why it's behaving like this - safety profile should deactivate at 35C. It also seems to be rejecting the safety profiles I'm sending. |
|
@cmoore-mayesh Are you experiencing this issue when the liquid temp exceeds 40C? |
|
I am not -- my H115i pump failed completely -- unrelated to this software, it was a VERY old unit and very well used, I think a good chunk of the coolant leeched out of it as I could hear water sloshing in it when I disassembled during troubleshooting. I'm also not using the trigger profiles either. I have a fairly aggressive curve for the pump and fans on the H150 I still have. |
|
@EvanMulawski Unfortunately, the same thing. Maybe try changing safety profile on every request to change fan speed? |
|
@XJIOP Can you attach the log file? Thanks. |
|
@EvanMulawski Sorry forgot new dll plugin. With last build missing corsair device. |
|
@XJIOP Thanks. New build. |
|
Here is logs from new build. After testing FanControl, I ran iCUE and my custom fan and lighting profile was removed. |
|
@EvanMulawski I think I found reason for safety profile, it turns on only if at 40C fan speed are less than 40%. I need to do more tests- |
|
@XJIOP New build. Trying one more thing to set the safety profile. (Just need the log after the plugin loads in Fan Control.) |
|
@EvanMulawski log after the plugin loads in Fan Control I tested FanControl again, this problem can be fixed by set fan speed to 40% at 40C, while the pump worked at 30%. Safety profile is activated like this Basically, I'm fine with it, but if you want to test more, I can help you with logs and so on. I just noticed another problem, sometime stuck liquid temp, tested with plugin from release. This usually happens when you change the curve and hysteresis. Logs stuck too and not write new data. Last lines from log After refresh sensors detection Restart FanCotnrol fixed it. |
|
@XJIOP I figured out the issue with setting the safety profile. Can you run Fan Control with the build in the previous comment and see if the safety profile activates at 41C instead of 40C? |
|
@EvanMulawski Yes with the last build safety profile is activated at 41С, but it is unclear when this profile should be disabled, liquid temp dropped to 30С and this profile was still active. I'm still worried that sometimes liquid temp stuck and corsair device no longer recognized until restart FanControl, last time this happened when FanControl was minimized in the tray. |
|
@XJIOP Do you have a full log file for when that issue occurred? Was iCUE completely closed when Fan Control was running? |
|
@EvanMulawski iCUE is completely closed and Corsair service stopped, when this happens again, I will upload here log, |
|
@XJIOP New build - testing various safety profiles. For now, just need the log after the plugin loads. |
|
Here log when stuck liquid temp, logs are stuck too and not write new data after this, last lines when I clicked Refresh sensors detection option. |
|
Last build, safety profile is no longer activated, tested up to 50C with disabled fans. |
|
@XJIOP New build - one more safety profile test. Regarding the other issue, can you try reproducing it after restarting your PC? The error in the log indicates the device was essentially disconnected and the driver lost communication. (The plugin needs to handle that properly though - it's on my to-do list.) |
|
@EvanMulawski Last build. Can you add a manual setting when safety profile should be enabled? or you want to disable it completely? About other issue, after restart FanControl it works again, but it happens often. Could it be because of this? I have a driver from iCUE. |
|
@XJIOP There will be an option to "disable" the safety profile.
Can you reproduce it after a restart of your computer?
No - it's the same driver iCUE uses. |
|
@EvanMulawski This happened again in 30 min after restarting PC, then I try to run the sensor detection update. iCUE and service disabled from autorun. |
|
@XJIOP New build - adds additional logging to identify the cause. Please try reproducing that issue again. |
|
@EvanMulawski Happened again Stuck Refresh sensors detection |
|
@XJIOP New build. Can you post the |
|
@EvanMulawski 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. I need to test this again, maybe it's because start delay 1 sec, trying to increase |
|
About the second stuck device issue, with last build still working stably. If it happens again, I'll upload the log here. |
|
Stuck after wake up from sleep mode. It happened twice. Maybe due that FanControl was moved from ssd to hdd, and drive wakes up late from sleep. log.txt |
EvanMulawski
changed the title
EvanMulawski
added
bug
|
Fixed in v1.4.0-beta.4 |
EvanMulawski
added
in-prerelease
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Normal
Stuck
The text was updated successfully, but these errors were encountered: