Create the ideal environment for a healthier, happier life with HDC2080 and STM32F091RC
Your climate, your control, our expertise
Published Feb 26, 2024
Click board™
Temp&Hum 12 Click
Dev. board
Nucleo-64 with STM32F091RC MCU
Compiler
NECTO Studio
MCU
STM32F091RC
Our technology and your comfort are perfectly aligned, bringing you the best in climate control solutions.
A
A
Hardware Overview
How does it work?
Temp&Hum 12 Click is based on the HDC2080, a Low Power Humidity and Temperature Digital Sensor from Texas Instruments. This sensor is factory calibrated to 2% relative humidity and 0.2°C temperature accuracy. It has an integrated heating element that is used to evaporate condensation, protecting the sensor that way. This heating element can be simply activated by setting a bit in the appropriate register. In the case when the heater is powered on, the typical current consumption is about 90mA. Internally, two sensors are connected to the two separated ADC sections, which can be set to sample measurements with the resolution of 9, 11 or 14 bits, based on the measurement time. The OTP memory holds the calibration coefficients that are applied to the measured value and the results are stored on the output registers, in the MSB/LSB format. These values are
then used in formulas found in the HDC2080 datasheet so that the final temperature or relative humidity data can be calculated. It is also possible to correct the offsets with custom values. HDC2080 IC uses the I2C protocol to communicate with the host MCU. Its I2C bus pins are routed to the mikroBUS™ I2C pins and are pulled to a HIGH logic level by the onboard resistors. The final I2C address of this IC is already determined by setting ADDR pin to GND (LOW logic level for 0). Temp&Hum 12 click supports programable temperature and humidity thresholds in the HDC2080 allow the device to send a hardware interrupt to wake up the microcontroller when necessary. In addition, the power consumption of the HDC2080 is significantly reduced, which helps to minimize self-heating and improve measurement accuracy. More information about these registers can be
found in the HDC2080 datasheet. HDC2080 IC itself is a very low power consumption device and it can work in two modes: sleep and active (measurement) mode. The device enters the sleep the mode as soon as possible, to save power. This makes the HDC2080 suitable to be used in battery-powered applications. In these applications, the HDC2080 spends most of the time in sleep mode, with the typical current consumption of 50 nA. While in the active mode, measurement can be configured either to automatic (with the predefined output data rate) or on-demand. In the automatic mode, the measurement is triggered in predefined time intervals, while on-demand measurement happens whenever the I2C command is sent. As soon as the single measurement is finished, the device falls back to the sleep mode.
Features overview
Development board
Nucleo-64 with STM32F091RC 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-M0
MCU Memory (KB)
256
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
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 STM32F091RC 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 Temp&Hum 12 Click driver.
Key functions:
temphum12_get_temperature- Temperature datatemphum12_get_humidity- Relative Huminidy datatemphum12_get_intrrupt_state- Interrupt state
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 TempHum12 Click example
*
* # Description
* This application measures temperature and humidity.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes driver init and configuration device for measurement.
*
* ## Application Task
* Reads Temperature and Humidity data and this data logs to the USBUART every 1 sec.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "temphum12.h"
// ------------------------------------------------------------------ VARIABLES
static temphum12_t temphum12;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
temphum12_cfg_t cfg;
uint16_t tmp;
uint8_t read_reg[ 2 ];
/**
* 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.
temphum12_cfg_setup( &cfg );
TEMPHUM12_MAP_MIKROBUS( cfg, MIKROBUS_1 );
temphum12_init( &temphum12, &cfg );
temphum12_default_cfg( &temphum12 );
Delay_ms( 1500 );
log_printf( &logger, "--- Start measurement ----\r\n" );
}
void application_task ( void )
{
float temperature;
float humidity;
temperature = temphum12_get_temperature( &temphum12,
TEMPHUM12_TEMP_IN_CELSIUS );
log_printf( &logger, "Temperature: %.2f \r\n", temperature );
Delay_1sec( );
humidity = temphum12_get_humidity( &temphum12 );
log_printf( &logger, "Humidity: %.2f \r\n", humidity );
log_printf( &logger, "-----------------------------\r\n" );
Delay_1sec( );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
