barometer9

---

Barometer 9 Click

Barometer 9 Click demo application is developed using the NECTO Studio, ensuring compatibility with mikroSDK's open-source libraries and tools. Designed for plug-and-play implementation and testing, the demo is fully compatible with all development, starter, and mikromedia boards featuring a mikroBUS™ socket.

---

Click Library

• Author : Stefan Ilic
• Date : Nov 2023.
• Type : I2C/SPI type

Software Support

Example Description

This example demonstrates the use of Barometer 9 Click board by reading and displaying the pressure and temperature measurements.

Example Libraries

• MikroSDK.Board
• MikroSDK.Log
• Click.Barometer9

Example Key Functions

• barometer9_cfg_setup Config Object Initialization function.

void barometer9_cfg_setup ( barometer9_cfg_t *cfg );

• barometer9_init Initialization function.

err_t barometer9_init ( barometer9_t *ctx, barometer9_cfg_t *cfg );

• barometer9_default_cfg Click Default Configuration function.

err_t barometer9_default_cfg ( barometer9_t *ctx );

• barometer9_read_part_id This function is used to read a Device ID of Barometer 9 Click board.

err_t barometer9_read_part_id ( barometer9_t *ctx, uint16_t *part_id );

• barometer9_get_temperature This function is used to read a temperature of Barometer 9 Click board in degree of Celsius.

err_t barometer9_get_temperature ( barometer9_t *ctx, float *temperature );

• barometer9_get_pressure This function is used to read a pressure of Barometer 9 Click board in Pascals.

err_t barometer9_get_pressure ( barometer9_t *ctx, float *pressure );

Application Init

The initialization of I2C or SPI module and log UART. After driver initialization, the app sets the default configuration.

void application_init ( void )
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    barometer9_cfg_t barometer9_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.
    barometer9_cfg_setup( &barometer9_cfg );
    BAROMETER9_MAP_MIKROBUS( barometer9_cfg, MIKROBUS_1 );
    err_t init_flag = barometer9_init( &barometer9, &barometer9_cfg );
    if ( ( I2C_MASTER_ERROR == init_flag ) || ( SPI_MASTER_ERROR == init_flag ) )
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }
    Delay_ms ( 100 );
    
    if ( BAROMETER9_ERROR == barometer9_default_cfg ( &barometer9 ) )
    {
        log_error( &logger, " Default configuration." );
        for ( ; ; );
    }
    
    uint16_t device_id = 0;
    barometer9_read_part_id ( &barometer9, &device_id );
    if ( BAROMETER9_DEVICE_ID != device_id )
    {
        log_error( &logger, " Read error " );
        for ( ; ; );
    }
    else
    {
        log_printf( &logger, " Device ID: 0x%.4X \r\n", device_id );
    }
    
    log_info( &logger, " Application Task " );
}

Application Task

The demo application reads and displays the Pressure [Pa] and Temperature [degree Celsius] data. Results are being sent to the UART Terminal, where you can track their changes.

void application_task ( void )
{
    float temperature = 0;
    float pressure = 0;

    barometer9_get_temperature( &barometer9, &temperature );
    barometer9_get_pressure( &barometer9, &pressure );
    log_printf( &logger, " Temperature: %.2f C \r\n Pressure %.3f Pa \r\n", temperature, pressure );
    log_printf( &logger, " - - - - - - - - - - \r\n" );
    Delay_ms ( 1000 );
}

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.

Additional Notes and Information

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.

---