Accurately monitor and control indoor climate conditions using BME280 and STM32G474RE
Tri-Meteo Nexus
Published Nov 08, 2024
Click board™
Weather Click
Dev. board
Nucleo 64 with STM32G474RE MCU
Compiler
NECTO Studio
MCU
STM32G474RE
Enhance weather forecasting and environmental research with our integrated sensor solution, providing valuable data for meteorologists and scientists to analyze climate patterns and trends
A
A
Hardware Overview
How does it work?
Weather Click is based on the BME280, a combined humidity and pressure sensor from Bosch Sensortec. The BME280 itself contains sensors from each of the environmental measurements. The humidity sensor has high overall accuracy and an extremely fast response time. The pressure sensor has extremely high accuracy and resolution as an absolute barometric sensor. The temperature sensor is basically used for temperature compensation, thus for accurate readings. Nevertheless, it has low noise and high resolution and can be used for ambient temperature readings. The Weather Click can work in one of three power modes. Sleep mode is the first mode the sensor enters after the Power-On reset, when no measurements are performed with
its power consumption at the minimum. In Forced mode, the sensor performs a single measurement and returns to Sleep mode. For the next measurement, the Forced mode must be selected again. The Normal mode means the sensor will take measurements in automated perpetual cycling between measurement and inactive periods. The sensors inside the BME280 have different output resolutions, with 16-bit ADC for humidity and up to 20-bit for pressure readings. An internal IIR filter helps suppress the disturbance of many shorter changes, such as a wind blowing into the sensor, slamming a door, and such. To achieve a high resolution and low noise of readings, the IIR filter must be enabled. Weather Click can use a standard 2-Wire I2C
interface supporting standard, fast, and high speeds or an SPI serial interface to communicate with the host MCU. The communication interface can be selected via SPI I2C 4-jumper sets, with the I2C interface selected by default. All four jumpers must be in place for the Weather Click to work properly. The I2C address can be selected via the ADDR jumper, with 0 set by default. This Click board™ can be operated only with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. Also, it comes equipped with a library containing functions and an example code that can be used as a reference for further development.
Features overview
Development board
Nucleo-64 with STM32G474R 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)
128k
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
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Nucleo 64 with STM32G474RE MCU as your development board.
Track your results in real time
Application Output
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.
2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.
3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.
Software Support
Library Description
This library contains API for Weather Click driver.
Key functions:
weather_get_ambient_data- Use this function to read the temperature, pressure and humidity dataweather_get_device_id- You can use this function as a check on click communication with your MCUweather_measurement_cfg- Use this function to set up new settings
Open Source
Code example
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.
/*!
* \file
* \brief Weather Click example
*
* # Description
* This demo-app shows the temperature, pressure and humidity measurement using Weather click.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Configuring clicks and log objects.
* Setting the click in the default configuration to start the measurement.
*
* ## Application Task
* Reads Temperature data, Relative Huminidy data and Pressure data,
* this data logs to USBUART every 1500ms.
*
* \author Katarina Perendic
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "weather.h"
// ------------------------------------------------------------------ VARIABLES
static weather_t weather;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
weather_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.
weather_cfg_setup( &cfg );
WEATHER_MAP_MIKROBUS( cfg, MIKROBUS_1 );
weather_init( &weather, &cfg );
weather_default_cfg( &weather );
}
void application_task ( void )
{
weather_data_t weather_data;
// Task implementation.
weather_get_ambient_data( &weather, &weather_data );
log_printf( &logger, " \r\n ---- Weather data ----- \r\n" );
log_printf( &logger, "[PRESSURE]: %.2f mBar.\n\r", weather_data.pressure );
log_printf( &logger, "[TEMPERATURE]: %.2f C.\n\r", weather_data.temperature );
log_printf( &logger, "[HUMIDITY]: %.2f %%.\n\r", weather_data.humidity );
Delay_ms( 1500 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
