The button with a vibrant yellow light brings a ray of sunshine to your interactions, illuminating actions and ensuring they stand out in style
A
A
Hardware Overview
How does it work?
Button Y Click is based on the 3006.2111, a high-quality, single-pole, single-throw (SPST) tactile switch from Marquardt. This is a high-quality, low-profile pushbutton with a reasonably large diameter of 6.8mm. It is equipped with a yellow LED, which can be dimmed by applying a PWM signal from the MCU. Therefore, the anode of the LED is connected to the PWM pin of the mikroBUS™. The embedded LED can be used for a signalization, but also for aesthetic purposes. The switch itself has very good characteristics: it has a low ON resistance (a resistance through the button while it is pressed) of less than 100mΩ, very low bouncing time (a time during which the contact plates settle down) of less than 1.5ms typically. The mechanical endurance of the tactile switch is rated to more than 500,000 cycles, while applying 14VDC, 10mA. The total travel distance of the button is 2.9 mm, while the tactile force of the button is 4N. The maximum voltage that should be used between the switch terminals is 28V, while the current should stay below 50mA. Two important properties that describe a button, are its mechanical endurance and bouncing delay. Those two attributes depend on each other, so
when a significant bouncing appears, it might be a sign of a switch deterioration. Likewise, a switch will develop larger bouncing effect as it is been used over time. The mechanical endurance is also affected by the force applied to the switch while operated, as well as its eccentricity (pressing the button off center). Bouncing time is a parameter which describes how fast contact plates of a switch are settled down. Each material has some elastic properties. This is also true for the contact plates of the button. Different types of switches have different mechanism to establish a contact, but they are all based on a common principle: they are made so they accumulate the pressure force, until there is enough energy stored so that the plate can be actuated very fast, turning the accumulated pressure into kinetic energy (resulting with the familiar click sound). The most often, a form of spring mechanism is used. However, when hitting the second, fixed plate, a moving plate will bounce off a few times, depending on the elasticity of the system, its speed and so on. There is no ideal dampening mechanism to reduce the bouncing completely. This button will accumulate force up to about 1N
before its actuated, providing a tactile feedback while clicking. The tactile switch used on Button Y click has an excellent bouncing duration of less than 1ms. However small, the bouncing of a button needs to be compensated, either in the application firmware, or the hardware. Button Y click has a simple debouncing circuit, made of a 10kΩ resistor and 10nF capacitor, which is sufficient for the most cases. The debounced signal will have a small delay, depending on a dampening circuitry. The delay is in the range of a few milliseconds, which is far less than a human can sense. Finally, the button is intended to be operated by a human, so even much larger delay is perfectly acceptable for this type of device. The button is active HIGH, which means that when it is pressed, a HIGH logic level will be applied to the INT pin. This switch will be pulled to a LOW logic level by the 10kΩ pull-down resistor while inactive, preventing the input pin of the MCU to become floating. The switch signal is routed to the INT pin of the mikroBUS™. An onboard SMD jumper labeled as VCC SEL is used to set the voltage for the HIGH logic level, allowing the Button Y click to be used with a wide range of different MCUs.
Features overview
Development board
Nucleo-64 with STM32F091RC 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)
256
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
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
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 Button Y Click driver.
Key functions:
buttony_pwm_stop
- This function stops the PWM moudle output.buttony_pwm_start
- This function starts the PWM moudle output.buttony_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
This example can be found in NECTO Studio. Feel free to download the code, or you can copy the code below.
/*!
* @file main.c
* @brief Button Y Click Example.
*
* # Description
* This library contains API for Button Y Click driver.
* One library is used for every single one of them.
* They are simple touch detectors that 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 backlight. When the button is pressed,
* reports the event in the console using UART communication.
*
* @author Nikola Peric
*
*/
#include "board.h"
#include "log.h"
#include "buttony.h"
static buttony_t buttony;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
buttony_cfg_t buttony_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.
buttony_cfg_setup( &buttony_cfg );
BUTTONY_MAP_MIKROBUS( buttony_cfg, MIKROBUS_1 );
err_t init_flag = buttony_init( &buttony, &buttony_cfg );
if ( PWM_ERROR == init_flag )
{
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
Delay_ms( 500 );
buttony_set_duty_cycle ( &buttony, 0.0 );
buttony_pwm_start( &buttony );
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 = buttony_get_button_state( &buttony );
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;
buttony_set_duty_cycle( &buttony, 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;
buttony_set_duty_cycle( &buttony, duty_cycle );
Delay_ms( 10 );
}
button_state_old = button_state;
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END