Stop electronics overheating! Add efficient cooling with this mini air conditioner.
A
A
Hardware Overview
How does it work?
Cooler Click is based on the DRV8213, an advanced brushless DC motor driver from Texas Instruments, as its core component. This innovative board integrates a miniature temperature sensor, TMP007, and a cooling fan, MF25060V2-1000U-A99, right on its surface, making it a ready-to-go cooling solution. It's perfectly suited for use in environments prone to overheating, such as server rack cooling, embedded systems and IoT devices, development board prototyping, gaming consoles and PC cooling, automotive electronics, medical equipment cooling, or similar applications, where continuous cooling is essential. The DRV8213 is a comprehensive motor driver featuring an integrated full-bridge driver with current sensing and regulation capabilities and a unique current sense output. It's designed for efficiency, using a 2-pin PWM interface for motor speed control through the
IN1 and IN2 pins on the mikroBUS™ socket, covering a wide PWM frequency range from 0 to 100kHz. Notably, its auto-sleep mode reduces the need for additional GPIO connections for sleep or turn-off functions by automatically entering a low-power mode when not in use. The DRV8213 is also enriched with several protection features, such as undervoltage lockout, overcurrent protection, and overtemperature shutdown, ensuring reliable operation under various conditions. The TMP007 sensor, another onboard component from Texas Instruments, employs infrared thermopile technology to measure temperatures without direct contact with the object. This capability accurately monitors the surrounding temperature where the Click board™ is placed. The sensor's output is digitized and processed along with the die temperature to compute the object temperature. It
uses an I2C interface for communication with the host MCU and an alert function via the ALR pin of the mikroBUS™ socket for temperature exceedance notifications. Complementing these components is the MF25060V2-1000U-A99 fan, a high-performance cooling fan operating on a 5VDC supply capable of reaching speeds up to 10,000 RPM. This fan is essential for dissipating heat efficiently, ensuring the system remains cool under operation. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC 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
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 via Debug Mode
1. Once the code example is loaded, pressing the "DEBUG" button initiates the build process, programs it on the created setup, and enters Debug mode.
2. After the programming is completed, a header with buttons for various actions within the IDE becomes visible. Clicking the green "PLAY" button starts reading the results achieved with the Click board™. The achieved results are displayed in the Application Output tab.
Software Support
Library Description
This library contains API for Cooler Click driver.
Key functions:
cooler_get_object_temperature
- This function reads the object's temperature data in degrees Celsius.cooler_set_out_state
- This function controls the operation of the cooler - on/off.
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 Cooler Click Example.
*
* # Description
* This example demonstrates the use of the Cooler click board
* by reading the target object temperature and controlling the cooler.
*
* The demo application is composed of two sections :
*
* ## Application Init
* The initialization of the I2C module, log UART, and additional pins.
* After the driver init, the app executes a default configuration.
*
* ## Application Task
* The demo application measures the temperature of the target object in degrees Celsius
* and enables a cooler if the temperature exceeds the temperature high limit value.
* Results are being sent to the UART Terminal, where you can track their changes.
*
* @author Nenad Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "cooler.h"
// Object temperature high limit
#define COOLER_TEMP_HIGH_LIMIT 30.0
static cooler_t cooler; /**< Cooler Click driver object. */
static log_t logger; /**< Logger object. */
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
cooler_cfg_t cooler_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.
cooler_cfg_setup( &cooler_cfg );
COOLER_MAP_MIKROBUS( cooler_cfg, MIKROBUS_1 );
err_t init_flag = cooler_init( &cooler, &cooler_cfg );
if ( ( ADC_ERROR == init_flag ) || ( I2C_MASTER_ERROR == init_flag ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( COOLER_ERROR == cooler_default_cfg ( &cooler ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
float temperature = 0;
if ( COOLER_OK == cooler_get_object_temperature( &cooler, &temperature ) )
{
log_printf( &logger, " Temperature: %.2f degC\r\n", temperature );
log_printf( &logger, " Cooler: " );
if ( COOLER_TEMP_HIGH_LIMIT < temperature )
{
if ( COOLER_OK == cooler_set_out_state( &cooler, COOLER_ENABLE ) )
{
log_printf( &logger, " Enabled.\r\n\n" );
}
}
else
{
if ( COOLER_OK == cooler_set_out_state( &cooler, COOLER_DISABLE ) )
{
log_printf( &logger, " Disabled.\r\n\n" );
}
}
}
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