TOP Contributors

  1. MIKROE (2762 codes)
  2. Alcides Ramos (374 codes)
  3. Shawon Shahryiar (307 codes)
  4. jm_palomino (118 codes)
  5. Bugz Bensce (90 codes)
  6. S P (73 codes)
  7. dany (71 codes)
  8. MikroBUS.NET Team (35 codes)
  9. NART SCHINACKOW (34 codes)
  10. Armstrong Subero (27 codes)

Most Downloaded

  1. Timer Calculator (139251 times)
  2. FAT32 Library (71751 times)
  3. Network Ethernet Library (57122 times)
  4. USB Device Library (47430 times)
  5. Network WiFi Library (43082 times)
  6. FT800 Library (42403 times)
  7. GSM click (29835 times)
  8. mikroSDK (28078 times)
  9. PID Library (26885 times)
  10. microSD click (26198 times)
Libstock prefers package manager

Package Manager

We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]

< Back
mikroSDK Library

Bluetooth Click

Rating:

0

Author: MIKROE

Last Updated: 2024-10-31

Package Version: 2.1.0.17

mikroSDK Library: 2.0.0.0

Category: BT/BLE

Downloaded: 196 times

Not followed.

License: MIT license  

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.

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "Bluetooth Click" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "Bluetooth Click" changes.

Do you want to report abuse regarding "Bluetooth Click".

  • mikroSDK Library 1.0.0.0
  • Comments (0)

mikroSDK Library Blog


Bluetooth Click

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.

bluetooth_click.png

Click Product page


Click library

  • Author : MikroE Team
  • Date : Jun 2020.
  • Type : UART GPS/GNSS type

Software Support

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.

Library Description

This library contains API for Bluetooth Click driver.

Standard key functions :

  • 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 );

Example key functions :

  • 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 );

Examples Description

This example reads and processes data from Bluetooth clicks.

The demo application is composed of two sections :

Application Init

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" );
}

Application Task

Reads the received data.


void application_task ( void )
{
    bluetooth_process( "AOK" );
} 

Note

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.


ALSO FROM THIS AUTHOR

MCP2517FD click

6

MCP2517FD Click is a compact add-on board representing a complete CAN solution used as a control node in a CAN network. This board features the MCP2517FD and ATA6563, an external CAN FD controller with an SPI interface, and a high-speed CAN transceiver from Microchip. The ATA6563, a low-level physical layer IC (PHY), provides a physical connection with the CAN bus itself, while the CAN controller MCP2517FD represents an interface between the MCU and the PHY. It features three operating modes with dedicated fail-safe features, remote wake-up via CAN, and ideally passive behavior when powered off on the CAN bus. This Click board™ is suitable for developing a wide range of automotive diagnostic applications, even on MCUs that don’t support CAN interface.

[Learn More]

Accel 18 Click

0

Accel 18 Click is a compact add-on board that contains an acceleration sensor. This board features the MC3419, a digital output 3-axis accelerometer with a feature set optimized for consumer product motion sensing from MEMSIC.

[Learn More]

HZ to V 2 Click

0

HZ to V 2 Click is a device that can convert input frequency of the signal with virtually any wave shape to a DC voltage output, with a level proportional to the input frequency.

[Learn More]