• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 4 answers
  • Subscribers 64 subscribers
  • Views 125 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.

BQ34Z100-G1: Support Needed: Fuel Gauge IC Max Error Issue

Abhishek Kumar
Prodigy 50 points
Part Number: BQ34Z100-G1
Other Parts Discussed in Thread: BQSTUDIO

Tool/software:

Dear Diego,

Dear Texas Instruments Support,

We are writing to report an issue we are encountering with a fuel gauge IC (Integrated Circuit) from your company. We would appreciate your assistance in identifying the root cause of the problem.

Problem Description:

  • We are experiencing a Max Error issue with our fuel gauge IC.
  • This Max Error value increases progressively between 1 and 100, although most observed cases have errors between 5% and 100%.
  • Reprogramming the device with a "golden image" (known good configuration) temporarily resolves the issue.

Our Concerns:

  • We are unsure what is causing the Max Error to increase and why it returns to normal after reprogramming.
  • We suspect the issue might be related to:
    • Sensor resistor malfunction
    • Lack of support for State of Charge (SoC) calculation tracking
    • Other component getting stuck

Request for Assistance:

  • We kindly request your help in diagnosing the root cause of this Max Error issue.
  • Specifically, we would like guidance on how to identify if the problem is due to:
    • A faulty sensor resistor
    • Software limitations with SoC tracking
    • Other potential causes
  • 0
    TI__Genius 17345 points

    Hi,

    Max Error will get updated at different events.

    Have you experienced an SOC jump?

    Can you share a log file MaxError of the increase.

    Please make sure you are getting Qmax updates throughout discharge.

    Regards,

    Diego

  • 0 in reply to Diego
    Prodigy 50 points

    Hi Diego,

    Thanks for your response.

    Regarding your questions:

    1. SOC Jump: Yes, we have experienced an SOC jump. The pack voltage and SOC are not aligning as expected.
    2. Max Error Log: I've already shared a reference picture demonstrating the Max Error values we've observed, such as 6, 7, 15, 100, and so on, at different points.
    3. Qmax Updates: To confirm if Qmax updates are being received throughout the discharge cycle, please provide guidance on how to verify this. Any reference images or videos would be helpful.

    I'm eager to resolve this issue and ensure the system is functioning correctly. Please let me know if you need any further information or assistance.

    Best regards,

    Abhishek.

  • 0 in reply to Abhishek Kumar
    TI__Genius 17345 points

    Hi Abhishek,

    Can you share a log of the SOC jump?

    Qmax Cell 0 will show the Qmax value.

    Regards,

    Diego

  • 0 in reply to Abhishek Kumar
    Prodigy 50 points

    Hi Diego,

    SOC Jumps and Voltage Data:


    As requested, we are sharing the data related to SOC jumps and discrepancies between SOC and voltage values in our [fuel guage -IC].

    Please let us know if you require any additional information or if there are specific steps we should take to address these issues. We are eager to collaborate with you to resolve these concerns.

    Thank you for your continued support

  • 0 in reply to Abhishek Kumar
    TI__Genius 17345 points

    Hi,

    So what you have sent are BQstudio screen shots. A log file is polling on the gauge reported data periodically. This can easily be created in BQstudio using the Start log button in the top right corner of BQstudio. Please press the start log button, record the SOC jump, stop log and share the file :)

    Regards,

    Diego

  • 0 in reply to Diego
    Prodigy 50 points

    Issue with SOC Mismatch and Max Error Increase in Battery Pack:

    Hi Diego,

    I am reaching out regarding an ongoing issue with a battery pack where the SOC (State of Charge) and voltage values do not match after a few charge/discharge cycles. While there is no SOC jump happening, the SOC values are inconsistent with the actual voltage readings. Additionally, in the same pack, the maximum error increases, and the pack fails to charge properly.

    I have already shared pictures of the issue for your reference. Interestingly, the problem seems to resolve temporarily after reprogramming the pack.

    Could you please advise on the possible root cause of this behavior and potential steps to mitigate this issue?

    Thank you for your support.

    Regards,

    Abhishek.



  • 0 in reply to Abhishek Kumar
    TI__Genius 17345 points

    Hi Abhishek,

    There are many things that could cause an issue like this, poor chemid match, device not calibrated, no learning cycle, parameters not properly configured, etc. 

     I will be unable to help you further debug this issue until I receive a log file of the error and your current configuration(.gg file) .

    Regards,

    Diego