Experience intuitive navigation with CY8CMBR3106S-LQXI and PIC18LF45K50
Quadruple touch, one slide
Published Aug 09, 2023
Click board™
Cap Touch 5 Click
Dev. board
EasyPIC v7a
Compiler
NECTO Studio
MCU
PIC18LF45K50
Discover a game-changing interface, seamlessly integrating four touch buttons and a slider. Explore its engineering marvel, transforming user interaction across diverse applications
A
A
Hardware Overview
How does it work?
Cap Touch 5 Click is based on the CY8CMBR3106S-LQXI, a CapSense® Express™ controller from Infineon, which has an advanced analog sensing channel and the Capacitive Sigma Delta PLUS (CSD PLUS) sensing algorithm, which delivers a signal-to-noise ratio (SNR) of greater than 100:1 to ensure touch accuracy even in extremely noisy environments. This controller is enabled with Infineon’s SmartSense™ Auto-tuning algorithm, which compensates for manufacturing variations and dynamically monitors and maintains optimal sensor performance in all environmental conditions. In addition, SmartSense Auto-tuning enables a faster time-to-market by eliminating the
time-consuming manual tuning efforts during development and production ramp-up. Advanced features like LED brightness control, proximity sensing, and system diagnostics save development time. These controllers enable robust liquid-tolerant designs by eliminating false touches due to mist, water droplets, or streaming water. The CapSense controller locks up the user interface in firmware to prevent touch inputs in streaming water. Additionally, it implements the advanced noise immunity algorithm, EMC, for stable operation in extremely noisy conditions. Besides that, it is also perfectly suited for low-power applications, such as those operated by a
battery, when a capacitive sensing controller with ultra-low average power consumption must be selected. The CY8CMBR3106S-LQXI controller draws an average current of 22µA per sensor. The Cap Touch 5 Click supports four CapSense buttons. Its sensitivity can be specified individually for each CapSense button and slider. Higher sensitivity values can be used for thick overlays or small button diameters, while lower sensitivity values should be used for large buttons or thin overlays to minimize power consumption. Therefore, this Click board™ comes without the overlay, so it is up to the user to choose the desired application and implementation.
Features overview
Development board
EasyPIC v7a is the seventh generation of PIC development boards specially designed for the needs of rapid development of embedded applications. It supports a wide range of 8-bit PIC microcontrollers from Microchip and has a broad set of unique functions, such as the first-ever embedded debugger/programmer over USB-C. The development board is well organized and designed so that the end-user has all the necessary elements in one place, such as switches, buttons, indicators, connectors, and others. With four different connectors for each port, EasyPIC v7a allows you to connect accessory boards, sensors, and custom electronics more efficiently than ever. Each part of the EasyPIC v7a development board
contains the components necessary for the most efficient operation of the same board. In addition to the advanced integrated CODEGRIP programmer/debugger module, which offers many valuable programming/debugging options and seamless integration with the Mikroe software environment, the board also includes a clean and regulated power supply module for the development board. It can use various external power sources, including an external 12V power supply, 7-23V AC or 9-32V DC via DC connector/screw terminals, and a power source via the USB Type-C (USB-C) connector. Communication options such as USB-UART and RS-232 are also included, alongside the well-
established mikroBUS™ standard, three display options (7-segment, graphical, and character-based LCD), and several different DIP sockets. These sockets cover a wide range of 8-bit PIC MCUs, from PIC10F, PIC12F, PIC16F, PIC16Enh, PIC18F, PIC18FJ, and PIC18FK families. EasyPIC v7a is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.
Microcontroller Overview
MCU Card / MCU
Architecture
PIC
MCU Memory (KB)
32
Silicon Vendor
Microchip
Pin count
40
RAM (Bytes)
2048
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the EasyPIC v7a as your development board.
Track your results in real time
Application Output
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.
2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.
3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.
Software Support
Library Description
This library contains API for Cap Touch 5 Click driver.
Key functions:
captouch5_read_button_status- This function reads button statuscaptouch5_read_slider_position- This function reads slider position
Open Source
Code example
The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.
/*!
* \file
* \brief CapTouch5 Click example
*
* # Description
* This demo app demonstrates basic functionality of CapTouch 5 Click
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes I2C module and driver, tests communication and configures device
*
* ## Application Task
* Waiting for touch sensor to detect something and then logs what is touched
*
* *note:*
* Click will go to sleep if doesn't get any command in 340ms
* When you start device try restarting your board few times to start device
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "captouch5.h"
// ------------------------------------------------------------------ VARIABLES
static captouch5_t captouch5;
static log_t logger;
static T_CAPTOUCH5_BUTTONS buttons;
static T_CAPTOUCH5_DEVICE_CONFIG device_cfg;
static uint8_t state_check;
// ------------------------------------------------------- ADDITIONAL FUNCTIONS
void captouch5_read_buttons( )
{
uint8_t press = 0;
if ( buttons.button1 == CAPTOUCH5_BUTTON_PRESSED )
{
log_info( &logger, "Button 1 : pressed" );
press = 1;
}
if ( buttons.button2 == CAPTOUCH5_BUTTON_PRESSED )
{
log_info( &logger, "Button 2 : pressed" );
press = 1;
}
if ( buttons.button3 == CAPTOUCH5_BUTTON_PRESSED )
{
log_info( &logger, "Button 3 : pressed" );
press = 1;
}
if (buttons.button4 == CAPTOUCH5_BUTTON_PRESSED)
{
log_info( &logger, "Button 4 : pressed" );
press = 1;
}
if (press)
{
log_printf( &logger, "\r\n" );
state_check = 1;
press = 0;
}
}
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
captouch5_cfg_t cfg;
/**
* Logger initialization.
* Default baud rate: 115200
* Default log level: LOG_LEVEL_DEBUG
* @note If USB_UART_RX and USB_UART_TX
* are defined as HAL_PIN_NC, you will
* need to define them manually for log to work.
* See @b LOG_MAP_USB_UART macro definition for detailed explanation.
*/
LOG_MAP_USB_UART( log_cfg );
log_init( &logger, &log_cfg );
log_info( &logger, "---- Application Init ----" );
// Click initialization.
captouch5_cfg_setup( &cfg );
CAPTOUCH5_MAP_MIKROBUS( cfg, MIKROBUS_1 );
captouch5_init( &captouch5, &cfg );
captouch5_default_cfg ( &captouch5, &device_cfg );
// uint8_t fam_id = captouch5_get_family_id( &captouch5 );
// if ( CAPTOUCH5_FAMILY_ID != fam_id )
// {
// log_info( &logger, "---- ID ERROR ----" );
// for ( ; ; );
// }
}
void application_task ( void )
{
uint16_t temp_byte;
uint16_t last_temp;
uint8_t error_data;
uint8_t temp_slider;
state_check = 0;
error_data = captouch5_process( &captouch5 );
if ( error_data == CAPTOUCH5_ERROR )
{
log_printf( &logger, "***** ERROR *****" );
state_check = 1;
return;
}
temp_byte = captouch5_read_slider_position( &captouch5 );
captouch5_read_button_status( &captouch5, &buttons );
if ( temp_byte != last_temp )
{
log_printf( &logger, "Slider position value: %u \r\n", temp_byte );
last_temp = temp_byte;
state_check = 1;
}
captouch5_read_buttons( );
Delay_ms ( 100 );
if ( state_check == 1 )
{
log_info( &logger, "--- Waiting for command ---\r\n" );
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
