Our cutting-edge solution serves as a K-Type thermocouple probe interface, offering unparalleled accuracy and control for all your temperature measurement needs
A
A
Hardware Overview
How does it work?
Thermo K Click is based on the MCP9600, a thermocouple EMF to temperature converter from Microchip. This converter typically has an accuracy of ±0.5°C for thermocouple hot-junction with very good hot and cold-junctions resolution of +0.0625°C. It features four programmable temperature alert outputs that monitor hot or cold-junction temperature, detects rising or falling temperature, and has up to 255°C of programmable hysteresis. In addition, it comes with integrated cold-junction compensation, and the correction coefficients are derived from the NIST Institute database. The Delta-Sigma ADC converter can work in 12/14/16/18-bit selectable resolutions, which is useful for detecting fast temperature transients. The MCP9600 provides
integrated thermocouple open-circuit and short-circuit detection, with an alert signal when the thermocouple wire is broken or disconnected, a feature that comes in handy. In the same way, the alert signal is asserted if the thermocouple wire is shorted to the ground or power. Regarding the alert, the MCP9600 will also notify the wrong polarity either in the Comparator or Interrupt modes. The Comparator mode is helpful for thermostat-type applications to switch fan controllers, LEDs, and more, while the Interrupt mode is more convenient for microprocessor-based systems. The low-power segment comes in Shutdown mode and Burst mode with 1 up to 128 temperature samples. The Thermo K Click uses a standard 2-Wire I2C interface to communicate
with the host MCU, supporting standard 100KHz frequency. The four alert outputs from the MCP9600 can be observed over the AL1, AL2, AL3, and AL4 pins of the mikroBUS™ socket. These are programmable push-pull outputs. The Thermo K Click comes with a PCC-SMP connector for connecting an appropriate probe that MIKROE offers, the K-type Glass Braid Insulated probe. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the PWR 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
Fusion for ARM 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 ARM® Cortex®-M based MCUs regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over WiFi. 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 ARM v8 provides a fluid and immersive working experience, allowing access anywhere and under any
circumstances at any time. Each part of the Fusion for ARM 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 ARM 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
![default](https://cdn.mikroe.com/rent-a-product/request-setup/mcu-cards/mcu-card-29-for-stm32-stm32f412re.png)
Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
512
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
262144
You complete me!
Accessories
The Type-K thermocouple, equipped with glass braid insulation, is a versatile tool designed for precision temperature measurements, particularly in high-temperature environments. With a calibrated Type-K configuration and a 24 AWG gage wire spanning 2 meters, this probe is engineered to provide reliable readings. Its operational temperature range extends to 480°C (900°F), making it suitable for demanding applications. The glass braid insulation ensures durability and stability during measurements, and the connector body can withstand temperatures up to 220°C (425°F). The Type-K thermocouple probe features a PCC-SMP connector at its end, which offers compatibility with THERMO Click and Thermo K Click boards. This connectivity makes it a valuable tool for various industrial and scientific settings, where precision and reliability in temperature monitoring are essential.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
![Thermo K Click Schematic schematic](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1ee790df-20f1-63f6-8272-0242ac120009/schematic.webp)
Step by step
Project assembly
Track your results in real time
Application Output
After pressing the "FLASH" button on the left-side panel, it is necessary to open the UART terminal to display the achieved results. By clicking on the Tools icon in the right-hand panel, multiple different functions are displayed, among which is the UART Terminal. Click on the offered "UART Terminal" icon.
![UART Application Output Step 1](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703a-40a0-6b58-88de-02420a00029a/UART-AO-Step-1.jpg)
Once the UART terminal is opened, the window takes on a new form. At the top of the tab are two buttons, one for adjusting the parameters of the UART terminal and the other for connecting the UART terminal. The tab's lower part is reserved for displaying the achieved results. Before connecting, the terminal has a Disconnected status, indicating that the terminal is not yet active. Before connecting, it is necessary to check the set parameters of the UART terminal. Click on the "OPTIONS" button.
![UART Application Output Step 2](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703a-eb29-62fa-ba91-02420a00029a/UART-AO-Step-2.jpg)
In the newly opened UART Terminal Options field, we check if the terminal settings are correct, such as the set port and the Baud rate of UART communication. If the data is not displayed properly, it is possible that the Baud rate value is not set correctly and needs to be adjusted to 115200. If all the parameters are set correctly, click on "CONFIGURE".
![UART Application Output Step 3](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703b-7543-6fbc-9c69-0242ac120003/UART-AO-Step-3.jpg)
The next step is to click on the "CONNECT" button, after which the terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.
![UART Application Output Step 4](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703c-068c-66a4-a4fc-0242ac120003/UART-AO-Step-4.jpg)
Software Support
Library Description
This library contains API for Thermo K Click driver.
Key functions:
thermok_get_temperature
- Temperature datathermok_get_status
- Get statusthermok_get_device_info
- Functions for read device info
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 ThermoK Click example
*
* # Description
* Demo application shows basic temperature reading using Thermo K click.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Configuring clicks and log objects.
* Reads the device ID and also checks the click and MCU communication.
*
* ## Application Task
* Reads Temperature data(Type K probe) and this data logs to USBUART every 500ms.
*
* \author Katarina Perendic
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "thermok.h"
// ------------------------------------------------------------------ VARIABLES
static thermok_t thermok;
static log_t logger;
static uint16_t device_info;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
thermok_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.
thermok_cfg_setup( &cfg );
THERMOK_MAP_MIKROBUS( cfg, MIKROBUS_1 );
thermok_init( &thermok, &cfg );
// Check communication and reads device ID
device_info = thermok_get_device_info( &thermok );
if ( ( device_info >> 8 ) == THERMOK_DEVICE_ID )
{
log_info(&logger, "---- Communication OK!!! ----" );
}
else
{
log_info(&logger, "---- Communication ERROR!!! ----" );
for ( ; ; );
}
Delay_1sec( );
}
void application_task ( void )
{
float temperature;
// Task implementation.
temperature = thermok_get_temperature( &thermok,
THERMOK_REG_HOT_JUNCTION_TEMP_THR,
THERMOK_TEMP_IN_CELSIUS );
log_printf( &logger, ">> Temperature is %.2f C\r\n", temperature );
Delay_ms( 1500 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END