Maintain controlled environments by monitoring pressure variations with ICP-10111 and STM32F446RE
Barometers: Nature's weather whisperers
Published Oct 08, 2024
Click board™
Barometer 4 Click
Dev Board
Nucleo 64 with STM32F446RE MCU
Compiler
NECTO Studio
MCU
STM32F446RE
Discover the versatility of barometers in diverse fields, from agriculture to aviation, as they contribute to efficiency and precision in a wide range of applications
A
A
Hardware Overview
How does it work?
Barometer 4 Click is based on the ICP-10111, an ultra-low power, low noise, digital output barometric pressure and temperature sensor from TDK InvenSense. It is based on an innovative MEMS capacitive pressure sensor technology that can measure pressure from 30kPa up to 110kPa with an accuracy of ±1Pa over a wide operating temperature range at the industry’s lowest power. This high-accuracy MEMS capacitive pressure sensor can also measure altitude differentials down to 8.5cm without the penalty of increased power consumption or reduced sensor throughput. The ICP-10111 also offers industry-leading temperature stability of the pressure sensor with a temperature coefficient offset of
±0.5Pa/°C. The high accuracy, temperature stability, and low power consumption offered by ICP-10111 make it ideally suited for applications such as drone flight control and stabilization, indoor/outdoor navigation, sports and fitness activity monitoring, and battery-powered IoT. The ICP-10111 also requires a supply voltage of 1.8V to work regularly. Therefore, a small LDO regulator, BH18PB1WHFV from Rohm Semiconductor, provides 1.8V out of mikroBUS™ power rails. This LDO cuts power consumption by lowering its current consumption to approximately 2μA when the application operates in the Standby state. Barometer 4 Click communicates with MCU using a standard I2C 2-Wire interface that supports
400kHz Fast Mode operation. Since the sensor for operation requires a 1.8V logic voltage level only, this Click board™ also features the PCA9306 voltage-level translator from Texas Instruments. The I2C interface bus lines are routed to the dual bidirectional voltage-level translator, allowing this Click board™ to work properly with both 3.3V and 5V MCUs. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC 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
Nucleo-64 with STM32F446RE 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-M4
MCU Memory (KB)
512
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
131072
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
Start by selecting your development board and Click board™. Begin with the Nucleo 64 with STM32F446RE MCU as your development board.
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 Barometer 4 Click driver.
Key functions:
barometer4_get_pressure_and_temperature- Barometer 4 get pressure and temperature functionbarometer4_get_raw_data- Barometer 4 get RAW data functionbarometer4_soft_reset- Barometer 4 software reset function
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 Barometer4 Click example
*
* # Description
* This library contains API for the Barometer 4 Click driver.
* The library initializes and defines the I2C bus drivers
* to write and read data from registers.
* This demo application shows an example of
* atmospheric pressure and temperature measurement.
*
* The demo application is composed of two sections :
*
* ## Application Init
* The initialization of the I2C module and log UART.
* After driver initialization and default settings,
* the app display device ID.
*
* ## Application Task
* This is an example that shows the use of a Barometer 4 Click board™.
* Logs the atmospheric pressure [ Pa ] and temperature [ degree Celsius ] data.
* Results are being sent to the Usart Terminal where you can track their changes.
*
* @author Nenad Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "barometer4.h"
static barometer4_t barometer4;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
barometer4_cfg_t barometer4_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.
barometer4_cfg_setup( &barometer4_cfg );
BAROMETER4_MAP_MIKROBUS( barometer4_cfg, MIKROBUS_1 );
err_t init_flag = barometer4_init( &barometer4, &barometer4_cfg );
if ( I2C_MASTER_ERROR == init_flag )
{
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
barometer4_default_cfg ( &barometer4 );
log_info( &logger, " Application Task " );
log_printf( &logger, "----------------------------\r\n" );
Delay_ms( 100 );
static uint16_t device_id;
err_t err_flag = barometer4_get_device_id( &barometer4, &device_id );
if ( BAROMETER4_ERROR == err_flag )
{
log_error( &logger, " Communication Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
log_printf( &logger, " Device ID : 0x%.4X \r\n", device_id );
log_printf( &logger, "----------------------------\r\n" );
Delay_ms( 1000 );
}
void application_task ( void )
{
static float pressure;
static float temperature;
barometer4_get_pressure_and_temperature( &barometer4, &pressure, &temperature );
log_printf( &logger, " Pressure : %.2f Pa\r\n", pressure );
log_printf( &logger, " Temperature : %.2f C\r\n", temperature );
log_printf( &logger, "----------------------------\r\n" );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
