Keep temperature and humidity in check with HDC1000 and STM32F091RC
Improve your comfort with our temperature and humidity mastery
Published Feb 26, 2024
Click board™
HDC1000 Click
Dev. board
Nucleo-64 with STM32F091RC MCU
Compiler
NECTO Studio
MCU
STM32F091RC
Improve your comfort and well-being with our temperature and humidity sensing solution, enabling you to create environments that promote productivity, health, and overall satisfaction
A
A
Hardware Overview
How does it work?
HDC1000 Click is based on the HDC1000, a digital humidity sensor with an integrated temperature sensor from Texas Instruments, providing long-term and excellent measurement accuracy at low power. The HDC1000 is a factory-calibrated sensor that measures humidity using a novel capacitive sensor. The sensing element of the HDC1000 is placed on the bottom part of the device, which makes it more robust against dirt, dust, and other environmental contaminants. It can read humidity over the full range of 0 to 100% RH with a typical accuracy of ±3% over 20% to 60% RH, while its maximum temperature range is from -40 to 125°C. It has a typical accuracy of ±0.2°C over 10 to 50°C. The HDC1000 communicates with MCU using the
standard I2C 2-Wire interface with a maximum frequency of 400kHz. Resolution is based on the measurement time and can be 8, 11, or 14 bits for humidity; 11 or 14 for temperature. Besides, the HDC1000 allows choosing the least significant bits (LSB) of its I2C slave address using the SMD jumpers labeled ADRs. This sensor has two modes of operation: Sleep mode and Measurement mode. After the Power-Up sequence, the HDC1000 is in sleep mode, where it waits for I2C interface input, including commands to configure the conversion times, read the status of the battery, trigger a measurement, and read measurements. Once it receives a command to initiate a measurement, the HDC1000 moves from Sleep
mode to Measurement mode. In Measurement mode, the HDC1000 acquires the configured measurements and sets the RDY line, routed to the INT pin of the mikroBUS™ socket, to a low logic state, indicating that the measurement process is complete. 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. However, the Click board™ 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 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 HDC1000 Click driver.
Key functions:
hdc1000_default_cfg- This function executes default configuration for HDC1000 Clickhdc1000_get_temperature_data- This function gets temperature data from the HDC1000 sensorhdc1000_get_humidity_data- This function gets humidity data from the HDC1000 sensor
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 HDC1000 Click example
*
* # Description
* Demo application code is used for measuring temperature and humidity.
*
* The demo application is composed of two sections :
*
* ## Application Init
* AppInit is used for Logger and Click initialization.
*
* ## Application Task
* This is an example which demonstrates the usage of HDC1000 Click board.
* HDC1000 measure temperature and humidity, and calculate dewpoint value from the HDC1000 sensor.
*
* \author Mihajlo Djordevic
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "hdc1000.h"
// ------------------------------------------------------------------ VARIABLES
static hdc1000_t hdc1000;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
hdc1000_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.
hdc1000_cfg_setup( &cfg );
HDC1000_MAP_MIKROBUS( cfg, MIKROBUS_1 );
hdc1000_init( &hdc1000, &cfg );
log_printf( &logger, "-- Configurating --\r\n" );
hdc1000_default_cfg( &hdc1000 );
Delay_ms ( 100 );
log_printf( &logger, "-- Start measurement --\r\n" );
log_printf( &logger, "-----------------------\r\n" );
}
void application_task ( void )
{
float humidity;
float temperature;
temperature = hdc1000_get_temperature_data( &hdc1000 );
log_printf( &logger, " Temperature : %0.2f degC\r\n", temperature );
humidity = hdc1000_get_humidity_data( &hdc1000 );
log_printf( &logger, " Humidity : %0.2f %%\r\n", humidity );
log_printf( &logger, "-----------------------\r\n" );
Delay_ms ( 1000 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
