• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 63 subscribers
  • Views 1138 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.

BQ28Z610: Firmware bq28z610_v0_20_build_25

Maurizio Bonelli
Expert 1400 points
Part Number: BQ28Z610
Other Parts Discussed in Thread: BQSTUDIO, BQ40Z50-R2

Hello everybody.

Today I have been reviewing my design and so I checked the site to see if any update has been deployed.

I've found the bq28z610_v0_20_build_25 released and then I have installed it onto one sample for testing.

At the first tentative, everything seems nice about the parameters I can check in short time, but one behaviour appears different from the previous.

My software checks the satus of the bit DSG (bit 6 of the BatteryStatus()) to signal charge or discharge status and in this version it is needed 60 seconds or more to detect the change of the status from DISCHARGE to CHG while about 1 second for CHARGE to DISCHARGE status.

In the previous v17, the time to change was approximately 1 second in both status.

The DSG bit in BatteryStatus() and in GaugingStatus() are not synchronized.

Is it something embedded in the new release of FW or do I have to set some parameters I do not know at the present time?

Additionallly, in this release there are several commands that appear in bqStudio: SMOOTH_SYNC, MFC_ENABLE_A  & _B and MFC_DISABLE but no documentation has yet been released for those new commands. 

Pheraps, are they related with the issue I have described above?

Thanks a lot for the quick reply.... 

  

  • 0
    Expert 1400 points
    Hello again...
    I am so sorry, the problem with DSG was real but probably was caused by a not perfect programming, also if I cannot explain it: programming again from the original .srec and adding again chemistry and .gg file (same as before) the BQ started to act as ever and DSG bits in BatteryStatus() and GaugingStatus() are exactly the same values.
    I do not understand what could be happened but I pass over and go ahead with my tests.
    Thank again to who has eventually done further tests due my previous message.

    In any case, I would like to know what the new commands do (no documentation at all, yet).
    thanks
  • 0 in reply to Maurizio Bonelli
    TI__Mastermind 42535 points
    Hi Maurizio

    Smooth Sync syncs the remaining capacity to true remaining cap and Full Charge Capacity to True Full Charge Capacity when smoothing is enabled. It's an advanced feature for RSOC smoothing.

    MFC stands for manual fet control. This is an emergency shutdown feature that was added and is similar to the MFC feature present in the bq40z50-R2 TRM. Please refer to that.
  • 0 in reply to Batt
    Expert 1400 points

    Thanks Batt.

    Then it seems the use of smooth_sync sounds better, but I would like to have a suggestion from you, from high experienced one.

    The battery will be used into a portable equipment, then after the factory shipping it will be unlikely discharged up to term_voltage while it will be surely charged up to full charge. Having this situation on field, do you suggest to enable the smooth_sync or don't?

    Are there any literature I can study which helps me to understand better?

    Thanks a lot