Our temperature measurement solution offers precision beyond measure, ensuring your processes run smoothly and efficiently.
A
A
Hardware Overview
How does it work?
Thermo 8 Click is based on the MCP9808, a digital temperature sensor with ±0.5 °C maximum accuracy, from Microchip. The MCP9808 uses a bandgap type temperature sensor, which is converted by a delta-sigma A/D converter to a digital value, available via the I2C interface. The user has the ability to select the resolution of the measurement, ranging from ±0.5°C, down to ±0.0625°C. The resolution is determined by the internal sample averaging. Therefore, a higher resolution results in longer conversion times. For example, the conversion time for the resolution of ±0.0625 °C is 250ms, while the conversion time for the resolution of ±0.5 °C is only 30ms. The temperature is stored to an output register after the conversion is done. This register is double-buffered, which means that the new data can be written in the background, while the host microcontroller (MCU) performs a reading of the current value. The thermal data is stored as a 13-bit value, in 2's complement format. Along with the thermal data, this register also contains bits that indicate a thermal alert condition. There are three possible alert conditions. The extensive alerting engine is one of the key features of the MCP9808.
The ALERT pin of the MCP9808 is routed to the INT pin of the mikroBUS™, which is labeled as ALE on this Click board™. It can be programmed to be asserted to a HIGH
or to a LOW logic level. However, the Click board™ uses the pull-up resistor to predetermine its idle state to a logic HIGH level. Depending on the application, this pin can be set to operate as a typical interrupt pin, or as a comparator. When set to operate as the interrupt, this pin will be latched until the host MCU sets the Interrupt Clear bit (bit 5 of the CONFIG register, more information in the MCP9808 datasheet). When set to operate as the comparator, the ALERT pin will be asserted only while the alert condition exists. As soon as the temperature falls within the programmed limits, the pin will be de-asserted. While the interrupt mode is useful when an MCU is used to control some process, having to acknowledge the action, the comparator mode can be used to directly control a device, such as a cooling fan in electronic equipment, or PC peripheral. The alert thresholds can be programmed by the user. There are dedicated registers, where the user can enter the threshold value, along with the sign. The value should be entered in 2's complement format. There is also a dedicated register where the thermal hysteresis can be entered, reducing the probability of false reporting when the temperature drifts near the threshold value. The hysteresis can be set in the range from 0 °C up to +6 °C, in four discrete steps. Besides the threshold registers,
there is another register which contains the value used to trigger a special alert mode: the critical temperature mode. This mode will force the device to work in the comparator mode, as long as the critical temperature condition exists. The same hysteresis value is applied to this threshold, reducing the probability of false reports. For more details about the alert modes, please refer to the datasheet of the MCP9808s. However, the Click board™ comes with the mikroSDK compliant library of functions, which simplify the firmware development by encapsulating all the conversion and initialization routines required by the MCP9808 IC. The MCP9808 also supports a SHUTDOWN mode, which reduces the power consumption by turning off the sensor. However, the last conversion is still available in the output register. Even the alert pin state remains unaffected when the SHUTDOWN mode is engaged. The I2C slave address of the device can be selected by switching a group of SMD jumpers, labeled as ADDR SEL. Each jumper will set the appropriate LSB of the device to either logic 0 or logic 1, determining the final I2C slave address. The power supply voltage can also be set by an SMD jumper labeled as VCC SEL, between 3.3V and 5V. This will also set the logic voltage level of the Click board™.
Features overview
Development board
Clicker 2 for Kinetis is a compact starter development board that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit ARM Cortex-M4F microcontroller, the MK64FN1M0VDC12 from NXP Semiconductors, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a JTAG programmer connector, and two 26-pin headers for interfacing with external electronics. Its compact design with clear and easily recognizable silkscreen markings allows you to build gadgets with unique functionalities and
features quickly. Each part of the Clicker 2 for Kinetis development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the Clicker 2 for Kinetis programming method, using a USB HID mikroBootloader or an external mikroProg connector for Kinetis programmer, the Clicker 2 board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Micro-B cable, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or
using a Li-Polymer battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several user-configurable buttons and LED indicators. Clicker 2 for Kinetis is an integral part of the Mikroe ecosystem, allowing you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping 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
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
NXP
Pin count
121
RAM (Bytes)
262144
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 8 Click driver.
Key functions:
thermo8_get_temperature
- This function returns the temperature value is deg Cthermo8_set_resolution
- This function sets the conversion resoult temperature step depending on the passed constant.thermo8_limit_set
-This function setting the temperature alarm levels for the lower, upper and critical alert levels.
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 Thermo8 Click example
*
* # Description
* This application measures temperature.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialize device.
*
* ## Application Task
* Wait for the interrupt pin to be triggered. When the
* measured temperature breaches the upper or lower limit the
* temperature value as well as the status of the breach is
* is shown on the serial port (UART).
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "thermo8.h"
// ------------------------------------------------------------------ VARIABLES
static thermo8_t thermo8;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
thermo8_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.
thermo8_cfg_setup( &cfg );
THERMO8_MAP_MIKROBUS( cfg, MIKROBUS_1 );
thermo8_init( &thermo8, &cfg );
Delay_ms( 100 );
thermo8_default_cfg( &thermo8 );
Delay_ms( 2000 );
}
void application_task ( void )
{
float t_data;
char alert;
char alert_on;
alert = thermo8_ale_get( &thermo8 );
if ( alert == 0 )
{
t_data = thermo8_get_temperature( &thermo8 );
alert_on = thermo8_get_alert_stat( &thermo8 );
}
if ( alert_on & THERMO8_TLOWER_REACHED )
{
log_printf( &logger, "Temperature under the low limit: %.2f C \r\n",
t_data );
}
if ( alert_on & THERMO8_TUPPER_REACHED )
{
log_printf( &logger, "Temperature over the high limit: %.2f C \r\n",
t_data );
}
Delay_ms( 2000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END