Skip to content
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

[Feature Request] Check if Fan really follows the target curve #2444

Open
n300home opened this issue Apr 8, 2024 · 5 comments
Open

[Feature Request] Check if Fan really follows the target curve #2444

n300home opened this issue Apr 8, 2024 · 5 comments

Comments

@n300home
Copy link

n300home commented Apr 8, 2024

Hi There,

Is there a possibility to implement a plausi check, if a fan really follows a designated target curve?
I'm asking, because I have a buggy PCH Fan Controller on my Mainboard. Sometimes the PCH fan speeds up to maximum RPM and stays there until:

  • I shutdown or standby my computer
  • or Disable/Enable this PCH Fan in in Fan-Controll

My idea would be to check against calibration curve, if its really plausible that the fan runs over 5000rpm although 0% PWM-Signal is given in target curve. If this plausi check fails -> send and overrule once more the actual target value to fan controller.

Relevant hardware specs and setup
My relevant "problem fan" is the PCH-Fan from Gigabyte X570 Aorus Master (rev.1). Imho there is a flapping Temp-Sensor, which sometimes sends inaccurate temperature data, what ends up in a "Panic Mode" in mainboards UEFI Fan Curve.

@Rem0o
Copy link
Owner

Rem0o commented Apr 8, 2024

That's what "Force Apply" is for.
image

@n300home
Copy link
Author

n300home commented Apr 8, 2024

Hi @Rem0o
Unfortunately no. I use the "force apply" feature. But ->
image

@Rem0o
Copy link
Owner

Rem0o commented Apr 8, 2024

Oh I see the % readout is still 0 and only the RPM sensor goes crazy. Force apply is based on the control sensor.

@Rem0o
Copy link
Owner

Rem0o commented Apr 8, 2024

I could add a new check indeed by checking the expected % out of the current RPM+calibration. If the difference is large, greater than let say 25%, we could assume there is an issue and fireup force-apply.

@n300home
Copy link
Author

n300home commented Apr 8, 2024

Oh that sounds really great :)
many thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants