Our versatile temperature measurement solution is designed to deliver accurate temperature data across a wide range of applications, giving you the confidence and precision you need
A
A
Hardware Overview
How does it work?
Thermo 4 Click is based on the LM75A, a digital temperature sensor and thermal watchdog from NXP Semiconductor. It is a temperature-to-digital converter that uses an on-chip band gap temperature sensor and Sigma-delta analog-to-digital conversion technique. It is also a thermal detector that provides an overtemperature detection output. The sensor can be configured for different operation conditions, in normal mode to periodically monitor the ambient temperature or in shutdown mode to minimize power consumption. In normal mode, the
temperature-to-digital conversion is executed every 100ms, while in shutdown mode, the device becomes idle, still holding the last temperature readings. Thermo 4 Click uses a standard 2-Wire I2C interface to communicate with the host MCU. The I2C address can be changed over the ADDR SEL jumper, with 0 positions set by default. The LM75A sensor has an overtemperature shutdown output pin that can interrupt the host MCU over the INT pin. On this output pin, the sensor can work in comparator mode or interrupt mode. In comparator mode, LM75A behaves like a
thermostat, while in interrupt mode, the output is used for thermal interruption. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. Also, this Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used as a reference for further development.
Features overview
Development board
Curiosity PIC32 MZ EF development board is a fully integrated 32-bit development platform featuring the high-performance PIC32MZ EF Series (PIC32MZ2048EFM) that has a 2MB Flash, 512KB RAM, integrated FPU, Crypto accelerator, and excellent connectivity options. It includes an integrated programmer and debugger, requiring no additional hardware. Users can expand
functionality through MIKROE mikroBUS™ Click™ adapter boards, add Ethernet connectivity with the Microchip PHY daughter board, add WiFi connectivity capability using the Microchip expansions boards, and add audio input and output capability with Microchip audio daughter boards. These boards are fully integrated into PIC32’s powerful software framework, MPLAB Harmony,
which provides a flexible and modular interface to application development a rich set of inter-operable software stacks (TCP-IP, USB), and easy-to-use features. The Curiosity PIC32 MZ EF development board offers expansion capabilities making it an excellent choice for a rapid prototyping board in Connectivity, IOT, and general-purpose applications.
Microcontroller Overview
MCU Card / MCU

Architecture
PIC32
MCU Memory (KB)
2048
Silicon Vendor
Microchip
Pin count
100
RAM (Bytes)
524288
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 4 Click driver.
Key functions:
thermo4_read_temperature_c
- This function reads temperature values in Celsius format.thermo4_read_temperature_f
- This function reads temperature values in Farenheit format.thermo4_reset
- This function is used to reset the 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 Thermo4 Click example
*
* # Description
* This demo example returns temperature values in three different format.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initalizes I2C driver and makes an initial log.
*
* ## Application Task
* Returns temperature values from the sensor.
*
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "thermo4.h"
// ------------------------------------------------------------------ VARIABLES
static thermo4_t thermo4;
static log_t logger;
static float temp_in_celsius;
static float temp_in_faren;
static float temp_in_kelvin;
static char txt [ 50 ];
static uint16_t inter_temp_data;
// ------------------------------------------------------- ADDITIONAL FUNCTIONS
void log_display( float value )
{
inter_temp_data = ( uint16_t ) value;
log_printf(&logger, "%s .", txt);
inter_temp_data = ( uint16_t ) ( value * 100.0 );
log_printf(&logger, "%s", txt);
}
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
thermo4_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.
thermo4_cfg_setup( &cfg );
THERMO4_MAP_MIKROBUS( cfg, MIKROBUS_1 );
thermo4_init( &thermo4, &cfg );
log_info( &logger, "---- Application Init ----" );
}
void application_task ( void )
{
temp_in_celsius = thermo4_read_temperature_c( &thermo4 );
temp_in_faren = thermo4_read_temperature_f( &thermo4 );
temp_in_kelvin = thermo4_read_temperature_k( &thermo4 );
log_printf( &logger, " Temperature celsius : %f C\r\n ", temp_in_celsius );
log_printf( &logger, " Temperature farenheit : %f F\r\n ", temp_in_faren );
log_printf( &logger, " Temperature kelvin : %f K\r\n ", temp_in_kelvin );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END