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.

BQ27426: FuelGauge power-up to initialization completion time

Part Number: BQ27426

The FuelGauge does not load the FS file when it is first powered up. It takes about 4 seconds to complete the initialization (INITCOMP is set to 1).

Why does it take 4 seconds?

What is the exact operation that FuelGauge performs in 4 seconds?

  • Hello Wang,

    The Fuel gauge takes upto 4 seconds to power on, initialize the peripherals and take voltage+current+temperature measurements.

  • The gauge measures current, voltage and temperature once a second. During startup, it calculates cell state and it will require that this is stable for initialization to complete, hence it can take a few seconds.

  • Sorry to trouble you again.
    Can you describe in detail, the steps of the initialization process and the time required to execute each step?

    For example:

    step1 get voltage+current+temperature, 1 sec;

    step2 calculate battery state, 1 sec;

    step3 wait for state stability, 2 sec.

    Total 4 seconds.

  • The gauge will boot up, which takes a few ms.

    Then it will take one second to complete all measurements (the gauge runs on a 1 second cycle).

    It will use the results from each measurement cycle to calculate DOD(OCV, T, I) and it will complete initialization after X seconds, with X depending on how stable the measurements are (=it tries to get a high quality DOD, which must be stable).

  • Thanks for you reply

    #1 Can boot up be done in 5ms?
    #2 What is the maximum value of x?
    #3 How do you determine the stability of the measurement? What is the minimum number of cycles required?
    #4 If FuelGauge starts loading FS file after power up, does INITCOMP set 1 after calculating stable DOD or after FS file loading is finished?

  • #1: No. tPUCD = 250s (see datasheet, table 6.8).
    #2: Default setting = 10.
    #3: The gauge calculates DOD(OCV, T, I) once a second. It must not change by more than 0.01.
    #4: INITCOMP is set when DOD is stable.

  • Thanks for you reply。

    #1-#3:

    step1:boot up-->250us;

    step2:get voltage+current+temperature, and calculates DOD(OCV, T, I) -->1 sec;

    step3:if more than 0.01,recty step2。Maximum 10 times(Max 10 sec)

    Is the above understanding correct?

    #4: Can DOD be stable during fs file loading? The actual test situation is that after the fs file is loaded, INITCOMP=1.

    #5:After loading the fs file, the ITPOR in Flag() is not cleared, and there is SOFT_RESET instruction at the end of the FS file. What is the reason for this?
    Is there any restriction when FS file is loaded?

  • #1-3: Yes.

    #4: The gauge will check DOD after receiving a reset (e.g. SOFT_RESET)

    #5: The SOFT_RESET command will eventually cause ITPOR to clear.

  • Thanks for you reply

    #4 When Fuelgauge is powered up, it starts loading the fs file, is the following process correct?

    #5 During the test, after loading the fs file, ITPOR is always 1, and I can't make ITPOR=0 by sending SOFT_RESET command manually.
    What is the reason for this?

    #6 Is there a limit to loading FS files? What is the limitation in the loading process?

    #7 Can the data in Fuelgauge be read immediately after the FS file is loaded? Do I need to wait for some status confirmation before I can start reading the Datamemory data in Fuelgauge?

    #8 If the FS file fails to load, according to the TRM description, it can be tried several more times. is it necessary to reset FuelGauge before re-load?

    #9 The Subclass ID 68 (0x44) is modified in the FS file, but there is no any description of Subclass ID 68 in the TRM. Is this SubclassID private? Is there any other documentation to get the data and description of Subclass ID 68?

  • #4: This looks correct.

    #5: Make sure that BAT_DET is 1. ITPOR will clear if the gauge detected a battery and you issued a SOFT_RESET while the gauge was in configuration update mode.

    #6: The gauge will automatically exit configuration update mode after approx. 4 seconds of no communication.

    #7: You can read it back immediately.

    #8: You don't need to reset the gauge.

    #9: 0x44 is the Power Subclass. It is private with several parameters that affect low power modes, which aren't intended to be user adjustable.