Control your projects easily with CTHS15CIC05 and STM32F410RB
Ignite action!
Published Aug 09, 2023
Click board™
Button Power Click
Dev Board
UNI Clicker
Compiler
NECTO Studio
MCU
STM32F410RB
Easily control device states using the intuitive POWER button, providing seamless on/off functionality tailored to your needs
A
A
Hardware Overview
How does it work?
Button Power Click is based on the CTHS15CIC05ONOFF, a capacitive touch sensor display by VCC (Visual Communications Company). This sensor is an all-in-one solution, providing capacitive touch sensing in an appealing housing with the backlit power symbol icon on the top. A minimum number of pins is used on this device: only four pins are exposed to the user. Two more pins are used besides the power supply pins (VCC and GND). The touch detection is indicated by a HIGH logic level on the OUT pin of the CTHS15CIC05ONOFF sensor, while the IN pin is used as the power supply for two internal LEDs, which are connected in the common cathode configuration. The forward voltage of the LEDs is typically 3.2V. The OUT
pin of the sensor is routed to the INT pin of the mikroBUS™, while the IN pin of the sensor is routed to the PWM pin of the mikroBUS™. The power symbol icon on the top of the touch sensor is visible even when the backlight is off, thanks to the LEXAN™ polycarbonate film with an inverse print of the icon placed on top of the sensor. When the internal LEDs are turned ON, the light will pass through the translucent power symbol icon, resulting in a uniformly lit power symbol icon. An interesting lighting effect can be designed when touched by applying a PWM signal to the IN pin. The sensor IC, the sensing pad, and two integrated LEDs are enclosed in a small square casing, measuring 15mm by 15mm by 11mm. It forms a compact and robust touch button, which has
many advantages over a mechanical button: it is not subject to wear since there are no moving parts, it does not exhibit any bouncing or chattering effect, it is durable and resistant to weather elements, and more. However, it can’t be used to close an electrical circuit, only to produce a logic signal translated to appropriate action by the host MCU. The sensor can be operated even with wet hands or while using certain gloves. The touch sensor can also be placed behind a clear glass or a plastic layer, such as polycarbonate or acrylic, up to 3mm thick. Although the sensor will perform self-calibration after being powered, it is best to test its functionality in these cases if the position will be fixed.
Features overview
Development board
UNI Clicker is a compact development board designed as a complete solution that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It supports a wide range of microcontrollers, such as different ARM, PIC32, dsPIC, PIC, and AVR from various vendors like Microchip, ST, NXP, and TI (regardless of their number of pins), four mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a debugger/programmer connector, and two 26-pin headers for interfacing with external electronics. Thanks to innovative manufacturing technology, it allows you to build
gadgets with unique functionalities and features quickly. Each part of the UNI Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the UNI Clicker programming method, using a third-party programmer or CODEGRIP/mikroProg connected to onboard JTAG/SWD header, the UNI Clicker board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Type-C (USB-C) connector, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or using a Li-Po/Li
Ion battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board (plus USB HOST/DEVICE), including the well-established mikroBUS™ socket, a standardized socket for the MCU card (SiBRAIN standard), and several user-configurable buttons and LED indicators. UNI Clicker is an integral part of the Mikroe ecosystem, allowing you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping 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
Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
128
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
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 UNI Clicker as your development board.
Track your results in real time
Application Output
This Click board can be interfaced and monitored in two ways:
Application Output- Use the "Application Output" window in Debug mode for real-time data monitoring. Set it up properly by following this tutorial.
UART Terminal- Monitor data via the UART Terminal using a USB to UART converter. For detailed instructions, check out this tutorial.
Software Support
Library Description
This library contains API for Button Power Click driver.
Key functions:
buttonpower_pwm_stop- This function stops the PWM moudle outputbuttonpower_pwm_start- This function starts the PWM moudle outputbuttonpower_get_button_state- This function reads the digital signal from the INT pin which tells us whether the button has been pressed or not
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 main.c
* @brief Button Power Click Example.
*
* # Description
* This example showcases how to initialize and use the whole family of Button clicks.
* One library is used for every single one of them. They are simple touch detectors which send
* a pressed/released signal and receive a PWM output which controls the backlight on the button.
*
* The demo application is composed of two sections :
*
* ## Application Init
* This function initializes and configures the logger and click modules.
*
* ## Application Task
* This example first increases the backlight on the button and then decreases the intensity of the backlight. When the button is touched,
* reports the event in the console using UART communication.
*
*
* @author Nikola Peric
*
*/
#include "board.h"
#include "log.h"
#include "buttonpower.h"
static buttonpower_t buttonpower;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
buttonpower_cfg_t buttonpower_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.
buttonpower_cfg_setup( &buttonpower_cfg );
BUTTONPOWER_MAP_MIKROBUS( buttonpower_cfg, MIKROBUS_1 );
err_t init_flag = buttonpower_init( &buttonpower, &buttonpower_cfg );
if ( PWM_ERROR == init_flag )
{
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
Delay_ms( 500 );
buttonpower_pwm_start( &buttonpower );
buttonpower_set_duty_cycle ( &buttonpower, 0.1 );
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
static float duty_cycle;
static uint8_t button_state;
static uint8_t button_state_old;
button_state = buttonpower_get_button_state( &buttonpower );
if ( button_state && ( button_state != button_state_old ) )
{
log_printf( &logger, " <-- Button pressed --> \r\n" );
for ( uint8_t n_cnt = 1; n_cnt <= 100; n_cnt++ )
{
duty_cycle = ( float ) n_cnt ;
duty_cycle /= 100;
buttonpower_set_duty_cycle( &buttonpower, duty_cycle );
Delay_ms( 10 );
}
button_state_old = button_state;
}
else if ( !button_state && ( button_state != button_state_old ) )
{
for ( uint8_t n_cnt = 100; n_cnt > 0; n_cnt-- )
{
duty_cycle = ( float ) n_cnt ;
duty_cycle /= 100;
buttonpower_set_duty_cycle( &buttonpower, duty_cycle );
Delay_ms( 10 );
}
button_state_old = button_state;
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
