Create innovative solutions with advanced control features using IQS266 and STM32G071RB
The art of intuitive control
Published Oct 08, 2024
Click board™
SwipeSwitch Click
Dev Board
Nucleo 64 with STM32G071RB MCU
Compiler
NECTO Studio
MCU
STM32G071RB
To simplify interactions and improve accessibility, our solution leverages the power of capacitive touch, gesture recognition, and proximity sensing, providing users with a natural and responsive way to engage with their devices
A
A
Hardware Overview
How does it work?
SwipeSwitch Click is based on the IQS266, an integrated trackpad controller circuit featuring ProxSense® and IQ Switch® technologies from Azoteq. This integrated touch controller features two receivers and three transmitters, allowing a 2x3 capacitive touch trackpad to be formed. Using a specific trace pattern on the PCB, the Click board™ can sense several swipe gestures, offering several different configuration parameters. By employing well-proven ProxSense® and IQ Switch® technologies, the IQS266 device can provide reliable touch detection in various environmental conditions. It uses the industry-standard I2C communication interface, with the additional RDY pin for the event signaling and communication protocol handshaking routines. Besides five capacitive touch-sensing electrodes, the IQS266 integrates a single proximity channel. This channel can wake the device from standby mode when the user approaches the touch panel, ensuring a low overall power consumption that way. CH0 is a dedicated proximity/touch channel, and it is treated as a separate channel group in the IQS266 settings. Both proximity and touch thresholds can be defined for this channel.
Automatic Tuning Implementation (ATI) ensures the optimal sensitivity of the sensing channels by monitoring the sampling values. The developer can set up the ATI targets for two groups of channels (channel 0 and channels 1-6). Once these targets are set, the ATI algorithm will try to match them, ensuring consistent behavior when used in various operating conditions. The ATI functionality can also be turned off/forced by the user to retune the sensor electrodes on demand. Otherwise, the IQS266 will automatically retune the electrodes whenever the counts drift outside a predefined ATI band to ensure optimal sensitivity. The RDY pin has two functions. It can be used as an interrupt event pin, signaling an event occurrence (when operated in the Event mode) or a "Data Ready" event. In this case, the RDY pin will be driven to a LOW logic level to signal an event, allowing it to generate an interrupt on the host MCU. However, the host MCU can pull the RDY pin down to initiate a communication window (communication protocol handshaking), requesting data from the device. The RDY pin is routed to the mikroBUS™ INT pin. The IQS266 can be set to operate in the Streaming or Event
modes. When operated in the Event mode, the RDY pin will indicate a communication window only after the selected event. There are several events: low power, swipe, tap, ATI, trackpad, touch, and proximity event. Each event is signalized by the RDY pin driven to a LOW logic level. More details about each event's RDY pin driving pattern can be found in the IQS266 datasheet. The IQS266 is very flexible, allowing many parameters to be tuned according to needs. These parameters include timeout periods for various modes (Zoom mode timeout, Low Power mode timeout, RDY timeout, and more), thresholds for various events and channels, some special sensing parameters, and such. The developer can set up these parameters by writing appropriate values to the registers of the IQS266 IC over the I2C interface. Please refer to the datasheet for a more detailed description of each register. However, the Click board™ is supported by a library of mikroSDK-compatible functions that simplify and speed up the development. It also comes with an example application that demonstrates their use.
Features overview
Development board
Nucleo-64 with STM32G071RB MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M0
MCU Memory (KB)
128
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
36864
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Nucleo 64 with STM32G071RB MCU as your development board.
Track your results in real time
Application Output via Debug Mode
1. Once the code example is loaded, pressing the "DEBUG" button initiates the build process, programs it on the created setup, and enters Debug mode.
2. After the programming is completed, a header with buttons for various actions within the IDE becomes visible. Clicking the green "PLAY" button starts reading the results achieved with the Click board™. The achieved results are displayed in the Application Output tab.
Software Support
Library Description
This library contains API for SliderSwitch Click driver.
Key functions:
swipeswitch_read_gestures- This function reads gesturesswipeswitch_read_x_coordinate- This function reads X coordinateswipeswitch_read_y_coordinate- This function reads Y coordinate
Open Source
Code example
This example can be found in NECTO Studio. Feel free to download the code, or you can copy the code below.
/*!
* \file
* \brief SwipeSwitch Click example
*
* # Description
* This Click is based on integrated touch controller featuring 2 receivers and 3 transmitters,
* allowing a 2x3 capacitive touch trackpad to be formed. By using a specific trace pattern on the PCB,
* the Click board is able to sense several different swipe gestures, offering several different configuration parameters.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization and configuration of the chip for measurement
*
* ## Application Task
* In the first test mode, it checks whether or not a new event ocurred (TAP or SWIPE).
* If it did, it writes out data regarding that event via UART.
* In the second test mode, X and Y coordinates are being read and logged via UART.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "swipeswitch.h"
#define SWIPESWITCH_GESTURE_MODE 0
#define SWIPESWITCH_POSITION_MODE 1
// ------------------------------------------------------------------ VARIABLES
static swipeswitch_t swipeswitch;
static log_t logger;
static uint8_t x_coordinate = 0;
static uint8_t y_coordinate = 0;
static uint8_t old_x_coordinate = 0;
static uint8_t old_y_coordinate = 0;
static uint8_t events = 0;
static uint8_t gestures = 0;
static uint8_t display_mode;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
swipeswitch_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.
swipeswitch_cfg_setup( &cfg );
SWIPESWITCH_MAP_MIKROBUS( cfg, MIKROBUS_1 );
swipeswitch_init( &swipeswitch, &cfg );
Delay_ms( 300 );
display_mode = SWIPESWITCH_GESTURE_MODE;
if ( display_mode == SWIPESWITCH_GESTURE_MODE)
{
log_printf( &logger, "<<< GESTURE MODE >>> \r\n" );
}
else if ( display_mode == SWIPESWITCH_POSITION_MODE)
{
log_printf( &logger, "<<< POSITION MODE >>> \r\n" );
}
}
void application_task ( void )
{
if ( display_mode == SWIPESWITCH_GESTURE_MODE)
{
events = swipeswitch_read_events( &swipeswitch );
gestures = swipeswitch_read_gestures( &swipeswitch );
if ( ( events & ( SWIPESWITCH_EVENT_SWIPE ) ) != 0 )
{
if ( ( gestures & SWIPESWITCH_GESTURE_SWIPE_UP ) != 0 )
{
log_printf( &logger, "SWIPE UP \r\n" );
}
if ( ( gestures & SWIPESWITCH_GESTURE_SWIPE_DOWN ) != 0 )
{
log_printf( &logger, "SWIPE DOWN \r\n" );
}
if ( ( gestures & SWIPESWITCH_GESTURE_SWIPE_LEFT ) != 0 )
{
log_printf( &logger, "SWIPE LEFT \r\n" );
}
if ( ( gestures & SWIPESWITCH_GESTURE_SWIPE_RIGHT ) != 0 )
{
log_printf( &logger, "SWIPE RIGHT \r\n" );
}
}
else if ( ( events & ( SWIPESWITCH_EVENT_TAP ) ) != 0 )
{
log_printf( &logger,"TAP \r\n" );
}
}
else if ( display_mode == SWIPESWITCH_POSITION_MODE)
{
x_coordinate = swipeswitch_read_x_coordinate( &swipeswitch );
y_coordinate = swipeswitch_read_y_coordinate( &swipeswitch );
if ( ( x_coordinate != old_x_coordinate) || ( y_coordinate != old_y_coordinate ) )
{
log_printf( &logger,"Coordinate : (%u , %u)\r\n", (uint16_t) x_coordinate, (uint16_t) y_coordinate );
old_x_coordinate = x_coordinate;
old_y_coordinate = y_coordinate;
}
}
Delay_ms( 300 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
