Intermediate
30 min

Experience intuitive navigation with CY8CMBR3106S-LQXI and PIC18F57Q43

Quadruple touch, one slide

Cap Touch 5 Click with Curiosity Nano with PIC18F57Q43

Published Feb 13, 2024

Click board™

Cap Touch 5 Click

Dev. board

Curiosity Nano with PIC18F57Q43

Compiler

NECTO Studio

MCU

PIC18F57Q43

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.

Cap Touch 5 Click top side image
Cap Touch 5 Click bottom side image

Features overview

Development board

PIC18F57Q43 Curiosity Nano evaluation kit is a cutting-edge hardware platform designed to evaluate microcontrollers within the PIC18-Q43 family. Central to its design is the inclusion of the powerful PIC18F57Q43 microcontroller (MCU), offering advanced functionalities and robust performance. Key features of this evaluation kit include a yellow user LED and a responsive

mechanical user switch, providing seamless interaction and testing. The provision for a 32.768kHz crystal footprint ensures precision timing capabilities. With an onboard debugger boasting a green power and status LED, programming and debugging become intuitive and efficient. Further enhancing its utility is the Virtual serial port (CDC) and a debug GPIO channel (DGI

GPIO), offering extensive connectivity options. Powered via USB, this kit boasts an adjustable target voltage feature facilitated by the MIC5353 LDO regulator, ensuring stable operation with an output voltage ranging from 1.8V to 5.1V, with a maximum output current of 500mA, subject to ambient temperature and voltage constraints.

PIC18F57Q43 Curiosity Nano double side image

Microcontroller Overview

MCU Card / MCU

default

Architecture

PIC

MCU Memory (KB)

128

Silicon Vendor

Microchip

Pin count

48

RAM (Bytes)

8196

You complete me!

Accessories

Curiosity Nano Base for Click boards is a versatile hardware extension platform created to streamline the integration between Curiosity Nano kits and extension boards, tailored explicitly for the mikroBUS™-standardized Click boards and Xplained Pro extension boards. This innovative base board (shield) offers seamless connectivity and expansion possibilities, simplifying experimentation and development. Key features include USB power compatibility from the Curiosity Nano kit, alongside an alternative external power input option for enhanced flexibility. The onboard Li-Ion/LiPo charger and management circuit ensure smooth operation for battery-powered applications, simplifying usage and management. Moreover, the base incorporates a fixed 3.3V PSU dedicated to target and mikroBUS™ power rails, alongside a fixed 5.0V boost converter catering to 5V power rails of mikroBUS™ sockets, providing stable power delivery for various connected devices.

Curiosity Nano Base for Click boards accessories 1 image

Used MCU Pins

mikroBUS™ mapper

NC
NC
AN
NC
NC
RST
NC
NC
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
NC
NC
PWM
NC
NC
INT
NC
NC
TX
NC
NC
RX
I2C Clock
PB2
SCL
I2C Data
PB1
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Click board™ Schematic

Cap Touch 5 Click Schematic schematic

Step by step

Project assembly

Curiosity Nano Base for Click boards front image hardware assembly

Start by selecting your development board and Click board™. Begin with the Curiosity Nano with PIC18F57Q43 as your development board.

Curiosity Nano Base for Click boards front image hardware assembly
Charger 27 Click front image hardware assembly
PIC18F47Q10 Curiosity Nano front image hardware assembly
Prog-cut hardware assembly
Curiosity Nano with PICXXX Access MB 1 - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
Necto image step 5 hardware assembly
Necto image step 6 hardware assembly
PIC18F57Q43 Curiosity MCU Step hardware assembly
Necto No Display image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Debug Image Necto Step hardware assembly

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 status

  • captouch5_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

Additional Support

Resources

Love this project?

'Buy This Kit' button takes you directly to the shopping cart where you can easily add or remove products.