10-05-2019, 08:04 AM
Hello all,
Was fixed a bug in ATS,
When,
'ALWAYS_ON = true'
Initially, sometimes, ATS had problems to acquire the actual PWM state( when service starts..it was a random situation.. ), and so ats now ships with the initial pwm value set to 190 be default( its the initial value before it start to compute the trip trigger points.. )..
I have done some tests yesterday during the night, and it seems ok, its now in the master branch, if someone wants it.
next release will be a point fix release to eliminate older profile code, to solve Luke's reported bug, and to install to Luarocks place, so that you can remove it easily( if you want to ), with 'luarocks remove ats'..
After that,
I will start to add more features like, disk temp monitoring( I need yet to think in a good priority mechanism, so that ats can choose what temps are dangerous, and what don't, between disks, cpu, gpu.. )..
Was fixed a bug in ATS,
When,
'ALWAYS_ON = true'
Initially, sometimes, ATS had problems to acquire the actual PWM state( when service starts..it was a random situation.. ), and so ats now ships with the initial pwm value set to 190 be default( its the initial value before it start to compute the trip trigger points.. )..
I have done some tests yesterday during the night, and it seems ok, its now in the master branch, if someone wants it.
next release will be a point fix release to eliminate older profile code, to solve Luke's reported bug, and to install to Luarocks place, so that you can remove it easily( if you want to ), with 'luarocks remove ats'..
After that,
I will start to add more features like, disk temp monitoring( I need yet to think in a good priority mechanism, so that ats can choose what temps are dangerous, and what don't, between disks, cpu, gpu.. )..