Design an advanced battery monitoring solution with BQ35100 and MK64FN1M0VDC12
Know your power, know your device
Published May 14, 2023
Click board™
BATT-MON 3 Click
Dev Board
Clicker 2 for Kinetis
Compiler
NECTO Studio
MCU
MK64FN1M0VDC12
Don't let a dead battery catch you off guard - choose innovative fuel gauge and battery diagnostics technology to track battery health and ensure optimal performance
A
A
Hardware Overview
How does it work?
BATT-MON 3 Click is based on the BQ35100, battery fuel gauge, and end-of-service monitor from Texas Instruments that provide gas gauging for lithium thionyl chloride (Li-SOCl2) and lithium manganese dioxide (Li-MnO2) primary batteries without requiring any forced discharge of the battery. The primary lithium gas gauging function uses voltage, current, and temperature data to provide accurate results alongside an ultra-low average power consumption. It also uses patented TI gauging algorithms to support the option of seamlessly replacing an old battery with a new one. This device measures the BT input using the integrated delta-sigma ADC, scaled by the internal translation network, through the ADC. A calibration process determines the translation gain function. It can also operate in three distinct modes: accumulator (ACC), state-of-health (SOH), and end-of-service (EOS)
mode. The device can be configured and used for only one of these modes in the field, as it is not intended to be able to switch between modes when in regular use. BATT-MON 3 Click communicates with MCU using the standard I2C 2-Wire interface to read data and configure settings with a maximum frequency of 400kHz. The BQ35100 is intended for systems with battery electronics that consume a low average current. This board is designed to be fully powered OFF when not required by controlling the enable pin routed to the PWM pin of the mikroBUS™ socket. When this pin is low, the Click board™ is fully powered down with no measurements being made, and no data is retained unless in a flash. An alarm and interrupt function is also available that outputs an interrupt signal to the ALR pin of the mikroBUS™ socket based on various configurable status and data options.
This feature is also indicated by a red LED marked as ALR. Besides, this Click board™ also features battery pack temperature sensing through an integrated temperature sensor or an external NTC thermistor connected to the onboard header labeled as NTC, using the integrated delta-sigma ADC where only one source can be used at a time. 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. 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
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
You complete me!
Accessories
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
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Clicker 2 for Kinetis as your development board.
Track your results in real time
Application Output
After loading the code example, pressing the "DEBUG" button builds and programs it on the selected setup.
After programming is completed, a header with buttons for various actions available in the IDE appears. By clicking the green "PLAY "button, we start reading the results achieved with Click board™.
Upon completion of programming, the Application Output tab is automatically opened, where the achieved result can be read. In case of an inability to perform the Debug function, check if a proper connection between the MCU used by the setup and the CODEGRIP programmer has been established. A detailed explanation of the CODEGRIP-board connection can be found in the CODEGRIP User Manual. Please find it in the RESOURCES section.
Software Support
Library Description
This library contains API for BATT-MON 3 Click driver.
Key functions:
battmon3_read_voltageThis function reads the battery voltage in millivolts.battmon3_read_currentThis function reads the battery current load from BATT+ to GND in milliamps.battmon3_read_used_capacityThis function reads the used battery capacity in mAh.
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 BATTMON3 Click example
*
* # Description
* This example demonstrates the use of BATT-MON 3 click by measuring the battery
* voltage, current and used capacity, as well as the chip internal temperature.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialized the driver and performs the click default configuration.
*
* ## Application Task
* Reads the battery voltage (mV), current (mA), used capacity (mAh) and the chip internal
* temperature (Celsius) and displays the results on the USB UART approximately once per second.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "battmon3.h"
static battmon3_t battmon3;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
battmon3_cfg_t battmon3_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.
battmon3_cfg_setup( &battmon3_cfg );
BATTMON3_MAP_MIKROBUS( battmon3_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == battmon3_init( &battmon3, &battmon3_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( BATTMON3_ERROR == battmon3_default_cfg ( &battmon3 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
uint16_t voltage;
int16_t current;
float temperature, used_capacity;
if ( BATTMON3_OK == battmon3_read_voltage ( &battmon3, &voltage ) )
{
log_printf ( &logger, " Voltage: %u mV\r\n", voltage );
}
if ( BATTMON3_OK == battmon3_read_current ( &battmon3, ¤t ) )
{
log_printf ( &logger, " Current: %d mA\r\n", current );
}
if ( BATTMON3_OK == battmon3_read_temperature ( &battmon3, &temperature ) )
{
log_printf ( &logger, " Temperature: %.3f C\r\n", temperature );
}
if ( BATTMON3_OK == battmon3_read_used_capacity ( &battmon3, &used_capacity ) )
{
log_printf ( &logger, " Used Capacity: %.3f mAh\r\n\n", used_capacity );
}
Delay_ms ( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
