Our temperature monitoring solution is your answer to maintaining precise and consistent temperatures for industrial processes and manufacturing
A
A
Hardware Overview
How does it work?
Thermo 16 Click is based on the TMP235, a high-accuracy temperature sensor IC Texas Instruments. The Click board™ itself has a reasonably small number of components because most of the measurement circuitry is already integrated on the TMP235 sensor. The TMP23X devices are a family of precision CMOS integrated-circuit linear analog temperature sensors with an output voltage proportional to temperature engineers can use in multiple analog temperature sensing applications. The TMP235 temperature sensor have an accuracy from 0°C to 70°C of ±1.25°C and provides a positive slope output of 10 mV/°C over the full –40°C to
+150°C temperature range. It is worth to mention that the TMP235 has extremely low power consumption - 9 μA (Typical). This makes Thermo 16 click a perfect solution for the development of the IoT, wearable and portable applications, logging devices, industrial and health-related time metering applications, and all the other applications that require an accurate temperature measurement for their operation. An analog signal from the thermal sensor, from Vout pin is routed to the AN pin of the mikroBUS™ socket. On the path from the sensor to the mikroBUS™ socket, R2 and C1 are forming the RC filter. R2 is 0 ohm by default, but the user can
increase the resistance in order to find a perfect match for desired purpose. Note that higher resistance may help filter any noise in signal, but may also increase the sensor response time, so when tuning the RC filter, it is crucial to find the ideal balance between these two. The TMP235 operates at power supply range from 2.3 V to 5.5 V. Thus, Thermo 16 click has the power supply selection jumper onboard, named VCC SEL. That way, the user can switch between 3.3V and 5V for sensor power supply.
Features overview
Development board
Nucleo-144 with STM32F413ZH MCU board offers an accessible and adaptable avenue for users to explore new ideas and construct prototypes. It allows users to tailor their experience by selecting from a range of performance and power consumption features offered by the STM32 microcontroller. With compatible boards, the
internal or external SMPS dramatically decreases power usage in Run mode. Including the ST Zio connector, expanding ARDUINO Uno V3 connectivity, and ST morpho headers facilitate easy expansion of the Nucleo open development platform. The integrated ST-LINK debugger/programmer enhances convenience by
eliminating the need for a separate probe. Moreover, the board is accompanied by comprehensive free software libraries and examples within the STM32Cube MCU Package, further enhancing its utility and value.
Microcontroller Overview
MCU Card / MCU

Architecture
ARM Cortex-M4
MCU Memory (KB)
1536
Silicon Vendor
STMicroelectronics
Pin count
144
RAM (Bytes)
327680
You complete me!
Accessories
Click Shield for Nucleo-144 comes equipped with four mikroBUS™ sockets, with one in the form of a Shuttle connector, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-144 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. Featuring an ARM Cortex-M microcontroller, 144 pins, and Arduino™ compatibility, the STM32 Nucleo-144 board offers limitless possibilities for prototyping and creating diverse applications. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-144 board out of the box, with an additional USB cable connected to the USB mini port on the board. Simplify your project development with the integrated ST-Link debugger and unleash creativity using the extensive I/O options and expansion capabilities. 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-144 board with our Click Shield for Nucleo-144, 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
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 Thermo 16 Click driver.
Key functions:
thermo16_get_temperature
- Temperature function.thermo16_generic_read
- Generic read function.
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 Thermo16 Click example
*
* # Description
* This demo-app shows the temperature measurement procedure using Thermo 16 Click.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Configuring Clicks and log objects.
*
* ## Application Task
* Reads ambient temperature data and this data logs to USBUART every 1500ms.
*
* \author Katarina Perendic
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "thermo16.h"
// ------------------------------------------------------------------ VARIABLES
static thermo16_t thermo16;
static log_t logger;
float temp;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
thermo16_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.
thermo16_cfg_setup( &cfg );
THERMO16_MAP_MIKROBUS( cfg, MIKROBUS_1 );
thermo16_init( &thermo16, &cfg );
}
void application_task ( void )
{
// Task implementation.
temp = thermo16_get_temperature ( &thermo16, THERMO16_TEMP_IN_CELSIUS );
log_printf( &logger, "** Temperature : %.2f C \r\n", temp );
Delay_ms ( 500 );
}
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