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.

WEBENCH®工具/ BQ78350-R1:In the overcharge of BQ78350, Cycle Count is suddenly updated to 655303;What should I do?

Part Number: BQ78350-R1
Other Parts Discussed in Thread: BQ78350, BQSTUDIO

Tool/software: WEBENCH® Design Tools

In the overcharge of BQ78350, Cycle Count is suddenly updated to 655303;What should I do?

  • The cycle count shouldn't change value like that . If you send the Reset command, do you still see the same value? I notice you have the 'Scan' button selected, maybe you are getting a bad reading on the SMBus due to lots of traffic on the bus.

    Matt
  • SMBus communication is good, and I find that when charging is approaching to full, the cycle count value will always change similarly. When waiting for charging to 100%, the value of FCC and Remaing Capacity will always be updated to 65535.I guess, charge to 100%!Maybe Remaing Capacity > FCC!I don't know if it has anything to do with that.
  • Did you modify the Cycle Count Percentage parameter?

    Here's how the CycleCount should work from the TRM:
    This read-word function returns the number of discharge cycles the battery has experienced. The value of CycleCount() increments when an accumulated discharge is more than Cycle Count Percentage of FullChargeCapacity() (if [CCT] = 1) or Design Capacity (if [CCT] = 0).
    NOTE: A minimum of 10% of Design Capacity change of the accumulated discharge is required for cycle count increment. This prevents an erroneous cycle count increment due to extremely low FullChargeCapacity().
  • Hello, I have not manually changed the Cycle Count Percentage parameter, which defaults to 90%.
    CycleCount mutations occur naturally during charging and discharging.It's strange!
  • Can you send me your dataflash settings. You can click the 'Export' button on the Data Memory screen of BQStudio to save this to a .gg file.
    Also, if you are able to capture a log (Click 'Start Log' on the Registers screen), it would be very helpful for debug.

    Thanks,
    Matt
  • I am not able to see why the Cycle Count would increment, but I do see some issues with the .gg file.

    -In the gg file, it shows that IPScale = 0x01. Make sure to scale all of you current settings in Data Memory with the new scaling. It looks like some of them are scaled, but not all of them. For example, the charge taper current is still 250mA which would be 2.5 A with the new scaling.
    - The protection for COV is set very low. There is no way to get to full charge because the over-voltage protection is set to turn off the charge FET at 3.7V.
    - The protection for CUV is set very high and is the same value as your setting for the EDV2 voltage. There should be no way for FCC to update or a qualified discharge to complete because your discharge FET will shut off when you reach 2.8 V.

    I would suggest writing the Cycle Count to zero in Data Memory, fixing these items and trying again. Make sure you have loaded the correct ChemID into the device using the Chemistry tab. If you still see the problem, then please collect a BQStudio log file by clicking the 'Start Log' button on the Registers tab. Send both the log file and the updated .gg file.

    thanks,
    Matt
  • No, once it is updated to such a value, it will be the same after restart. I have confirmed that it is exactly such a value in the register address!
  • Hi, Can you send both the log file and the updated gg file?
    I assume you have made the corrections to the data flash I previously suggested?

    Thanks,
    Matt