Capture the essence of your environment with HDC1080 and ATmega1284
Measuring more than just temperature and humidity
Published Nov 08, 2023
Click board™
Temp&Hum 11 Click
Dev Board
EasyAVR v7
Compiler
NECTO Studio
MCU
ATmega1284
The future of climate control is here, and we invite you to be part of it today with our advanced technology.
A
A
Hardware Overview
How does it work?
Temp&Hum 11 Click is based on the HDC1080, 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 14-bit ADC section, which can be set to sample measurements with the resolution of 8, 11 or 14 bits, based on the measurement (integration) 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 HDC1080 datasheet so that the final temperature or relative humidity data can be calculated. HDC1080 IC is a very low power consuming device and it can work in two modes: sleep and active (measurement) mode. The device enters the sleep the mode as soon as possible, in order to save power. This makes the HDC1080 suitable to be used for battery-powered applications. In these applications, the HDC1080 can spend most of the time in the sleep mode that has a typical current consumption in the magnitude of nanoamperes. The measurement is triggered after the command is sent over the I2C interface. As soon as the single measurement is finished, the device falls back to a sleep mode. The host should wait for the acquisition to be completed before reading the output registers. However, the Click board™ is
supported by a library of mikroSDK compatible functions, which simplify the development. The heating element can be used to reduce the offset which is a common problem for most RH sensors. It also helps with the condensation, evaporating the excess moisture. The current consumption is increased when the heater is on. It can be enabled by configuring the appropriate register, but it won't be actually activated until a measurement is triggered. Therefore, to increase its temperature, measurement frequency should be increased. The Click board™ can be interfaced with both 3.3V and 5V MCUs without the need for any external components. Thanks to the HDC1080 and its support for a wide supply voltage range, the Click board™ can be simply used with any MCU that supports I2C communication.
Features overview
Development board
EasyAVR v7 is the seventh generation of AVR development boards specially designed for the needs of rapid development of embedded applications. It supports a wide range of 16-bit AVR microcontrollers from Microchip and has a broad set of unique functions, such as a powerful onboard mikroProg programmer and In-Circuit debugger over USB. The development board is well organized and designed so that the end-user has all the necessary elements in one place, such as switches, buttons, indicators, connectors, and others. With four different connectors for each port, EasyAVR v7 allows you to connect accessory boards, sensors, and custom electronics more
efficiently than ever. Each part of the EasyAVR v7 development board contains the components necessary for the most efficient operation of the same board. An integrated mikroProg, a fast USB 2.0 programmer with mikroICD hardware In-Circuit Debugger, offers many valuable programming/debugging options and seamless integration with the Mikroe software environment. Besides it also includes a clean and regulated power supply block for the development board. It can use a wide range of external power sources, including an external 12V power supply, 7-12V AC or 9-15V DC via DC connector/screw terminals, and a power source via the USB Type-B (USB-B)
connector. Communication options such as USB-UART and RS-232 are also included, alongside the well-established mikroBUS™ standard, three display options (7-segment, graphical, and character-based LCD), and several different DIP sockets which cover a wide range of 16-bit AVR MCUs. EasyAVR v7 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.
Microcontroller Overview
MCU Card / MCU
Architecture
AVR
MCU Memory (KB)
128
Silicon Vendor
Microchip
Pin count
40
RAM (Bytes)
16384
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 EasyAVR v7 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 11 Click driver.
Key functions:
temphum11_get_temperature- This function reads temperature data in desired unit.temphum11_get_humidity- This function reads relative huminidy datatemphum11_read_data- This function reads data from the desired register.
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 TempHum11 Click example
*
* # Description
* This click has two sensors which can be set to sample measurements with the resolution
* of 8, 11 or 14 bits, based on the measurement time. Calibration coefficients that are applied
* to the measured value and the results are stored in the MSB/LSB format, on the output registers.
* These values are then used in formulas so that the final temperature or relative humidity data can be calculated.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes driver init, test comunication and configuration chip for measurement.
*
* ## Application Task
* Reads Temperature and Humidity data. This data logs to USBUART every 1500ms.
*
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "temphum11.h"
// ------------------------------------------------------------------ VARIABLES
static temphum11_t temphum11;
static log_t logger;
static float temperature;
static float humidity;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
temphum11_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.
temphum11_cfg_setup( &cfg );
TEMPHUM11_MAP_MIKROBUS( cfg, MIKROBUS_1 );
temphum11_init( &temphum11, &cfg );
// Test comunication
if ( temphum11_read_data( &temphum11, TEMPHUM11_REG_DEVICE_ID ) == TEMPHUM11_DEVICE_ID )
{
log_printf( &logger, "--- Comunication OK!!! ---\r\n" );
}
else
{
log_printf( &logger, "--- Comunication ERROR!!! ---\r\n" );
for ( ; ; );
}
temphum11_default_cfg( &temphum11 );
log_printf( &logger, "--- Start measurement --- \r\n" );
Delay_ms( 500 );
}
void application_task ( void )
{
temperature = temphum11_get_temperature( &temphum11, TEMPHUM11_TEMP_IN_CELSIUS );
log_printf( &logger, " Temperature : %.2f\r\n", temperature );
humidity = temphum11_get_humidity( &temphum11 );
log_printf( &logger, " Humidity : %.2f\r\n", humidity );
log_printf( &logger, "-----------------\r\n" );
Delay_ms( 1500 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
