Experience the power of high-accuracy temperature sensing technology for better performance and energy efficiency
A
A
Hardware Overview
How does it work?
Thermo 28 Click is based on the AS6221, a digital temperature sensor from ams AG with increased reliability and improved accuracy specifications optimal for thermal management and protection applications. It integrates a digital temperature sensor with a SI bipolar transistor as a sensing element, a high-resolution analog-to-digital converter (ADC), a data processing circuit, and serial interface logic functions in one package. The voltage is digitized and converted to a 16-bit temperature result in degrees Celsius, giving a fully calibrated digital output
with outstanding accuracy of up to ±0.9°C typical over a temperature range of 20°C to 42°C. This Click board™ communicates with MCU using the standard I2C 2-Wire interface to read data and configure settings, supporting a high clock frequency operation. It also allows the choice of the four least significant bits of its I2C slave address by positioning the SMD jumper labeled ADDR SEL to an appropriate position providing the user with a selection of four slave addresses. In addition to communication signals, the AS6221 also possesses an additional interrupt alert signal,
routed on the INT pin of the mikroBUS™ socket, indicating when a specific interrupt event occurs that depends on the value of the temperature reading relative to programmable limits. This Click board™ can only be operated with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. However, the Click board™ comes equipped with a library containing functions and an example code that can be used as a reference for further development.
![Thermo 28 Click top side image](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1edddec6-6ca5-689e-bdff-02420a0004ce/01-thermo-28-click-front.png)
![Thermo 28 Click lateral side image](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1edddec7-2b2c-6272-b134-02420a0004ce/02-thermo-28-click-side.png)
![Thermo 28 Click bottom side image](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1edddec7-dcd9-6a88-9cd6-02420a0004ce/03-thermo-28-click-back.png)
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-stm32f401rb.png)
Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
128
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
65536
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
![Thermo 28 Click Schematic schematic](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1ee790a4-64b9-6eac-9005-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 28 Click driver.
Key functions:
thermo28_get_temperature
Thermo 28 get temperature function.thermo28_set_config
Thermo 28 set configuration function.thermo28_set_continuous_conversion
Thermo 28 set continuous conversion 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 main.c
* @brief Thermo 28 Click example
*
* # Description
* This example demonstrates the use of Thermo 28 click board™
* by reading and displaying the temperature measurements.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration.
*
* ## Application Task
* This is an example that shows the use of a Thermo 28 click board™.
* Reads the temperature measurement in degree Celsius and displays the results.
* Results are being sent to the Usart Terminal where you can track their changes.
*
* @author Nenad Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "thermo28.h"
static thermo28_t thermo28;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
thermo28_cfg_t thermo28_cfg; /**< Click config object. */
/**
* 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.
thermo28_cfg_setup( &thermo28_cfg );
THERMO28_MAP_MIKROBUS( thermo28_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == thermo28_init( &thermo28, &thermo28_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
Delay_ms( 100 );
if ( THERMO28_ERROR == thermo28_default_cfg ( &thermo28 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
Delay_ms( 100 );
}
void application_task ( void )
{
float temperature;
if ( THERMO28_OK == thermo28_get_temperature( &thermo28, &temperature ) )
{
log_printf( &logger, " Temperature [degC]: %.2f \r\n", temperature );
Delay_ms( 1000 );
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END