Achieve optimal heat management of electronic systems with DRV8213 motor driver, MF25060V2-1000U-A99 cooling fan, and STM32F091RC
Compact cooling solution for managing heat in electronic systems
Published May 07, 2024
Click board™
Cooler Click
Dev Board
Nucleo-64 with STM32F091RC MCU
Compiler
NECTO Studio
MCU
STM32F091RC
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
Nucleo-64 with STM32F091RC MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M0
MCU Memory (KB)
256
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Nucleo-64 with STM32F091RC MCU as your development board.
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
