-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
maxPwmChangePerCycle buggy, keeps fan off #326
Comments
Hi @jwefers , thx for reporting. I am not sure what was going on with this code, I might have let copilot go a bit far without thinking about it 😄 Thx! |
…Cycle-keeps-fan-off reworked DirectControlLoop to fix custom values for "maxPwmChangePerCycle"
i'll get to it eventually, its not urgent - i'll get around to investigate/test the fix. Thanks for staying on it |
Thanks for picking up my PR and making the direct algo happen. I think i dis
Describe the bug
when using controlAlgorithm.direct.maxPwmChangePerCycle with any value, it wants to set the correct pwm value, but then sets the fan speed to zero instead.
As last time, i'll try to properly debug this when i find time, but right now, Stalker 2 was more important.
To Reproduce
Steps to reproduce the behavior:
config:
I assume curve and sensor do not matter, use anything.
What happens is, Debug shows correct desired PWM, but actually set PWM is zero and fan stays off.
When just using direct without maxPwmChangePerCycle, it works as expected.
Expected behavior
As temp in curves are changing, target PWM is slowly approached
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
uname -a
: Linux xxx 6.11.9-arch1-1 1 SMP PREEMPT_DYNAMIC Sun, 17 Nov 2024 16:06:17 +0000 x86_64 GNU/Linuxsensors -v
: sensors version 3.6.0+git with libsensors version 3.6.0+gitfan2go version
: 0.9.0The text was updated successfully, but these errors were encountered: