TOP Contributors

  1. MIKROE (2659 codes)
  2. Alcides Ramos (356 codes)
  3. Shawon Shahryiar (307 codes)
  4. jm_palomino (112 codes)
  5. Chisanga Mumba (90 codes)
  6. S P (73 codes)
  7. dany (71 codes)
  8. MikroBUS.NET Team (35 codes)
  9. NART SCHINACKOW (34 codes)
  10. Armstrong Subero (27 codes)

Most Downloaded

  1. Timer Calculator (136951 times)
  2. FAT32 Library (70064 times)
  3. Network Ethernet Library (56015 times)
  4. USB Device Library (46333 times)
  5. Network WiFi Library (41956 times)
  6. FT800 Library (41265 times)
  7. GSM click (29050 times)
  8. mikroSDK (26479 times)
  9. PID Library (26446 times)
  10. microSD click (25411 times)
Libstock prefers package manager

Package Manager

We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]

< Back
mikroSDK Library

Touchpad 4 click

Rating:

0

Author: MIKROE

Last Updated: 2024-04-03

Package Version: 2.1.0.13

mikroSDK Library: 2.0.0.0

Category: Capacitive

Downloaded: 104 times

Not followed.

License: MIT license  

Touchpad 4 Click is a compact add-on board that easily integrates projected capacitive touch into user's applications. This board features the IQS7211A, a tiny capacitive touch controller from Azoteq.

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "Touchpad 4 click" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "Touchpad 4 click" changes.

Do you want to report abuse regarding "Touchpad 4 click".

  • Information
  • Comments (0)

mikroSDK Library Blog


Touchpad 4 click

Touchpad 4 Click is a compact add-on board that easily integrates projected capacitive touch into user's applications. This board features the IQS7211A, a tiny capacitive touch controller from Azoteq.

touchpad_4_click.png

click Product page


Click library

  • Author : Luka Filipovic
  • Date : Jun 2021.
  • Type : I2C type

Software Support

We provide a library for the Touchpad4 Click as well as a demo application (example), developed using MikroElektronika compilers. The demo can run on all the main MikroElektronika development boards.

Package can be downloaded/installed directly from NECTO Studio Package Manager(recommended way), downloaded from our LibStock™ or found on Mikroe github account.

Library Description

This library contains API for Touchpad4 Click driver.

Standard key functions :

  • touchpad4_cfg_setup Config Object Initialization function.

    void touchpad4_cfg_setup ( touchpad4_cfg_t *cfg );
  • touchpad4_init Initialization function.

    err_t touchpad4_init ( touchpad4_t *ctx, touchpad4_cfg_t *cfg );
  • touchpad4_default_cfg Click Default Configuration function.

    err_t touchpad4_default_cfg ( touchpad4_t *ctx );

Example key functions :

  • touchpad4_reset Reset function.

    void touchpad4_reset ( touchpad4_t *ctx );
  • touchpad4_get_touch Read touch informations.

    err_t touchpad4_get_touch ( touchpad4_t *ctx, touchpad4_info_t *touch_info );
  • touchpad_get_channels Read channel information.

    err_t touchpad_get_channels ( touchpad4_t *ctx, uint32_t *channels );

Example Description

This example showcases ability of the device to read touch coordinates, active/inactive channels, and gesture informations.

The demo application is composed of two sections :

Application Init

Initialize host communication modules(UART and I2C) and additional pins, for device control. Then resets device and set default configuration where Channels and pins are mapped and configured, and set communication with device only on touch/event. In the end one of 3 examples is set;


void application_init ( void ) 
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    touchpad4_cfg_t touchpad4_cfg;  /**< Click config object. */

    /** 
     * 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.
    touchpad4_cfg_setup( &touchpad4_cfg );
    TOUCHPAD4_MAP_MIKROBUS( touchpad4_cfg, MIKROBUS_1 );
    err_t init_flag = touchpad4_init( &touchpad4, &touchpad4_cfg );
    if ( I2C_MASTER_ERROR == init_flag ) 
    {
        log_error( &logger, " Application Init Error. " );
        log_info( &logger, " Please, run program again... " );

        for ( ; ; );
    }

    touchpad4_reset( &touchpad4 );

    init_flag = touchpad4_default_cfg ( &touchpad4 );
    if ( TOUCHPAD4_ERROR == init_flag ) 
    {
        log_error( &logger, " Configuration. " );
        log_info( &logger, " Please, run program again... " );

        for ( ; ; );
    }

    example_selector = TOUCHPAD4_EXAMPLE_TOUCH;

    log_info( &logger, " Application Task " );
}

Application Task

There are 3 examples that shocaes ability of the device:

  • Reading touch coorinates and addinal informations of touch strength, and touch area and logging them,
  • Reading channel statuses and show them by logging them,
  • Reading gesture events and logging them;

void application_task ( void ) 
{
    if ( !touchpad4_get_ready( &touchpad4 ) )
    {
        switch ( example_selector )
        {
            case TOUCHPAD4_EXAMPLE_TOUCH:
            {
                touchpad4_touch_reading( );
                break;
            }
            case TOUCHPAD4_EXAMPLE_CHANNEL:
            {
                touchpad4_channel_reading( );
                break;
            }
            case TOUCHPAD4_EXAMPLE_GESTURE:
            {
                touchpad4_gesture_reading( );
                break;
            }
            default:
            {
                log_error( &logger, " Select Example" );
                break;
            }
        } 
    }
}

The full application code, and ready to use projects can be installed directly from NECTO Studio Package Manager(recommended way), downloaded from our LibStock™ or found on Mikroe github account.

Other Mikroe Libraries used in the example:

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.Touchpad4

Additional notes and informations

Depending on the development board you are using, you may need USB UART click, USB UART 2 Click or RS232 Click to connect to your PC, for development systems with no UART to USB interface available on the board. UART terminal is available in all MikroElektronika compilers.


ALSO FROM THIS AUTHOR

I2C 1-Wire click

5

This example shows ID numbers from Unique ID Click and several Thermo Sensors (DS1820), connected on each channel. If there is no device detected on the channel, warning note is shown on TFT.

[Learn More]

Charger click

2

Charger click carries both a battery charger controller and a battery charge monitor. The smaller chip is MCP73831, a single-cell Li-Ion and Li-Polymer charge management controller. The larger IC is DS2438, a smart battery monitor. The monitor communicates with the MCU through a 1-Wire interface. The click is designed to use a 5V power supply.

[Learn More]

Inclinometer 2 click

0

Inclinometer 2 Click is a compact add-on board that measures the orientation angle of an object with respect to the force of gravity. This board features the IIS2ICLX, high accuracy, and resolution two-axis inclinometer from STMicroelectronics. It allows selectable full-scale measurements in ranges of ±0.5/±1/±2/±3g in two axes with a configurable host interface that supports both SPI and I2C serial communication. The sensing element is manufactured using a dedicated micromachining process developed by STMicroelectronics to produce inertial sensors and actuators on silicon wafers.

[Learn More]