TOP Contributors

  1. MIKROE (2642 codes)
  2. Alcides Ramos (347 codes)
  3. Shawon Shahryiar (307 codes)
  4. jm_palomino (112 codes)
  5. Chisanga Mumba (90 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 (136222 times)
  2. FAT32 Library (69489 times)
  3. Network Ethernet Library (55708 times)
  4. USB Device Library (45992 times)
  5. Network WiFi Library (41639 times)
  6. FT800 Library (40792 times)
  7. GSM click (28789 times)
  8. PID Library (26332 times)
  9. mikroSDK (26056 times)
  10. microSD click (25142 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-01-31

Package Version: 2.1.0.10

mikroSDK Library: 2.0.0.0

Category: Battery Charger

Downloaded: 67 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( 2000 );
        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( 2000 );
    }

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

    charge_state = charger9_fault_ind ( &charger9 );

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

        Delay_ms( 3000 );
        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

CAN FD 4 click

0

The CAN FD 4 Click is a Click board™ that features the NCV7344D10R2G, a Controller Area Network (CAN) transceiver, from ON Semiconductor.

[Learn More]

Touchpad click

2

Touchpad click is a capacitive touch input device driven by Microchip’s low-powered MTCH6102 controller. The touchpad surface is covered with a sheet of black plastic to demonstrate the chip’s support for cover layers. Touchpad click communicates with the target MCU through the mikroBUS I2C interface. Designed to use a 3.3V power supply.

[Learn More]

LTE IoT 2 click

5

LTE IoT 2 click is a Click board that allows connection to the LTE networks, featuring Quectel BG96 LTE module, which offers two LTE technologies aimed at Machine to Machine communication (M2M) and Internet of Things (IoT).

[Learn More]