-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Commander Core "Pump Failure" at 0 RPM #122
Comments
Hi @Asylian1, where do you see the pump failure message? Can you post a screenshot/picture and the CorsairLink.log file (located in the Fan Control directory)? |
Sure, here's the log and a picture of the pump failure icon showing on the pump: |
So update - I did reconstruct the profile I had set from the ground up and reproduced the issue. It seems when I employ my fan curve that involves putting the fans connected to one of the cores to 0%, that this then causes the AIO to flip out and cause this issue. As how to fix not sure yet. @EvanMulawski |
Another update - so this seems to only happen when the pump control specifically is set to 0%. Before update the metric was fine so not sure why it causes the AIO to sneeze an error like it's doing. I just manually set the pump to 0% to confirm this theory and it did indeed induce the pump failure message. Is this just normal expected behavior for the pump itself or something in FanControl you think? @EvanMulawski Here's logs: |
Ah, that explains it. The device must think it's pump failure if the pump RPM is zero - since you can't "officially" set the pump to 0 RPM in iCUE. Does it occur if you set the pump to 1%? And does it exit from pump failure status if you increase it after setting it to 0%? |
Yea it still occurs at 1%, although that still registers at 0 rpm. After the error is triggered seems I can no longer control the fans and in order to clear said error I have to do a full shut down. |
Actually it is fine at 1%, this time it's at around 600 rpm. Think the ui bugged a bit when I did it before. No errors yet. |
Ohh and another thing - it's the INSTANT I select 0% on manual control even if there are still rpms left going. So it doesn't seem that the pump needs to go to 0 rpm in order to trigger the error, it automatically throws one the instant it gets a 0% command regardless of current rpm. |
When you are able, can you determine the lowest percentage that can be set before the pump turns off? Please follow these steps:
With this information, I will be able to set a minimum value for the pump to prevent this from occurring. Thanks! |
Just making a comment as I have also experimented with lowering the pump speed in idle to make it quieter a while ago. In my case with a H170i Elite LCD (non-XT), it's around 44% (~1540 RPM) where the pump starts making a grinding noise probably due to the lack of waterflow, just a guess as I'm not an expert on the mechanics of Corsair AIOs. It gets louder with lowering the speed below 40% (~1410 RPM), reducing it even further makes the pump slow down with horrible noises to end up at ~600 RPM at 20%. Going any lower to the 1-19% range seems to have no effect, the pump keeps running at ~600 RPM, and setting it to 0% stops it completely. Also I have noticed that if I don't decrease the speed gradually but set it to between 1-19% with one click, then it ends up in a lowered speed of the initial RPM, for example it goes from ~2750 RPM to ~1700 RPM if the starting point was 100%. |
Mitigated in v1.4.3 |
Hi - been using FanControl for a while now, but just noticed that for whatever reason with this fresh install of Windows 11 and an update to the pump firmware, it seems that whenever I run FanControl I'm getting a pump failure message (which is untrue the pump seems to be just fine) with red LEDs flashing etc..
Is there a way around this? Do I need to factory reset the Commander Core attached?
The text was updated successfully, but these errors were encountered: