• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 79 subscribers
  • Views 2714 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP432P401R: Problem with Fuel Tank MKII Battery BoosterPack SDK example

Cristian Monea
Expert 1795 points

Part Number: MSP432P401R

Hello! I'm using the Fuel Tank MKII Battery BoosterPack Plug-In Module with a MSP-EXP432P401R Rev. 2.1 Launchpad and the example from MSP432 Simplelink SDK 1.40.1.00 (boostxl_batpakmkii_fuelgauge_MSP_EXP432P401R_nortos_ccs).

I've noticed that when first running the example it does not read the State of Charge and Remaining Capacity (it says 0% and 0 mAh). All other parameters are read fine. These are the steps to reproduce the issue:

1. Connect battery to plug-in module;

2. Connect the plug-in module to the Launchpad;

3. Disconnect 3V3 and 5V jumpers from the Launchpad;

4. Connect the USB cable to the Launchpad;

5. Switch the battery pack on.

6. Program and run the example.

When this happens, if I stop the program and restart, then it reads OK.

Can anybody reproduce the issue? Is there a problem with my hardware or is it a software-related problem?

  • 0
    TI__Expert 7785 points

    Hi Cristian,

    I can kind of reproduce the issue that you described. When i ran the example per your 6th step, I see the "Initializing BQ27441 Configuration" message, followed by 3 "Battery Information" messages that report 0% SOC and 0mAh Remaining Capacity. However, subsequent 'Battery Information" messages then start to report valid remaining capacity, state of charge, etc.

    Is this the same behavior that you are seeing? or does your board always report 0% and 0mAh until you restart the program?

    It's likely that the battery fuel gauge reports 0 values for a few moments after the initial configuration because its internal algorithm needs to acquire some cell measurements before it can calculate state of charge and other gauging predictions.

    Regards,
    Eric C

  • 0 in reply to Eric Chen
    Expert 1795 points

    Hi, Eric. It reports 0 until I restart the program. And I left it running for minutes. I think the problem is related with the startup config of the monitor circuit.

  • 0 in reply to Eric Chen
    Expert 1795 points

    I've tested the example again and noticed a difference. It was stuck showing 0 even after restarting the program.

    Instead, after plugging in the charging cable (it showed immediately "Status : charging") and restarting the program, it showed some values ("Remaining Capacity: 1mAh" (and rising), "State of Charge: 100%").

    Did you manage to investigate this issue?

  • 0 in reply to Cristian Monea
    TI__Expert 7785 points

    Hi Cristian,

    I suspect you may not have a jumper populated on JP6 BIN, as I see the same behavior on my BoosterPack if I remove my JP6 jumper.

    Shorting across JP6 tells the fuel gauge that the battery is connected. Note that in an actual application, the BIN input pin would be designed to detect the battery connect/disconnect event automatically. This BoosterPack was not designed this way and requires an external jumper to manually pull the BIN pin low to simulate a battery insertion.

    If you don't have a spare jumper to short across JP6 BIN, the fuel gauge can be configured to bypass hardware battery insertion detection and allow the host MCU to notify the fuel gauge of the battery insertion event via software. Attached is a project with the additional code to configure software battery insertion. Notice Lines 81 - 96 inside main.c

    BOOSTXL-BATPAKMKII_FuelGauge_MSP432P401R.zip

    Regards,
    Eric C

  • 0 in reply to Eric Chen
    Expert 1795 points
    Thank you for your help. It works now.

**Attention** This is a public forum