What is the best configuration for cap sense ?
We are using manual tuner, is it best ?
or do we need to use smart sense ?
When using cap sense v7.
You can use either SmartSense or manual tuning, both tuning methods work. In SmartSense, the component takes care of tuning the sensors and setting the parameters. The limitation is that this works only in ideal conditions such as Cp < 65pF. In other challenging designs, we need to set manual tuning and tune the sensors as per requirement. You can take a look at our AN CapSense design guide for more details on SmartSense and Manual tuning.
Please let us know the issue that you are facing. Is CapSense getting stuck, indicating that the button is active always? How did you determine the CapSense ISR is not working?
Have you tried using CapSense Tuner to check how the sensors are responding? It could be as simple as a wrong threshold value that is set.
If the issue is with the incorrect value of thresholds, then you can switch to manual tuning and set the right parameters and get it to work. We generally recommend using SmartSense to obtain the parameters and set them in manual tuning so that you can overtune the sensors if required.
With 15pF capacitance, the sensors should work reliably even in smartsense, but we need to tuner waveforms to figure out what is happening.
When we were using CapSense CSD P4, there was no issue in the field.
When we moved from CSD P4 to CapSense V7.
We are receiving a malfunction of PSoC4 on the same PCB . e.g: hang in capsense but still operatable with IR remote through IR sensor. we are facing this issue since we have moved to new library.
Help us out to find out the issue. i think there should be something wrong in your new library files like in changing of status of switch or something else. because we were using same hardware earlier with old library, at that time , no issues were there.
Also we have shared RAW count & Threshold is fine.
Yes, from the video shared, the raw count and baseline seem to be fine indicating CapSense is operating correctly. Was this graph obtained while the sensors were not functioning? If so, there is some error in the firmware logic.
If not, we need the graph while the sensors were not working for further debug.