Maintain the charge balance between batteries
A
A
Hardware Overview
How does it work?
Balancer 4 Click is based on the MP2672A, a highly integrated and flexible switch-mode battery charger for two-cell Lithium-Ion batteries in series from Monolithic Power Systems (MPS). The MP2672A features a cell balance function that monitors the voltage across each cell and equalizes them if the difference exceeds the mismatch threshold. It features up to 2A of programmable charge current for batteries with two cells in series, alongside protections like battery temperature monitoring, programmable charging safety timer protection, JEITA-compliant battery NTC monitoring, cell over-voltage protection (OVP), thermal regulation, and thermal shutdown. The MP2672A has a narrow voltage DC (NVDC) power structure. It automatically detects the battery voltage and charges it in three phases: pre-charge, constant current, and voltage charge. With a deeply discharged battery, the MP2672A regulates the system output to a minimum voltage level, which powers the system
instantly while simultaneously charging the battery via integrated FET. It also offers flexible new charging cycle initiation compatible with Standalone mode and Host-control mode of operation selectable through an onboard switch labeled as HOST SEL. Diverse and robust protections include a thermal regulation loop to decrease the charge current if the junction temperature exceeds the thermal loop threshold and battery temperature protection compliant with JEITA standards. Other safety features include input over-voltage protection (OVP), battery OVP, thermal shutdown, battery temperature monitoring, and a configurable backup timer to prevent prolonged charging of a dead battery. Balancer 4 Click communicates with MCU using the standard I2C 2-Wire interface to read data and configure settings, supporting a Standard Mode operation up to 100kHz. It also has two LED indicators, red and green, marked with CHARGE and POWER, which can visually show
the existence of a good power supply to the MP2672A and the active status of the battery charging process. Also, an NTC function is available for temperature-qualified charging, where the MP2672A continuously monitors the battery’s temperature by measuring the voltage on the onboard NTC header pins. This Click board™ can operate with both 3.3V and 5V logic voltage levels selected via the VCC SEL jumper. It allows both 3.3V and 5V capable MCUs to use the communication lines properly. Additionally, there is a possibility for the MP2672A power supply selection via jumper labeled as VIN SEL to supply the MP2672A from an external power supply terminal in the range from 4V to 5.75V or with 5V voltage level from mikroBUS™ power rail. However, the 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 STM32F446RE 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-M4
MCU Memory (KB)
512
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
131072
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
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 Balancer 4 Click driver.
Key functions:
balancer4_write_register
This function writes a desired data byte to the selected register by using I2C serial interface.balancer4_write_and_verify_register
This function writes a desired data byte to the selected register and verifies if it is written correctly by reading it.balancer4_read_register
This function reads a data byte from the selected register by using I2C serial interface.
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 main.c
* @brief Balancer4 Click example
*
* # Description
* This example demonstrates the use of Balancer 4 click board by configuring
* the click board for charging and then reading the status and fault registers.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and configures the click board for charging.
*
* ## Application Task
* Reads and displays the status and fault registers on the USB UART every 500ms approximately.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "balancer4.h"
static balancer4_t balancer4;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
balancer4_cfg_t balancer4_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.
balancer4_cfg_setup( &balancer4_cfg );
BALANCER4_MAP_MIKROBUS( balancer4_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == balancer4_init( &balancer4, &balancer4_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( BALANCER4_ERROR == balancer4_default_cfg ( &balancer4 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
uint8_t status, fault;
if ( BALANCER4_OK == balancer4_read_register ( &balancer4, BALANCER4_REG_STATUS, &status ) )
{
log_printf ( &logger, "\r\n - STATUS - \r\n", status );
log_printf ( &logger, " Battery status: " );
if ( status & BALANCER4_STATUS_BATTERY_MISSING )
{
log_printf ( &logger, "missing\r\n" );
}
else
{
log_printf ( &logger, "present\r\n" );
log_printf ( &logger, " Charging status: " );
switch ( status & BALANCER4_STATUS_CHG_STAT_MASK )
{
case BALANCER4_STATUS_NOT_CHARGING:
{
log_printf ( &logger, "not charging\r\n" );
break;
}
case BALANCER4_STATUS_PRE_CHARGE:
{
log_printf ( &logger, "pre-charge\r\n" );
break;
}
case BALANCER4_STATUS_CONSTANT_CHARGE:
{
log_printf ( &logger, "constant current or constant voltage charge\r\n" );
break;
}
case BALANCER4_STATUS_CHARGING_COMPLETE:
{
log_printf ( &logger, "charging complete\r\n" );
break;
}
}
}
}
if ( BALANCER4_OK == balancer4_read_register ( &balancer4, BALANCER4_REG_FAULT, &fault ) )
{
if ( fault )
{
log_printf ( &logger, "\r\n - FAULT - \r\n" );
if ( fault & BALANCER4_FAULT_WD )
{
log_printf ( &logger, " The watchdog timer has expired\r\n" );
}
if ( fault & BALANCER4_FAULT_INPUT )
{
log_printf ( &logger, " Input OVP has occured\r\n" );
}
if ( fault & BALANCER4_FAULT_THERMAL_SD )
{
log_printf ( &logger, " Thermal shutdown\r\n" );
}
if ( fault & BALANCER4_FAULT_TIMER )
{
log_printf ( &logger, " The safety timer has expired\r\n" );
}
if ( fault & BALANCER4_FAULT_BAT )
{
log_printf ( &logger, " Battery OVP has occured\r\n" );
}
switch ( fault & BALANCER4_FAULT_NTC_MASK )
{
case BALANCER4_FAULT_NTC_COLD:
{
log_printf ( &logger, " An NTC cold fault has occured\r\n" );
break;
}
case BALANCER4_FAULT_NTC_COOL:
{
log_printf ( &logger, " An NTC cool fault has occured\r\n" );
break;
}
case BALANCER4_FAULT_NTC_WARM:
{
log_printf ( &logger, " An NTC warm fault has occured\r\n" );
break;
}
case BALANCER4_FAULT_NTC_HOT:
{
log_printf ( &logger, " An NTC hot fault has occured\r\n" );
break;
}
}
}
}
Delay_ms ( 500 );
}
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
Additional Support
Resources
Category:Battery charger