Beginner
10 min

Experience instant comfort and get instant temperature results with ADT7422 and MK64FN1M0VDC12

The gold standard in temperature sensing

Surface temp 2 Click with Clicker 2 for Kinetis

Published Nov 11, 2023

Click board™

Surface temp 2 Click

Development board

Clicker 2 for Kinetis

Compiler

NECTO Studio

MCU

MK64FN1M0VDC12

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.

Surface temp 2 Click hardware overview image

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.

Clicker 2 for Kinetis dimensions image

Microcontroller Overview

MCU Card / MCU

default

Architecture

ARM Cortex-M4

MCU Memory (KB)

1024

Silicon Vendor

NXP

Pin count

121

RAM (Bytes)

262144

Used MCU Pins

mikroBUS™ mapper

NC
NC
AN
NC
NC
RST
NC
NC
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
Critical Overtemperature Indicator
PA10
PWM
Over/Undertemperature Indicator
PB13
INT
NC
NC
TX
NC
NC
RX
I2C Clock
PD8
SCL
I2C Data
PD9
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Schematic

Surface temp 2 Click Schematic schematic

Step by step

Project assembly

Clicker 2 for PIC32MZ front image hardware assembly

Start by selecting your development board and Click board™. Begin with the Clicker 2 for Kinetis as your development board.

Clicker 2 for PIC32MZ front image hardware assembly
Buck 22 Click front image hardware assembly
Prog-cut hardware assembly
Micro B Connector Clicker 2 - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
Necto image step 5 hardware assembly
Necto image step 6 hardware assembly
Flip&Click PIC32MZ MCU step hardware assembly
Necto No Display image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Debug Image Necto Step hardware assembly

Track your results in real time

Application Output

After loading the code example, pressing the "DEBUG" button builds and programs it on the selected setup.

Application Output Step 1

After programming is completed, a header with buttons for various actions available in the IDE appears. By clicking the green "PLAY "button, we start reading the results achieved with Click board™.

Application Output Step 3

Upon completion of programming, the Application Output tab is automatically opened, where the achieved result can be read. In case of an inability to perform the Debug function, check if a proper connection between the MCU used by the setup and the CODEGRIP programmer has been established. A detailed explanation of the CODEGRIP-board connection can be found in the CODEGRIP User Manual. Please find it in the RESOURCES section.

Application Output Step 4

Software Support

Library Description

This library contains API for Surface temp 2 Click driver.

Key functions:

  • surfacetemp2_get_temperature - Get Temperature function

  • surfacetemp2_set_crit_trsh - Set Critical Temperature Threshold function

  • surfacetemp2_get_ct_pin - Get CT pin state function

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 
 * \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 );
}

void main ( void )
{
    application_init( );

    for ( ; ; )
    {
        application_task( );
    }
}

// ------------------------------------------------------------------------ END

Additional Support

Resources