\mainpage Main Page
With the range up to a 100m and low power consumption, Bluetooth click is a great solution if you are looking for a simple way to integrate Bluetooth 2.1 communication to your device. It features the RN-41 low power, class 1 Bluetooth radio module. Bluetooth click communicates with the target board MCU through UART interface and is designed to run on 3.3V power supply only.
- Author : MikroE Team
- Date : Jun 2020.
- Type : UART GPS/GNSS type
We provide a library for the Bluetooth 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 form compilers IDE(recommended way), or downloaded from our LibStock, or found on mikroE github account.
This library contains API for Bluetooth Click driver.
- Config Object Initialization function.
void bluetooth_cfg_setup ( bluetooth_cfg_t *cfg );
- Initialization function.
BLUETOOTH_RETVAL bluetooth_init ( bluetooth_t *ctx, bluetooth_cfg_t *cfg );
- The function enter the command mode of the RN-41 Bluetooth module on Bluetooth Click board.
void bluetooth_enter_command_mode ( bluetooth_t *ctx );
- The function set the authentication value to the RN-41 Bluetooth module on Bluetooth Click board.
void bluetooth_set_authentication ( bluetooth_t *ctx, uint8_t auth_value );
- The function set security pin code string to the RN-41 Bluetooth module on Bluetooth Click board.
BLUETOOTH_RETVAL bluetooth_set_security_pin_code ( bluetooth_t *ctx, uint8_t *sp_code );
This example reads and processes data from Bluetooth clicks.
The demo application is composed of two sections :
Initializes driver and wake-up module.
void application_init ( void )
{
log_cfg_t log_cfg;
bluetooth_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.
bluetooth_cfg_setup( &cfg );
BLUETOOTH_MAP_MIKROBUS( cfg, MIKROBUS_1 );
bluetooth_init( &bluetooth, &cfg );
Delay_ms( 500 );
log_printf( &logger, "Configuring the module...\n" );
do
{
log_printf( &logger, " --- Command mode --- \r\n" );
bluetooth_enter_command_mode( &bluetooth );
}
while( bluetooth_process( "CMD" ) != 1 );
do
{
log_printf( &logger, " --- Device name --- \r\n" );
bluetooth_set_device_name( &bluetooth, &DEVICE_NAME_DATA[ 0 ] );
}
while( bluetooth_process( "AOK" ) != 1 );
do
{
log_printf( &logger, " --- Status string --- \r\n" );
bluetooth_set_extended_status_string( &bluetooth, &EXTENDED_STRING_DATA[ 0 ] );
}
while( bluetooth_process( "AOK" ) != 1 );
do
{
log_printf( &logger, " --- Operating mode --- \r\n" );
bluetooth_set_operating_mode( &bluetooth, 0 );
}
while( bluetooth_process( "AOK" ) != 1 );
do
{
log_printf( &logger, " --- Authentication --- \r\n" );
bluetooth_set_authentication( &bluetooth, 1 );
}
while( bluetooth_process( "AOK" ) != 1 );
do
{
log_printf( &logger, " --- Pin code --- \r\n" );
bluetooth_set_security_pin_code( &bluetooth, &PIN_CODE_DATA[ 0 ] );
}
while( bluetooth_process( "AOK" ) != 1 );
do
{
log_printf( &logger, " --- Exit command mode --- \r\n" );
bluetooth_exit_command_mode( &bluetooth );
}
while( bluetooth_process( "END" ) != 1 );
log_printf( &logger, "The module has been configured.\n" );
}
Reads the received data.
void application_task ( void )
{
bluetooth_process( "AOK" );
}
Before starting to use this click, it must be paired with other device.
The full application code, and ready to use projects can be installed directly form compilers IDE(recommneded) or found on LibStock page or mikroE GitHub accaunt.
Other mikroE Libraries used in the example:
- MikroSDK.Board
- MikroSDK.Log
- Click.Bluetooth
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. The terminal available in all Mikroelektronika compilers, or any other terminal application of your choice, can be used to read the message.