Experience the perfect blend of precision and performance with our temperature sensing solution, crafted to ASTM E1112 clinical thermometry standards.
A
A
Hardware Overview
How does it work?
Surface temp 2 Click is based on the ADT7422, a high-accuracy 16-bit digital temperature sensor with a programmable interrupt and critical temperature indicator from Analog Devices. The ADT7422 has high accuracy and linearity over the entire rated temperature range without needing correction or calibration by the user. Operating at 3.3V, the average supply current is typically 210 μA. The ADT7420 has a shutdown mode that powers down the device and offers a shutdown current of typically 2.0 μA at 3.3 V. The ADT7422 Digital Temperature Sensor is designed to meet the ASTM E1112 standard of clinical thermometry specification. This sensor is used in applications such as Vital Signs Monitoring (VSM), medical equipment, thermocouple cold junction compensation, and laser diode temperature control. This Click board™ has a sensing pad, which is thermally connected to an ADT7422 for temperature sensing. It uses a 16-bit ADC to
monitor and digitize the temperature to 0.0078°C of resolution. The ADC resolution, by default, is set to 13 bits (0.0625°C). An internal temperature sensor generates a voltage proportional to absolute temperature, which is compared to an internal voltage reference and input into a precision digital modulator. A Σ-Δ modulator digitizes the sensor output, the charge balance type ADC. This type of converter utilizes time-domain oversampling and a high-accuracy comparator to deliver 16 bits of resolution. Surface temp 2 Click communicates with MCU using the standard I2C 2-Wire interface with a maximum frequency of 400kHz. The ADT7422 has a 7-bit slave address with the first five MSBs fixed to 10010. The address pins A0 and A1 are programmed by the user and determine the value of the last two LSBs of the slave address, which can be selected by onboard SMD jumpers labeled as ADDR SEL, allowing selection of the slave
address LSBs. It also generates a programmable interrupt signal (over/under temperature indicator) routed on the INT pin and critical overtemperature indicator CT routed on the PWM pin of the mikroBUS™ socket. Those pins have two over/under temperature modes: Comparator and Interrupt mode. The Interrupt mode is the default overtemperature mode, which sets the INT pin high when the temperature exceeds the internally defined limit value, while in Comparator mode, the INT pin returns to an inactive state when the temperature drops below that limit value. The CT pin is activated if a critical overtemperature event occurs. This Click board™ can be operated only with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. Also, it 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
Fusion for TIVA v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different 32-bit ARM® Cortex®-M based MCUs from Texas Instruments, regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over a WiFi network. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, Fusion for TIVA v8 provides a fluid and immersive working experience, allowing access
anywhere and under any circumstances at any time. Each part of the Fusion for TIVA v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector.
Communication options such as USB-UART, USB HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. Fusion for TIVA v8 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

Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
Texas Instruments
Pin count
128
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 Surface temp 2 Click driver.
Key functions:
surfacetemp2_get_temperature
- Get Temperature functionsurfacetemp2_set_crit_trsh
- Set Critical Temperature Threshold functionsurfacetemp2_get_ct_pin
- Get CT pin state 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 SurfaceTemp2 Click example
*
* # Description
* This example demonstrates the use of Surface Temp 2 Click.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initalizes the driver and configures the Click board.
*
* ## Application Task
* Reads the temperature in Celsius and displays the value on the USB UART each second.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "surfacetemp2.h"
// ------------------------------------------------------------------ VARIABLES
static surfacetemp2_t surfacetemp2;
static log_t logger;
uint8_t setup_val;
float temperature;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
surfacetemp2_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.
surfacetemp2_cfg_setup( &cfg );
SURFACETEMP2_MAP_MIKROBUS( cfg, MIKROBUS_1 );
surfacetemp2_init( &surfacetemp2, &cfg );
setup_val = SURFACETEMP2_CFG_FLT_Q_4 | SURFACETEMP2_CFG_CT_MODE | SURFACETEMP2_CFG_RES_16;
surfacetemp2_setup ( &surfacetemp2, setup_val );
surfacetemp2_set_high_trsh( &surfacetemp2, 40.00 );
surfacetemp2_set_low_trsh( &surfacetemp2, 10.00 );
surfacetemp2_set_crit_trsh( &surfacetemp2, 70.00 );
surfacetemp2_set_hys_val( &surfacetemp2, 5 );
log_info( &logger, "---- Application Task ----" );
Delay_ms ( 1000 );
}
void application_task ( void )
{
temperature = surfacetemp2_get_temperature( &surfacetemp2 );
log_printf( &logger, " Temperature : %.2f C \r\n", temperature );
Delay_ms ( 1000 );
}
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
Additional Support
Resources
Category:Temperature & humidity