• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Subscribers 63 subscribers
  • Views 719 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-R2: Discharge FET behavior when OCD operation is released

user5768972
Intellectual 450 points
Part Number: BQ40Z50-R2

A battery pack equipped with 40Z50 is connected to the device, and bit2: CHG and bit1: DSG of Manufacturing Status are observed.

Once the 40Z50 OCD is running. (Stay connected to the machine)

Next, when I charged the battery pack for a short time (while still connected to the machine) to release the OCD, bit1: DSG of Manufacturing Status became 1.

Since bit1: DSG of Manufacturing Status became 1, the battery pack does not output voltage when it is removed from the machine. (= discharge FET is off)

Why do you get this result?

  • 0 in reply to user5768972
    TI__Guru** 105740 points

    Hello,

    If you trip CUV protections the gauge will prevent discharge indicated by XDSG. Check section "2.2 Cell Undervoltage Protection" of the TRM, XDSG = 1 when tripped

    Can you share the .gg file and log of the test?

    Sincerely,

    Wyatt Keller

  • 0 in reply to Wyatt Keller
    Intellectual 450 points

    Mr.Wyatt Keller

    Thank you for answering.

    I will check the XDSG.

    Kazuto Takahashi

  • 0 in reply to user5768972
    Intellectual 450 points

    I tested with the following procedure.

    First exam

    (1) Connect the load to the battery pack to operate the OCD.

    (2) Detach the load on the battery pack.

    (3) Charge the battery pack.

    (4) Stop charging before the OCD operation is released.

    The logs from (3) to (4) are as follows.

    DateTime Voltage Current OpStatA OpStatB
    10:37:37 15389 3 0x2985 0x0000
    10:37:38 15390 3 0x2985 0x0000
    10:37:39 15390 6 0x2985 0x0000
    10:37:40 15390 6 0x2985 0x0000
    10:37:42 15389 4 0x2985 0x0000
    10:37:43 15390 6 0x2985 0x0000
    10:37:44 15487 734 0x2987 0x0000
    10:37:45 15494 1010 0x2987 0x0000
    10:37:47 15501 1011 0x2987 0x1000
    10:37:48 15506 1010 0x2987 0x1000
    10:37:49 15509 1013 0x2987 0x1000
    10:37:50 15442 584 0x2987 0x1000
    10:37:51 15414 6 0x2985 0x1000
    10:37:52 15411 5 0x2985 0x1000
    10:37:54 15409 6 0x2985 0x1000

    At the same time as charging starts, bit1 of operation status becomes H, and when charging is stopped bit1 is L.

    Second exam

    (1) Connect the load to the battery pack to operate the CUV.

    (2) Detach the load on the battery pack.

    (3) Charge the battery pack.

    (4) Stop charging before the CUV operation is released.

    The logs from (3) to (4) are as follows.

    DateTime Voltage Current OpStatA OpStatB
    10:54:14 15408 0 0x2985 0x1000
    10:54:15 15407 0 0x2985 0x1000
    10:54:16 15407 0 0x2985 0x1000
    10:54:17 15498 549 0x2987 0x1000
    10:54:18 15510 1007 0x2987 0x1000
    10:54:19 15515 1006 0x2987 0x1000
    10:54:20 15519 1008 0x2987 0x1000
    10:54:22 15524 1008 0x2987 0x1000
    10:54:23 15527 1008 0x2987 0x1000
    10:54:24 15529 1010 0x2987 0x1000
    10:54:26 15444 37 0x2985 0x1000
    10:54:27 15434 0 0x2985 0x1000
    10:54:28 15431 0 0x2985 0x1000
    10:54:29 15430 3 0x2985 0x1000

    At the same time as charging starts, bit1 of operation status becomes H, and when charging is stopped bit1 is L.

    Although OCD is not released, bit1 of operation status is H at the same time as charging, and bit1 of operation status is H at the same time as charging, although CUV is not released.

    Is this behavior correct?

  • 0 in reply to user5768972
    TI__Guru** 105740 points

    Hello,

    Check to make sure the recovery conditions are met for CUV to be cleared in your test, it may not be meeting the conditions.

    Sincerely,

    Wyatt Keller

  • 0 in reply to Wyatt Keller
    Intellectual 450 points

    私が訪ねているのは下記の内容です。
    CUV、OCDがリリースされていなくても充電時にDSGがHになるのは異常では無いのか？

    宜しくお願いします。

  • 0 in reply to user5768972
    Intellectual 450 points

    Sorry.

    I have the following questions.

    Isn't it abnormal that the DSG becomes H when charging even if the CUV and OCD have not been released?

    best regards..

  • 0 in reply to user5768972
    TI__Guru** 105740 points

    Hello,

    The DSG flag in GaugeStatus should only be set when the gauge is discharging or relaxed. You may want to check your thresholds (like quit current, relax times) if this bit is toggling often.

    Sincerely,

    Wyatt Keller

  • 0 in reply to Wyatt Keller
    Intellectual 450 points

    Here's what I want to know:

    Even if the battery (gauge IC) is operating CUV, OCD, is it normal for DSG to become H when charged (even if CUV, OCD is operating)?

    The reason I want to know this is because I am trying to program the machine as follows.

    (1) Monitor the DSG.

    (2) If the DSG becomes L, it is judged that the battery is in an abnormal state (the protection circuit has worked).

    (3) After that, when the DSG becomes H, it is judged that the normal state has been restored (the protection circuit has been released).

    However, this method cannot be used because the DSG becomes H even if the protection circuit is not released.

    Therefore

    (1) Monitor DSG, XDSG, SS.

    (2) If XDSG is H or DSG is L or SS is H, it is judged that the battery is in an abnormal state (protection circuit has worked).

    (3) After that, when XDSG is L, DSG is H, and SS is L, it is judged that the normal state has been restored (the protection circuit has been released).

    I will take this method. Is there any problem with this method?

    further

    Does XDSG remain H during protective operation (CUV, OCD) (does it not change until protective operation is released)?

    Is SS (CUV, OCD) still H (does it not change until the protective action is released)?

    Please tell us about these two as well.

  • 0 in reply to user5768972
    TI__Guru** 105740 points

    Hello,

    I would not use the DSG bit for determining a safety event.

    If you monitor the XDSG, it can be set from many different ways:

    It will clear when the safety status clears. The SS bit would be most useful for looking if any of the safety status bits are set since it OR's all of the bits.

    Sincerely,

    Wyatt Keller

  • 0 in reply to Wyatt Keller
    Intellectual 450 points

    Thank you.

    I understand that.

  • 0 in reply to Wyatt Keller
    Intellectual 450 points

    Thank you.

    I understand that.