[Experimental] Manual Fan Control #2272
Replies: 205 comments 813 replies
|
At this setting, the fan speed on the left side of the machine(CPU fan) is at full speed. |
|
@FliesQQ how fast fans will speed up still depends on hardware of course :) actual command is being sent immediately (i.e. every second) |
|
So this is already very good now. |
|
If GPU and CPU both in use, seems like CPU fan curve not function correct. |
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? |
|
@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? |
|
Yes, you should download updates from this thread only :) I don't plan to merge manual fan control into mainstream branch yet. |
I got it. |
This comment has been hidden.
This comment has been hidden.
|
@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 :) |
|
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. |
|
@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 |
|
Yes, it's really a pity. |
|
@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) |
|
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 |
|
Great news |
|
Log extract: 2024-03-23 20:43:21: Mode = 0 : OK As you can see, the FanCPU and FanGPU percentages don't match what is actually running (confirmed by hwinfo fan reading) |
|
@fscottcopeland can you switch scale to RPM? Asus has quite specific interpretation of % points :) |
|
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. |
|
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. |
|
@Summersoff what's your laptop? Duo 16 2023 too? |
|
@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. |
|
@fscottcopeland if you disable custom fan curve, it's back to whatever default fan behavior is for each of your modes :) |
|
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. |
|
Thank you so much! it works great! |
|
@yesnt10 amazing |
|
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 |
|
@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 |
|
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 |
|
@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. |
|
Very nice. I'll check it out. --- EDIT --- |
|
@manciuszz my idea to keep things simple on this stage |
|
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: ***@***.***>
|
|
@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) |
|
Nice feature, thanks! |
|
And it can fully turn off it after I switch to Turbo and back to Silence. |
|
@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. |
|
@seerge That's really stupid. |
|
|
|
PS: 0.154.0 can set minimal 1800RPM and real 1800~2400 RPM |
|
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 ... |
|
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. |
|
I think for office use you can get away with fans being completely off at all. Its also good for battery life |
|
Yeah, and i have heard about, 4800HS performance better than newest 7840H under 10W, a Surprise. |
|
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. |
|
I'm glad it works |
|
Working exactly as expected on G713RW. GHelper keeps on delivering!
|
|
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. |
|
Are you sure it's related ? may be it's just some gpu issues? try to run fans on minimal speeds otherwise :) |
|
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. |
|
@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 :) |
|
Thank you! Works a lot better to control the fans on Zephyrus G14 2024 (GA403UI). |
|
@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 ... :| |
|
@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. |
|
@l-naumann I have updated build in main post, now it should re-apply fan speeds after wake up no matter what |
|
@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. |
|
@l-naumann i have updated build in main post again. Now you can set min-fan speed as a parameter in config |
|
@seerge hi seerge probably i got a bug when i try the latest ghelper experimental version with using hysteresis sliders the left side show current gpu and cpu fan rpm but right side doesnt show it correctly also my gpu fan doesnt work only cpu fan work, normally my config.json has fan_hysteresis: 1 value and my fans work very well but at this point i changed sliders to very low and only my cpu fan work but very low rpm and gpu fan doesnt work like old versions 
|
|
@seerge also i tested it on game normally on load this game with same fan curve setting my cpu and gpu fan should run above 4.500-5000rpm 
|
|
@seerge i literally like old fan control algorithm this new algorithm not good for me :D i like aggressive fan |
|
@gigantf15 you need to do calibration, then app would measure RPM for every 5% step. After that it will be accurate. Minimal hysteresis - is your "old" aggressive fan. |
@seerge my config.json still has fan_hysteresis: 1 code, should i remove it? also can u add translation for Türkish? Fan Gecikmesi Yükselmesi => Hysteresis Up, Fan Gecikmesi Azalması => Hysteresis Down, Very Low => Çok Düşük, Low => Düşük, Medium => Orta, High => Yüksek, Very High => Çok Yüksek. |
|
@gigantf15 minimal hysteresis - is when fans can increase their speed up to 50%(!) per second. It's exactly as it was before. What you have in your config is absolutely correct. |
|
it's literally useless for 40 series because our gpu hardware or software doesnt support watt limits u can change only cpu or memory clock |
I found a bug: when selecting the default setting, the temperature limit does not return to the default, it remains the same as it was selected before
|
|
Hey @seerge would you be able to add the ability to change calibration speed / accuracy? By that, I mean: Perhaps if there was a way to run a longer, more accurate calibration, this would help things. I imagine: |
|
First of all your device must have a very slow fan reaction, if it doesn't manage to change fan on extra 5% in 5 seconds (+ on calibration start it adds an extra 5 seconds just to stay on zero-level) Current calibration logic, is that if on each next step it sees a lower speed by some reason, it would discard / lower all previous step(s). So it accounts for possible nonsense-readings from sensors or so. I can add a custom param for calibration time, so you can just set it to 10s for yourself. There is no need to do a second step of 10 seconds tho, as app just uses maximum observed RPM for each step. |
|
Hey @seerge so I hear the fans click on within the 5 seconds, but I don't think they reach a stable speed within the 5 second period. I'm not sure about taking the max fan speed and using that as the value - I've found the fans tended to overspeed and then reduce slightly - so the long-term "stable" RPM at a given point can be slightly different to the "max" observed fan speed Therefore, I think getting the fans up to speed and then getting an average RPM over a few seconds (rather than just picking the max value) would provide a better representation of what the fans actually do. |
|
@fscottcopeland can you try build from this post #5308 ? (other user asked pretty much same thing, so I have added it there). It should stay on each step for 10 seconds for your model. |
|
Hi, I've been using G-Helper and wanted to report two bugs I found on my ROG Zephyrus G15 GA503RM (v0.247.0). Bug 1 – Fan sensor mislabeling in the header When the CPU fan speeds up, the fan curve panel at the bottom incorrectly attributes the RPM change to the GPU fan instead of the CPU fan. For example, the CPU fan was physically spinning at ~5200 RPM, but the panel displayed "GPU: 5200 RPM" rather than reflecting it under the CPU fan. The fans themselves are spinning correctly; it appears to be a sensor labeling issue in the fan curve display. 
Bug 2 – Fan calibration applies with a consistent ~500 RPM offset The fan calibration feature doesn't seem to apply accurately. During calibration at 100%, there was a consistent ~500 RPM discrepancy between the value shown in the calibration panel (CPU: 6200 RPM, GPU: 6300 RPM) and the value displayed in the G-Helper header (CPU: 6700 RPM, GPU: 6800 RPM). It's unclear which reading is accurate, but this offset appears to carry over to all fan curve settings, causing the actual fan speed to deviate significantly from the configured target. I've attached screenshots for both. Hope this helps, and thanks for the great tool! 
|
|
@cheonmux hello, can you post a separate issue and upload app log there? Ideally after running calibration. Thanks! |
|
Hello, when I set the gpu power to for example a higher or lower one like 45W and then close the fans and power tab and reopen it shows it back to the original one which is 25W and I cannot change it. What could cause it? |
|
@crxptt1 what model do you have ? only new ones support GPU Power on firmware level, for the rest it does nothing. |
|
System Model Vivobook_ASUSLaptop K3605ZC_K3605ZC That's my model I guess that could be the reason it doesn't work. But at least now I can control CPU and GPU fan, thanks for that update! |
|
Hi i want to request something on fan setting so if i set fan curve like this turning off at 60 but actualy off at 55, and turn on again after hit 60 again, so there is 5c gap Can you make setting that can set the gap so that (for example), it after hiting 60c fan would on and turns off at 40c and turns on again at 60c so that the fan is really given time to cool properly? because now ghelper have ability to set manualy without rely algorithm from bios |
|
@statting what you ask is effectively a very delayed reaction on temp change, just try to set both hysteresis sliders to HIGH / HIGHEST |
|
some times fan reading (red font under curve) disapear and fan stop reacting on temp change despite setiing low/high clicking calibration shows like this switching betwen profile fan reading (red font under curve) appear again and calibration button works now oh anyway, on this ghelper my max fan speed calibrated at 7100, but on official ghelper and armoury at 6700 |
|
@statting it's likely something really-really broken with Asus drivers on your device, try to completely reinstall Asus System Control Interface |
|
Hello seerge. I have been using the ghelper since some time and love it. Although like majority of users i never posted a thank you post, except for now when am facing an issue. So am sorry for that first. I recently picked the experimental branch ghelper to enable fan control on my laptop which is zenbook flip 14 oled (UP5401ZA) which has no dGPU and a 12500h CPU and has two fans. On latest 2 builds, the fan on right, controlled by GPU Fan Profile was ramping up to full speed as soon as the graph was changed to anything over 0%. The other fan followed along nicely. I straight up downloaded v244.2 and it seems to control the fan nicely, but i think readings reported are wrong. Not that it matters much but just pointing it out. I even tried updating to latest ASUS Control Interface with no luck. I don't know what info to provide you with, so if you need anything, please let me know. |
|
@marsweed i suggest to click |
|
@seerge sorry i never reverted back. but i moved to CachyOs linux the day i had posted and i have not seen windows since, on that laptop. My laptop fan run quieter and the body stays cool as well. It is a win win for me. If i ever go back to windows, i will create an issue for the same and provide all possible info i can. Still, thank you for the app. It is really a great piece of software coming from a single guy. |
|
Hi seerge. |
|
understanding your meaning, tonight after restart windows, the log as below: after calibrating, speed turned normal |
|
@xiaozzh great, that's what calibration is for :) |
|
So, it means, everytime restart windows, all need to calibrate? |
|
@xiaozzh you definitely don't have to calibrate every time. Doing it once is more than enough. |
|
hi |
|
@Ulysses996 hello, it's not much changes in terms on fan controls between releases :) Only minor tweaks mentioned in release notes. Try to click Calibrate, and if something doesn't work - post a new issue including app logs and mentioning it's Experimental build. |
|
Hi with ver 0.250 fan calibrating not work. i have fa507. with prev version fan calibrating id ok but now this happen : |
|
@C4r3s-1 hello, it's not much changes in terms on fan controls between releases :) Only minor tweaks mentioned in release notes. Try to click Calibrate, and if something doesn't work - post a new issue including app logs and mentioning it's Experimental build. |
|
hi brother just want to say that |
|
@Ahmedmo04 it's false positive. |
|
I know I'm just telling you brother 😹 it's windows defender I'm telling you that version only and the other version is okay, anyway thank you I wish great day I'm really love your program and that version because my laptop is not supported for manual mode and you made me get ride of asus software, 6MB program kick company software it's you developer not company with money I wish you more success and happy life. |
|
bonjour voila je voudrait faire une donnation a ghelper mais pas de carte de banque j ai simplement un compte paypal . |
|
@claudius009 there is a paypal link on that page :) in a second row. Maximum power limits are defined by actual hardware. |
|
petite question Overlay va t il aussi fonctionné bientot pour les jeux directx 9 ? |
|
@claudius009 overlay can work for directx 9 games evne now, just make sure you use windowed-fullscreen mode there (don't use exclusive fullscreen as it may block overlay) |
|
voila don 10.87 euro effectuez via pay pal j espère vous avez bien reçus |
|
@claudius009 merci :) |
|
0.264 works perfect on asus rog strix g16 614ji, much better than standart ver. |
|
Trying the PawnIO version of 269 and it is saying manual control is inactive (it said it on both v40 and v67 of the asus driver) |
|
@RainofTerra for PawnIO version you need to install PawnIO (it should prompt you for it under |
|
I figured it was probably that, but the ASCI error seemed weird so I figured I'd check (I assume its just leftover from the other version?) |
|
@RainofTerra yeah, cause OG warning label didn't get updated :) thanks for spotting .. i'll update it. Warning appears when fan control can't connect to a driver (in this case to missing pawnio) |
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
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 always handled by firmware / BIOS and follow its 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
Potential downsides and risks
💾 Download Experimental Release
Warning
Please test on your own risk (!) and only as a last resort in case you can't achieve desired fan behavior otherwise. Experimental release is provided "as is" without warranty of any kind.
Possible params for
%APPDATA%\GHelper\config.json(with their default values)"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 100If 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 RPMsYou will see what is actually being set as your fan speeds on
Fans+Powerscreen under fan curves chart. Don't forget to clickApply.All reactions