Advanced tab [all gen]
The Advanced tab provides advanced configuration parameters. In SMARTSENSE mode, most of the advanced parameters are tuned automatically. Select Manual tuning to control and configure the CAPSENSE™ middleware parameters.
The parameters in the Advanced tab are systematically arranged in the following subtabs:
-
General subtab [various gen] 1 – Contains the parameters common for all widgets irrespective of the sensing method used for the widgets.
-
CSD Settings subtab [various gen] – Contains the parameters common for widgets that use the CSD sensing method. Relevant if at least one widget uses the CSD sensing method.
-
CSX Settings subtab [various gen] – Contains the parameters common for widgets that use the CSX sensing method. Relevant if at least one widget uses the CSX sensing method.
-
ISX Settings subtab [5th gen LP] – Contains the parameters common for widgets that use the ISX sensing method. Relevant if at least one widget uses the ISX sensing method.
-
Widget Details subtab [various gen] – Contains the parameters specific to a widget and/or sensor.
Also, see the Widget Sensing Method [all gen] section.
Hover over the parameter value to display its description.
General subtab [various gen]
The General subtab contains the parameters common for all widgets irrespective of Widget Sensing Method [all gen] used for a widget.
5th generation LP CAPSENSE

5th generation CAPSENSE

4th generation CAPSENSE

The General subtab description contains the following sections:
- Scan settings [5th gen LP], [5th gen]
- Wake-on-Touch settings [5th gen LP]
- Miscellaneous [various gen]
- Regular (non-proximity) widget – raw count filter parameters [various gen]
- Proximity widget – raw count filter parameters [various gen]
- Low Power widget – raw count filter parameters [5th gen LP]
- Baseline filter settings / Active widget baseline filter settings [various gen]
Scan settings [5th gen LP], [5th gen]
| Parameter/Group name | Description | CAPSENSE™ generation | |
|---|---|---|---|
| 5th LP | 5th | ||
| Scan mode | Selects a sensor sequencing method. INT driven (default) – In Interrupt driven mode, the CPU extracts the results and programs the MSC HW for the next scan in the scope of the End of Scan interrupt servicing routine. CS-DMA – In Chained Scan DMA mode, the DMA functionality extracts the results and programs the MSC HW for the next scan. The CPU does not need to intervene between scans | √ | |
| Sensor connection method | Selects the method how to connect a sensor to the CAPSENSE™ HW block. AMUXBUS – In this mode, the CSD sensors, shield electrodes, and Rx electrodes are connected to the MSC HW using the analog bus and can be assigned to any GPIO which supports a connection with the analog bus for the particular device. **CTRLMUX **(default)– In this mode, the CSD sensors, shield electrodes, and Rx electrodes are connected to the MSC HW using the direct connection and can be assigned to the dedicated pads only. | √ | |
| CAPSENSE™ IMO clock frequency (MHz) | The frequency of the CAPSENSE™ IMO clock. | √ | |
| Modulator clock divider | Selects the Modulator clock divider used for the CSD, CSX, and ISX sensing methods (Widget Sensing Method [all gen]). This divider defines the operating frequency of the MSC block. | √ | √ |
| Actual modulator clock frequency (kHz) | This field shows the real ModClk, which depends on the PeriClk and selected Modulator clock divider. | √ | √ |
| Number of init sub-conversions | Selects the number of initialization sub-conversions at the start of the scan. This part of scan is intended to ensure proper initialization of CAPSENSE™ hardware and does not perform the raw count measurement. | √ | √ |
| Enable CIC2 hardware filter | The cascaded integrator-comb 2 (CIC2) filter is a second-order digital low-pass (decimation) filter for delta-sigma converters. It provides a higher resolution result for the equivalent scan time. MSCLP has a built-in CIC2, which improves the effective resolution and thereby the SNR for a given scan period. | √ | √ |
Wake-on-Touch settings [5th gen LP]
| Parameter/Group name | Description |
|---|---|
| Wake-on-Touch scan interval (us) | The desired scan interval in Wake-on-Touch mode. The real interval depends on ILO frequency which have a big tolerance (above +/- 50%), see device datasheets. |
| Number of frames in Wake-on-Touch | The maximum number of frames in Wake-on-Touch mode under no touch. The valid range is [1..65535]. |
Miscellaneous [various gen]
The miscellaneous settings are applicable to the whole CAPSENSE™ middleware behavior.
| Parameter/Group name | Description | CAPSENSE™ generation | ||
|---|---|---|---|---|
| 5th LP | 5th | 4th | ||
| Enable sensor auto-reset | When enabled, the baseline is always updated and when disabled, the baseline is updated only when the difference between the baseline and raw count is less than the noise threshold. When enabled, the feature prevents the sensors from permanently turning on when the raw count accidentally rises due to a large power supply voltage fluctuation or other spurious conditions. | √ | √ | √ |
| Enable self-test library | The CAPSENSE™ middleware provides the Built-In Self-Test (BIST) library to support the design compliant with the safety-integrity level of Class B (IEC-60730) white goods and automotive, and design for manufacturing testing. The library includes a set of tests for board validation, middleware configuration, and operation. The feature includes safety functions to reduce the risk, validate boards at manufacturing, and verify the middleware operation at run-time. The BIST tests are classified into two categories: Hardware tests – To confirm the CAPSENSE™ HW block and sensor hardware (external to chip) function correctly: - Chip analog-routing verification - Pin faults checking - PCB-trace opens/shorts checking - Integration capacitors and sensors capacitance measurement - VDDA measurement FW tests – To confirm the integrity of data used for decision-making on the sensor status: - Global and widget specific configuration verification - Sensor baseline duplication - Sensor raw count and baseline are in the specified range - The application layer is responsible for running BIST tests. | √ | √ | √ |
| Enable multi-frequency scan | The MFS provides superior immunity against external noises and is suitable for applications subjected to harsh environments. MFS implementation for the 4th generation CAPSENSE™ When the MFS is enabled, each sensor is scanned three times with three different sensor frequencies. The base frequency F0 (zero channel) is the nominal sensor frequency. The second F1 and the third F2 frequencies are obtained by increasing the sense clock-divider by 1 and by 2 correspondingly. SMARTSENSE and the multi-frequency features are mutually exclusive. If SMARTSENSE is enabled, MFS cannot be enabled. Note: Enabling the MFS increases RAM usage by three times approximately. Enabling the MFS increases the sensor scan duration by three times.MFS implementation for the 5th generation and 5th generation LP CAPSENSE™ When MFS is enabled for a particular widget, the Configurator creates two supplementary widgets with the same properties but different CSD Sense clock divider or CSX Tx clock divider. The supplementary widgets have “_F1” and “_F2” suffixes in their names. Their sensors are ganged with the main widget sensors. The slot assignment should be performed manually on the Scan Configuration tab[5th gen LP], [5th gen]. The Enable multi-frequency scan check box displays as checked when the MFS is enabled for all widgets, and partially checked when the MFS is enabled only for some widgets. You can enable or disable the MFS for a particular widget on the Widget Details subtab [various gen]. SMARTSENSE * and the multi-frequency features are mutually exclusive. If the SMARTSENSE is enabled, MFS cannot be enabled for CSD widgets. Note: * 5th generation LP allows you to combine MFS with SMARTSENSE – HW parameters mode. | √ | √ | √ |
| Enable external frame start | Enables the external frame scan only under the rising edge of the signal on the dedicated pin (see Scan Configuration tab[5th gen LP], [5th gen]). The constraints for the external frame signal are as follows: - A period between the two subsequent EFS pulses is larger than the full scan duration including processing. An EFS signal that arises during the scan will be stored and the next scan will start immediately even if the processing has not completed yet. - The minimal pulse width is longer than 2 ILO cycles. - The maximal pulse width is shorter than frame duration. | √ | ||
| Enable CDAC Scaling | Applicable only for the devices having factory programmed CDAC trim code in SFLASH (Example: PSOC™ 4100-TP). | √ | ||
Regular (non-proximity) widget – raw count filter parameters [various gen]
The regular widget raw count filter applies to raw counts of sensors belonging to non-proximity widgets. These parameters can be enabled only when one or more non-proximity widgets are added to the Basic tab [all gen]. The filter algorithm is executed when any processing function is called by the application layer. When enabled, each filter consumes RAM to store a previous raw count (filter history). If multiple filters are enabled, the total filter history correspondingly increases so that the size of the total filter history is equal to a sum of all enabled filter histories.
Software filter [all gen]
| Parameter/Group name | Description |
|---|---|
| Enable IIR filter (First order) | Enables the IIR filter (See equation below) with a step response similar to an RC low-pass filter, thereby passing the low-frequency signals (finger touch responses). Output = (N) / (K) × input + ((K-N)) / (K) × previousOutput where: K is always 256. N is the IIR filter raw count coefficient selectable from 1 to 128 in the Configurator. A lower N (set in the IIR filter raw count coefficient parameter) results in lower noise, but slows down the response. This filter eliminates high-frequency noise. Consumes 2 bytes of RAM per each sensor to store a previous raw count (filter history). |
| IIR filter raw count coefficient | The coefficient (N) of IIR filter for raw counts is explained in the Enable IIR filter (First order) parameter. The range of valid values: 1-128. |
| Enable median filter (3-sample) | Enables a non-linear filter that takes three of most recent samples and computes the median value. This filter eliminates spike noise typically caused by motors and switching power supplies. Consumes 4 bytes of RAM per each sensor to store a previous raw count (filter history). |
| Enable average filter (4-sample) | The finite-impulse response filter (no feedback) with equally weighted coefficients. It takes four of most recent samples and computes their average. Eliminates periodic noise (e.g. noise from AC mains). Consumes 6 bytes of RAM per each sensor to store a previous raw count (filter history). |
| Note: If multiple filters are enabled, the execution order is as follows: 1. Median filter 2. IIR filter 3. Average filter |
Hardware filter [5th gen LP]
| Parameter/Group name | Description |
|---|---|
| Enable IIR filter (First order) | Enables the hardware IIR filter for Low Power widgets. The design of these parameters is different from the regular widget raw count filter parameters. These dedicated parameters allow for setting Low Power filter configuration and behavior differently compared to the other widgets. RawCount = (1) / (2^iirRCcoef)RawCount_New + (1-(1) / (2^iirRCcoef))RawCount_Previous where, iirRCcoef – IIR filter raw count coefficient; valid range: 1 to 8. A low coefficient means lower filtering; a higher coefficient means a higher response time. Note: There is no filtering for coefficient value “0”. |
| IIR filter raw count coefficient |
Proximity widget – raw count filter parameters [various gen]
The Proximity widget raw count filter applies to raw counts of sensors belonging to the proximity widgets. These parameters can be enabled only when one or more proximity widgets are added on the Basic tab [all gen].
Software filter [all gen]
| Parameter/Group name | Description |
|---|---|
| Enable IIR filter (First order) | The design of these parameters is the same as the Regular (non-proximity) widget – raw count filter parameters [various gen]. The Proximity sensors require high-noise reduction. These dedicated parameters allow for setting the proximity filter configuration and behavior differently compared to other widgets. |
| IIR filter raw count coefficient | |
| Enable median filter (3-sample) | |
| Enable average filter (4-sample) |
Hardware filter [5th gen LP]
| Parameter/Group name | Description |
|---|---|
| Enable IIR filter (First order) | Enables the hardware IIR filter for Proximity widgets. The equation is the same as for hardware IIR filter for regular widgets. |
| IIR filter raw count coefficient |
Low Power widget – raw count filter parameters [5th gen LP]
The Low Power widget raw count filter applies to raw counts of sensors belonging to Low Power widgets, these parameters can be enabled only when one or more Low Power widgets are added on the Basic tab [all gen].
| Parameter/Group name | Description |
|---|---|
| Enable IIR filter (First order) | Enables the hardware IIR filter for Low Power widgets. The design of these parameters is different from theRegular (non-proximity) widget – raw count filter parameters [various gen]. These dedicated parameters allow for setting Low Power filter configuration and behavior differently compared to the other widgets. RawCount = (1) / (2^iirRCcoef)RawCount_New + (1-(1) / (2^iirRCcoef))RawCount_Previous where, *iirRCcoef – *IIR filter raw count coefficient; the valid range: 1 to 8. A low coefficient means lower filtering, a higher coefficient – a higher response time. |
| IIR filter raw count coefficient | |
| Baseline coefficient (fast) | Baseline IIR filter coefficient (fast) selection for sensors in Low Power widgets only. The range of valid values: 1-15. When the raw count starts increasing, the baseline value is updated quickly to attempt to track the raw count using iirBLcoeffast. |
| Baseline coefficient (slow) | Baseline IIR filter coefficient (slow) selection for sensors in Low Power widgets only. The range of valid values: 1-15. Once the noise threshold is exceeded, the baseline is updated slowly (using iirBLcoefslow) under raw count increase due to a touch or signal event. |
Baseline filter settings / Active widget baseline filter settings [various gen]
The baseline filter settings are applied to all sensor baselines. But, filter coefficients for the Proximity, regular, and Low Power widgets can be controlled independently from each other.
The design baseline IIR filter is the same as the Enable IIR filter (First order) parameter. But, filter coefficients can be separate for both baseline and raw count filters to produce a different roll-off. The baseline filter is applied to a filtered raw count (if the widget raw count filters are enabled).
| Parameter/Group name | Description | CAPSENSE™ generation | ||
|---|---|---|---|---|
| 5th LP | 5th | 4th | ||
| Regular widget baseline coefficient | Select the Baseline IIR filter coefficient for sensors in non-proximity widgets. The range of valid values: 1-255. | √ | √ | √ |
| Proximity widget baseline coefficient | The design of these parameters is the same as the Regular widget baseline coefficient, but with a dedicated parameter allows controlling the baseline update-rate of the proximity sensors differently compared to other widgets. | √ | √ | √ |
CSD Settings subtab [various gen]
Contains the parameters common for widgets that use the CSD sensing method (see Widget Sensing Method [all gen]). This subtab is relevant only if at least one widget uses the CSD sensing method.
5th generation LP CAPSENSE

5th generation CAPSENSE

4th generation CAPSENSE

CSD Settings subtab parameters [various gen]
The CSD Settings subtab contains the following parameters:
| Parameter name | Description | CAPSENSE™ generation | ||
|---|---|---|---|---|
| 5th LP | 5th | 4th | ||
| Modulator clock divider | Selects the modulator clock divider used for the CSD sensing method (see Widget Sensing Method [all gen]). Defines the operating frequency of the CSD block. | √ | ||
| Actual modulator clock frequency (kHz) | This field shows the real ModClk, which depends on the CSD peripheral clock and selected Modulator clock divider. | √ | ||
| Inactive sensor connection | Selects the state of the sensor when it is not scanned. Ground (default) – Inactive sensors are connected to the ground. High-Z – Inactive sensors are floating (not connected to GND or Shield). Shield – Inactive sensors are connected to Shield. Ground is the recommended selection for this parameter when water tolerance is not required for the design. Select Shield when the design needs water tolerance or to reduce the sensor parasitic capacitance in the design. | √ | √ | √ |
| IDAC sensing configuration | Selects the type of IDAC switching: IDAC Sourcing (default) – Sources current into the modulator capacitor (Cmod). The analog switches are configured to alternate between the Cmod and GND. IDAC Sourcing is recommended for most designs because of the better SNR. IDAC sinking – Sinks current from the modulator capacitor (Cmod). The analog switches are configured to alternate between VDD and Cmod. | √ | ||
| Enable IDAC auto-calibration | When enabled, values of the CSD widget IDACs are automatically set by the middleware. Select this parameter for robust operation and to enable SMARTSENSE. | √ | ||
| Enable compensation IDAC | Used to compensate for sensor parasitic capacitance to improve performance. Enable it unless one IDAC is required for general purpose (other than CAPSENSE™) in the application. | √ | ||
| Enable CDAC auto-calibration | When enabled, the values of the CSD widget CDACs are automatically set by the middleware. Select this parameter for robust operation. | √ | ||
| Enable compensation CDAC | Used to compensate for sensor parasitic capacitance to improve the system performance. | √ | ||
| Raw count calibration level | The raw count calibration level. | √ | √ | √ |
| Enable shield electrode | Used to reduce the sensor parasitic capacitance, enable water-tolerant CAPSENSE™ designs, and enhance the detection range for the Proximity. When the shield electrode is disabled, configurable parameters associated with the shield electrode are hidden. | √ | ||
| Enable shield tank (Csh) electrode | The shield tank capacitor is used to increase the drive capacity of the shield electrode driver. Enable it when the shield electrode capacitance is higher than 100 pF. The recommended value for a shield tank capacitor is 10nF/5V/X7R or an NP0 capacitor. The shield tank capacitor is not supported in configuration that includes both CSD and CSX sensing-based widgets. | √ | ||
| Shield SW resistance | Select the resistance of switches to drive the shield electrode. The four options: Low; Medium (default); High; Low EMI. | √ | ||
| Total shield count | Selects the number of shield electrodes required in the design. Most designs work with one dedicated shield electrode but, some designs require multiple dedicated shield electrodes to ease the PCB layout routing or to minimize the PCB area used for the shield layer.The minimum value is 0 (for example, shield signal could be routed to sensors using the Inactive sensor connection parameter) and the maximum value is equal to the total number of CAPSENSE™-enabled port pins available for the selected device. | √ | √ | |