Member
Joined 2018
Member
Joined 2018
Hi @CyberPit yes, it's better, but the potentiometer isn't as responsive.
Debounce 3 and potentiometer AUXADC0 in the same position, sometimes a different value appears there:
Param Value: 0.78515625
Param Value: 0.7861328125
And here's how AUXADC5 behaves with debounce 3:
Param Value: 0.1982421875
Param Value: 0.2001953125
Does it happen to you as well, or is it just an anomaly on my hardware?
Do you also use such debounce? It's only a 10-bit AUXADC, but I still feel like something is wrong.
Many Thanks, Tom
Debounce 3 and potentiometer AUXADC0 in the same position, sometimes a different value appears there:
Param Value: 0.78515625
Param Value: 0.7861328125
And here's how AUXADC5 behaves with debounce 3:
Param Value: 0.1982421875
Param Value: 0.2001953125
Does it happen to you as well, or is it just an anomaly on my hardware?
Do you also use such debounce? It's only a 10-bit AUXADC, but I still feel like something is wrong.
Many Thanks, Tom
In addition to this, all the noise that comes to the ADC penetrates into the useful signal, I got rid of this problem by simply installing a 10th order low-pass filter with a cutoff frequency of 3Hz after the ADC.
Many thanks @CyberPit @uriy-ch
debounce didn't quite suit me, or rather, I didn't find a value that solves my problem. Adding a low pass is better, it stabilizes after a while, just need to fix negative values. So far, it seems stable to me.
3 Hz doesn't work for me: there's simply always a 0 at the output. However, 4 Hz works fine.
debounce didn't quite suit me, or rather, I didn't find a value that solves my problem. Adding a low pass is better, it stabilizes after a while, just need to fix negative values. So far, it seems stable to me.
3 Hz doesn't work for me: there's simply always a 0 at the output. However, 4 Hz works fine.