Infineon-ModusToolbox CAPSENSE Configurator 6.20 User Guide-UserManual-v01 00-EN
Infineon-ModusToolbox CAPSENSE Configurator 6.20 User Guide-UserManual-v01 00-EN
Intended audience
This document helps application developers understand how to use the CAPSENSE™ Tuner as part of creating a
ModusToolbox™ application.
Document conventions
Convention Explanation
Bold Emphasizes heading levels, column headings, menus and sub-menus
Italics Denotes file names and paths.
Denotes APIs, functions, interrupt handlers, events, data types, error handlers, file/folder names,
Courier New
directories, command line inputs, code snippets
File > New Indicates that a cascading sub-menu opens when you select a menu item
user guide Please read the Important Notice and Warnings at the end of this document 002-24353 Rev. *M
www.infineon.com 2024-02-13
ModusToolbox™ CAPSENSE™ Tuner user guide
• Widget – A CAPSENSE™ functional unit consisting of one sensor or a group of similar sensors, implementing
a specific higher-level functionality such as a Button, Proximity Sensor, Linear Slider, Radial Slider, Matrix
Buttons or Touchpad.
Reference documents
Refer to the following documents for more information as needed:
Table of contents
Table of contents
1 Overview ............................................................................................................................... 5
2 Launch the CAPSENSE™ Tuner ................................................................................................. 6
2.1 From the Device Configurator................................................................................................................. 6
2.2 make command ...................................................................................................................................... 7
2.3 VS Code and Eclipse ................................................................................................................................ 7
2.4 Executable (GUI) ...................................................................................................................................... 7
2.5 From the Command Line ........................................................................................................................ 8
3 Quick start............................................................................................................................. 9
4 GUI description .....................................................................................................................11
4.1 Menus..................................................................................................................................................... 11
4.2 Main toolbar .......................................................................................................................................... 12
4.3 Tabs toolbars ......................................................................................................................................... 13
4.4 Widget Explorer pane ............................................................................................................................ 15
4.5 Widget/Sensor parameters pane .......................................................................................................... 15
4.6 Notice List .............................................................................................................................................. 16
4.7 Tabs........................................................................................................................................................ 17
5 Tuner communication setup ...................................................................................................18
5.1 I2C .......................................................................................................................................................... 18
5.2 UART ...................................................................................................................................................... 18
5.3 RTT ......................................................................................................................................................... 19
5.4 Communication and Low power mode ................................................................................................ 22
5.5 Status bar .............................................................................................................................................. 22
6 Widget View tab ....................................................................................................................24
6.1 Touch Signal Graph ............................................................................................................................... 24
7 Graph View tab......................................................................................................................25
7.1 Graph View tab toolbar ......................................................................................................................... 25
7.2 Graph functionality ............................................................................................................................... 27
8 SNR Measurement tab ...........................................................................................................29
8.1 SNR Measurement procedure ............................................................................................................... 29
8.2 SNR measurement pane ....................................................................................................................... 30
8.3 Graph chart ............................................................................................................................................ 30
8.4 SNR options ........................................................................................................................................... 31
9 Touchpad View tab ................................................................................................................33
9.1 Widget selection .................................................................................................................................... 33
9.2 Display settings ..................................................................................................................................... 33
9.3 Show signal............................................................................................................................................ 34
9.4 Touch report .......................................................................................................................................... 34
9.5 Hot keys ................................................................................................................................................. 34
10 Gesture View tab ...................................................................................................................36
Table of contents
Overview
1 Overview
The CAPSENSE™ Tuner is a stand-alone tool included with the ModusToolbox™ software. The tool is used to
tune CAPSENSE™ applications.
Prior to using the CAPSENSE™ Tuner, create a CAPSENSE™ application and program it into the device. Refer to
the CAPSENSE ™ Configurator user guide and the CAPSENSE™ middleware documentation for help. Your
application must contain the CAPSENSE™ Middleware and a communication interface (I2C, UART or RTT). The
Tuner works with the KitProg3, MiniProg4, and UART devices.
2. (Skip this step for MSCLP.) On the Parameters pane, select an appropriate input Clock.
3. For the MSC and MSCLP HW blocks, select the CapSense resource category on the Peripherals tab.
This command opens the CAPSENSE™ Tuner GUI for the specific application in which you are working.
Quick start
3 Quick start
This section provides a simple workflow for how to use the CAPSENSE™ Tuner.
1. Create a CAPSENSE™ application with a tuner communication interface, and program the application
into the device. Refer to the Eclipse IDE for ModusToolbox™ user guide and the CAPSENSE™ Configurator
user guide for more details.
Note: The simplest way to start with CAPSENSE™ Tuner is to use the PSoC™ 6 CAPSENSE™ Buttons and
Slider code example configured to work on PSoC™ 6 MCU kits or PSoC™ 4 MSC CAPSENSE™ CSD
Button Tuning to work on PSoC™ 4 MCU kits.
Note: Refer to the KitProg user guide for the supported configurations and modes. For this example, I2C
address, sub-address, and speed must match the configuration.
Note: For the I2C communication, the Tuner only supports the 2-Bytes Sub-address.
6. Touch the sensors on the hardware and notice the change in the sensor/widget status on Widget View Tab.
7. Open the Graph View tab. Check the sensors in the Widget Explorer Pane to observe sensor signals in the
graph. Touch the sensors and notice the signal change on the Graph View Tab.
8. Change widget/sensor parameter values as needed. Then, apply the new settings to the device using the
Apply to Device command.
Quick start
You can do this when using Manual or SmartSense (hardware parameters only) modes for tuning:
• To edit the threshold parameters, use SmartSense (hardware parameters only) mode.
• To edit all the parameters, use Manual mode.
• When SmartSense (Full Auto-Tune) is selected for CSD tuning mode, parameters are read-only (except the
Finger Capacitance parameter).
9. Save the Tuner parameters. Click the Apply to Project command.
10. Exit the Tuner application.
GUI description
4 GUI description
The CAPSENSE™ Tuner application contains menus, a main toolbar, tabs toolbars, panes (sections 4.4, 4.5),
tabs, and a status bar, all used to tune a CAPSENSE™ application.
4.1 Menus
4.1.1 File
• Open… – Opens a <file_name>.cycapsense configuration file. This command is visible only when running
the Tuner independently from the Eclipse IDE.
• Apply to Device – Commits changed values of a widget/sensor parameter to the device. This command
becomes active if a value of any configuration parameter from the Tuner application changes (that is, if the
parameter values in the Tuner and the device are different). This is an indication to apply the changed
parameter values to the device. For Read Only mode of the communication interfaces, this command is
grayed out.
• Apply to Project – Commits changed values of a widget / sensor parameter to the CAPSENSE™ project.
• Open in System Explorer – This opens your computer’s file explorer tool to the folder that contains the
*.cycapsense file.
• Import… – Imports a specified configuration file.
• Export… – Exports the current configuration file into a specified file.
• Export Register Map to PDF… – Exports the current configuration register map in PDF format for the latest
version of the middleware available on the date of the CAPSENSE™ Tuner release.
• Recent files – Shows recent files that you can open directly.
• Exit – Asks to save changes if there are any and closes the Tuner. Changes are saved to the configuration
file.
4.1.2 Edit
• Undo – Undoes the last action or sequence of actions.
• Redo – Redoes the last undone action or sequence of undone actions.
4.1.3 View
• Widget Explorer – Hides or shows the Widget Explorer pane where widgets and sensors tree display.
• Notice List – Hides or shows the Notice List pane. The pane is shown by default.
• Widget/Sensor Parameters – Hides or shows the Widget/Sensor Parameters pane.
• Gesture Event History – Logs the detected gestures information. Displays in the View when any gesture is
available.
• Gesture Monitor – Provides visual indication for a detected gesture. Displays in the View when any gesture
is available
• OpenOCD Log – Hides or shows the OpenOCD Log pane.
• Toolbar – Hides or shows the Toolbar. Enabled by default.
• Reset View – Resets the view to the default.
GUI description
4.1.4 Communication
• Connect – Connects to the device via a communication channel selected in the Tuner Communication
Setup dialog. If the channel was not previously selected, the Tuner Communication dialog is shown.
• Disconnect – Closes the communication channel with the connected device.
• Start – Starts reading data from the device.
• Stop – Stops reading data from the device.
4.1.5 Tools
• Tuner Communication Setup… – Opens the configuration dialog to set up a communication channel with
the device.
• Options… – Opens the configuration dialog to set up Tuner preferences: Display, SNR, Logging,
Advanced.
• Logging – Starts or stops data logging into a specified file.
4.1.6 Help
• View Help – Opens the CAPSENSE™ Tuner guide (this document).
• About CAPSENSE™ Tuner – Opens the About box to display the version information, with links to open
https://www.infineon.com and the current session log file.
• Opens the configuration dialog to set up a communication channel with the device. The same
as the Tools > Tuner Communication Setup menu command.
• Connects to the device via a communication channel selected in the Tuner Communication
Setup dialog. The same as the Communication > Connect menu command.
• Closes the communication channel with the connected device. The same as the
Communication > Disconnect menu command
• Starts reading data from the device. The same as the Communication > Start menu command.
• Stops reading data from the device. The same as the Communication > Stop menu command.
• Opens a configuration file. The same as the File > Open menu command.
• Commits changed values of a widget/sensor parameter to the device. The same as the File >
Apply to Device menu command.
• Commits changed values of a widget / sensor parameter to the CAPSENSE™ project. The same
as the File > Apply to Project menu command.
• Imports a specified configuration file. The same as the File > Import menu command.
GUI description
• Exports the current configuration file into a specified file. The same as the File >Export menu
command.
• Starts or stops data logging into a specified file. The same as the Tools > Logging menu
command.
• Read mode – Selects the Tuner communication mode with a device (I2C and UART with LP).
• Synchronized –Application firmware periodically calls a corresponding Tuner function:
Cy_CapSense_RunTuner(). The Tuner synchronizes data reading and firmware execution to preserve
data coherency. CAPSENSE™ middleware waits for the Tuner read/write operation to be completed
prior to execution of sensor scan and processing tasks. The Tuner does not read/write data until
CAPSENSE™ middleware completes scanning and data processing tasks for all widgets in the
application. The SNR and noise measurements are most accurate, and most tuning parameters can be
edited in real time updating in this mode.
• Asynchronized – The Tuner reads data asynchronously with sensor scanning and data processing. Due
to this, data coherency may be corrupted. So, the Tuner may read only partially updated sensor data.
For example, the device completed scanning of only the first sensor in a row. At this moment, the Tuner
reads data of the latest scan from the first sensor and data of previous scans from the remaining sensor.
This can occur to all sensors, when the Tuner reads data prior to the completion of data processing
tasks, such as baseline update and filter execution. SNR and noise measurements are less accurate due
to non-coherent data reading and only a limited set of tuning parameters can be edited in real time in
this mode.
Asynchronized mode may work unreliably with low power widgets configurations when the application
is mostly in Deep Sleep. The Tuner may miss the time window when the device awakes and is able to
communicate with the Tuner.
• Undoes the last action or sequence of actions. The same as the Edit > Undo menu command.
• Redoes the undone action or sequence of undone actions. The same as the Edit > Redo menu
command.
GUI description
Graph SNR
Widget Touchpad Gesture
Option Description View Measurement
View tab View tab View tab
tab tab
Opens a custom
Open image √
image.
GUI description
Note: For CSX widgets, the sensor tree displays individual nodes (Rx0_Tx0, Rx0_Tx1 …) contrary to the
CAPSENSE™ Configurator where the CSX electrodes are displayed (Rx0, Rx1 … Tx0, Tx1 ...).
Note: For MSC HW configurations with enabled Multi-frequency mode, there is a Median checkbox in the
Widget Explorer for each sensor that shows a set of F0 values received from a kit in the Graph View
tab.
Widget parameters
• Widget general parameters – Cannot be modified from the CAPSENSE™ Tuner because corresponding
parameter values reside in the application flash widget structures that cannot be modified at runtime.
• Widget hardware parameters – Cannot be modified for the CSD widgets when CSD tuning mode is set to
SmartSense (Full Auto-Tune) or SmartSense (hardware parameters only) in the CAPSENSE™ Configurator.
• All Widget hardware parameters require hardware re-initialization. In Manual tuning mode, the
availability of changing the Widget hardware parameters and Apply to Device command depends on the
mode and communication protocol.
Protocol I2C UART RTT
Mode Read/Write
Apply to Device
√ √ √
Widget hardware
parameters √ √ √
GUI description
• Capacitive DAC parameters – Cannot be modified for the CSD widgets when CSD tuning mode is set to
SmartSense (Full Auto-Tune) , SmartSense (hardware parameters only) or appropriate CDAC mode is set to
AUTO in the CAPSENSE™ Configurator.
• Widget threshold parameters – Cannot be modified for the CSD widgets when CSD tuning mode is set to
SmartSense (Full Auto-Tune) in the CAPSENSE™ Configurator. In Manual tuning mode (for all widgets), the
availability of changing Widget threshold parameters and Apply to device command depends on the mode
and communication protocol.
Protocol I2C UART RTT
Mode Read/Write
Apply to Device
√ √ √
Widget threshold
parameters √ √ √
• Position filter parameters, Adaptive IIR filter parameters, Ballistic multiplier parameters and
Centroid parameters – Cannot be modified at runtime from the Tuner because, unlike the other
parameters, these parameter values reside in the application flash widget structures that cannot be
modified at runtime.
Sensor Parameters
• Sensing parameters
• When IDAC/CDAC is enabled, the parameter is read-only and displays values as calibrated by the
firmware.
• When the auto-calibration is disabled, the IDAC/CDAC value entered in the CAPSENSE™ Configurator
displays and the parameter becomes writable in Read/Write mode.
• Capacitance (fF) – When BIST is enabled in the CAPSENSE™ Configurator, the sensor/electrode
capacitances are read-only, and display values calculated by the firmware. In this case, the application
code must have BIST-related function calls. When BIST is disabled, the Capacitance (fF) group is hidden.
Note: The Position filter parameters, Adaptive IIR filter parameters, and Gesture parameters reflect data
stored in a loaded configuration file. Actual values may vary on a target device connected to the
CAPSENSE™ Tuner.
GUI description
4.7 Tabs
The CAPSENSE™ Tuner consists of the following tabs:
• Widget View – Displays the widgets, their touch status, and the touch signal bar graph.
• Graph View – Displays the sensor data charts.
• SNR Measurement – Provides the SNR measurement functionality.
• Touchpad View – Displays the touchpad heatmap.
• Gesture View – Displays the Gesture operation.
Note: The parameters in the Tuner Communication Setup dialog must be identical to the parameters of
the EZI2C or UART driver in the application.
5.1 I2C
To establish the I2C communication between the Tuner and target device, configure the Tuner communication
parameters to match the parameters of the device EzI2C settings.
The I2C communication can work in the two Read modes (see Main toolbar).
5.2 UART
To establish the UART communication between the Tuner and target device, configure the Tuner
communication parameters to match the parameters of the device UART settings.
Depending on the application capabilities, the UART communication may work in two modes: Read/Write and
Read Only (see Status bar).
Note: Recommended – enable the UART Flow control on the target device for bitrates equal or higher
than 1000000.
5.3 RTT
The Real Time Transfer (RTT) is an interface specified by SEGGER based on basic memory reads and writes to
transfer data bidirectionally between the target and host. Before configuring the RTT setup dialog, it is
recommended to familiarize yourself with the RTT protocol fundamentals at https://wiki.segger.com/RTT.
The data transfer between the host and target devices is organized through channels. The Tuner communicates
to the server (OpenOCD) via the TCP/IP protocol. The server in turn uses the SWD interface to communicate
with the device.
RTT communication advantages:
To start the RTT server in your local environment, select Start RTT server locally and modify the following
fields:
• Executable – The .elf file generated by the firmware build. In most cases, it will be prefilled automatically
based on the ModusToolbox™ project.
• TCP ports range – Used for the RTT communication. Each port is mapped to a channel. Set up at least two
channels because Channel 0 has limitations.
• Tuner TCP port – The TCP port used by the Tuner.
• OpenOCD .cfg file – Provides the .cfg file name for OpenOCD. In most cases, it will be detected
automatically based on the application target device and will not display on the GUI. If becomes visible
when the .cfg file name value cannot be detected by the Tuner automatically and must be selected
manually. The .cfg file name can be found in the .launch file of your project.
To manage the RTT server, the Tuner uses the rtt.tcl file, which can be found along with the Tuner executable
(or capsense-tuner.app/Contents/Resources/ on macOS). It starts an OpenOCD session, which lasts while the
Tuner is connected to the device.
Note: Only one instance of OpenOCD can run at a time. If you want to debug the application
simultaneously, refer to RTT communication with simultaneous debug.
To connect to an existing RTT server, unselect Start RTT server locally and modify the following fields.
• Include a header
#include "SEGGER_RTT/RTT/SEGGER_RTT.h"
• Initialize RTT
SEGGER_RTT_Init();
• Implement the send and receive functions. Assign them to the callbacks.
Static void rtt_tuner_send(void * context);
static void rtt_tuner_receive(uint8_t ** packet, uint8_t ** tunerPacket, void * context);
...
cy_capsense_context.ptrInternalContext->ptrTunerSendCallback = rtt_tuner_send;
cy_capsense_context.ptrInternalContext->ptrTunerReceiveCallback = rtt_tuner_receive;
...
/* Lock RTT */
SEGGER_RTT_LOCK();
SEGGER_RTT_BUFFER_UP *buffer = _SEGGER_RTT.aUp + RTT_TUNER_CHANNEL;
/* Unlock RTT */
SEGGER_RTT_UNLOCK();
}
...
• The PSoC™ side firmware ensures that after the device exits Deep Sleep mode, the device stays in the active
state with the working communication channel, which enables the Tuner to receive at least one packet
with valid data.
• The device sleeps less than the Tuner-defined timeout (see the LP command timeout in the Tuner
Configuration Options dialog, Advanced tab).
• Implement the Deep Sleep callback, which waits for the completion of an EzI2C/UART transaction before
the transition to Deep Sleep.
Also recommended:
• Add Cy_SysLib_Delay 100-500 ms after the CAPSENSE™ initialization completes before the transition to
Deep Sleep to give the Tuner time to exchange packets with the device.
The Tuner has the following timeouts by default:
UART interface
RTT interface
• Read/Write – Provides data transmission in two reverse directions: target device → Tuner→ target
device. You can change the parameters of the widgets/sensors at runtime. To upload the modified
configuration, click the Apply to Device button.
• Read only – Provides data transmission in one direction: target device → Tuner. You cannot upload the
parameters of the widgets/sensors to the device at runtime. But for the I2C protocol you can still
upload parameters that do not require re-initialization.
• Baud rate (UART) – The data rate, at which CAPSENSE™ operates with the current settings.
• Tuner TCP port (RTT) – Used by the Tuner to connect to the RTT server.
• RTT Server (RTT) – Indicates if the RTT server is started locally or on a specific host.
• Supply voltage – The supply voltage.
• Logging – Either ON (when the data logging to a file in progress) or OFF.
The Widget and/or sensors are highlighted when the device reports their touch status as active.
Some additional features are available depending on the widget type.
Note: For 5th generation CAPSENSETM configuration with enabled Multi-frequency mode, there is a
Median graph on the Sensor Signal graph for each sensor.
For Multi-frequency mode, three varieties are scanned for each sensor at three different
frequencies and three different raw-counts are obtained for the same sensor. The sensor state is
estimated by one median value calculated from the obtained three raw-counts.
A Median graph shows a set of F0 values received from a kit. The graph becomes visible if at least
one of the graphs F0, F1, F2 is visible. Then, the Tuner calculates the actual value of F0 from
received data.
• Chart settings – Opens the menu for editing the chart line series parameters.
• Crosshairs – Consists of two lines parallel to the coordinate axes. The vertical component always
shows the X coordinate of the mouse cursor and moves with the mouse pointer synchronously on all
four charts – Sensor Data, Sensor Signal, Status, and Position regardless of their scale and shift. The
horizontal component is visible only on the chart (active chart) over which the mouse cursor is
hovering. The Crosshairs context menu has many more options:
• Vertical marker lines – When you left-click, the Tuner adds a Vertical marker line with a value equal to
the X coordinate of the mouse cursor synchronously on all four charts – Sensor Data, Sensor Signal,
Status, and Position regardless of their scale and shift. Press the [Esc] key to erase all previously drawn
Vertical marker lines. You can change the characteristics of Vertical marker lines or disable them in the
submenu Chart settings > Vertical marker lines.
• Stopping bars – When performing Stop communication, the Tuner adds a rectangular mark after the
current endpoint synchronously on all four charts. After a new start of communication, new chart
points will be added after the last Stopping bar. You can change the Stopping bars characteristics or
disable them in the Chart settings > Stopping bars submenu.
• Color – To change a sensor series color on the Legend pane, either double-click or right-click the sensor
and select the Color option from the displayed menu. The “Please choose a color for …” dialog displays.
You can change the color for the graph lines of the same sensor(widget) on all the charts of the Graph View
and on the Touch Signal Graph of the Widget View simultaneously.
Select a color and click OK. To select a color for all the graphs at the same time, press and hold the [Ctrl] key
while clicking.
The progress bar provides graphical guidance to the user to complete the SNR measurement. The bar displays
the progress and user-addressed relevant messages.
The measured noise, signal, and SNR values are displayed below the progress bar. The SNR value is calculated
as Signal divided by Noise rounded up to 2 decimal points.
The result has the following meaning:
a. PASS – The SNR is above the required limit (green).
b. FAIL – The SNR is below the required limit (red).
c. N/A – The SNR cannot be calculated because noise/signal samples are not collected yet (grayed
out).
• Context menu – Provides the options to change the appearance of graphs. To display the context menu,
right-click any chart.
Line style (for Noise and Signal only) Scatter shape Color
For a description of Legend, Spike, Clear, and Save image, go to the Tabs toolbars table.
• Noise sample count – The count of samples to acquire during the noise measurement operation.
• Signal sample count – The count of samples to acquire during the signal measurement operation.
• SNR pass value – The minimal acceptable value of the SNR.
• Ignore spike limit – Ignores a specified number of the highest and the lowest spikes at noise / signal
calculation. That is, if you specify number 3, then three upper and three lower raw counts are ignored
separately for the noise calculation and for the signal calculation.
• Noise calculation method – Allows selecting the method to calculate the noise average. The following
methods are available for selection:
• Peak-to-peak (by default) – Calculates noise as a difference between the maximum and minimum value
collected during the noise measurement.
• RMS – Calculates noise as a root mean-square of all samples collected during the noise measurement.
• Progress bar text mode – This label is shown with the progress bar:
• Hide (by default) – No label.
• Percent – The number of samples in percent acquired during the signal measurement operation.
• Value – The number of samples acquired during the signal measurement operation.
• Signal graph below noise – Displays the signal series below the noise threshold on the graph.
• Show spike points – Highlights the spike points on the graph.
• Show legend – Shows the graph legend. The Legend has the context menu to change its position. Right-
click the Legend to see the menu.
Note: The Touchpad View tab is disabled when there are no touchpad widgets in the configuration.
• CSD combo box – Selects any CSD touchpad to display in the heatmap.
• CSX combo box – Selects any CSX touchpad to display in the heatmap.
• Flip X-axis – Flips the displayed X-axis to match the orientation of a physical touchpad.
• Flip Y-axis – Flips the displayed Y-axis to match the orientation of a physical touchpad.
• Swap XY-axes – Swaps the X- and Y-axes for the touchpad.
• Display mode – The drop-down menu with 3 options for the display format:
• Touch reporting – Shows current detected touches only.
• Line drawing – Joins the previous and current touches in a continuous line.
• Touch Traces – Plots all the reported touches as dots.
• Data type – The drop-down menu to select the signal type to display: Diff count, RawCount, and Baseline.
Under Multi-frequency mode, RawCount and Baseline are available for three channels: 0, 1, 2.
• Value type – The drop-down menu to select the type of a value to display:
• Current – The last received value.
• Max hold – The maximum value out of latest “Number of samples” received.
• Min hold – The minimum value out of latest “Number of samples” received.
• Max-Min – The difference between maximum and minimum values.
• Average – The average value of latest “Number of samples” received.
• Number of samples – Defines a length of history of data for the Line Drawing, Touch Traces, Max hold, Min
hold, Max-Min, and Average options.
• Display touch position – Selects the touchpad from which data displays in the heatmap. The options:
• Display only CSX
• Display only CSD
• Display both.
• Color range – Defines a range of sensor signals within which the color gradient is applied. If a sensor signal
is outside the range, a sensor color is either minimum or maximum out of the available color palette.
Note: The Gesture View tab is disabled when there are no gesture widgets in the configuration.
• Combo box – Selects the widget with Gesture enabled to display the Gesture from it on this pane.
• Flip X-axis – Flips the direction of the X-axis to match the orientation of a physical widget.
• Flip Y-axis – Flips the direction of the Y-axis to match orientation of a physical widget.
• Swap XY-axes – Swaps the X- and Y-axes to match orientation of a physical widget.
If the Delay checkbox is enabled, a Gesture picture is displayed only for the specified time-interval. If disabled,
the last reported gesture picture is displayed until a new Gesture is reported.
11.1.1 Theme
Defines the visual style of widgets.
• Log directory – Browse for the application directory the CAPSENSE™ Tuner log files are located in.
• Log file prefix – The prefix name is the user's input for the log file name. For example, <prefix_name>-
<time_stamp>.csv.
• Number of samples – Defines a log session duration in samples. The header is repeated after a number of
samples.
• Data configuration check box table – Selects data to collect into a log file.
• Device reset on connection – If this option is enabled, the target reset is performed on Connect and
Disconnect for 5th generation LP CAPSENSE™ devices, which helps to establish connection even if the device
was in Deep Sleep mode.
• LP command timeout (ms) – Defines the timeout for Read and Write commands for 5th generation LP
CAPSENSE™ devices. During this time, the Tuner will repeatedly try to read/write data until the device
wakes up from Deep Sleep and the operation succeeds. Default: 250000 ms.
• I2C response delay (ms) – Configures a delay after the ONE_SCAN command is sent and before the device
response is read via the I2C communication protocol in Synchronous mode. The value indicates that the
host will not make read requests until the specified time has elapsed. Recommended for long scans to
prevent possible noise.
Troubleshooting
12 Troubleshooting
Problem Workaround
An easy way to allow the current user access to the Linux machine's serial
On common Linux distributions, the serial ports is by adding the user to the dialout group. This can be done using the
UART ports (usually /dev/ttySx or following command:
/dev/ttyUSBx devices) belongs to the root $sudo usermod -a -G dialout $USER
user and to the dialout group. Standard
users are not allowed to access these Note: For this command to take effect, you must log out and then
devices. log back in.
On macOS, the CAPSENSE™ Tuner can't be Launch the Tuner from within the Device Configurator or use the
launched from the Launchpad. command line option.
On common Linux distributions, the Tuner
forbids communication interface selection Refer to the “Installation Procedure on Ubuntu Linux (x64)” section in the
after re-plugging KitProg during Cypress Programmer 2.1 CLI User Guide.
communication.
KitProg3 UART is accessible but not able to
Use third-party UART to USB bridge.
read data on Linux kernel 4.15 and above
Update the KitProg3 firmware to version 1.11.243 or above.
or Mac OS X 10.13 and above.
Cannot establish communication with a
Refer to the Communication and Low power mode section.
device that operates in Low power mode.
Unable to connect to the device via the
RTT communication protocol. The
RTT support is not enabled in the application. Refer to the Setting up RTT
OpenOCD log displays an error “Could not
communication in the application section.
find symbol '_SEGGER_RTT' in
executable”.
Note: The Tuner provides information about the root cause of connection to KitProg issue in an
operation log. The operation log location can be found in the About CAPSENSE™ Tuner box.
Version changes
13 Version changes
This section lists and describes the changes for each version of this tool.
Version changes
Revision history
Revision history
Revision Date Description
** 2018-11-26 New doc.
*A 2018-12-05 Documents were updated with changes requested in BVI-353.
*B 2019-02-26 Updated tо version 1.1.
*C 2019-10-16 Updated to version 2.0.
*D 2019-11-01 Added section for launching from Device Configurator.
*E 2020-03-27 Updated to version 3.0.
*F 2020-09-01 Updated to version 3.10.
*G 2020-12-14 Updated to version 3.11.
*H 2021-03-11 Updated to version 3.15.
*I 2021-09-29 Updated to version 4.0.
*J 2022-09-29 Updated to version 5.0
*K 2023-02-07 Updated to version 6.0
*L 2023-06-01 Updated to version 6.10.
Updated to version 6.20.
*M 2024-02-13
Added the Hot keys section.