TOP Contributors

  1. MIKROE (2784 codes)
  2. Alcides Ramos (405 codes)
  3. Shawon Shahryiar (307 codes)
  4. jm_palomino (133 codes)
  5. Bugz Bensce (97 codes)
  6. S P (73 codes)
  7. dany (71 codes)
  8. MikroBUS.NET Team (35 codes)
  9. NART SCHINACKOW (34 codes)
  10. Armstrong Subero (27 codes)

Most Downloaded

  1. Timer Calculator (141228 times)
  2. FAT32 Library (74037 times)
  3. Network Ethernet Library (58659 times)
  4. USB Device Library (48767 times)
  5. Network WiFi Library (44485 times)
  6. FT800 Library (44034 times)
  7. GSM click (30784 times)
  8. mikroSDK (29602 times)
  9. PID Library (27342 times)
  10. microSD click (27189 times)
Libstock prefers package manager

Package Manager

We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]

< Back
mikroSDK Library

Charger 9 Click

Rating:

0

Author: MIKROE

Last Updated: 2024-10-31

Package Version: 2.1.0.13

mikroSDK Library: 2.0.0.0

Category: Battery Charger

Downloaded: 231 times

Not followed.

License: MIT license  

Charger 9 Click is a Li-Ion (Li+, Li-Po) battery charger, capable of charging one, two or three battery cells.

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "Charger 9 Click" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "Charger 9 Click" changes.

Do you want to report abuse regarding "Charger 9 Click".

  • mikroSDK Library 1.0.0.0
  • Comments (0)

mikroSDK Library Blog


Charger 9 Click

Charger 9 Click is a Li-Ion (Li+, Li-Po) battery charger, capable of charging one, two or three battery cells. It is based on the MAX1757, an integrated Li+ battery charger with many features that allow safe and reliable charging.

charger9_click.png

Click Product page


Click library

  • Author : MikroE Team
  • Date : Dec 2019.
  • Type : GPIO type

Software Support

We provide a library for the Charger9 Click as well as a demo application (example), developed using MikroElektronika compilers. The demo can run on all the main MikroElektronika development boards.

Package can be downloaded/installed directly form compilers IDE(recommended way), or downloaded from our LibStock, or found on mikroE github account.

Library Description

This library contains API for Charger9 Click driver.

Standard key functions :

  • Config Object Initialization function.

    void charger9_cfg_setup ( charger9_cfg_t *cfg );

  • Initialization function.

    CHARGER9_RETVAL charger9_init ( charger9_t ctx, charger9_cfg_t cfg );

Example key functions :

  • Enable function

    CHARGER9_RETVAL charger9_enable ( charger9_t *ctx, CHARGER9_STATE pwr_state );

  • Fast-Charge Indicate function

    CHARGER9_RETVAL charger9_fast_charge_ind ( charger9_t *ctx );

  • Full-Charge Indicate function

    CHARGER9_RETVAL charger9_full_charge_ind ( charger9_t *ctx );

Examples Description

This application is battery charger, capable of charging one, two or three battery cells.

The demo application is composed of two sections :

Application Init

Initializes GPIO driver and turns OFF the charger as initial state.


void application_init ( void )
{
    log_cfg_t log_cfg;
    charger9_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.

    charger9_cfg_setup( &cfg );
    CHARGER9_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    charger9_init( &charger9, &cfg );

    charger9_enable( &charger9, CHARGER9_DISABLE );
    en_flag = CHARGER9_DISABLE;
    Delay_ms ( 100 );

    log_printf( &logger, "** Charger 9 initialization done ** \r\n" );
}

Application Task

Checks which command was sent by user and performs the selected command. Also checks the fault condition, and when fault condition is detected sends a report message to the uart terminal and turns OFF the charger.


void application_task ( )
{   
    CHARGER9_RETVAL charge_state;

    if ( en_flag == CHARGER9_DISABLE )
    {
        charger9_enable( &charger9, CHARGER9_ENABLE );
        en_flag = CHARGER9_ENABLE;

        Delay_ms ( 1000 );
        Delay_ms ( 1000 );
        log_printf( &logger, "** Charger 9 is enabled ** \r\n" );
    }

    charge_state = charger9_full_charge_ind( &charger9 );

    if ( charge_state == CHARGER9_IND_ACTIVE )
    {
        log_printf( &logger, "** Full-Charge state ** \r\n" );
        Delay_ms ( 1000 );
        Delay_ms ( 1000 );
    }

    charge_state = charger9_fast_charge_ind( &charger9 );
    if ( charge_state == CHARGER9_IND_ACTIVE )
    {
        log_printf( &logger, "** Fast-Charge state ** \r\n" );
        Delay_ms ( 1000 );
        Delay_ms ( 1000 );
    }

    charge_state = charger9_fault_ind ( &charger9 );

    if ( charge_state == CHARGER9_IND_ACTIVE )
    {
        charger9_enable( &charger9, CHARGER9_DISABLE );
        en_flag = CHARGER9_DISABLE;

        Delay_ms ( 1000 );
        Delay_ms ( 1000 );
        Delay_ms ( 1000 );
        log_printf( &logger, "** Fault condition! ** \r\n" );
        log_printf( &logger, "** Charger 9 is disabled ** \r\n" );
    }
}

Note

When user sends a desired command to the charger, a report message will be sent to the uart terminal as indication to the user. The possible commands, for Charger 9 control, will be written to the uart terminal. The alarm sound will be generated on the determined commands: enable, disable and fault condition detecting.

The full application code, and ready to use projects can be installed directly form compilers IDE(recommneded) or found on LibStock page or mikroE GitHub accaunt.

Other mikroE Libraries used in the example:

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.Charger9

Additional notes and informations

Depending on the development board you are using, you may need USB UART Click, USB UART 2 Click or RS232 Click to connect to your PC, for development systems with no UART to USB interface available on the board. The terminal available in all Mikroelektronika compilers, or any other terminal application of your choice, can be used to read the message.


ALSO FROM THIS AUTHOR

I2C to CAN Click

0

I2C to CAN Click is a compact add-on board that contains I2C to CAN-physical transceiver, which extends a single-master I2C bus through harsh or noisy environments. This board features the LT3960, a robust high-speed transceiver that extends a single-master I2C bus up to 400kbps using the CAN-physical layer from Analog Devices. One LT3960 from SCL and SDA I2C lines creates equivalent differential buses (CAN) on two twisted pairs, while the second LT3960 recreates the I2C bus locally for any slave I2C devices on the other end of the twisted pairs. A built-in 3.3V LDO powers both the I2C and CAN lines from a single input supply from 4V to 60V. This Click board™ is suitable for industrial and automotive networking, remote sensor applications, and more.

[Learn More]

AudioAmp 6 Click

0

Audio Amp 6 Click is a mono/subwoofer audio amplifier, capable of delivering up to 18.5W per channel with the 4Ω load. It is based on the TPA3138D2, a class-D integrated amplifier, which utilizes a highly efficient switching scheme.

[Learn More]

LTE IoT 5 Click

0

LTE IoT 5 Click is an add-on board with a compact and cost-effective secure-cloud multi-band solution designed for IoT applications. This board features the SARA-R510M8S, a cellular module that supports LTE Cat M1/Cat NB2 bands with integrated high-performance standard precision M8 GNSS receiver for global position acquisition from u-Blox. Equipped with familiar AT commands set over the UART interface, USB interface, and Network and Status indicators this low power size-optimized solution, specifically designed for IoT, also provides over-the-air firmware updates, end-to-end trusted domain security, and u-Blox’s leading GNSS technology.

[Learn More]