Tool to Control Fan - fanctl

[tuxd3v]

Just wanted to thank you once again for this great utility. Works nicely on mainline (5.0-RC X), but the fan seems to rev up every 2-3 min despite tempt being lower than my minimum values for CPU/GPU set in ats.conf. Ideas as to why this may happen ?

Hello Luke,
You Welcome,  
I am using it since maybe August of last year, on its several iterations..
Now the worst performance should be around ~0.0011% cpu time..
I think I can lower it a bit more( maybe ~0.0009% ), but now starts to be very difficult to do so..

This values can be better measured, for example, in a up-time of 1 month or so( because when ATS starts, it consumes more CPU... it needs to calculate the triggers to use during its work, but after that, it is almost all the time sleeping in a C loop code section..sleeping ).

I plan to add more options to it, like options to drive a pwm via GPIO, or even if disks connected are getting temps too high..
I am planning to develop a kernel driver for the PWM part, via GPIO, with dma and so on..
I am planning for the H6 first, because its cheaper( If I burn something testing, I burn something less expensive ). 

I haven't understood you completely..
You say that the Fan starts spinning at intervals around 2-3 minutes, even when temps are outside activation window?
It could be that, temps reach the minimum, for very brief intervals of time, and ats starts?

By default the Fan activates in this window[40-60]( Above 60C is always in maximum speed, bellow 40C it stops.. ):

Code:

    MAX_CONTINUOUS_THERMAL_TEMP    = 60,
    MIN_CONTINUOUS_THERMAL_TEMP    = 40,

1)You can grow up the minimum level to lets say ie: 50C, so that fan only starts spinning at ie: 50C ..
In that case it will be in '/etc/ats.conf':

Code:

MAX_CONTINUOUS_THERMAL_TEMP = 60,
MIN_CONTINUOUS_THERMAL_TEMP = 50,

And restart the service after.

Code:

systemctl restart ats

I don't know if the problem is with the minimum threshold( to activate fan), or if you want the fan always on?

2)For Always on in '/etc/ats.conf':

Code:

ALWAYS_ON = true,

And restart the Service:

Code:

systemctl restart ats

In this case Fan is always on, but the Algorithm for pwn is the same, so fan adjusts itself to temps, if temps higher, it rise power, if temps lower it lower the power applied to the fan.. 

3) For checking triggers:
With service running, start ats in test mode "by hand", typing:

Code:

ats -t

It will show you the range/temps/power applied for that situations, were fan will be active..

4) For seeing in real time the actions taken by ATS:
stop service ats first.

Code:

service ats stop

And then, start it "by hand"...in test mode:

Code:

ats -t

It will print information about the state were it his..
Temps acquired, and power delivered to the Fan, on each cycle..

There are other type of turnings that can be made for example to adjust the triggers themselves, internally( in the C backend ), for different cooler/fans..
But for that I would need to have that cooler/fan, to adjust for it..