• 23.07.2025, 18:53
  • Register
  • Login

  • You are not logged in.

 

low pass filter?

Dear visitor, welcome to Aqua Computer Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

Asryan

Junior Member

low pass filter?

Wednesday, December 9th 2020, 7:51am

Hi,

I really have trouble to understand the low pass filter and what's damping means.

I have set up some virtual sensors for
CPU
GPU

and an average of the two for front fans and exhaust back fans

i've set the average of 20s for X=avg (t)
and i was tole to put timespan of 20s and dampng of 25 for low pass filter but i don't understand really what that means.

if someone can help !


Also i've noticed that at startup my cpu temps is around 30c but the avg is way higer for 30s and the result of my virtual sensor is 100c so the fans are at 100% for nothing and i don't understand why. How can i fix that?

Thanks again

sebastian

Administrator

Wednesday, December 9th 2020, 7:55am

make few screenshots from your settings. Take a look at fallback values from your data sources.
Wait a few minutes.

k2viper

Full Member

RE: low pass filter?

Wednesday, December 9th 2020, 9:15am

Quoted from "Asryan"

Also i've noticed that at startup my cpu temps is around 30c but the avg is way higer for 30s and the result of my virtual sensor is 100c so the fans are at 100% for nothing and i don't understand why. How can i fix that?

At startup the values of CPU/GPU temps are not being read yet, and a "Fallback value" is used until the actual reading begins.
Default is 100 (probably), just change the fallback values to your typical startup CPU/GPU temp respectively to get correct approximations.

Asryan

Junior Member

Wednesday, December 9th 2020, 1:00pm

thanks,

here's some screen of my settings :

https://drive.google.com/drive/folders/1…UmO?usp=sharing

for the fallback i'm at 70% but i was talking about the virtual sensors being at 100c while the cpu is only at 30c i don't understand why it does this calcul :)

thanks again

sebastian

Administrator

Wednesday, December 9th 2020, 1:34pm



1. you can use for pictures the upload funtion from this forum,


2. you have 2 filters, an average and a low pass, wenn both in series your filter is slower.


Your values (inputs and outputs) are valid, you have to play with the values/settings. Every system is different.

Asryan

Junior Member

Wednesday, December 9th 2020, 1:40pm

Aaah i thought i needed to put both, should i just use the average?

k2viper

Full Member

Wednesday, December 9th 2020, 2:02pm

Depends on what you are trying to get out of your virtual sensors.
Looks like you're going to control your cpu fan depending on reported cpu temp, but want to smooth the temp output to make fan speed changing more smoothly.
In that case, use Average(t) as second, not first filter in a chain. Low pass is better for smoothing small fast fluctuations. Leave lp(t) settings as it is, but experiment with timespan in Average(t) to make its output more reliable without short spikes in your real usage scenario.

Asryan

Junior Member

Wednesday, December 9th 2020, 2:04pm

I should put low pass then average is it what you are saying?

sebastian

Administrator

Wednesday, December 9th 2020, 2:08pm

Use only the low pass filter OR the avergae filter. Not both together in one signal path.

Asryan

Junior Member

Wednesday, December 9th 2020, 2:27pm

Oh ok i've put average then thanks :)


Also i've set up a custom one on which i do an average of CPU and GPu for intake and exhaust, do you think that's a good idea?




I've also a question about those fallback settings, it's not clear for me

Capture d’écran 2020-12-09 144012.jpg

thanks

This post has been edited 4 times, last edit by "Asryan" (Dec 9th 2020, 2:44pm)

k2viper

Full Member

Wednesday, December 9th 2020, 3:26pm

What is actually unclear with them?


Read on your screenshot: If data source is not available, a value set as "fallback value" is used. The problem is that you start a PC, windows boot up and fans start running at 100%, making noise.

To avoid this, you need to set both your CPU and GPU data sources fallback values to the typical startup values. E.g. you start up your PC and typical startup CPU temp is 35C. Then set CPU data source fallback value to 35.
On your screenshot, fallback value for GPU is set to 75. I doubt you have such high gpu temp at startup.

Fallback time is the time fallback value will be transmitted to data source at startup or after the data source become unavailable (e.g. you uninstall the GPU driver and its temp monitoring becomes unavailable).

Asryan

Junior Member

Wednesday, December 9th 2020, 3:31pm

Oh ok thanks,

For fallback time it correspond to the time of what exactly?


And if the sensors are not working, it will use the fallback power set up in fans right?


And what about test data output?

Will it be good like this? thanks again



Capture d’écran 2020-12-09 153052.jpg

Capture d’écran 2020-12-09 153110.jpg

k2viper

Full Member

Wednesday, December 9th 2020, 7:50pm

Fallback power under the Fan setup tab is used while data source (selected to drive current Fan's controller) is unavailable. E.g. you selected GPU temp or some virtual sensor created in Playground. But reading of GPU temp and Playground sensors are processed by Aquacomputer service, which is not running outside of Windows. So until Windows is start up or shutting down, this Fallback power will be used.

Test output value is for testing purposes when complex virtual sensors with many switches and dependencies are being created, outputting a set test value will help testing is output behave correctly with current scenario, or it needs adjustments.

Will it be good or not, you find for yourself.

This post has been edited 1 times, last edit by "k2viper" (Dec 9th 2020, 8:02pm)

Similar threads