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: Temperature performance

Part Number: BQ34Z100-G1
Other Parts Discussed in Thread: BQ34Z100

Hi,

I am using a BQ34z100-g1 with an 8s2p LiFePO4 batteries. The nominal capacity of the battery is 3200mAh.

I have obtained the golden image of the battery and load it in the bq24z100-g1. 

I sent my system to a  controlled  temperature test(1000 hours at a temperature of 85ºC). This test is carried out with the system off. When my device returned I checked it and everything was in perfect state but the Bq34z100-G1, that was damage. It did not respone to any communications and we had to replace it.

- What are the possible causes of this damage? 

Bes regards,

  • Hi Gorka,

    There isn't enough information here to begin to speculate. The device is rated to an abs max operating temperature of 85 deg C.

    If the issue persists after running another test, please share the debug steps used to bring up the device. Was the device power cycled? Was the device powered? Where were the voltages measured? When applying power to the BAT pin and regin, was voltage seen on reg25 pin? Was the device in ROM mode? What addresses were used to communicate with the device? AA and 16? Please let us know the full debug steps taken.

    Sincerely,
    Bryan Kahler
  • Hi Brian,
    Before the test I was able to communicate with the bq34z100-g1 and obtained the data I wanted (SoC, SoH, RM, FCC,...)
    During the test the device nor the system were powered. After the test, I power it, the voltage on all bq34z100-g1 pins were correct but I did not achieve to communicate with the bq34z100.
    - Whta is the ROM mode?
    - The adreesses used were the same before and after the test. Why could they change?

    Best regards,
  • Hi Gorka,

    The device is in ROM mode when the firmware is not executing.

    If the firmware was unable to load, the address would change to 0x16 instead of 0xAA. Please try communicating with the device at that address.

    Sincerely,
    Bryan Kahler