BQ34Z100-G1: Battery returning Garbage Data to Embedded Chip

Melvin nG

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

I'm using this code to return the data from the battery pack:

The Lithium battery pack that I am has 25.2V.

This is the garbage data that it seems to be returning for each of the addresses.

Battery Charge: 4294967039%
Remaining Capacity: 4294967039 mAh
Battery Pack Voltage: 4294967039 mV
Average Current Draw: -257 mA
Instantaneous Current Draw: -257
Instantaneous Current Draw LSB: 4294967295
Instantantous Current MSB: 4294967295
Battery Temperature: -298 C
Power Draw: -1103806.50 W

I also have an EV2300 but I'm not sure how to start debugging this issue to return proper data.

over 7 years ago

0 Swaminathan Ramanathan75031 over 7 years ago

TI__Expert 6575 points

Hi,
Looking at the code, I am not sure why it is not working.
I did find that the SateOfCharge() is only a read unsigned word command 0x02, and it does not involve 0x03 which will read the MaxError().
Apart from that, you could use the "Advanced Comm" tab in bqStudio with the EV2300 and check what the commands return and compare them to the results you are getting.
If you are seeing the proper response using bqStudio, I would recommend using a logic analyzer or bus sniffer to compare the transactions with bqStudio, with the ones from the micro.
I would also recommend looking at the following app note: www.ti.com/.../bq34z100-g1.pdf
Regards,
Swami

0 Melvin nG over 7 years ago in reply to Swaminathan Ramanathan75031

Prodigy 40 points

Also not getting the proper response. This is the read out from the registers:

When I ping the address 0x04/0x05, it returns garbage that seems the same no matter what I write to it:

0 Melvin nG over 7 years ago in reply to Melvin nG

Prodigy 40 points

Nvm, was able to make sense of the data above, it is the address number 4 that gives the correct output. But for some reason the code is still giving me stupid data.

0 Melvin nG over 7 years ago in reply to Melvin nG

Prodigy 40 points

Managed to find the mistake. I had to make sure that the I2C was initiated properly, so I used this code to check which ports the I2C was connected to: github.com/.../i2c_port_address_scanner.ino

Put in the correct pins, in my case Wire.begin(2, 14); and the I2C started talking to each other.

Power management

Power management forum

BQ34Z100-G1: Battery returning Garbage Data to Embedded Chip