• State Resolved
  • Locked Locked
  • Replies 19 replies
  • Subscribers 63 subscribers
  • Views 5394 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.

BQ34Z100-G1: Programming a new Chemical ID into the BQ34Z100-G1 from an external file

Alan Ogburn73
Intellectual 290 points
Part Number: BQ34Z100-G1
Other Parts Discussed in Thread: BQ78350, BQSTUDIO, BQ34Z100

Hi,

We have used the online tool to get a new Chemical ID for our battery, which is 2133.

In Battery Management Studio, Chemistry programming,  Chem ID 2133 is not available.  There is a button "Update Chemistry from an External File" which I have tried to use. I have downloaded sluc564do containing ChemUpdate597, and sluc261 containing various files, which seems to include the chemistry for ID2133.  Unfortunately I don't know how to use this information. Do I need to run "Chemical Updater-597-windows-installer"?

I should be grateful for any guidance on getting Chemical ID2133 into the BQ34Z100-G1

Thanks,

Alan Ogburn

  • 0
    TI__Guru* 76230 points
    Hello Alan,
    Copy those files contained in the chemupdater www.ti.com/.../sluc564 and replace the exiting files in the directory of your own computer below with those copied and you will be able to see chem id 2133 to program on the gauge.

    C:\ti\BatteryManagementStudio\chemistry

    I hope this helps
    thanks
    Onyx
  • 0 in reply to Onyx Ahiakwo
    Intellectual 290 points

    Hi Onyx,

    Thanks for the instructions, but please see the screen shots above as something hasn't worked.

    As you can see, the new files in the Chemistry folder copied across OK, but when I open BQ studio and go into chemistry, no IDs are listed at all.

    I tried some simple things like restarting BQ studio and restarting the computer but they make no difference.

    Regards,

    Alan

  • 0 in reply to Onyx Ahiakwo
    Intellectual 290 points
    Hi Onyx, it didn't work and I have just posted a reply with some screen shots illustrating what happens.
    I look forward to hearing back from you.
    Thanks,
    Alan
  • 0 in reply to Alan Ogburn73
    TI__Guru* 76230 points
    Hi Alan,
    Your screen shot post is showing the bq78350. That device uses CEDV and does not use chem ids so you shouldn't try programming a chem id on there.

    thanks
    Onyx
  • 0 in reply to Onyx Ahiakwo
    Intellectual 290 points

    Hi Onyx,

    You are right of course! We have both chips in our circuit and I was plugged into the wrong one.

    I was certain then, that when I connected to the BQ34Z100G1 it would all work.  But it still didn't.

    Delving into it a bit deeper, it seems we need bqstudio 1.3.54.1 or higher, and we only have bqstudio 1.3.54.

    So I am going to download the latest version and see where we go from there.

    See attached screen shot, this time connected to the BQ34Z100-G1.

    Thanks,

    Alan

  • 0 in reply to Alan Ogburn73
    Intellectual 290 points

    Hello again Onyx,

    We installed bqstudio1.3.54.1 and now the new chemistry files from ChemUpdate597 appear as expected.

    Thank you for your help.

    Regards,

    Alan

  • 0 in reply to Alan Ogburn73
    Intellectual 290 points

    Hi,

    With the new Chemistry ID2133, we still get poor accuracy for battery capacity, with the full charge being underestimated by about 15%.

    The attached plots show data recorded from the BQ34Z100-G1 during a discharge > relaxation > calibration cycle.  Of particular interest is the delay in registering the start of charging.  The blue trace is the integral of current measured by the BQ chip.

    On the second page is the charge recorded by the Digatron being used to charge / discharge the battery during the cycle.  It can be seen that there is very good agreement between the BQ integrated current and the Digatron record.  This means that the problem is not due to poor current calibration of the BQ34Z100.

    Plots BatA4 13-10-2017.docx

    Could you please give an idea what is going wrong here.  Changing the chemistry has made no significant difference.

  • 0 in reply to Alan Ogburn73
    TI__Guru* 76230 points
    Hi Alan,

    After changing the chem id, you must run a learning cycle before the gauge can be accurate.

    thanks
    Onyx
  • 0 in reply to Onyx Ahiakwo
    Intellectual 290 points

    Hi Onyx,

    The plots I sent you were the result of a learning cycle with the new Chem ID.

    The procedure I followed was:

    1. Discharge the battery at C/5 (7A) to its minimum voltage with taper current of 300mA
    2. Relax battery for a few hours
    3. Select IT_ENABLE to enable impedance tracking
    4. Charge the battery at C/5 (7A) to its maximum voltage with taper current of 100mA
    5. Relax battery for 3 hours
    6. Discharge the battery at C/5 (7A) to its minimum voltage with taper current of 300mA

    I think this procedure conforms to the application report SLUA597 - 'Achieving The Successful Learning Cycle'

    This was the second cycle the battery had been through with the new chemical ID, and the capacity error is around 15%.

    What puzzles me about the plots is that 'RemCap' does not start to register charge until about 5Ah have already gone into the battery, and this discrepancy is about the same amount as the total capacity error observed.  Please look at the plots closely, and I think you will see what I mean.

    Thanks,

    Alan

  • 0 in reply to Alan Ogburn73
    TI__Guru* 76230 points
    Hi Alan

    Are your batteries lead acid or Li-ion. The expected error in accuracy of the gauge is 15% or less for lead acid.

    IF you are however using lithium ion cells and max error is at 15%, i would recommend you redo your test following the steps below:

    - Program the defualt srec.
    -Configure the gauge with your settings
    -program the chem id
    -Enable IT
    -Issue a reset command
    -discharge to empty using c/7
    -reset 5 hours
    -charge to full and make sure FC gets set. rate doesn't matter
    -Rest 2 hours
    -discharge to empty using c/7
    -rest 5 hours.

    pls make sure to log using bqstudio incase learning still fails. Send the log file and gg file at the end of learning. pls makse to Log continuouly and not in batches.

    thanks
    Onyx


    -
  • 0 in reply to Onyx Ahiakwo
    Intellectual 290 points

    Hi Onyx,

    Firstly, sincere apologies for not getting back to you sooner with the data.

    I ran a learning cycle following your instructions to the letter, and we got a good result - better than 1% error. The log file and .gg file for this are attached.

    Fullscreen BatA4_postcal_20-10-2017_bq34z100G1.gg.csv.txt Download 
    * Texas Instruments Data Flash File
* File created Fri Oct 20 09:16:56 2017
*
* Device Number 100
* Firmware Version 0.16
* Build Number not available
* Order Number not available
*
* bqz Device Number 100
* bqz Firmware Version 0.16
* bqz Build Number 17
*
* Field Order: Class name, Subclass name, Parameter name, Parameter Value, Display Units
"Configuration","Safety","OT Chg","55.0","1degC"
"Configuration","Safety","OT Chg Time","2","Seconds"
"Configuration","Safety","OT Chg Recovery","50.0","1degC"
"Configuration","Safety","OT Dsg","60.0","1degC"
"Configuration","Safety","OT Dsg Time","2","Seconds"
"Configuration","Safety","OT Dsg Recovery","55.0","1degC"
"Configuration","Charge Inhibit Cfg","Chg Inhibit Temp Low","0","1degC"
"Configuration","Charge Inhibit Cfg","Chg Inhibit Temp High","45.0","1degC"
"Configuration","Charge Inhibit Cfg","Temp Hys","5.0","1degC"
"Configuration","Charge","Suspend Low Temp","-5.0","1degC"
"Configuration","Charge","Suspend High Temp","55.0","1degC"
"Configuration","Charge","Pb EFF Efficiency","100","%"
"Configuration","Charge","Pb Temp Comp","24.960","%"
"Configuration","Charge","Pb Drop Off Percent","96","%"
"Configuration","Charge","Pb Reduction Rate","10.000","%"
"Configuration","Charge Termination","Taper Current","100","mAmp"
"Configuration","Charge Termination","Min Taper Capacity","25","mAmpHr"
"Configuration","Charge Termination","Cell Taper Voltage","100","mVolt"
"Configuration","Charge Termination","Current Taper Window","40","Seconds"
"Configuration","Charge Termination","TCA Set %","99","Percent"
"Configuration","Charge Termination","TCA Clear %","95","Percent"
"Configuration","Charge Termination","FC Set %","100","Percent"
"Configuration","Charge Termination","FC Clear %","98","Percent"
"Configuration","Charge Termination","DODatEOC Delta T","10.0","1degC"
"Configuration","Charge Termination","NiMH Delta Temp","3.0","1degC"
"Configuration","Charge Termination","NiMH Delta Temp Time","180","Seconds"
"Configuration","Charge Termination","NiMH Hold Off  Time","100","Seconds"
"Configuration","Charge Termination","NiMH Hold Off Current","240","mAmp"
"Configuration","Charge Termination","NiMH Hold Off  Temp","25.0","1degC"
"Configuration","Charge Termination","NiMH Cell Negative Delta Volt","17","mVolt"
"Configuration","Charge Termination","NiMH Cell Negative Delta Time","16","Seconds"
"Configuration","Charge Termination","NiMH Cell Neg Delta Qual Volt","4200","mVolt"
"Configuration","Data","Manufacture Date","2017-10-20","Day + Mo*32 + (Yr -1980)*256"
"Configuration","Data","Serial Number","00a4","hex"
"Configuration","Data","Cycle Count","0","Count"
"Configuration","Data","CC Threshold","9000","mAmpHr"
"Configuration","Data","Max Error Limit","100","%"
"Configuration","Data","Design Capacity","18425","MilliAmpHour"
"Configuration","Data","Design Energy","6633","MilliWattHour"
"Configuration","Data","SOH Load I","-400","MilliAmp"
"Configuration","Data","Cell Charge Voltage T1-T2","4100","mV"
"Configuration","Data","Cell Charge Voltage T2-T3","4250","mV"
"Configuration","Data","Cell Charge Voltage T3-T4","4150","mV"
"Configuration","Data","Charge Current T1-T2","50","Percent"
"Configuration","Data","Charge Current  T2-T3","50","Percent"
"Configuration","Data","Charge Current  T3-T4","50","Percent"
"Configuration","Data","JEITA T1","0","degC"
"Configuration","Data","JEITA T2","10","degC"
"Configuration","Data","JEITA T3","45","degC"
"Configuration","Data","JEITA T4","60","degC"
"Configuration","Data","Design Energy Scale","10","Number"
"Configuration","Data","Device Name","bq34z100-G1","-"
"Configuration","Data","Manufacturer Name","Texas Inst.","-"
"Configuration","Data","Device Chemistry","LION","-"
"Configuration","Discharge","SOC1 Set Threshold","1000","mAh"
"Configuration","Discharge","SOC1 Clear Threshold","1500","mAh"
"Configuration","Discharge","SOCF Set Threshold","500","mAh"
"Configuration","Discharge","SOCF Clear Threshold","750","mAh"
"Configuration","Discharge","Cell BL Set Volt Threshold","2400","mVolt"
"Configuration","Discharge","Cell BL Set Volt Time","2","Seconds"
"Configuration","Discharge","Cell BL Clear Volt Threshold","2500","mVolt"
"Configuration","Discharge","Cell BH Set Volt Threshold","4300","mVolt"
"Configuration","Discharge","Cell BH Volt Time","2","Seconds"
"Configuration","Discharge","Cell BH  Clear Volt Threshold","4200","mVolt"
"Configuration","Discharge","Cycle Delta","0.05","%"
"Configuration","Manufacturer Data","Pack Lot Code","0000","hex"
"Configuration","Manufacturer Data","PCB Lot Code","0000","hex"
"Configuration","Manufacturer Data","Firmware Version","0000","hex"
"Configuration","Manufacturer Data","Hardware Revision","0000","hex"
"Configuration","Manufacturer Data","Cell Revision","0000","hex"
"Configuration","Manufacturer Data","DF Config Version","0000","hex"
"Configuration","Lifetime Data","Lifetime Max Temp","30.0","1degC"
"Configuration","Lifetime Data","Lifetime Min Temp","20.0","1degC"
"Configuration","Lifetime Data","Lifetime Max Chg Current","0","mAmp"
"Configuration","Lifetime Data","Lifetime Max Dsg Current","0","mA"
"Configuration","Lifetime Data","Lifetime Max Pack Voltage","1120","20mV"
"Configuration","Lifetime Data","Lifetime Min Pack Voltage","1225","20mV"
"Configuration","Lifetime Temp Samples","LT Flash Cnt","0","Count"
"Configuration","Registers","Pack Configuration","a9e1","flags"
"Configuration","Registers","Pack Configuration B","af","flags"
"Configuration","Registers","Pack Configuration C","30","flags"
"Configuration","Registers","LED_Comm Configuration","03","flags"
"Configuration","Registers","Alert Configuration","0000","flags"
"Configuration","Registers","Number of series cell","7","num"
"Configuration","Lifetime Resolution","LT Temp Res","1.0","1degC"
"Configuration","Lifetime Resolution","LT Cur Res","100","mA"
"Configuration","Lifetime Resolution","LT V Res","1","20mV"
"Configuration","Lifetime Resolution","LT Update Time","60","Seconds"
"Configuration","LED Display","LED Hold Time","4","Num"
"Configuration","Power","Flash Update OK Cell Volt","2800","mVolt"
"Configuration","Power","Sleep Current","10","mAmp"
"Configuration","Power","FS Wait","0","Seconds"
"System Data","Manufacturer Info","Block A 0","00","hex"
"System Data","Manufacturer Info","Block A 1","00","hex"
"System Data","Manufacturer Info","Block A 2","00","hex"
"System Data","Manufacturer Info","Block A 3","00","hex"
"System Data","Manufacturer Info","Block A 4","00","hex"
"System Data","Manufacturer Info","Block A 5","00","hex"
"System Data","Manufacturer Info","Block A 6","00","hex"
"System Data","Manufacturer Info","Block A 7","00","hex"
"System Data","Manufacturer Info","Block A 8","00","hex"
"System Data","Manufacturer Info","Block A 9","00","hex"
"System Data","Manufacturer Info","Block A 10","00","hex"
"System Data","Manufacturer Info","Block A 11","00","hex"
"System Data","Manufacturer Info","Block A 12","00","hex"
"System Data","Manufacturer Info","Block A 13","00","hex"
"System Data","Manufacturer Info","Block A 14","00","hex"
"System Data","Manufacturer Info","Block A 15","00","hex"
"System Data","Manufacturer Info","Block A 16","00","hex"
"System Data","Manufacturer Info","Block A 17","00","hex"
"System Data","Manufacturer Info","Block A 18","00","hex"
"System Data","Manufacturer Info","Block A 19","00","hex"
"System Data","Manufacturer Info","Block A 20","00","hex"
"System Data","Manufacturer Info","Block A 21","00","hex"
"System Data","Manufacturer Info","Block A 22","00","hex"
"System Data","Manufacturer Info","Block A 23","00","hex"
"System Data","Manufacturer Info","Block A 24","00","hex"
"System Data","Manufacturer Info","Block A 25","00","hex"
"System Data","Manufacturer Info","Block A 26","00","hex"
"System Data","Manufacturer Info","Block A 27","00","hex"
"System Data","Manufacturer Info","Block A 28","00","hex"
"System Data","Manufacturer Info","Block A 29","00","hex"
"System Data","Manufacturer Info","Block A 30","00","hex"
"System Data","Manufacturer Info","Block A 31","00","hex"
"Gas Gauging","IT Cfg","Load Select","1","Number"
"Gas Gauging","IT Cfg","Load Mode","0","Number"
"Gas Gauging","IT Cfg","Res Current","10","mAmp"
"Gas Gauging","IT Cfg","Max Res Factor","50","num"
"Gas Gauging","IT Cfg","Min Res Factor","1","num"
"Gas Gauging","IT Cfg","Ra Filter","500","num"
"Gas Gauging","IT Cfg","Min PassedChg NiMH-LA 1st Qmax","50","%"
"Gas Gauging","IT Cfg","Maximum Qmax Change","100","%"
"Gas Gauging","IT Cfg","Cell Terminate Voltage","2500","mVolt"
"Gas Gauging","IT Cfg","Cell Term V Delta","200","mVolt"
"Gas Gauging","IT Cfg","ResRelax Time","500","Seconds"
"Gas Gauging","IT Cfg","User Rate-mA","0","MilliAmp"
"Gas Gauging","IT Cfg","User Rate-Pwr","0","mW/cW"
"Gas Gauging","IT Cfg","Reserve Cap-mAh","0","MilliAmpHour"
"Gas Gauging","IT Cfg","Reserve Energy","0","mWh/cWh"
"Gas Gauging","IT Cfg","Max Scale Back Grid","4","num"
"Gas Gauging","IT Cfg","Cell Min DeltaV","0","mVolt"
"Gas Gauging","IT Cfg","Ra Max Delta","15","%"
"Gas Gauging","IT Cfg","Design Resistance","42","mOhms"
"Gas Gauging","IT Cfg","Reference Grid","4","-"
"Gas Gauging","IT Cfg","Qmax Max Delta %","10","mAmpHour"
"Gas Gauging","IT Cfg","Max Res Scale","32000","Num"
"Gas Gauging","IT Cfg","Min Res Scale","1","Num"
"Gas Gauging","IT Cfg","Fast Scale Start SOC","10","%"
"Gas Gauging","IT Cfg","Charge Hys V Shift","40","mVolt"
"Gas Gauging","IT Cfg","Smooth Relax Time","1000","s"
"Gas Gauging","Current Thresholds","Dsg Current Threshold","60","mAmp"
"Gas Gauging","Current Thresholds","Chg Current Threshold","75","mAmp"
"Gas Gauging","Current Thresholds","Quit Current","40","mAmp"
"Gas Gauging","Current Thresholds","Dsg Relax Time","60","Seconds"
"Gas Gauging","Current Thresholds","Chg Relax Time","60","Seconds"
"Gas Gauging","Current Thresholds","Cell Max IR Correct","400","mV"
"Gas Gauging","State","Qmax Cell 0","18425","mAmpHr"
"Gas Gauging","State","Cycle Count","0","num"
"Gas Gauging","State","Update Status","00","num"
"Gas Gauging","State","Cell V at Chg Term","4200","mVolt"
"Gas Gauging","State","Avg I Last Run","-299","mAmp"
"Gas Gauging","State","Avg P Last Run","-1131","MilliWattHour"
"Gas Gauging","State","Cell Delta Voltage","2","mVolt"
"Gas Gauging","State","T Rise","20","Num"
"Gas Gauging","State","T Time Constant","1000","Num"
"Ra Tables","Ra0 Table","Ra Flag","ff55","Hex"
"Ra Tables","Ra0 Table","Ra 0","105","Num"
"Ra Tables","Ra0 Table","Ra 1","100","Num"
"Ra Tables","Ra0 Table","Ra 2","113","Num"
"Ra Tables","Ra0 Table","Ra 3","143","Num"
"Ra Tables","Ra0 Table","Ra 4","98","Num"
"Ra Tables","Ra0 Table","Ra 5","97","Num"
"Ra Tables","Ra0 Table","Ra 6","108","Num"
"Ra Tables","Ra0 Table","Ra 7","89","Num"
"Ra Tables","Ra0 Table","Ra 8","86","Num"
"Ra Tables","Ra0 Table","Ra 9","85","Num"
"Ra Tables","Ra0 Table","Ra 10","87","Num"
"Ra Tables","Ra0 Table","Ra 11","90","Num"
"Ra Tables","Ra0 Table","Ra 12","110","Num"
"Ra Tables","Ra0 Table","Ra 13","647","Num"
"Ra Tables","Ra0 Table","Ra 14","1500","Num"
"Ra Tables","Ra0x Table","Ra Flag","ffff","Hex"
"Ra Tables","Ra0x Table","Ra 0","105","Num"
"Ra Tables","Ra0x Table","Ra 1","100","Num"
"Ra Tables","Ra0x Table","Ra 2","113","Num"
"Ra Tables","Ra0x Table","Ra 3","143","Num"
"Ra Tables","Ra0x Table","Ra 4","98","Num"
"Ra Tables","Ra0x Table","Ra 5","97","Num"
"Ra Tables","Ra0x Table","Ra 6","108","Num"
"Ra Tables","Ra0x Table","Ra 7","89","Num"
"Ra Tables","Ra0x Table","Ra 8","86","Num"
"Ra Tables","Ra0x Table","Ra 9","85","Num"
"Ra Tables","Ra0x Table","Ra 10","87","Num"
"Ra Tables","Ra0x Table","Ra 11","90","Num"
"Ra Tables","Ra0x Table","Ra 12","110","Num"
"Ra Tables","Ra0x Table","Ra 13","647","Num"
"Ra Tables","Ra0x Table","Ra 14","1500","Num"
"Calibration","Data","CC Gain","2.552","mohm"
"Calibration","Data","CC Delta","2.547","mohm"
"Calibration","Data","CC Offset","-1511","num"
"Calibration","Data","Board Offset","-22","num"
"Calibration","Data","Int Temp Offset","0","degC"
"Calibration","Data","Ext Temp Offset","0","degC"
"Calibration","Data","Voltage Divider","34450","mVolt"
"Calibration","Current","Deadband","5","mAmp"
"Security","Codes","Sealed to Unsealed","36720414","hex"
"Security","Codes","Unsealed to Full","ffffffff","hex"
"Security","Codes","Authen Key3","01234567","hex"
"Security","Codes","Authen Key2","89abcdef","hex"
"Security","Codes","Authen Key1","fedcba98","hex"
"Security","Codes","Authen Key0","76543210","hex"

    bq_Bat_A4_discharge_and_learning_23-10-2017.log

    I have also run a separate charge/discharge cycle using the same battery after the successful learning cycle, with a stepped discharge characteristic and that has shown up some problems.  Looking at the data, it looks as though the battery thinks it is exhausted if discharge current stops for a while when its voltage is lower than 3.5V per cell.  the data for that is also attached, together with a record of battery capacity recorded by our Digatron simultaneously. 

    I don't know if the voltage at which the battery decides it is exhausted is determined by the Chemical ID, or is in a parameter that we can set separately ourselves.

    Finally, current calibration in the bq34z100 has a factor of 2, i.e. indicated 500mA is really 1000mA.

    BatA4 Stepped discharge 31-10-2017.pdfbq_Bat_A4_chg_then_stepped_dsg_31-10-2017.log

     

  • 0 in reply to Alan Ogburn73
    TI__Guru* 76230 points
    Hi Alan,
    I reviewed your files and it was difficult to come to a conclusion as to what must have gone wrong.

    The gauge did indeed run a rem cap simulation while the battery was at rest that caused the the drop from around 20% to 1%. My suspicion is that the device learnt a large resistance value for the last set of resistance grid points the made the SOC drop.

    There are a few experiments i want you to run one after the other:
    -The first would be to reproduce this test to see if you can replicate the behaviour . Extract a gg file before you start the test and at the completion of the test. I want to check the average I last run and the resistance values to verify if a large wrong value was learnt by the device.
    -The second experiment would repeat the test but disable the DODWT flag in pack configuration B register and issue a reset command before you start the test to see if the issue occurs.
    --The third experiment would be to repeat the test but disable the VconsEN flag in pack configuration B register and issue a reset command before you start the test to see if the issue occurs.
    ---The last experiment would be to repeat the test but disable the FConven flag in pack configuration B register and issue a reset command before you start the test to see if the issue occurs.

    You can run all 4 of these tests concurrently on different packs to avoid delays. pls make sure to extract gg files before the tests begin for all four and after the tests complete.

    Let me know if you have questions

    thanks
    Onyx
  • 0 in reply to Onyx Ahiakwo
    Intellectual 290 points
    Hi Onyx,
    Thanks for the test instructions. I'm working through them and just have the results for the charge/discharge cycle with the DODWT flag disabled. For the next test you want me to disable the VconsEN flag.
    However, should I set the DODWT flag TRUE again first?
    Similarly, when I do the last test should I set VconsEN true when I disable FConven?
    Thanks,
    Alan
  • 0 in reply to Alan Ogburn73
    TI__Guru* 76230 points
    Hi Alan,
    Since we are trying to find which flag is the culprit, the others should be in the state they were when the issue occcured while the test in question has the necessary flag flipped.

    thanks
    Onyx
  • 0 in reply to Onyx Ahiakwo
    Intellectual 290 points

    Hi Onyx,

    I have at last got all the data together.

    In addition to the log files and gg files, I have plotted comparisons for each test illustrating RemCap from the bq34Z100 versus the ampere hours recorded by the Digatron. Each graph also shows bq34Z100 indicated current and Digatron current, which show that the bq current calibration is correct and the data are synchronised.

    I look forward to hearing back from you.

    Many thanks,

    Alan

    Test data for Onyx bq34Z100G1.zip

  • 0 in reply to Alan Ogburn73
    TI__Guru* 76230 points
    Hi Alan,
    Did any of the three test correct the issue you were seeing. Given it has been so long i don't recollect what the issue was. Can you explain what the problem was and see if any of the experiments you ran rectified the issue?
    thanks
    Onyx
  • 0 in reply to Onyx Ahiakwo
    Intellectual 290 points

    Hi Onyx,

    Did you receive the information I sent you on Friday (it was all in a zip file)?

    I ran all the test sequences with various flags disabled as instructed and sent you all the log files, before and after each test.

    The flags made very little difference.  What is happening is that the reported remaining capacity (RemCap) from the bq34Z100 is very low, even though the device is correctly reading the current.  The graphs I enclosed in my last message illustrate this very well.  We record current and charge using the Digatron, and I superimposed the Digatron results onto the bq34Z100 results in the graphs so we can make a direct comparison.

    So far we have programmed in the right chemistry (you helped me with this) and run learning cycles to your instructions.  The first learning cycle always looks OK with the correct capacity appearing in RemCap.  However, as soon as we start using the battery it inevitably puts in an incorrect step reduction in RemCap.  In high current discharges it will even switch RemCap to zero shortly after the start of discharging, rendering the fuel gauge completely useless.

    It seems to me that either there is a problem with the fuel gauge that we have unearthed (unlikely if lots of people are using it) or there is something fundamentally wrong with the settings.  I feel we really need your help in solving this problem.

    Please look at the data I sent you on Friday.  If you didn't receive it, please let me know and I'll resend it.

    Thanks,

    Alan

  • 0 in reply to Alan Ogburn73
    TI__Guru* 76230 points
    Hi Alan,
    Sorry i haven't been able to look into this further as i have been assinged other tasks. My colleague who owns support of this device will be reviewing your files and will get back to you mid next week. I will coordinate with him to see what we can figure out.

    thanks
    Onyx
  • 0 in reply to Onyx Ahiakwo
    Intellectual 290 points

    Hi Onyx,

    thanks for your continued support.  It is much appreciated.

    Alan