Tool to Control Fan - fanctl

[tuxd3v]

Hello Luke,
I think I understood what you were talking about.. 

I reproduced that behaviour..
stopping ats,
then running ats in test mode..

Code:

root@rockpro64:~# ats -t
info:'SYSTEM' Table
info:    'BOARD' Table
info:        'NAME' = ROCKPRO64
info:        'CPU'  = RK3399
info:    'THERMAL0_CTL' = /sys/class/thermal/thermal_zone0/temp
info:    'THERMAL1_CTL' = /sys/class/thermal/thermal_zone1/temp
info:    'PWM_CTL'      = /sys/class/hwmon/hwmon0/pwm1
warn:    'MAX_CONTINUOUS_THERMAL_TEMP' outside range] -20, 70 [
        'MAX_CONTINUOUS_THERMAL_TEMP' = 60
info:    'MIN_CONTINUOUS_THERMAL_TEMP' = 60

ATS, has hard-limits for temps..
When you configure it to:

Code:

      -- Max Temperature Allowed for adjusting fan pwm( On this threshold, and above, fan is always on MaxValue )
      MAX_CONTINUOUS_THERMAL_TEMP     = 70,
      -- Min Temperature  threshold to activate/deactivate Fan
      MIN_CONTINUOUS_THERMAL_TEMP     = 60,

You are hitting the higher hard limit range: ] -20, 70 [
So Ats warns you,
And corrects 'MAX_CONTINUOUS_THERMAL_TEMP' to 60C

In this situation you end with higher and lower trigger points equal..
Without code changes, the Closest you can get in /etc/ats.conf would be:

Code:

      -- Max Temperature Allowed for adjusting fan pwm( On this threshold, and above, fan is always on MaxValue )
      MAX_CONTINUOUS_THERMAL_TEMP     = 69,
      -- Min Temperature  threshold to activate/deactivate Fan
      MIN_CONTINUOUS_THERMAL_TEMP     = 60,

An output in test mode:

Code:

root@rockpro64:~# ats -t
info:'SYSTEM' Table
info:    'BOARD' Table
info:        'NAME' = ROCKPRO64
info:        'CPU'  = RK3399
info:    'THERMAL0_CTL' = /sys/class/thermal/thermal_zone0/temp
info:    'THERMAL1_CTL' = /sys/class/thermal/thermal_zone1/temp
info:    'PWM_CTL'      = /sys/class/hwmon/hwmon0/pwm1
info:    'MAX_CONTINUOUS_THERMAL_TEMP' = 69
info:    'MIN_CONTINUOUS_THERMAL_TEMP' = 60
info:    'MAX_PWM' = 255
info:    'MIN_PWM' = 40
info:    'ALWAYS_ON' = false
info:    'PROFILE_NAME' = profile0
info:    'PROFILE'      = 0
info:'Pratio' timers
info:    'Pratio[ -20 - 60 [' = 0
info:    'Pratio[ 60 ]'       = 40
info:    'Pratio[ 61 ]'       = 63
info:    'Pratio[ 62 ]'       = 87
info:    'Pratio[ 63 ]'       = 111
info:    'Pratio[ 64 ]'       = 135
info:    'Pratio[ 65 ]'       = 159
info:    'Pratio[ 66 ]'       = 183
info:    'Pratio[ 67 ]'       = 207
info:    'Pratio[ 68 ]'       = 231
info:    'Pratio[ 69 ]'       = 255
info:    'Pratio[ 69 - 70 ['  = 255
Stop ATS Service first [ service ats stop ]..

No more warnings, and so no internal adjustments..

But even So, I could reproduce your report:

Code:

--------------------
Running for[ seconds ]................ 0
CPU Temperature[ max 70 °C ].......... 58
GPU Temperature[ max 70 °C ].......... 49
Fan PWM Duty Cycle value[ 0 - 255 ]... 0
--------------------
Stopping for[ seconds ]............... 120
CPU Temperature[ max 70 °C ].......... 58
GPU Temperature[ max 70 °C ].......... 49
Fan PWM Duty Cycle value[ 0 - 255 ]... 0
--------------------

I will look into the code, and check it..
The power is activated in 2 phases, probably the first one is running, on this conditions..

Thanks for reporting that!