[Experimental] Manual Fan Control

[seerge]

Hello fellow community,

Recently I have discovered a way to directly set fan speed in percentage points for each fan individually.
It uses same method as MyASUS does when runs your "fan testing".

In existing and standard way to set a "custom" fan curve - fan behavior would be still handled by BIOS and follow it's internal algorithm. This BIOS algorithm is different for different models, sometimes includes a very high hysteresis (delays before acting), can override some custom fan behavior, etc.

In "alternative" approach, it's possible to actually literally manually set fan speed every second based on temperature readings.

This build implements "manual" fan control as soon as you check Apply Custom Fan Curve, when you uncheck it - fan behavior will be returned back to BIOS.

Current implementation details

• More precise fan speeds, following custom fan curve as close as possible
• Fan speeds are being updated every second
• CPU and GPU temps are calculated as an average from last 6 seconds (can be set via config)
• CPU fan follows CPU temp, GPU fan follows GPU temp, Mid fan follows CPU temp
• If GPU temp is not available by some reason (for example GPU is disabled or sleeping) - GPU fan will follow CPU temp instead
• If CPU temp is also not available by some reason - fan behavior will be returned back to BIOS defaults
• Minimum fan speed is 20% unless it's set to OFF completely (similar to how BIOS handles this)
• Maximum fan speed is 100%
• Fan speed will follow line between dots, not only dots themselves
• Fans will react on temp change almost immediately

Potential downsides and risks

• If you quit application incorrectly during manual fan control, fans may keep running on last used speed and will not react on temperature changes
• No idiot-protection. If you set fan speeds to be low, they will be low and your device will heat up quickly

Please test on your own risk (!) and only as a last resort in case you can't achieve desired fan behavior otherwise

GHelper.zip

Updated 26.10.2024 (0.197)

Possible params for config.json (with their default values)

"fan_min": 20, - minimum fan speed (in %) when it's not OFF
"fan_hysteresis": 6, - number of seconds to calculate average CPU / GPU temp (set 1 for instant reaction)
"fan_shift" : 50, - weighted average coefficient between CPU (or GPU) temp and MAX(CPU,GPU) temps in a range from 0 to 100

• If you want GPU (CPU) fan to follow only GPU (CPU) temp, leave it as is
• If you want GPU (CPU) fan to follow MAX(CPU,GPU) temps, set it to 100
• If you want GPU (CPU) fan to follow average between GPU(CPU) and MAX(CPU,GPU) set it to 50, etc :)

If you see a big (more than 500RPM) difference between fan curve and actual readings - try to click Calibrate, it will run a quick measurement process and adjust Y-axis to match actual maximum RPMs

You will see what is actually being set as your fan speeds on Fans+Power screen under fan curves chart. Don't forget to click Apply.

[FliesQQ]

At this setting, the fan speed on the left side of the machine(CPU fan) is at full speed.

At this setting, the fan speed on the right side of the machine(GPU fan) is at full speed.

But, At this setting, fan speed raise to max speed need almost 1 min, not particularly fast.
However, It's worked.

[seerge]

@FliesQQ how fast fans will speed up still depends on hardware of course :) actual command is being sent immediately (i.e. every second)

[FliesQQ]

So this is already very good now.
But FN Lock not work.
And use this should I stop all ASUS services? Now my running Asus service is 0.

[FliesQQ]

If GPU and CPU both in use, seems like CPU fan curve not function correct.

[abdulkadirozyurt]

@abdulkadirozyurt in relation to this experimental build it's only ones listed in the head post here :) As for the rest you can check Power user settings

I didn't mean the one about this experimental build, I actually asked if there is any documentation about what all the entries in config.json mean and what they do. Thank you anyway.

I would also like to point out something like this.

With this 0.194 beta version, I was able to control the fan on my 2021 asus tuf gaming f17 model code device, which I normally could not control the fan. However, today I upgraded to 0.195 pre-release version and the fan control was canceled. First I closed ghelper completely, then I deleted the GHelper folder in %AppData%, then I deleted the exe file of GHelper. Then I downloaded the 0.194 stable version and when I tried again, the fan control did not work again. Then I did the same thing again, deleted everything that needed to be deleted, downloaded this beta version and it worked.

But here's the thing, I started using the beta version and then the stable version came, I upgraded to the stable version and it was working. I deleted everything and installed the 0.194 stable version and it stopped working, I don't understand why this happened?

[seerge]

@abdulkadirozyurt Power user settings - is a full list of config settings that you may change (that don't exist in UI)

If you are using Experimental build - you need to keep using it , mainstream branch does not have this manual fan control.

[abdulkadirozyurt]

@abdulkadirozyurt Power user settings - is a full list of config settings that you may change (that don't exist in UI)

If you are using Experimental build - you need to keep using it , mainstream branch does not have this manual fan control.

Okay, I get it now, so I shouldn't update until I see this experimental feature in the new stable release description, right? Will this feature come to the stable release in the future?

[seerge]

Yes, you should download updates from this thread only :) I don't plan to merge manual fan control into mainstream branch yet.

[abdulkadirozyurt]

Yes, you should download updates from this thread only :) I don't plan to merge manual fan control into mainstream branch yet.

I appreciate it.

[seerge]

@FliesQQ values that is being set look correct and along the fan curve.

You have mentioned that fans take time to spin up, most probably it’s slightly lagging because of that. Cause, as I understand, temps jump quickly in your testing :)

[FliesQQ]

Yes, the temperature changes too quickly and the fan responds too slowly. If the temperature fluctuates, it is possible that the temperature has risen, but the fan speed setting is still at the low temperature speed.

[seerge]

@FliesQQ fan "setting" is what you see in a red label (so it's practically instant). But how fast actual fans would react on this - is something outside of my control unfortunately

[FliesQQ]

Yes, it's really a pity.

[seerge]

@FliesQQ you can tackle that with a fan curve :) rise it to higher RPMs a bit faster

P.S. I have also updated build in the header-message, now it will refresh speeds once every 500ms (so twice more frequent)

[inthecatsdreams]

Before this update it was impossible for me to set a custom fan curve because of the bios rejecting it, now I can finally set the one I want! Thank you so much!

EDIT: My Laptop is TUF A15 with an RTX 3050

[seerge]

Great news

[fscottcopeland]

Unfortunately this build doesn't appear to be respecting my fan curves still :(

Log extract:

2024-03-23 20:43:21: Mode = 0 : OK
2024-03-23 20:43:21: GET GPU CLOCKS: 0, 0
2024-03-23 20:43:21: GET CLOCK LIMIT: 0
2024-03-23 20:43:21: ReadGPUPowerBase: -65536
2024-03-23 20:43:21: Manual fan control OFF
2024-03-23 20:43:22: Mode = 0 : OK
2024-03-23 20:43:22: GET GPU CLOCKS: 0, 0
2024-03-23 20:43:22: GET CLOCK LIMIT: 0
2024-03-23 20:43:22: ReadGPUPowerBase: -65536
2024-03-23 20:43:22: FanCPU = 32-3C-46-4B-50-55-5A-5F-0C-16-1F-28-31-39-43-4A : OK
2024-03-23 20:43:22: FanGPU = 28-32-37-3C-41-46-4B-50-0C-16-1F-28-31-39-41-4A : OK
2024-03-23 20:43:22: Manual fan control ON
2024-03-23 20:43:22: PowerLimit A3 = 40 : OK
2024-03-23 20:43:22: PowerLimit A0 = 60 : OK
2024-03-23 20:43:22: PowerLimit C1 = 80 : OK
2024-03-23 20:43:23: PowerLimit C0 (GPU BOOST) = 25 : OK
2024-03-23 20:43:23: PowerLimit C2 (GPU TEMP) = 87 : OK
2024-03-23 20:43:23: PowerLimit A3 = 40 : OK
2024-03-23 20:43:23: PowerLimit A0 = 60 : OK
2024-03-23 20:43:23: PowerLimit C1 = 80 : OK
2024-03-23 20:43:23: PowerLimit C0 (GPU BOOST) = 25 : OK
2024-03-23 20:43:23: PowerLimit C2 (GPU TEMP) = 87 : OK

As you can see, the FanCPU and FanGPU percentages don't match what is actually running (confirmed by hwinfo fan reading)

[seerge]

@fscottcopeland can you switch scale to RPM? Asus has quite specific interpretation of % points :)

[fscottcopeland]

Here you go. I've included my HWiNFO graphs too, in case it helps. GPU seems to hit ~71c and then jumps to 5000RPM, despite the 70c point being 4200RPM and 75c being 4600RPM. CPU doesn't seem right either.

[fscottcopeland]

The frustrating thing is that if I disable the custom fan curve, the fans then run slower - e.g. the GPU fan won't then jump to 5000rpm as soon as it hits 70c.

[fscottcopeland]

@Summersoff what's your laptop? Duo 16 2023 too?

[seerge]

@Summersoff then it's just a BIOS idiot-protection, which is actually ... good :) I have similar behavior on my ROG Ally. It would keep fans off until something like 55-60C and then no matter what app sets to it - will ramp them up.

[seerge]

@fscottcopeland if you disable custom fan curve, it's back to whatever default fan behavior is for each of your modes :)

[fscottcopeland]

Yeah. Such a shame. The stock balanced fan curve isn't aggressive enough - whilst the manual fan curve gets overridden and then becomes OTT. I really need a balance in between.

[yesnt10]

Thank you so much! it works great!

[seerge]

@yesnt10 amazing

[manciuszz]

Testing it atm. Seems to work fine so far. Though an optional hysteresis feature would be nice, cause I hear the fans whooshing up and down often

[seerge]

@manciuszz they do :) because one main complains that people accuse G-Helper of - is that fans are "slow" to react and "don't follow curve precisely" (even though when fans are controlled by BIOS it's absolutely not related to the app)

I can add a hysteresis in a form of calculating an average of CPU / GPU temps for last 3 or 5 seconds, instead of acting immediately

[manciuszz]

That would be a nice to have. Preferably, hysteresis could be adjustable by the user, that would allow the user to set their preference whether they want faster reaction times or more stable fan speeds. I personally don't hear the fans because I'm wearing a headset, but I don't think the fans should be whooshing up and down that often either xD

[seerge]

@manciuszz I have updated build in the main post, and added default hystheresis in a form of using average temperature for last 6 seconds. It can be also adjusted via config.

[manciuszz]

Very nice. I'll check it out.

--- EDIT ---
It works really well. I also think the fan shift and hysteresis settings should be available in the UI, so we can do adjustments on the fly, instead of close app/edit config/reopen sequence.

[seerge]

@manciuszz my idea to keep things simple on this stage

[FliesQQ]

I've give up using this function... Now I'm using default setting.

…

________________________________ 发件人: Serge ***@***.***> 发送时间: 2024年3月24日 18:13 收件人: seerge/g-helper ***@***.***> 抄送: FliesQQ ***@***.***>; Mention ***@***.***> 主题: Re: [seerge/g-helper] [Experimental] Manual Fan Control (Discussion #2272) @Summersoff<https://github.com/Summersoff> "same problem" in what sense ? — Reply to this email directly, view it on GitHub<#2272 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AH6FUHMO4CMMCEVIINFIDV3YZ2RNFAVCNFSM6AAAAABFET5V5GVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DQOJRG43TI>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[seerge]

@FliesQQ no worries, default fan curves are best choice for majority :)

Btw I did few more tweaks, and updated release in a header-message here. So you may also check that and see if fans react faster now (or not)

[ElluIFX]

Nice feature, thanks!
It works great on my Zephyrus M15 and acts rapidly.
But sometimes it can't turn off the CPU fan:

Could it be that my method of forcing CPU fan off is not supported？

[ElluIFX]

And it can fully turn off it after I switch to Turbo and back to Silence.

[seerge]

@ElluIFX since it shows 0% in red label, this is what app actually sets as fan speed. As I mentioned in other comment here, it is possible that BIOS would override that as an idiot-protection if CPU is too hot for it's thinking.

[ElluIFX]

@seerge That's really stupid.
What's more, maybe another check box is required for switching the legacy custom mode and this new one.
Anyway, it's a cool feature for me to avoid the broken fan from making noise, thank you.

[Akalikaton]

My Laptop is ROG G14 2020, it's very intersting, after Calibre i cant set the Fan unter 2900 RPM. The Situation is just same like 0.154.0.
I hope the Fan can keep 1000 RPM with 15 TDP, a good Plan for Document read and simple surfing.

[Akalikaton]

PS: 0.154.0 can set minimal 1800RPM and real 1800~2400 RPM

[seerge]

Currently I have set min fan speed to be 25% and max 100% correspondingly (for most laptops 25% would be 1800-2000RPM) Theoretically i can allow even 1% in manual mode, but i'm not sure if it's healthy for the fans ...

[Akalikaton]

Recently i use my G14 almost only PDF and Powerpoint reading, so light, lang battery life and quiet are much important. Maybe i should buy Macbook Air M3...But now G14 works also very well.

[seerge]

I think for office use you can get away with fans being completely off at all. Its also good for battery life

[Akalikaton]

Yeah, and i have heard about, 4800HS performance better than newest 7840H under 10W, a Surprise.

[hadixcanimm]

I bought my laptop in 2019, and Armory Crate didn't allow me to make manual fan adjustments. Since then, I've been researching for a solution every few months. Then I found you and have been using your software, constantly checking for updates, but I still couldn't find a solution for fan adjustments... until today. It's working perfectly now, and your software allows me to make manual fan adjustments. My device is ASUS TUF 506LI. I think the only thing left for me is one setting; being able to undervolt directly on my device without the ThrottleStop application.

[seerge]

I'm glad it works

[Constrat]

Working exactly as expected on G713RW.
Tried the calibration first and I got scared how fast they started ramping up, also with this version I was able to get a much higher calibration max value: (6600 and 6800)
Before I was only able to reach 5400 and 6000, because it was too slow to ramp up.

GHelper keeps on delivering!

[hadixcanimm]

When I completely shut down the fans, I occasionally encounter a blue screen error. On the blue screen, I see an error code like 'fail tdr'. Prior to the blue screen, there are black screens resembling the graphics card attempting to restart itself, followed by the blue screen error.

I don't think it's due to overheating because I monitor the temperatures and they usually hover around 50-60 degrees.

[seerge]

Are you sure it's related ? may be it's just some gpu issues? try to run fans on minimal speeds otherwise :)

[hadixcanimm]

I've set the fans to 1800rpm and never encounter a blue screen, but sometimes, when I turn off the fans, it gives a blue screen error at an uncertain time. To make sure, I formatted the computer and installed Windows 11. I've installed all drivers and will test it.

[seerge]

@hadixcanimm well, apparently something is overheating then :) it may be not CPU or GPU directly, but something on the motherboard itself or so (w/o own temperature sensor). And running fans apparently keep it in a good condition probably :)

[l-naumann]

Thank you! Works a lot better to control the fans on Zephyrus G14 2024 (GA403UI).
However, the fan now runs slightly faster on the slowest setting than with the old build. I use my laptop 95% for office and programming and I can't keep it fanless in balanced mode. Occasionally the fans have to rev up briefly, so I would prefer to run them permanently on very low RPM. At 20% they already produce a very high-pitched noise. Could you add a power-user setting to set the min fan percentage?
I also think that you need an adjustable hysteresis. When the processor is boosted for a short time, there are brief temperature peaks that cause the fans to spin up immediately.

[seerge]

@l-naumann ok. Problem is that different models seem to have different minimum fan speed (and corresponding fan % setting that triggers that) .

At first my idea to mimic asus own fan curves, where 0% = OFF, and 1% = is usually something like 1800RPM (or around 25% of max speed), so people will not have to re-edit their fan curves when they switch.

Reality is more complicated than it is.

Also there is some deviations from actual set value (in %) and real fan speed often. On my G14 2022 20% setting = 25% speed, but from what I have seen here sometimes deviation reaches up to 15% in total ... :|

[l-naumann]

@seerge I see. Maybe the automatic calibration could identify when fans start spinning by increasing fans in 1% steps, starting at 0%. When fans start spinning, add 1-2% as a safety margin and set it as new min percentage.

[seerge]

@l-naumann I have updated build in main post, now it should re-apply fan speeds after wake up no matter what

[l-naumann]

@seerge Thank you, seems to work! Could you please provide a build with min fan percentage = 0% again? Apart from that, this version is perfect for me.

[seerge]

@l-naumann i have updated build in main post again. Now you can set min-fan speed as a parameter in config
"fan_min": 20, - minimum fan speed (in %) when it's not OFF

[Valour549]

So I've been using Armory (all drivers and components fully updated) for the last few weeks on my new Scar 18, and I've spent a lot of time adjusting my fans curves in Manual mode (I dont use any other modes). Today I finally got around to playing some games, and I found out that my fan curves weren't being respected at all! The problem is that the moment I enter a game, all three fans immediately go on full blast, even though my CPU and GPU temps were still in the 60s and my fan curve for 60C most definitely isnt full blast. I have three questions atm:

1. Does this happen for anyone else using AC?
2. Does the fan control in the mainstream g-helper have this issue?
3. I assume this issue definitely won't happen with the experimental fan control right?

[seerge]

@Valour549 hello,

Fans are controlled by firmware / BIOS, even if you use a custom fan curve. BIOS algorithms are different from model to model, and don't always follow your curve precisely, that's absolutely normal. It could be that BIOS senses increased power usage and therefore ramps up fans in advance.

So both AC and mainstream G-Helper build will most likely behave same :) You can try to customize curve a bit more to see if changes something for your.

Experimental build linked here will behave differently as it is able to manually set fan speed. So you are free to try it if you really want precise control :)

[SalvatoreCrobu]

Hi, "fan_shift" and "fan_hysteresis" are not working anymore. I've tried using the normal and the experimental version of G-helper but none of them follow that commands. I am following the json and closing G-Helper before editing. Can you help me?

[seerge]

@SalvatoreCrobu what exactly is not working ?

[SalvatoreCrobu]

Slow fan rump up and gpu fan not following cpu temp

[seerge]

@SalvatoreCrobu can you post a screenshot from Fans+Power tab ? it shows temps for last X seconds (set as fan_hysteresis) in a red label there. If you set it to 2 it should be only 2 last temperatures

P.S. Also it could be that manual fan control is not working cause of broken Asus System Control Interface that you may need to reinstall

[orionflame]

Hi, any idea why the cpu fans might be 0 rpm? Calibrate spins either cpu or the gpu fan up and then back. You can see the CPU temp is really high because I am encoding but before the fans would be at max rpm in this case.

[seerge]

@orionflame

• Do fans actually spin in that moment?
• Do you have anything else running that can override that (asus services under Extra ?)
• Does it work fine with just a default fan behavior (i.e. uncheck Apply)

[orionflame]

Ok so from what I see in the Ghelper tray tooltip, it shows GPU fans at 50% but CPU fans at 0%, so it's quite low fan noise only one one side.

I don't have anything else other than Ghelper. I was going to try the other app I mentioned before to see if it can actually spin the fans. I wonder if the service center somehow caused damage to the fans. I need to check this.

If I uncheck Apply, then it becomes completely silent so I think no.

[orionflame]

Ok even asus fan control app doesn't seem to spin up the CPU fans, I still read 0 in both your app and that app for CPU fan RPM, so I think the CPU fans the service center didn't connect it properly.

[seerge]

@orionflame if you were servicing fans recently, and any other apps or methods don't help (like default bios behavior) - then most likely it's just broken fans :)

[orionflame]

I am surprised they would make such a mistake that would damage the laptop. I will let you know when I get it back and see if it works like before.

[Valour549]

There seems to be an issue where if there is no GPU temp reading, it still doesn't follow CPU temp ("fan_min": 30, "fan_hysteresis": 6, "fan_shift" not set). The GPU fan has been sitting completely still for many many minutes, despite reading multiple values of 0.

Some feedback: It would be good to either have finer breakdown of numbers, or have the dots click into preset positions on the Y-axis. Because at the moment, a 35% could be 3300RPM on the high end and 2900RPM on the low end. The dots should also have boundaries along the X-axis (first dot 20-29C, second dot 30 to 39C, etc). At the moment all these degrees of freedom is making setting a fan curve much harder than it should be.

[Valour549]

Ah it's another old setting that doesn't really do too much apart from Disabled, as this video shows. Any chance of adding a config that stops G-Helper from messing with peripherals? I really like the "skip_aura" : 1, option, would be nice great to have one too for peripherals.

[seerge]

@Valour549 how exactly is G-Helper "messing with peripherals" ? Unless you open mouse settings and change them - it won't do anything by itself

[Valour549]

It's constantly logging my omni receiver XDDDD
log.txt

[Valour549]

1. Is panel overdrive always disabled when on Battery, or does it depend on whether the screen is in 60Hz mode or 240Hz?

2. I noticed that even if ASUSSmartDisplayControl is not running, GHelper still switches to 60Hz when on battery just fine. Can GHelper also disable overdrive when on battery without ASUSSmartDisplayControl? Not really sure how to check if panel overdrive is in effect...

[seerge]

@Valour549

1. It just tries to get battery charge from your mouse
2. When Auto (on battery) or 60hz is selected G-Helper would disable Overdrive. ASUSSmartDisplayControl is not needed here, furthermore it will be interfering by following Armoury's settings.

[Noisrevid]

Just wanted to comment to say that this manual fan control build works perfect on Zenbook S16 (AMD Ryzen AI 9 365/370), even though the app still says "Manual fan control not supported" it actually works! Full RPM control.. Respects any settings and never deviates going lower or higher than I specify. This makes the Zenbook S16 a way more tolerable/controllable machine now in regards to fan noise. Edit: I'm betting that fan control is now possible on many other Asus notebooks because of your new finding!

[seerge]

@orionflame you can achieve that by setting following in a config - then both fans will follow max temp from CPU and GPU.
Check readme in the main post.

"fan_shift" : 100,

[orionflame]

Thanks it works! I just got my laptop back both fans are at the same RPM at about 71% 4100-4200 RPM. I was looking for my older messages here but if I am not wrong, there is no way to achieve 100% for all laptops right? Because I calibrated multiple times but I never get 100% fan speed despite what the graph shows.

[seerge]

@orionflame the only thing Calibrate button does - is sets fan speeds to 100% and then measures how much RPM is that, to adjust Y-Axis on the chart accordingly. So if you drag dot on the char to the top - it is 100%

[orionflame]

Oh yes it adjusted the max rpm to 5800 but currently for the CPU at 85C, it's not using 100% fan speed unlike the custom graph values.

At this stage, i pressed calibrate again and I didn't notice any noise level change so this seems to be that this is the maximum speed. So I think the fans never go to 5800 RPM. But I might be wrong.

When I use Asus Fan Control at 100% speed, I am seeing 4800 and 4477 for CPU and GPU respectively. I didn't notice any noise level change also, so not sure where the discrepancy is coming from.

This is how it looked when I had the fan control ON:

When I have it OFF and refreshed the current RPM:

I think AFC seems accurate because in the last image the RPMs match what Ghelper also reports, albeit rounded down.

If I use AFC at 100%, then Ghelper will report higher RPM like 4600 to 4800:

I am only using both for comparing RPMs, so it's only for testing. So not sure how AFC can reach higher RPMs but Ghelper will not go above 4200. Because clearly Ghelper will reflect higher RPMs when AFC does it, but not by itself.

Maybe it's some kind of mechanism because after seeing 4800 RPM for a while using AFC, it does drop lower.

[seerge]

@orionflame it could be that firmware still overrides fan speeds by some reason. AFC does same thing as this experimental build of G-Helper - uses "myasus fan test command" to set fan speeds. Fan speed is set in %. You can't set speed higher than 100% :)

[Snow2040]

Hello, I am using the latest manual fan control experimental build with an asus dash tuf f15 517zr laptop and the fan_shift, and hysteresis options are just not there in the config file, otherwise everything works fine.
here are the contents of the file:
{
"performance_mode": 2,
"performance_1": 2,
"gpu_mode": 1,
"internal_display": "",
"screen_max": 144,
"frequency": 144,
"overdrive": 1,
"charge_limit": 60,
"performance_0": 4,
"m4": "",
"keyboard_brightness": 3,
"keyboard_brightness_ac": 1,
"topmost": 0,
"mid_fan": 0,
"xgm_fan": 0,
"fan_profile_cpu_0": "1E-31-39-3C-42-49-4F-59-00-08-0D-31-3E-47-50-59",
"fan_profile_gpu_0": "17-27-2F-33-3D-46-4F-5A-04-0A-10-30-3C-44-46-50",
"limit_total_0": 25,
"limit_cpu_0": 17,
"limit_fast_0": 125,
"fan_profile_cpu_1": "14-25-31-3B-41-4A-55-64-11-29-3E-4B-56-64-64-64",
"fan_profile_gpu_1": "14-32-3C-40-46-4C-53-62-16-1B-3A-44-4D-54-58-5F",
"limit_total_1": 45,
"limit_cpu_1": 34,
"limit_fast_1": 125,
"fan_profile_cpu_2": "1E-3C-41-42-47-4B-4C-62-00-03-0C-0C-16-22-22-29",
"fan_profile_gpu_2": "1E-3C-41-42-47-4B-4C-62-00-08-11-11-1D-26-26-2D",
"limit_total_2": 10,
"limit_cpu_2": 10,
"limit_fast_2": 125,
"cpu_temp_0": -1,
"auto_uv_0": 0,
"gpu_core_2": -250,
"gpu_temp_2": 75,
"auto_apply_power_0": 1,
"gpu_memory_2": -250,
"auto_apply_0": 1,
"auto_apply_power_2": 1,
"auto_apply_2": 0,
"auto_uv_3": 0,
"cpu_temp_3": -1,
"cpu_uv_3": 0,
"igpu_uv_3": 0,
"gpu_boost_2": 5,
"igpu_uv_2": 0,
"cpu_uv_2": 0,
"cpu_temp_2": -1,
"auto_uv_2": 0,
"cpu_uv_0": 0,
"igpu_uv_0": 0,
"gpu_boost_0": 5,
"gpu_temp_0": 87,
"gpu_core_0": 0,
"gpu_memory_0": 0,
"gpu_core_1": 50,
"gpu_memory_1": 100,
"auto_boost_2": 0,
"auto_boost_1": 1,
"fan_max": 64,
"screen_auto": 1,
"gpu_boost_4": 25,
"gpu_temp_4": 87,
"toggle_clamshell_mode": 0,
"gpu_auto": 0,
"auto_apply_power_1": 1,
"limit_cpu_4": 20,
"limit_total_4": 25,
"auto_apply_power_4": 1,
"auto_apply_4": 1,
"limit_fast_4": 125,
"fan_profile_gpu_4": "14-20-2C-37-40-4B-57-64-16-32-43-4F-59-5F-64-64",
"fan_profile_cpu_4": "14-2E-37-3D-42-4C-55-5C-11-26-38-4C-55-59-5B-64",
"mode_base_4": 1,
"mode_name_4": "Performance (GPU)",
"gpu_core_4": 0,
"gpu_memory_4": 0,
"auto_boost_4": 1,
"auto_apply_1": 1,
"auto_uv_1": 0,
"cpu_temp_1": -1,
"cpu_uv_1": 0,
"igpu_uv_1": 0,
"gpu_boost_1": 25,
"gpu_temp_1": 87,
"skip_version": "0.194",
"aura_mode": 0,
"charge_full": 0,
"powermode_0": "ded574b5-45a0-4f42-8737-46345c09c238",
"fan_max_0": 84,
"powermode_2": "00000000-0000-0000-0000-000000000000",
"kill_gpu_apps": 1,
"aura_speed": 1,
"limit_slow_0": 35,
"limit_slow_4": 30,
"fan_max_1": 84,
"visual": 11,
"color_temp": 50,
"m3": "",
"limit_slow_2": 10,
"limit_slow_1": 55,
"optimized_usbc": 0,
"auto_boost_0": 1,
"mode_base_3": 1,
"mode_name_3": "No boost",
"fan_profile_cpu_3": "14-1E-23-29-35-40-52-62-11-1A-30-40-46-4E-56-5A",
"fan_profile_gpu_3": "14-18-1C-25-36-42-52-59-16-27-35-42-4D-4E-51-64",
"limit_total_3": 20,
"limit_slow_3": 30,
"limit_cpu_3": 19,
"limit_fast_3": 80,
"auto_boost_3": 0,
"auto_apply_power_3": 1,
"auto_apply_3": 1,
"gpu_clock_limit_1": 3000,
"mode_base_5": 1,
"mode_name_5": "Performance (CPU)",
"fan_profile_cpu_5": "14-27-2C-33-3C-46-55-63-11-13-2A-3C-53-5B-64-64",
"fan_profile_gpu_5": "14-20-2A-32-42-4B-56-64-16-1F-3B-4D-57-5A-5D-64",
"limit_total_5": 40,
"limit_slow_5": 45,
"limit_cpu_5": 32,
"limit_fast_5": 80,
"auto_apply_power_5": 1,
"auto_apply_5": 1,
"gpu_boost_5": 5,
"gpu_temp_5": 87,
"gpu_core_3": 50,
"gpu_memory_3": 100,
"gpu_core_5": 0,
"gpu_memory_5": 0,
"gpu_fix": 1,
"boot_sound": 1,
"start_count": 61,
"max_frequency": 144,
"donate_click": 1,
"bw_icon": 0
}

[seerge]

@Snow2040 hello, you need to add those values manually to the config.

[Snow2040]

Thanks for the clarification.

[Clairvoyant413]

Hey seerge, can you please give the link to the last version (0.191 to be specific) of the experimental build? This one seems to bug out alot and not set the fans to the set curve and doesn't show the temp of the CPU/GPU. I'm on FA706IHRB

[seerge]

@Clairvoyant413 hello, on your screenshot manual fan control is simply not enabled. Most likely you have broken Asus System Control interface that you need to reinstall.

When fan control is working - you will see a red label under fan charts showing currently set fan speeds.

There is no changes in terms of fan control between 0.194 and any other build posted here for the last half of the year or so. The only thing i'm doing - is merging other changes from the mainstream branch to experimental build :)

[Clairvoyant413]

This worked :) thanks man, it was helpful.

[orionflame]

I just noticed the CPU fan was running at 0 when I noticed the hot air coming and then Ghelper tray was showing 0 RPM. I brought the app up but it hung up for minutes (the window was showing but no controls) so I had to kill it. I worried the CPU fan had an issue again so run AFC and it spin both up to max speed. Then I stopped that and re-run Ghelper and it seemed to work now.

Could this be due to service you are using that might have hung up? Is it a good idea to have visual or sound alarm for when a fan is 0 RPM? I don't know if 0 RPM is ever a good idea to have so would be good if there was a way to signal this.

Or even a visual indicator in the tray like flashing red.

[seerge]

@orionflame may be Asus driver has stopped responding ? Try to reinstall Asus System Control interface - it may help.

What proceeded to this situation?

App switches back to default (firmware based) fan control as it sees that it's impossible to set fan speeds. There is no point flashing when fans are set to 0 cause it's still based on fan curve, and 0 is intentional then :)

[orionflame]

I am not sure if the asus driver stopped working. Is there a way to verify this? It would be nice if GH can relaunch the stopped driver? Because when I launched AFC it pushed the fans to 100% which made me realize at least the fans are working.

I guess a way to tell if the software is using firmware or the custom curve, experimental mode would be useful IMO. In any case the app didn't come back into view properly so I guess it hung up on some driver waiting for input? Maybe it needs a time out?

[seerge]

@orionflame usually it says that in a log, but if app spots that (i.e. if at least one fan speed command fails - it will turn manual control off).

When manual fan control is working - it shows current fan speeds that app sets under a red label at Fans+Power (and it also writes that to the log all the time). If you don't see it there - manual fan control is not working.

[sandbox4dev]

Hey there,

I just wanted to say thanks for your awesome software!
The fan control is working great on my ASUS Vivobook S 16X m5602ra-kv048 with a Ryzen 7 6800H with no dGPU, even though the message said it wasn't supported. The minimum speed limit through the config file is working perfectly too, and the temperature limits are spot on.

I don't know if this is normal, but during calibration, it showed a max speed of 6800 RPM for the CPU and 5800 RPM for the iGPU, even though there's only one fan.

Sometimes, if the 'Apply cooler profile' checkbox is checked and I right-click the ghelper tray icon and select 'Exit', the fan starts spinning at maximum speed. This behavior persists even after a reboot. The only way to fix it is by starting ghelper, unchecking the box, and then clicking 'Exit'

Just a few other things I noticed (not sure if they're related):

• I couldn't install fPPT, and the adjustment isn't showing up in the menu. I checked with UXTU, and it seems like it should be possible.
• I don't think the SPL adjustment is doing anything (I checked the actual values in HWInfo).
• The sPPT adjustment works fine.
• My laptop only has a static white backlight with 3 levels.
• The button mappings in the extra settings menu aren't relevant for my model.

It would be amazing if you could add the ability to control the iGPU core frequency. In UXTU, I can set it between 400-2200 MHz in 200 MHz increments.

Thanks again for the great software!

[seerge]

@sandbox4dev hello,

• When you Exit from app it just sets back one of 3 default modes. As it obviously not going to control fans anymore. That's why your fans start behaving differently. You can verify that in %appdata%\GHelper\log.txt
• App sets fPPT together with sPPT in your case and also uses UXTU's library under the hood (for ROG / TUF / ProArt there is better and more official asus-way)
• I think it works too. Check app log to see if command is accepted.
• I don't want to add that. In my experience that after setting iGPU clocks in UXTU, you can't "unset" them back to defaults. So you need to reboot for that.

[sandbox4dev]

You're totally right! The f,s(PPT) limits are the same for both.

The logs show:

07.10.2024 18:02:23: STAPM: 40 OK
07.07.10.2024 18:02:23: STAPM2: 40 OK

But I can't figure out what this limit means when I look at it in HWInfo.

Is there a way to set the CPU Package Power Traking(PPT) to less than 54W using a config file?

ASUS software is giving me the bare minimum. Battery limit and three preset modes. lol

Thanks for your help!

[seerge]

@sandbox4dev

That means power limits work.

That's not how you check actual power limits tho. You need to run some CPU heavy benchmark (like Cinebench23) and monitor actual CPU power consumption in the same HWinfo for example. In your case it should be like 45W for the first 2 minutes or so and then drop to 40w.

[wrccclight]

Why is my fan speed 500 to 1000 higher than my preset speed? How should I set it up?

[seerge]

@wrccclight because fan speed is set in % points, and then BIOS interprets them. You can try to click Calibrate to match RPM-axis closer to actual speeds.

Or also you can try to set lower minimum fan speed in config, like

"fan_min": 0,

[Devisione]

thank you very much for this patch. on zephyrus g16 with ultra 9 + 4090 worked just this version. add please toogle button in the main branch.

[seerge]

@Devisione hello, glad to hear. But on this stage I don't plan to merge this experimental features with the mainstream branch :)

[sunlooksgreen]

Hello Seerge,

Last update seems to have broken in my computer the ability to change fan speed..
could you please post link to last version before 0.197?

thanks in advance

pd: tried to reinstall Asus System Control but it didn't help

[seerge]

@sunlooksgreen hello, there are no changes related to fan control in 0.197 . I'm just merging other (unrelated) updates from the mainstream branch into this one periodically. Upload the log form the app here.

[sunlooksgreen]

ok here they are:
config.json
log.txt

and here is a screenshot..

don't know what happened.. before I could read in red the fan's data whereas now it says model not supported..

Thanks Seerge!

Regards
Albert

[seerge]

@sunlooksgreen I think you are just using a mainstream build now (not the one from this branch), probably cause you have auto-updated to it. Just download one from the head post in this thread and you will be ok.

[sunlooksgreen]

Thanks Seerge! will check it out and report back

[zackriso]

Amazing tool, thank you!

I noticed sometimes when I reboot, the fan curve does not automatically apply, even though I set the tool to Run on Startup.

Another question please: is there a reason why we cannot run the fans at a lower RPM than 20% (in my case 1400 RPM)? Can we at least have the possibility to try at 15 or 10%? If it does not work, then we can run it up to 20%.

[zackriso]

Ohh got it. Can can do so by RPM instead, for example, right now the lowest I can set in the graph is 1400 RPM, can I set it to 800RPM in the config file?

[seerge]

You can't set RPM, you can set minimum percentage (as this is the unit being used to send a command to a driver)

[zackriso]

Thanks!

One last thing. I did the calibration, and I set it to 1400RPM, however under the main Ghelper window, it still show 2000-2100 RPM.

[seerge]

@zackriso cause calibration only measures how much RPM would 100% be (and adjusts that if needed). Min RPM on Y-axis is hardcoded to 1800 (which corresponds to ~20% in most of the cases). Since you lowered that - it's not aware, so just ignore that

[zackriso]

Ahh got it. in my case, I do see 1400 RPM as the lowest value, then 1600, and then 1800. Each has an actually different fan speed

[zackriso]

How do I "reset" Ghelper to 100% defaults, including resetting all calibrations done, and so on?

[seerge]

@zackriso calibration is only needed for correct RPM display on Y-axis on the chart, it's cosmetic.
If you want to reset all settings inside the mode - click Factory Defaults, as it's pretty much self explanatory

[zackriso]

From my testing, Calibration seems to work best only when the "Apply Custom Fan Curve" is unchecked. Otherwise, it acts weird.

And I think once I set the fan_min to let's say 15%, I think the calibration has to be run again.

[zackriso]

Sorry for my too many questions, but I just love this tool!

Anyway to set the CPU temp limit under Advanced to a lower value than 75C?

[zackriso]

@seerge Any ideas?

[seerge]

@zackriso you can do that by adding param to config. But i do not advice it as it makes not much sense. By reaching throttle temp CPU just drops it's power, so you will end up having something like 10w power limit with such lower temp setting.

[zackriso]

@seerge: in my case it actually does make sense to lower it. I am trying to reach the quietest setup possible with 10,000 Cinebnech points, so I will use CPU temp limit, power limits, CPU undervolting all together to get to that point. The HX AI 370 is a 12-cores CPU, I think it can reach 24,000 points without contraints.

[seerge]

@zackriso temp limit also limits power, you can just set lower power limits then :) you will get more predictable power limits at least in this case

[zackriso]

@seerge: True, yes, though the good thing about temp limit is that if you run a heavy workload over a long period of time, the CPU compounds heat over time, and setting the CPU temp limit will make it downclock on its own, regardless if the power limit was reached or not. Also, if am running low fan RPMs, and the CPU has not reached the power limit (eg, 35 watts), then the CPU temp limit will kick in at 65C for example. Its an additional option that helps in many scenarios.