Unlock the full potential of any battery with SPV1050 and STM32F091RC
Embrace the future of battery charging
Published Feb 26, 2024
Click board™
Peltier Click
Dev. board
Nucleo-64 with STM32F091RC MCU
Compiler
NECTO Studio
MCU
STM32F091RC
Charge any battery type, including lithium-based, solid-state thin film and super-capacitor
A
A
Hardware Overview
How does it work?
Peltier Click is based on the SPV1050, an ultralow power energy harvester and battery charger from STMicroelectronics that can charge lithium-based batteries. A thermoelectric harvester produces green energy for energy harvesting with many advantages: maintenance-free because of the use of a highly reliable and compact solid-state device; silent and quiet; highly efficient in environmental terms because the heat is harvested from waste heat sources and converted into electricity. Because of this feature, the Peltier click can be used for various applications such as WSN, HVAC, building and home automation, industrial control, remote metering, lighting, security, surveillance, and wearable and biomedical sensors. The SPV1050 is an ultralow power and high-efficiency energy harvester and battery charger, which implements the MPPT function and integrates the switching elements of a buck-boost converter. The SPV1050 device allows the charge of a lithium
battery by tightly monitoring the end-of-charge and the minimum battery voltage to avoid over-discharge and preserve the battery life. The power manager is suitable for TEG harvesting sources, as it covers the input voltage range from 75 mV up to 18 V and guarantees high efficiency in both buck-boost and boost configurations. Furthermore, the SPV1050 device shows very high flexibility thanks to the trimming capability of the end-of-charge and undervoltage protection voltages. In such a way, any source and battery are matched. The MPPT is programmable by a resistor input divider and allows maximizing the source power under any temperature and irradiance condition. Some of the key features of the SPV1050 are its transformerless thermoelectric generators and PV modules energy harvester, high efficiency for any harvesting source, and up to 70 mA maximum battery charging current. It is a fully integrated buck-boost DC-DC converter with a
programmable MPPT by external resistors, 2.6 V to 5.3 V trimmable battery charge voltage level (± 1% accuracy), 2.2 V to 3.6 V trimmable battery discharge voltage level (± 1% accuracy) with two fully independent LDOs (1.8 V and 3.3 V output). The SPV1050 can turn LDO control pins on/off, and it has a battery disconnect function for battery protection while the battery is connected and ongoing charge logic open drain indication pins. The SPV1050 is an ultralow power energy harvester with an embedded MPPT algorithm, a battery charger, and a power manager designed for applications up to 400 mW. 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.
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.
Li-Polymer Battery is the ideal solution for devices that demand a dependable and long-lasting power supply while emphasizing mobility. Its compatibility with mikromedia boards ensures easy integration without additional modifications. With a voltage output of 3.7V, the battery meets the standard requirements of many electronic devices. Additionally, boasting a capacity of 2000mAh, it can store a substantial amount of energy, providing sustained power for extended periods. This feature minimizes the need for frequent recharging or replacement. Overall, the Li-Polymer Battery is a reliable and autonomous power source, ideally suited for devices requiring a stable and enduring energy solution. You can find a more extensive choice of Li-Polymer batteries in our offer.
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
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.
2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.
3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.
Software Support
Library Description
This library contains API for Peltier Click driver.
Key functions:
peltier_enable_ldo2- Enables LDO2 functionpeltier_disable_ldo2- Disables LDO2 functionpeltier_battery_charge- Check ongoing battery charge flag pin function
Open Source
Code example
The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.
/*!
* \file
* \brief Peltier Click example
*
* # Description
* This application is ultralow power energy harvester and battery charger.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes GPIO driver, disables both 1.8V and 3.3V outputs and starts write log.
*
* ## Application Task
* This example demonstrates the use of Peltier Click board by first enableing 1.8V output, second
by enableing 3.3V output, then enabling both outputs and finally disabling both outputs in 5 seconds intervals.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "peltier.h"
// ------------------------------------------------------------------ VARIABLES
static peltier_t peltier;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
peltier_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.
peltier_cfg_setup( &cfg );
PELTIER_MAP_MIKROBUS( cfg, MIKROBUS_1 );
peltier_init( &peltier, &cfg );
}
void application_task ( void )
{
log_printf( &logger, " 1.8V output \r\n" );
log_printf( &logger, "------------------\r\n" );
peltier_enable_ldo1( &peltier );
peltier_disable_ldo2( &peltier );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, " 3.3V output \r\n" );
log_printf( &logger, "------------------\r\n" );
peltier_disable_ldo1( &peltier );
peltier_enable_ldo2( &peltier );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, " Both outputs \r\n" );
log_printf( &logger, "------------------\r\n" );
peltier_enable_ldo1( &peltier );
peltier_enable_ldo2( &peltier );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, " Disable outputs \r\n" );
log_printf( &logger, "------------------\r\n" );
peltier_disable_ldo1( &peltier );
peltier_disable_ldo2( &peltier );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
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
