• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 64 subscribers
  • Views 235 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.

BQ40Z60: Another problem starting the charging functionality

Leonard Hall
Prodigy 10 points
Part Number: BQ40Z60
Other Parts Discussed in Thread: BQSTUDIO

I have the development board and my first battery management board. I based my design off the development board but removed the fuse, TS 1 to 4, and LED outputs.

I made the mistake of not grounding the fuse pin and fixed that with a jumper wire. I also wired in a 10k resistor to TS1 so that I could enable a temperature input on both the FET and Cell temperatures.

I am powering the charger input with 20V on a 4s system.

I can get the dev board to charge but not my board despite having almost identical settings.

Almost a direct copy of BQ40Z60EVM-578

BM Studio output:

I have also included the settings:

beacon4.gg.csv

Thanks for your help!

  • 0
    TI__Mastermind 25225 points

    Hi Leonard,

    Would it be possible to receive a short log file of the gauge attempting to be charged? This will give us more insight into what is happening within the gauge at this time.

    Regards,

    Anthony Baldino

  • 0 in reply to Anthony
    Prodigy 10 points

    Beacon.log
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    Tue Apr 09 11:53:16 ACST 2024
    Device Version Info = 4600_0_15
    BQZ Device Name = bq40z60
    BQZ Firmware Version = V0_15_BLD21
    Design Capacity = 4400
    Design Voltage = 10800
    Specification Info = 0x0031
    Manufacturer Date = 1980-1-1
    Serial Number = 0x0001
    Manufacturer Name = Texas Instruments
    Device Name = bq40z60
    Device Chemistry = LION
    Sample,DateTime,ElapsedTime,ManufAccess,RemCapAlarm,RemTimeAlarm,BattMode,@Rate(@),@TimeFull,@TimeEmpty,@RateOK,Temperature,Voltage,Current,AvgCurr,MaxErr,RSOC,ASOC,RemCap,FullChgCap,RunTimeEmty,RunTimeEmty,AvgTimeFull,ChgCurr,ChgVolt,BattStat,CycleCnt,TurboPwr,TurboCurr,SoH,OpStatA,OpStatB,TempRange,ChgStat,ChgrStat,GaugeStat,ITStat,MfgStat,SafetyAlertAB,SafetyStatAB,SafetyAlertCD,SafetyStatCD,PFAlertAB,PFStatAB,PFAlertCD,PFStatCD,CellVolt1,CellVolt2,CellVolt3,CellVolt4,vBAT,Vacp,CellCurr1,CellCurr2,CellCurr3,CellCurr4,CellPower1,CellPower2,CellPower3,CellPower4,Power,AvgPow,IntTemp,TS1Temp,TS2Temp,TS3Temp,TS4Temp,CellTemp,FETTemp,FltRemQ,FltRemE,FltFullChgQ,FltFullChgE,TrueRemQ,TrueRemE,InitialQ,InitialE,TrueFullChgQ,TrueFullChgE,T_sim,T_ambient,RaScale1,RaScale2,RaScale3,RaScale4,CompRes1,CompRes2,CompRes3,CompRes4,PackGrid,LStatus,CellGrid1,CellGrid2,CellGrid3,CellGrid4,StateTime,DOD0_1,DOD0_2,DOD0_3,DOD0_4,DOD0 Passed Q,DOD0 Passed E,DOD0 Time,DODEOC_1,DODEOC_2,DODEOC_3,DODEOC_4,QMax1,QMax2,QMax3,QMax4,QMaxDOD0_1,QMaxDOD0_2,QMaxDOD0_3,QMaxDOD0_4,QMaxPassedQ,QMaxTime,Tk,Ta,RawDOD_1,RawDOD_2,RawDOD_3,RawDOD_4,CBTime1,CBTime2,CBTime3,CBTime4,CBDOD_1,CBDOD_2,CBDOD_3,CBDOD_4,CBTotalDODChg,SOH_FC_Q,SOH_FC_E,ChgVoltReg,ChgCurrReg,LogRowTime(ms),LogStatus
    1,2024-04-09 11:53:21,4.007,0x0147,300,10,0x6081,0,65535,65535,1,25.8,13771,0,0,100,16,15,649,4205,65535,65535,65535,2000,16400,0x00C0,0,-21603,-16987,100,0x0147,0x0000,0x08,0x0002,0x0000,0xD0,0x0011,0x0418,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,3453,3406,3457,3455,13772,8,0,0,0,0,0,0,0,0,0,0,19.5,25.8,-53.3,-53.3,-53.3,25.8,19.5,649,821,4205,6144,649,821,3556,5323,4205,6144,25.8,25.8,1000,1000,1000,1000,0,0,0,0,0,4,0,0,0,0,151792,13304,13967,13240,13267,0,0,29,0,0,0,0,4400,4400,4400,4400,0,0,0,0,2,674,1.0,1000,13344,13988,13264,13296,0,0,0,0,0,0,0,0,0,4386,6405,0,0,1014,SUCCESS
    2,2024-04-09 11:53:25,8.022,0x0147,300,10,0x6081,0,65535,65535,1,25.8,13771,0,0,100,16,15,649,4205,65535,65535,65535,2000,16400,0x00C0,0,-21603,-16987,100,0x0147,0x0000,0x08,0x0002,0x0000,0xD0,0x0011,0x0418,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,3453,3406,3457,3455,13769,4,0,0,0,0,0,0,0,0,0,0,19.5,25.8,-53.3,-53.3,-53.4,25.8,19.4,649,821,4205,6144,649,821,3556,5323,4205,6144,25.8,25.8,1000,1000,1000,1000,0,0,0,0,0,4,0,0,0,0,151796,13304,13967,13240,13267,0,0,29,0,0,0,0,4400,4400,4400,4400,0,0,0,0,2,674,1.0,1000,13344,13988,13264,13296,0,0,0,0,0,0,0,0,0,4386,6405,0,0,1016,SUCCESS
    3,2024-04-09 11:53:29,12.032,0x0147,300,10,0x6081,0,65535,65535,1,25.8,13771,0,0,100,16,15,649,4205,65535,65535,65535,2000,16400,0x00C0,0,-21603,-16987,100,0x0147,0x0000,0x08,0x0002,0x0000,0xD0,0x0011,0x0418,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,3452,3406,3457,3456,13769,5,0,0,0,0,0,0,0,0,0,0,19.5,25.8,-53.3,-53.3,-53.3,25.8,19.5,649,821,4205,6144,649,821,3556,5323,4205,6144,25.8,25.8,1000,1000,1000,1000,0,0,0,0,0,4,0,0,0,0,151800,13304,13967,13240,13267,0,0,29,0,0,0,0,4400,4400,4400,4400,0,0,0,0,2,674,1.0,1000,13344,13988,13264,13296,0,0,0,0,0,0,0,0,0,4386,6405,0,0,1018,SUCCESS
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Thanks Anthony, I am sure I am just missing something silly.

    Let me know if there is anything else you need.

    I would also be happy to pay for some consulting time if that is available

  • 0 in reply to Leonard Hall
    TI__Mastermind 25225 points

    Hi Leonard,

    I have a couple quick questions if you don't mind.

    I took a look into the log file to see that GAUGE_EN and CHGR_EN were both disabled for this test, along with DSG being detected the entire test due to no current being passed through the system. The gauge should move into CHG mode when the current across PACK is greater than the CHG Current Threshold, which in your .gg file is represented as 50mA. Can you please confirm that there is a current present at the PACK connection when this test is being done?

    Also, the log file shows that FET_EN is being toggled at multiple times throughout the test. Can you please go more into depth about why this is being done?

    Regards,

    Anthony Baldino

  • 0 in reply to Anthony
    Prodigy 10 points

    Hi Anthony,

    Anthony said:
    I have a couple quick questions if you don't mind.

    I really appreciate your help. Sorry for the slow reply I have been in another facility away from my lab. The log I got you was done remotely so I tried to do a reset then provide some stimulus or state change in a hope that it may help. I will be back in 20 hours and be able to repeat the test.

    Anthony said:
    Also, the log file shows that FET_EN is being toggled at multiple times throughout the test. Can you please go more into depth about why this is being done?

    I think I asked for this to be done simply to try to provide some state change.

    Anthony said:
    I took a look into the log file to see that GAUGE_EN and CHGR_EN were both disabled for this test

    I can repeat the test with these enabled.

    Anthony said:
    along with DSG being detected the entire test due to no current being passed through the system.

    I am sorry but I don't understand the "DSG" state and what you mean by charge across the pack. In this case I am using 4 series 18650 cells on the same PCB so it is a little difficult to measure the pack current without soldering in an external pack. I can do this and measure the current into the pack if it helps.

    Previously I loaded the batteries until the monitor shut them off in a hope this would trigger the charging cycle. Is this why I am in the DSG state?

    Could you help me understand what you mean by "current across PACK". I wouldn't expect there to be current flowing through the pack when it has reached the minimum voltage but I would have thought it would still charge. I am sure I am misunderstanding what you have said I am sorry!

    Could you perhaps tell me exactly what you would like me to do in a test that you think would be most helpful.

    Thanks for your time and assistance!!

  • 0 in reply to Leonard Hall
    TI__Mastermind 25225 points

    Hi Leonard,

    Leonard Hall said:

    I am sorry but I don't understand the "DSG" state and what you mean by charge across the pack. In this case I am using 4 series 18650 cells on the same PCB so it is a little difficult to measure the pack current without soldering in an external pack. I can do this and measure the current into the pack if it helps.

    Previously I loaded the batteries until the monitor shut them off in a hope this would trigger the charging cycle. Is this why I am in the DSG state?

    Could you help me understand what you mean by "current across PACK". I wouldn't expect there to be current flowing through the pack when it has reached the minimum voltage but I would have thought it would still charge. I am sure I am misunderstanding what you have said I am sorry!

    Sorry for the confusion, I can go more in depth about my previous comments:

    My curiosity comes from what the current is at your Vsys point (which in most of our schematics is called PACK+) in the schematic below when FET_EN is enabled. When I previously said current across PACK, this is what I was referring to.

    Typically, if FET_EN is enabled, the mode that the gauge will be in is dependent on the current being seen at the sense resistors. If there is a current observed at the sense resistor that is more negative than the DSG Current Threshold, the gauge will enter DSG mode. Vise versa with a positive current, if the observed current is greater than the CHG Current Threshold, the gauge will enter CHG mode.

    However, there is the topic of the Quit Current, where if the current is within this zone for long enough, the gauge will enter relax mode. When looking at the Status Registers on bqStudio, the DSG bit will be set if the gauge is either in DSG or relax. In the sent logs before, there was no current being passed through (meaning it was less than the Quit Current) so I believe the gauge was in relax mode.

    Please let me know if this helps.

    Regards,

    Anthony Baldino

  • 0 in reply to Anthony
    Prodigy 10 points

    Thanks Anthony, 

    This post helped me work out what was happening. What I didn't realise was the CHGSTAT represents the presence of a charging current, not if the charger is trying to charge. The problem was an incorrect resistor in the charger feedback voltage divider network.

    Everything is working now and I really appreciate the time you provided to help me work through my problem!