Achieve precise temperature monitoring with TMP75C and STM32F091RC
Hot or cold, we've got you covered!
Published Feb 26, 2024
Click board™
Thermo 22 Click
Dev Board
Nucleo-64 with STM32F091RC MCU
Compiler
NECTO Studio
MCU
STM32F091RC
Temperature sensing solution that effortlessly interfaces with your microcontroller, providing accurate temperature data for enhanced system performance
A
A
Hardware Overview
How does it work?
Thermo 22 Click is based on the TMP75C, a digital temperature sensor optimal for thermal management and protection applications from Texas Instruments. This temperature sensor is characterized by high accuracy; a temperature range of 0°C to +70°C provides typical ±0.25°C accuracy. The temperature sensing device for the TMP75C is the chip itself. A bipolar junction transistor inside the chip is used in a band-gap configuration to produce a voltage proportional to the chip temperature. The voltage is digitized and converted to a 12-bit temperature result in degrees Celsius, with a resolution of 0.0625°C. The default operational mode of the TMP75C is Continuous-Conversion mode (CC), where the ADC performs continuous temperature conversions and stores
each result in the temperature register, overwriting the result from the previous conversion. After the Power-Up cycle, the TMP75C immediately starts a conversion. Alongside CC mode, it also has Shutdown and One-shot modes, which reduce power consumption in the TMP75C when continuous temperature monitoring is not required. Thermo 22 Click communicates with MCU using the standard I2C 2-Wire interface to read data and configure settings. Besides, it also allows the choice of the least significant bit of its I2C slave address by positioning the SMD jumpers labeled ADDR SEL to an appropriate position marked as 0 and 1. This way, the TMP75C provides the opportunity of the eight possible different I2C addresses by positioning the SMD jumper to an appropriate position.
In addition to I2C communication, it uses an interrupt pin routed to the INT pin of the mikroBUS™ socket, representing the programmable temperature limit feature and alert that allows the sensor to operate as a stand-alone thermostat or an overtemperature alarm for system shutdown. This Click board™ can only be operated 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 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 Thermo 22 Click driver.
Key functions:
thermo22_read_temperatureThis function reads the temperature data in Celsius.thermo22_set_temperature_high_limitThis function sets the temperature high limit at which the overtemperature alert flag is being set.thermo22_get_int_pinThis function returns the INT pin logic state, which indicates the overtemperature alert.
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 Thermo22 Click example
*
* # Description
* This example demonstrates the use of Thermo 22 click board by reading and displaying
* the temperature measurements.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration which
* enables continuous conversation and sets the overtemperature limits to 35.0 Celsius.
*
* ## Application Task
* Reads the temperature measurement in Celsius and displays the results on the USB UART
* every 200ms approximately. It also checks the overtemperature alert indicator and displays
* an appropriate message if the indicator is active.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "thermo22.h"
static thermo22_t thermo22;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
thermo22_cfg_t thermo22_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.
thermo22_cfg_setup( &thermo22_cfg );
THERMO22_MAP_MIKROBUS( thermo22_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == thermo22_init( &thermo22, &thermo22_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( THERMO22_ERROR == thermo22_default_cfg ( &thermo22 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
float temperature;
if ( THERMO22_OK == thermo22_read_temperature ( &thermo22, &temperature ) )
{
log_printf ( &logger, " Temperature: %.2f C \r\n\n", temperature );
if ( !thermo22_get_int_pin ( &thermo22 ) )
{
log_printf ( &logger, " Over temperature alert! \r\n\n" );
}
Delay_ms ( 200 );
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
