Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
In Capsense_CSD, if the debounce is set to say 5 then it means the finger has to be present on the button for so many number of scans. In this case, for five scans the finger has to be on the button. The debounce feature removes the high amplitude high frequency noise.
But when the CapSense is used in the applications, where the main loop is long, the response time of Capsense button may be very poor if the debounce is set to high number. CapSense buttons will be scanned in continuous loop. If the loop is long and the debounce is high like 5, then this long loop should be executed 5 times for the button to be detected as ON. This gives very slow response.
Solutions to avoid this:
1) Debounce value: Do not set this as high number or dont leave it as default value which is 5. If the loop is long then already the interval between scan is long so high debounce number is not needed. Use the debounce value of 2.
2) Do multiple scans in the same loop: Inside the long loop, scan the CapSense buttons twice or more. Decide your debounce time that is how time you want your button to be active to be detected as ON. This depends on the noise freqency in the system. Then do the multiple scannings so that scannings are done to cover the required debounce time.