• State Resolved
  • Locked Locked
  • Replies 27 replies
  • Answers 7 answers
  • Subscribers 67 subscribers
  • Views 3294 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.

BQ27510 bqeasy error "Dataflash.GasGauging.State.UpdateStatus does NOT = 2"

Gerry S
Intellectual 890 points
Other Parts Discussed in Thread: BQ27500, BQ27510, BQ27541, BQ27510-G1

Hello,

I'm using the bqEasy Software for callibrating my Li-Ion pack. Wen done with the full training I get the following error:

"Dataflash.GasGauging.State.UpdateStatus does NOT =  2. Impedance track learning cycle was not completed correctly. Verify procedure and repeat."

What does this mean. Does the battery have to be fully charged before I click "All Done"

Thanks.

  • 0
    TI__Genius 14985 points

    First, some background on this item:

    If you go to the Data Flash screen in EVSW and click on the Gas Gauging tab you can find the item called Update Status.

    Before starting the learning cycle, it should have been initialized to 0 by bqEasy when the the gauge is reset.

    During the learning cycle, it should automatically update itself to 1 after the full charge and relaxation is complete. This will indicate that the gauge updated Qmax for the first time since the charge started from fully empty and ended at fully charged. The gauge now has a pretty good idea of the actual capacity of the real cell.

    Then, after the discharge and relaxation it will update itself to 2. This means the learning cycle was successful and Qmax will be updated again, as will the resistance tables (Ra in data flash).

    If Update Status doesn’t go to 2 then there was a problem with the learning cycle.

    There are a few reasons why Update Status might not change to 2.

    First, make sure that IT is enabled before starting the learning cycle. There is a button in bqEasy which should have done this if you went step by step.

    Second, if the RUP_DIS bit on the RAM screen gets set, that means there was some disqualifying event during the learning cycle and the algorithm disabled Ra updates.

    An example of a disqualifying event is any interruption of the charge or discharge (they must be continuous and constant from empty to full and from full to empty). Also, if the currents were too low or too high, or if the temperature was out of range. Current should be around C/2 for charging and C/5 for discharging. Temp should be at room.

    Also, make sure calibration was done so that voltage, temp, and currents are all measured accurately and the algorithm is not using wild uncalibrated values. I don’t expect they would be that wild without calibrations, but it’s something to check.

    Finally, to try to debug what event might be causing it to fail, I like to log the RAM (click Start Logging on the DataRAM screen) and also enable AutoExport of all GG parameters (see Options menu on Data Flash screen).

  • 0 in reply to dMax
    TI__Genius 14985 points

    Let me add one more clarification:

    The discharge current needs to be continuous, but it doesn't need to be absolutely constant for the learning cycle to be succesfull.  For example, you might be discharging through a resistor and as the cell voltage drops the current will drop.  This is fine. 

  • 0 in reply to dMax
    Intellectual 890 points

    Hi David,

    Thanks for your reply.

    I'll try what you asked, but does the charger need to be on all the time. For eg. when I'm draining the battery to empty, I disconnect the charger. Maybe I'm doing it wrong.

  • 0 in reply to Gerry S
    TI__Genius 14985 points

    Are you doing the learning cycle with your battery connected to one of our EVM boards or in your actual system?

    I might not be understanding your question correctly, but you don't need the charger on while you are discharging, as long as your gauge is being powered by the battery.  You want your discharge current to be drawn from the battery, not the charger.

  • 0 in reply to dMax
    Intellectual 890 points

    I'm using the EVM2300.

    I disconnect the charger during discharge, but connect it back when the battery is flat so that I can initialize the Impedance Track Algo in one of the steps of bqEasy.

     

  • 0 in reply to Gerry S
    Intellectual 890 points

     

    Hi David,

    Could you tell me what a learning cycle is? Is it Discharge, wait 5 hours and Initialize impedance Track algo, charge and then wait 2 hours?

    These are the steps I'm taking:

    1. Charger is connected to battery. Press Reset in bqEasy

    2. Disconnect charger and now start discharging through a 6ohm resistor.

    3. Wait till charge on battery drops to almost zero.

    4. Wait 5 hours.

    5. Now the "Impedance Track Algo" has to be initialised. The bqEasy software wont respond as the gauge has no power because the battery is discharged. This requires me to connect the charger. However, I now have to wait for the battery to get charged to approx 2.0v so that bqeasy can connect.

    6. Once I reach 2V, I start the impedance track algo.

    7. When fully charged, wait another 2 hours.

    8.Now discharge to empty and wait 5 hours.

     

    Q1> When should I see the update status change to 1 and 2. Between which steps?

    Q2>  On the screen where the "RUP_DIS" bit is displayed, which color is "1" and which is "0"? There is no legend on the screen.

    Q3> Also, what are the required charger specs. The usermanual has no specifications on the charger.

     

     

  • 0 in reply to Gerry S
    TI__Genius 14985 points

    The learning cycle technically starts when you enable IT and begin the first charge.  Update Status will change to 1 after you charge and relax.  Then you discharge to your termination voltage and relax 5 hours.  Then Update Status should change to 2.

    The termination voltage is what the system considers a shutdown voltage, for example 3V.  You should have configured this in step 2 of bqEASY and it will be written to dataflash.

    Your problem is that you are completely discharging the battery.  You actually should only discharge the battery to your termination voltage.  You either need to watch your discharge and manually stop the discharge when it reaches that voltage, or you can automatically stop it with the circuit that uses a FET or relay shown in bqEASY.

     

    Note: If you are using one of our pack-side gauges like bq27541 then Update Status will start at 2 when you enable IT.  Then it will change to 4 when you have a successful charge, then to 6 when you have completed the learning cycle successfully.  This is different from the system-side gauges like bq27500, bq27505, bq27510, which go from 0 to 1 to 2 during the learning cycle.

  • 0 in reply to dMax
    TI__Genius 14985 points

    To answer you last question: On the DataRAM screen a green means the bit is 0, a red means 1.

  • 0 in reply to dMax
    Intellectual 890 points

    Thanks for your answers. It's much clearer now. Will report back.

  • 0 in reply to Gerry S
    Prodigy 40 points

    Hello,

    Ive been having very similar problems with successfully completing the learning cycle. After multiple trials I have been unable to get the status bit to even change to 1. In my system, I connect the battery to a 7ohm resistance to discharge, and only let it go until it reaches 3V, which is the minimum operating condition for the device I am using the battery in. Is it okay to do this or do I need to let the battery go all the way to 0 before I disconnect it from the load and let it sit for 5 hours? Also, should I be leaving the battery connected to the charger during the 2 hr "relaxation" period? Any help would be much appreciated. Thank you!

  • 0 in reply to Bryan White
    TI__Genius 14985 points

    Hi Bryan,

    First, we need to figure out why you can't get Update Status to change to 01.  Why don't you attach some screenshots of your DataRAM and DataFlash (Gas Gauging tab) screens immediately before you start the learning cycle?  I'll check for common mistakes.

    Make sure you are starting from a discharged and relaxed battery.  A discharged battery means about 3V in your case.  Let it sit for at least two hours after you reach 3V.  The voltage may rise somewhat as it relaxes after you remove the load; this is fine.

    Now you will enable IT by either clicking the Enable IT button in bqEASY or manually sending command 0x21 to the Control() register in the DataRAM screen.  This will make the IT Enable register in Data Flash (Gas Gauging tab) change to 01.  (Don't manually change this register to 01.  You must send the IT Enable command to properly start the algorithm.) If you enable IT successfully and all other settings are nominal (room temp, etc.), you should see the RUP_DIS bit clear (go from red to green) and the VOK and QEN bits must get set (turn green).  If this doesn't happen, you are not ready to start the learning cycle.

    Once IT is enabled, you can start your charge using a CC/CV method.  Limit your current to approximately C/2 until you get to 4.2V, then the current will start to taper off as the battery becomes fully charged.  Your charger should continue charging (applying 4.2V at this point) until its taper current is reached.  If your charger stops charging (removed 4.2V) when the current drops to 100mA (for example), you must make sure your Taper Current register in Data Flash (Configuration tab) is HIGHER than this value (for example, 110mA).  This makes the gauge consider the battery to be fully charged when the voltage reaches 4.2V AND the charging current drops below 110mA.  If your charger stops at 120mA and the gauge is waiting for 110mA, the gauge will never consider the battery to be fully charged.  How do you know if the gauge believes the battery to be full?  The FC bit on the DataRAM screen (Flags register) will be set (red). 

    Lesson 1: Make sure the gauge has IT enabled successfully before starting your learning cycle.

    Lesson 2: Make sure the gauge sees the battery as fully charged after the charging portion of your learning cycle.  If FC never gets set, Update Status will never change to 01.

    Confirm those items, and review my first reply to bluehash above for other tips of what might be going wrong. 

    To answer your specific questions:

    a) Don't let the battery go to 0V!  That will damage your battery.  You need to keep your battery intact, as well as keep the gauge powered continuously.  If you totally discharge your battery then your gauge will obviously power down AND you will need to get a new battery.

    b) You can leave the charger connected during relaxation.  Your charger may shut off on its own if it is a real charger, or if you are just using a power supply with a current limit, then the current will eventually taper to 0mA (or maybe a few mA) once the battery if fully charged.  This is fine to leave connected during the 2 hours of relaxation.  You can just remove it before you start your discharge.

  • 0 in reply to dMax
    Prodigy 40 points

    Hello David,

    Thanks for getting back to me I appreciate it. So these screens were taken during the relax period before I clicked Initialize IT. The battery is not connected to either the charger or resistor load. I disconnected it from the load when the voltage level reached 3V, but since then it has climbed back up, which you mentioned in your last message. I noticed the FC bit was red which was a good sign at this stage, although I dont know if the CHG and DSG bits are what they should be. I would guess that a green CHG bit would mean the system thinks the battery is charging, but I could be wrong. I also looked at the Taper Current level and noticed that it was set at around 1300mA. Im pretty sure this is the charging the current of the battery, so I guess the current should always drop below this as it reaches its full capacity. Should I try and observe the current as the battery charges so that the taper current level is closer to what the actual cutoff is? I am using a charging circuit board as opposed to a power supply so I would need to rig an ammeter to check this. Hopefully everything looks good here, you helped clear up a lot of things already so I feel like im at least moving in the right direction. Thank you!

    -Bryan

  • 0 in reply to Bryan White
    TI__Genius 14985 points

    Hi Bryan,

    I see a couple of problems if this is your starting point before you start your learning cycle.

    First, IT Enable in Data Flash is already set to 01.  This is probably because you tried and failed a learning cycle, but never re-initialized it to 00.  Go ahead and click on "01", type "00" and hit the enter key to rewrite it to 00.  The safest way would actually be to go through bqEASY again, but I think this will get you going.

    Now, I also noticed that your temperature is -41.45C.  It looks like you haven't calibrated temperature or you removed the thermistor.  If the gauge thinks this is the temperature it will fail to learn because everything will be disqualified due to the extreme temperature.  You must let it learn at nominal temperature, and if it thinks the temperature is otherwise then it will not work.

    If these screenshots are taken after you discharged the battery, then it doesn't make sense that your FC bit is set (red).  You shouldn't see FC set until you fully charge the battery!  If you really have Taper Current set to 1300mA then that's probably the reason.  That is an unreasonable value for your battery size.  Click on it and type in 130mA (just to be conservative), then hit enter.  This is assuming that your charger quits charging when the current drops below 130mA.  Chargers usually stop at 100mA or less, which is why 130mA is a reasonable setting, but you might want to tighten it down if you figure out your charger's actual quit current.

  • 0 in reply to dMax
    Prodigy 40 points

    Hey David,

    So I fixed the temperature issue, turns out the thermistor wasn't connected properly, so now it reads a temp of about 23-26 degrees C, which is much more realistic, and within the temp range of the software. I also changed the taper current level to 130mA like you suggested, as well as manually reset the IT Enable Bit which seemed to fix the FC bit. Sorry I guess I read that one backwards before haha. These screens were taken right after I disconnected the load before the IT was initialized, similar to the when I took the screens from my last message. The only thing I noticed that I thought was unusual was that both the CHG and DSG bit were set while the battery was discharging. Also is it normal that the cycle count value is set to 2? This is the first time ive seen this value change.

    Thanks,

    Bryan

  • 0 in reply to Bryan White
    TI__Genius 14985 points

    Hi Bryan,

    First off, I just noticed that your firmware version appears to be bq27510 (v1.11).  This is our original bq27510 firmware version (and still ships on our EVMs), but we've released bq27510-G1 (v1.12).  Before you start your learning cycle and create your golden DFI, and assuming you want to use the latest and greatest in your production system, I recommend that you upgrade your EVM to bq27510-G1 (v1.12) in three steps:

    1. Install the new EVSW: http://focus.ti.com/docs/prod/folders/print/bq27510-g1.html#toolssoftware
    2. Download the v1.12 SENC file from the same section.
    3. Follow the instructions in this app note to program the new SENC into your EVM: http://www.ti.com/litv/pdf/slua453a

    Cycle Count increments every time the gauge counts enough discharging coulombs to equal the data flash parameter CC Threshold.  Since you've been messing with this EVM for a while without restoring the data flash, it's pretty likely that Cycle Count would have incremented by now.  :)

    Well, it looks like you are all set for a successful learning cycle now (although something can always jump up and bite you).  Hey, that's how we learn, right?  :)

    What I recommend, to keep everything clean and smooth, is to upgrade your EVM to v1.12, start bqEASY from the beginning so all your settings are reset, and go from there.  Let me know how it goes.

    Best regards,

    David

  • 0 in reply to dMax
    Prodigy 40 points

    Hey David,

    Ive upgraded the firmware on the EVM like you mentioned, and fixed a small number of configuration details that I missed before, and even after 3 or 4 more attempts I still can not get to an Update Status of 1. One thing ive noticed is that the RUP_DIS bit is set from the beginning, and does not clear until the relaxation time after the initial discharge before the IT is enabled. Ive read that the learning cycle is disrupted once this bit is set, but I cannot find anything that explains why it sets. Even right after I click the reset button on step 5 of bqEASY it is still set from the start. Can you think of any reason why this would be happening, or have any other suggestions as to why I am not able to complete a learning cycle? Thanks for your continued support!

    Bryan

  • 0 in reply to Bryan White
    TI__Genius 14985 points

    It's normal for the RUP_DIS bit to be set until you enable IT.  Unless the IT algorithm is running, updates to the resistance tables will not occur, and this is what RUP_DIS (R updates disabled) indicates.

    Can you confirm that RUP_DIS is cleared (green) after you enable IT, but the VOK and QEN bits are set (red).  This should be the condition after you enable IT, and before you start your charging.

  • 0 in reply to dMax
    Prodigy 165 points

    I'm experiencing the very same problems here with BQ27510-G1. And after just a few weeks, we seem to be lucky compared to others trying "3-4 months" already ;-)

    Cycle update doesn't change either. Not even to a 1. And it doesn't even give the measured capacity.

    It would be very helpfull, if the device (or software) could give a hint, of why it didn't want to accept a valid cycle. Just stating "didn't work" (my translation of the bit not changing to a 1) leaves me to making wild guesses about possible reasons. And try again and again. Maybe a future improvement of the firmware / BQeasy-software could detail on the reasons. It then would more deserve the name "BQeasy "...

    As David has been emphasizing, the charge and discharge currents should be around C/2 and C/5. This would require my charger to charge with 3000mA. Our charger simply doesn't allow such high currents (max power dissipation!). Is this really an issue? Is a 1000mA charge ok? Recommended charging curves for Li-Ion batteries go from a constant current to a constant voltage charge. So, reducing the charging current is an inherent feature of the charger. Could this be the reason for the BQ not to accept the cycle as valid? (I would assume, the battery monitor would rather monitor, "as is" instead of insisting of "having an attitude").

    Changing parameters in the BQeasy configuration often produces a runtime error when writing to the BQ. What is "runtime error 6, overflow " indicating? I would like to make the configuration, that I think suits best my setup. But how can I, if the software doesn't tell me, where the problems with my parameters is?

    As temperature seems to be an issue, can the max. allowed temperature limit be changed, after the battery has been fully charged, or do I need to discharge / charge all the way again? (Charging time, waiting time, discharging time, waiting time: 2 working days...).

    Is there a way to speed things up somehow? I have seen, the BQ is counting relaxation time, charging time etc. Can the BQ be fooled, to go with a reduced waiting time? Or does it insist on the very last second? I can go with a reduced accuracy of capacity prediction, but I need a sucess now! Is there a way to force the cycle count to 1, if I know the battery is actually full?

    Our charger is reducing charge (tickle charge) to a few 100 µA. Is this low enough for the BQ to detect a full battery?

    It seems like the voltage measurements are sensitive enough to detect changes of 4µV.  When discharging in a real-life device, some digital noise on the power paths is a common issue. Could that noise be a reason for the problem?

    Termination voltage from the charger is nominally 4100mV. Accuracy is +/-50mV approx. Should I reduce this value in the configuration to make sure, this voltage is achieved in every circumstance?

    Thanks for your help!

    Phil

     

  • 0 in reply to dMax
    Prodigy 165 points

    I'm experiencing the very same problems here with BQ27510-G1. And after just a few weeks, we seem to be lucky compared to others trying "3-4 months" already ;-)

    Cycle update doesn't change either. Not even to a 1. And it doesn't even give the measured capacity.

    It would be very helpfull, if the device (or software) could give a hint, of why it didn't want to accept a valid cycle. Just stating "didn't work" (my translation of the bit not changing to a 1) leaves me to making wild guesses about possible reasons. And try again and again. Maybe a future improvement of the firmware / BQeasy-software could detail on the reasons. It then would more deserve the name "BQeasy "...

    As David has been emphasizing, the charge and discharge currents should be around C/2 and C/5. This would require my charger to charge with 3000mA. Our charger simply doesn't allow such high currents (max power dissipation!). Is this really an issue? Is a 1000mA charge ok? Recommended charging curves for Li-Ion batteries go from a constant current to a constant voltage charge. So, reducing the charging current is an inherent feature of the charger. Could this be the reason for the BQ not to accept the cycle as valid? (I would assume, the battery monitor would rather monitor, "as is" instead of insisting of "having an attitude").

    Changing parameters in the BQeasy configuration often produces a runtime error when writing to the BQ. What is "runtime error 6, overflow " indicating? I would like to make the configuration, that I think suits best my setup. But how can I, if the software doesn't tell me, where the problems with my parameters is?

    As temperature seems to be an issue, can the max. allowed temperature limit be changed, after the battery has been fully charged, or do I need to discharge / charge all the way again? (Charging time, waiting time, discharging time, waiting time: 2 working days...).

    Is there a way to speed things up somehow? I have seen, the BQ is counting relaxation time, charging time etc. Can the BQ be fooled, to go with a reduced waiting time? Or does it insist on the very last second? I can go with a reduced accuracy of capacity prediction, but I need a sucess now! Is there a way to force the cycle count to 1, if I know the battery is actually full?

    Our charger is reducing charge (tickle charge) to a few 100 µA. Is this low enough for the BQ to detect a full battery?

    It seems like the voltage measurements are sensitive enough to detect changes of 4µV.  When discharging in a real-life device, some digital noise on the power paths is a common issue. Could that noise be a reason for the problem?

    Termination voltage from the charger is nominally 4100mV. Accuracy is +/-50mV approx. Should I reduce this value in the configuration to make sure, this voltage is achieved in every circumstance?

    Thanks for your help!

    Phil

     

  • 0 in reply to Phil54870
    TI__Intellectual 2100 points

    Hello Phil,

    I've tried to address each of your questions:

    --Usually when the Update_Status doesn't even get set to '1', this means that the gauge didn't learn a new capacity for the battery, which is the first step.  In order to get a new capacity, you have to make sure that you are charging from a completely discharged condition all the way up to the full-charge condition.  First, make sure that you discharge your cell all the way to the termination voltage.  Then, charge your battery up to the point that it is full.  This is where the problem usually lies.  For Li-Ion, we use a CC/CV profile.  You need to make sure that the charger continues to charge for a period of time AFTER it meets the taper current condition (set in step 2 of bqEASY).  This way, the FC bit will be set, and the gauge can learn a new QMax.  If the FC bit is not set after your charge, you will not learn. 

    Note that your charger voltage is 4.1V.  make sure that this is reflected in your bqEASY settings.  One of the termination conditions is that the battery have a voltage within 100mV of the charger voltage.  If your bqEASY settings have it left at 4.2V, then this will never happen. 

    --With respect to charge/discharge rates: the C/2, C/5 guideline is really a maximum allowable charge/discharge rate.  If you charge at less than C/2 or discharge at less than C/5, this is really not a problem.  (In fact, it is arguably slightly better, but it takes a much longer time). 

    --I have actually never seen the 'runtime error 6: overflow'.  Could you send me some details on how/when this happens?  It might also help if you could post/send me your bqEASY project file or configuration settings. You might be writing something that is out of range.

    --I'm a little confused by your question on temperature.  You have a flash setting that you program a  max/min charge and discharge temperature.  This is generally set during step 2 of bqEASY and then left alone.

    --Unfortunately, the process really cannot be sped up very much.  The low (C/5, C/2) currents are needed so that the gauge can get an accurate picture of the battery's behavior.  The relaxation period time is also necessary because the gauge must wait for the battery voltage to stabilize. 

    --Your charger should be OK in terms of current, just make sure that your charging voltage is set to 4100mV in bqEASY, and the taper current is set to a reasonably high current (~50-100mA is typical depending on application).  Note that you cannot set the taper current below 1mA.  Trickle charging to 100uA is OK, but make sure that the taper current is set well above this value.

    --The voltage measurement is heavily filtered, and should not be sensitive to digital noise in our experience.

    --Setting the charge voltage to 4100mV is OK.  This means that the gauge will be looking for the taper current condition between 4 and 4.1 V to indicate termination of charge.

    Let me know if this helps.

     

    Cheers,

    Charles

  • 0 in reply to Charles Herder
    Prodigy 165 points

    Hello Charles,

     thanks for your answer.

    -- This is what I tried to do. I discharged the battery down to 3400mV (below this voltage, my system will shut down anyway, so this is the lowest voltage the battery will see). I gave it some relaxing time and then started the cycle. If wouldn't want to post the logfile here, it's a bit lengthy ;-)  If you give me your email-adr, I can send it.

    I indeed reduced the termination voltage to 4100mV in the configuration. After it reached 4080mV, I forced the charger to shutdown, reducing charging current to 0. I then gave the BQ another 40 mins to "think it over".  Taper voltage is 100mV, so it should have seen a full state.

    -- You said, the charger needs to charge, even after the current dropped below the taper current. So, this means, I_charge>0 but < I_taper? How long does it need to see this? How large must this current be?

    -- Here's my configuration:

    [Device]
    Type=0510
    Version=0112
    DFI Filname=C:\Program Files\Texas Instruments\bq Evaluation Software\Plugins\Device Defaults\bq27510_1_12.dfi
    [Setup]
    1A_Proj_Name.Project_Name=bqn8mare
    [Project]
    Name=bqn8mare
    [Completion]
    1B=True
    2A=True
    2B=True
    2C=True
    2D=True
    2E=True
    2F=True
    2G=True
    2H=True
    3A=True
    3B=True
    3C=True
    3D=True
    3E=True
    3F=True
    4A=True
    4B=True
    4C=True
    [Configuration]
    2A_Cell_Char.Num_Parallel_Cells=1
    2A_Cell_Char.Nom_Cell_Capacity=5600
    2A_Cell_Char.Min_Cell_Vltg=3000
    2B_Chg_Params.Max_Chg_Cell_Vltg=4100
    2B_Chg_Params.Max_Chg_Taper_Curr=100
    2B_Chg_Params.Max_Chg_Temperature=80
    2B_Chg_Params.Min_Chg_Temperature=-5
    2C_Dsg_Params.Min_Dsg_Cell_Vltg=3400
    2C_Dsg_Params.Max_Dsg_Temperature=70
    2C_Dsg_Params.Max_Steady_Dsg_Current=1200
    2C_Dsg_Params.Min_Active_Dsg_Current=150
    2C_Dsg_Params.Initial_Standby_Current=10
    2C_Dsg_Params.SOC1_THRSH=150
    2C_Dsg_Params.SOCF_SET=90
    2C_Dsg_Params.SOCF_CLEAR=120
    2D_Reserve_Capacity.Capacity=0
    2D_Reserve_Capacity.Capacity_Units_mAh?=True
    2E_Load_Characteristic.Is_Constant_Current?=True
    2F_Application_Configuration.PFC_Code=0
    2F_Application_Configuration.Bat_Low_Active_Low?=False
    2F_Application_Configuration.Bat_Gd_Active_Low?=True
    2F_Application_Configuration.LOW_GD_FN=0
    2G_Rem_Capacity_Method.Is_Constant_Load?=True
    2H_Misc_Info.CurrentSenseResistor=10
    2H_Misc_Info.ThermistorConfig=1
    2H_Misc_Info.Int_Focv=0
    2H_Misc_Info.Int_Brem=0
    2H_Misc_Info.Soc_Int_Pol=-1
    2H_Misc_Info.OpcfgB_Wrtemp=-1
    2H_Misc_Info.OpcfgB_Bie=-1

    -- As the temperature window seems a concern, I set the limits as wide as possible. I'm using the internal temperature sensor, as the external sensor is connected to the battery charger (I'm aware, that this will reduce accuracy later). Internal temperature of  the BQ never went beyond 47°C.

    -- Is there a way to work with an adjustable power supply in order to simulate a real life battery? While this wouldn't give any meaningfull impedance values, it could be a way to get a success in the cycle procedure. I start losing faith, I'll ever see cycle count turn to 2 before xmas...

    -- And again: Why doesn't the software SAY, what is wrong? If I tell BQeasy, the battery is full, it IS full. If the BQ believes, some condition is not yet met, I expect it to just tell me.
    Like "temperature too high", "cell voltage hasn't reached maximum value", "taper current too high", "cell voltage hasn't stabilized". Is this really asked too much?

    -- If TI believes, it's all so easy, would it offer a service to obtain the golden configuration for us? We are willing to pay for it!

     

    Regards,

    Phil

     

  • 0 in reply to Phil54870
    Prodigy 165 points

     ...another day over, another day hoping in vain. The flags VOK and QEN keep staying zero.

    Unless you can point out a reason in my configuration, I'm giving up. I now understand, why competitors advertise their component with "no training cycle needed"...

    Please email a configuration, that you think will work for my battery data. I'm willing to test everything, if there is a realistic chance, the counter will finally go upwards.

    Regards, Phil

  • 0 in reply to Phil54870
    TI__Expert 4050 points

    hi Phil,

    The screen shot you attached has show VOK and QEN bits are not set. Have you sent IT enable command?

    I assume you already went through the app note: http://focus.ti.com/lit/an/slua544/slua544.pdf  on how to generate golden image. No training cycle gauge is low end gauge and will not provide the high accuracy unless you want to go that route. If you can attach your gg file I will be happy to take a look. We have many customers who decided to use TI gauge for the best performance they are looking for.

    Thanks

    Ming

  • 0 in reply to Ming Yu
    Prodigy 165 points

    Hello Ming,

     I can see, those bits are not set. The key question is: why not? Of course, I have sent the IT command on the BQeasy.

    Are you sure, I should include the logfile in this post? I've been logging the whole day and it is LONG. Maybe you can contact me by email, so I can send you the logfile that way.

    Yes, I have read that app note. However, it still leaves my questions open.

    I'm amongst the customers, who decided to use a TI gas gauge in order to get best perfomance - that's, why I have it on my PCB now. However, I'm not convinced, this was a good decision...

    Regards, Phil

     

  • 0 in reply to Phil54870
    TI__Expert 4050 points

    Hi Phil,

    I actually is looking for DF dump (gg file) or DFI file so that I can see what has been programmed into the gauge. How do I contact you? May be a short phone call can clear things up.

     

    Thanks

    Ming

  • 0 in reply to Ming Yu
    Prodigy 165 points

    Hello again,

     here's my logfile from the last charging cycle.

    Regards,

    Phil

  • 0 in reply to Phil54870
    Intellectual 260 points

    Sorry to reply so late but when I was looking for solutions to my problem, this post help me but didn't alert me on another problem.

    BAT_DET (battery insertion) must be set. See http://e2e.ti.com/support/power_management/battery_management/f/180/p/315063/1096852.aspx#1096852