Versatile and compact solution for adding audio signalization features to various electronic applications, catering to the needs of developers and engineers in different fields
A
A
Hardware Overview
How does it work?
Buzz Click is based on the EPT-14A4005P, a piezoelectric transducer from Sanco Electronics. It uses a DC voltage to produce an audio signal while drawing a maximum current of 2mA from a wide operating voltage, in this case, 3.3V or 5V. As its name suggests, a piezo buzzer’s core comprises the piezoelectric ceramic element and a metal plate held together by an adhesive. When a DC is passed through, the piezoceramic element contracts and expands, which causes a vibration that produces sound waves. The buzzer has a resonant frequency of 4000Hz, at which the
buzzer vibrates, thus making a sound. The buzzer is 13.8x6.8mm in dimensions, and besides this Click board™, it can be bought separately from MIKROE. The onboard buzzer driver can be controlled by either a digital GPI pin or a PWM line of a mikroBUS™ socket. Users can create a sound using the Sound library supported in MIKROE compilers or utilize the microcontroller’s internal PWM module to generate the signal for the buzzer. Signal frequency determines the sound pitch, and the duty cycle determines the amplitude (sound volume). Both GPI and PWM lines are connected to
the buzzer by default. The user can separate one of the lines by removing the corresponding jumper (J2 or J3). This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the PWR SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. Also, this Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used as a reference for further development.
Features overview
Development board
EasyPIC v7a is the seventh generation of PIC development boards specially designed for the needs of rapid development of embedded applications. It supports a wide range of 8-bit PIC microcontrollers from Microchip and has a broad set of unique functions, such as the first-ever embedded debugger/programmer over USB-C. The development board is well organized and designed so that the end-user has all the necessary elements in one place, such as switches, buttons, indicators, connectors, and others. With four different connectors for each port, EasyPIC v7a allows you to connect accessory boards, sensors, and custom electronics more efficiently than ever. Each part of the EasyPIC v7a development board
contains the components necessary for the most efficient operation of the same board. In addition to the advanced integrated CODEGRIP programmer/debugger module, which offers many valuable programming/debugging options and seamless integration with the Mikroe software environment, the board also includes a clean and regulated power supply module for the development board. It can use various external power sources, including an external 12V power supply, 7-23V AC or 9-32V DC via DC connector/screw terminals, and a power source via the USB Type-C (USB-C) connector. Communication options such as USB-UART and RS-232 are also included, alongside the well-
established mikroBUS™ standard, three display options (7-segment, graphical, and character-based LCD), and several different DIP sockets. These sockets cover a wide range of 8-bit PIC MCUs, from PIC10F, PIC12F, PIC16F, PIC16Enh, PIC18F, PIC18FJ, and PIC18FK families. EasyPIC v7a is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development 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
![default](https://dbp-cdn.mikroe.com/catalog/mcus/resources/PIC18F26K42.jpeg)
Architecture
PIC
MCU Memory (KB)
64
Silicon Vendor
Microchip
Pin count
28
RAM (Bytes)
4096
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
![BUZZ Click Schematic schematic](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1ee790b4-8cb9-6708-8536-0242ac120009/schematic.webp)
Step by step
Project assembly
Track your results in real time
Application Output
After pressing the "FLASH" button on the left-side panel, it is necessary to open the UART terminal to display the achieved results. By clicking on the Tools icon in the right-hand panel, multiple different functions are displayed, among which is the UART Terminal. Click on the offered "UART Terminal" icon.
![UART Application Output Step 1](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703a-40a0-6b58-88de-02420a00029a/UART-AO-Step-1.jpg)
Once the UART terminal is opened, the window takes on a new form. At the top of the tab are two buttons, one for adjusting the parameters of the UART terminal and the other for connecting the UART terminal. The tab's lower part is reserved for displaying the achieved results. Before connecting, the terminal has a Disconnected status, indicating that the terminal is not yet active. Before connecting, it is necessary to check the set parameters of the UART terminal. Click on the "OPTIONS" button.
![UART Application Output Step 2](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703a-eb29-62fa-ba91-02420a00029a/UART-AO-Step-2.jpg)
In the newly opened UART Terminal Options field, we check if the terminal settings are correct, such as the set port and the Baud rate of UART communication. If the data is not displayed properly, it is possible that the Baud rate value is not set correctly and needs to be adjusted to 115200. If all the parameters are set correctly, click on "CONFIGURE".
![UART Application Output Step 3](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703b-7543-6fbc-9c69-0242ac120003/UART-AO-Step-3.jpg)
The next step is to click on the "CONNECT" button, after which the terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.
![UART Application Output Step 4](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703c-068c-66a4-a4fc-0242ac120003/UART-AO-Step-4.jpg)
Software Support
Library Description
This library contains API for BUZZ Click driver.
Key functions:
buzz_set_duty_cycle
- This function sets the PWM duty cycle in percentages ( Range[ 0..1 ])buzz_pwm_stop
- This function stops the PWM moudle outputbuzz_pwm_start
- This function starts the PWM moudle outputbuzz_play_sound
- This function plays sound on buzzer
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 BUZZ Click example
*
* # Description
* This example demonstrates the use of Buzz click boards.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and logger.
*
* ## Application Task
* Plays the Imperial March melody. Also logs an appropriate message on the USB UART.
*
* ## Additional Functions
* imperial_march( void ) - this function plays the Imperial March melody.
*
* @note
* The minimal PWM Clock frequency required for this example is the frequency of tone C6 - 1047 Hz.
* So, in order to run this example and play all tones correctly, the user will need to decrease
* the MCU's main clock frequency in MCU Settings for the certain architectures
* in order to get the required PWM clock frequency.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "buzz.h"
#define W 4*Q // Whole 4/4 - 4 Beats
#define H 2*Q // Half 2/4 - 2 Beats
#define Q 250 // Quarter 1/4 - 1 Beat
#define E Q/2 // Eighth 1/8 - 1/2 Beat
#define S Q/4 // Sixteenth 1/16 - 1/4 Beat
#define VOLUME 100 // goes up to 1000
static buzz_t buzz;
static log_t logger;
static void imperial_march( ) {
buzz_play_sound( &buzz, BUZZ_NOTE_A6, VOLUME, Q );
Delay_ms( 1 + Q );
buzz_play_sound( &buzz, BUZZ_NOTE_A6, VOLUME, Q );
Delay_ms( 1 + Q );
buzz_play_sound( &buzz, BUZZ_NOTE_A6, VOLUME, Q );
Delay_ms( 1 + Q );
buzz_play_sound( &buzz, BUZZ_NOTE_F6, VOLUME, E + S );
Delay_ms( 1 + E + S );
buzz_play_sound( &buzz, BUZZ_NOTE_C7, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_A6, VOLUME, Q );
Delay_ms( 1 + Q );
buzz_play_sound( &buzz, BUZZ_NOTE_F6, VOLUME, E + S );
Delay_ms( 1 + E + S );
buzz_play_sound( &buzz, BUZZ_NOTE_C7, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_A6, VOLUME, H );
Delay_ms( 1 + H );
buzz_play_sound( &buzz, BUZZ_NOTE_E7, VOLUME, Q );
Delay_ms( 1 + Q );
buzz_play_sound( &buzz, BUZZ_NOTE_E7, VOLUME, Q );
Delay_ms( 1 + Q );
buzz_play_sound( &buzz, BUZZ_NOTE_E7, VOLUME, Q );
Delay_ms( 1 + Q );
buzz_play_sound( &buzz, BUZZ_NOTE_F7, VOLUME, E + S );
Delay_ms( 1 + E + S );
buzz_play_sound( &buzz, BUZZ_NOTE_C7, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_Ab6, VOLUME, Q );
Delay_ms( 1 + Q );
buzz_play_sound( &buzz, BUZZ_NOTE_F6, VOLUME, E + S );
Delay_ms( 1 + E + S );
buzz_play_sound( &buzz, BUZZ_NOTE_C7, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_A6, VOLUME, H );
Delay_ms( 1 + H );
buzz_play_sound( &buzz, BUZZ_NOTE_A7, VOLUME, Q );
Delay_ms( 1 + Q );
buzz_play_sound( &buzz, BUZZ_NOTE_A6, VOLUME, E + S );
Delay_ms( 1 + E + S );
buzz_play_sound( &buzz, BUZZ_NOTE_A6, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_A7, VOLUME, Q );
Delay_ms( 1 + Q );
buzz_play_sound( &buzz, BUZZ_NOTE_Ab7, VOLUME, E + S );
Delay_ms( 1 + E + S );
buzz_play_sound( &buzz, BUZZ_NOTE_G7, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_Gb7, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_E7, VOLUME, Q );
Delay_ms( 1 + Q );
buzz_play_sound( &buzz, BUZZ_NOTE_F7, VOLUME, E );
Delay_ms( 1 + E );
Delay_ms( 1 + E );
buzz_play_sound( &buzz, BUZZ_NOTE_Bb6, VOLUME, E );
Delay_ms( 1 + E );
buzz_play_sound( &buzz, BUZZ_NOTE_Eb7, VOLUME, Q );
Delay_ms( 1 + Q );
buzz_play_sound( &buzz, BUZZ_NOTE_D7, VOLUME, E + S );
Delay_ms( 1 + E + S );
buzz_play_sound( &buzz, BUZZ_NOTE_Db7, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_C7, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_B6, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_C7, VOLUME, E );
Delay_ms( 1 + E );
Delay_ms( 1 + E );
buzz_play_sound( &buzz, BUZZ_NOTE_F6, VOLUME, E );
Delay_ms( 1 + E );
buzz_play_sound( &buzz, BUZZ_NOTE_Ab6, VOLUME, Q );
Delay_ms( 1 + Q );
buzz_play_sound( &buzz, BUZZ_NOTE_F6, VOLUME, E + S );
Delay_ms( 1 + E + S );
buzz_play_sound( &buzz, BUZZ_NOTE_A6, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_C7, VOLUME, Q );
Delay_ms( 1 + Q );
buzz_play_sound( &buzz, BUZZ_NOTE_A6, VOLUME, E + S );
Delay_ms( 1 + E + S );
buzz_play_sound( &buzz, BUZZ_NOTE_C7, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_E7, VOLUME, H );
Delay_ms( 1 + H );
buzz_play_sound( &buzz, BUZZ_NOTE_A7, VOLUME, Q );
Delay_ms( 1 + Q );
buzz_play_sound( &buzz, BUZZ_NOTE_A6, VOLUME, E + S );
Delay_ms( 1 + E + S );
buzz_play_sound( &buzz, BUZZ_NOTE_A6, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_A7, VOLUME, Q );
Delay_ms( 1 + Q );
buzz_play_sound( &buzz, BUZZ_NOTE_Ab7, VOLUME, E + S );
Delay_ms( 1 + E + S );
buzz_play_sound( &buzz, BUZZ_NOTE_G7, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_Gb7, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_E7, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_F7, VOLUME, E );
Delay_ms( 1 + E );
Delay_ms( 1 + E );
buzz_play_sound( &buzz, BUZZ_NOTE_Bb6, VOLUME, E );
Delay_ms( 1 + E );
buzz_play_sound( &buzz, BUZZ_NOTE_Eb7, VOLUME, Q );
Delay_ms( 1 + Q );
buzz_play_sound( &buzz, BUZZ_NOTE_D7, VOLUME, E + S );
Delay_ms( 1 + E + S );
buzz_play_sound( &buzz, BUZZ_NOTE_Db7, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_C7, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_B6, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_C7, VOLUME, E );
Delay_ms( 1 + E );
Delay_ms( 1 + E );
buzz_play_sound( &buzz, BUZZ_NOTE_F6, VOLUME, E );
Delay_ms( 1 + E );
buzz_play_sound( &buzz, BUZZ_NOTE_Ab6, VOLUME, Q );
Delay_ms( 1 + Q );
buzz_play_sound( &buzz, BUZZ_NOTE_F6, VOLUME, E + S );
Delay_ms( 1 + E + S );
buzz_play_sound( &buzz, BUZZ_NOTE_C7, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_A6, VOLUME, Q );
Delay_ms( 1 + Q );
buzz_play_sound( &buzz, BUZZ_NOTE_F6, VOLUME, E + S );
Delay_ms( 1 + E + S );
buzz_play_sound( &buzz, BUZZ_NOTE_C7, VOLUME, S );
Delay_ms( 1 + S );
buzz_play_sound( &buzz, BUZZ_NOTE_Ab6, VOLUME, H );
Delay_ms( 1 + H );
}
void application_init ( void ) {
log_cfg_t log_cfg; /**< Logger config object. */
buzz_cfg_t buzz_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.
buzz_cfg_setup( &buzz_cfg );
BUZZ_MAP_MIKROBUS( buzz_cfg, MIKROBUS_1 );
err_t init_flag = buzz_init( &buzz, &buzz_cfg );
if ( init_flag == PWM_ERROR ) {
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
buzz_set_duty_cycle ( &buzz, 0.0 );
buzz_pwm_start( &buzz );
log_info( &logger, " Application Task " );
}
void application_task ( void ) {
log_printf( &logger, "Playing the Imperial March melody ...\r\n" );
imperial_march( );
Delay_ms( 10000 );
}
void main ( void ) {
application_init( );
for ( ; ; ) {
application_task( );
}
}
// ------------------------------------------------------------------------ END