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.

Problem with BQ3060, ESD?

Other Parts Discussed in Thread: BQ3060

Hello everyone.

Yesterday I let battery(57,4Ah Li-ion with bq3060 integrated in batterypack) to discharge to lowest voltage it can. Today I wanted to see  the accurate voltage with EV2300, but got and error that EV2300 doesn’t recognize the device. Afterwards I tried to communicate with BQ3060 through my microcontroller(I used Live variables in my IDE to see values it reads from BQ3060) and it was all incorrect and strange values, for example voltage 5.6, temperature 315 etc.

Afterwards I tried to use EV2300 and microcontroller on other battery which is also 57,5Ah Li-ion with BQ3060, but EV2300 didn’t recognize it too and my microcontroller didn’t read anything.

Is it possible that I could have damaged BQ3060 with electrostatic-discharge from my body when I touched SMBus wires?

This week I have started to feel electrostatic discharge every time I touch water tap.

Thanks in advance.

  • I supposed that ESD damage could be possible, especially it you have felt ESD zaps around your place. If you have access to an oscilloscope, then you could monitor the SMBus signals and see if the address command (first word) gets acknowledged. This would provide a clue as to whether the firmware is running. The hardware ACKs the address and passes control over to the FW. You could also try removing and reapplying power to the device to see if a reset helps.

  • Thanks, for answer.

    I have only old USSR oscilloscope, so I can't examine SMBus. Tomorrow I will get my logic analyzer and I will check if messages get acknowledged.

    By the way I just checked that what ever I want to read from BQ3060, it always reads 0x17. Any idea why is that so?

    Regarding reapplying power - I can't really do that because bq3060 is integrated in battery pack and we can't dissemble it. 

  • By the way , this 0x17 read that I get for everything I try to read is BQ3060 address. Maybe that somehow solves the mystery, but I don't know how.