• State
  • Locked Locked
  • Replies 13 replies
  • Subscribers 63 subscribers
  • Views 443 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

BQ40Z50-R1: BQ40Z50R1

Max
Intellectual 930 points
Part Number: BQ40Z50-R1
Other Parts Discussed in Thread: BQ24780S, EV2400, BQSTUDIO

Tool/software:

Hi 

we have built a 4S1P pack with BQ40Z50-r1 IC (16.8V),

Currently the battery packs are used in the production on our products ,We have some queries to be cleared which is listed below

1.In our 4S1P during the charging/Discharging we found SM bus communication error which could not capture, Since it is occurring very randomly, the SMBus error occur randomly on any of the parameters during logging.

2.When we charge the battery suddenly from 90%(charging the battery by BQ24780S charger ic )suddenly charge failed occurs, Once we disconnect the charger and again we connect the battery is charging. This scenario occurs rarely and it is difficult to capture.

Also When the Smbus error occurs ,it is possible to reset the battery without affecting the product performance, by fiving reset command to the battery pack.

Attached the gg file FYI

4S1P_AEgasgauge file.xlsx

  • 0
    TI__Mastermind 28450 points

    Hi Max,

    It is difficult to determine a root cause without a log file representing the issue, however within the .gg file the Lifetime Safety Events track which protections have been triggered. If charge is being disabled, then it is most likely a protection being triggered that would open the charge FET. Based on the .gg file, the protections that have triggered that would disable the charge FET can be seen below:

    Producing the failure again and seeing which one of these increases would show which protection is being triggered at this time.

    Regards,

    Anthony

  • 0 in reply to Anthony
    Intellectual 930 points

    Hi

    we are also facing this issues too

    1.In our 4S1P during the charging/Discharging we found SM bus communication error which could not capture, Since it is occurring very randomly, the SMBus error occur randomly on any of the parameters during logging.

  • 0 in reply to Max
    TI__Mastermind 28450 points

    Hi Max,

    What is the polling rate that the device is being read from at? Is EV2400 being used as the host?

    Regards,

    Anthony

  • 0 in reply to Anthony
    Intellectual 930 points

    Hi 

    We are reading the data 2sec once and logging the data 10sec once in our product.

    We have connected controller-charger IC-Battery on the Sm bus line .we are not using EV2400 as the host.

    Regards

    ANANDAN N

  • 0 in reply to Max
    TI__Mastermind 28450 points

    Hi Max,

    Are there any other components sharing the communication line with the gauge? This could potentially be causing collisions on the line.

    Regards,

    Anthony

  • 0 in reply to Anthony
    Intellectual 930 points

    Hi

    No we have series termination resistor on the lines, Other than that there is no other components sharing sm bus with the gauge.

    Regards

    MAX

  • 0 in reply to Max
    TI__Mastermind 28450 points

    Hi Max,

    Is it possible to receive a scope capture of the error? Also, what is the cell voltage at the time of the error? Could it potentially reaching shutdown?

    Regards,

    Anthony

  • 0 in reply to Anthony
    Intellectual 930 points

    Hi 

    Actually we could not capture the error through scope. Since it is occurring randomly.

    The battery is charging and at this scenario sm bus communication error occurs.

  • 0 in reply to Max
    TI__Mastermind 28450 points

    Hi Max,

    This is difficult to determine a root cause since a scope capture cannot be received and that EV2400 is not in use as the host, if it is possible to draw a correlation between this issue and what is occurring when it triggers would allow us to get a better idea.

    Does the issue subside when a reset is sent?

    Regards,

    Anthony

  • 0 in reply to Anthony
    Intellectual 930 points

    Hi

    I am looking into it.

    Also we found another issues, We have built 4S1P(16.4V)battery packs and we have put them on inventory with shut down mode enabled. The battery packs got failed where one cells goes less than 2.8V and we have set the CUV as 2.8V.Kindly help us to solve the issue, Since we are getting failures.

  • 0 in reply to Max
    TI__Mastermind 28450 points

    Hi Max,

    What is the CUV: Delay value? The DSG FET will not trigger until the voltage is less than the threshold for the amount of time allotted by this value.

    Regards,

    Anthony

  • 0 in reply to Anthony
    Intellectual 930 points

    We have set the delay time as 2sec but also the battery gets deeply discharged where one cell reaches a voltage of 2v per cell.

    Regards

    MAX

  • 0 in reply to Max
    TI__Mastermind 28450 points

    Hi Max,

    If possible, please provide a bqStudio log file of this occurrence. This would allow us to confirm what is occurring within the gauge at this time.

    Is it possible to see if the XDSG bit is correctly being set when this protection triggers?

    Regards,

    Anthony