BQ34Z100-G1 without Thermistor?

You can configure the gauge to use the internal thermistor, although using an external thermistor connected to the battery is preferred. We typically use a 10 mohm sense resistor with the gauge.

Hello Thomas,
I was not able to get running the EV2300 and the bq34z100EVM at Windows 7 64Bit.
Fortunately I have an old Laptop with WinXP, where the bqStudio 1.3.45 is running now.
Is there a solution for Win7 64Bit?

At first, I tested with a single Li-Cell, and the voltage readout is quite correct.
Under load I can also readout the average current, but the up-to-date current (Register 0x10, 0x11) is always zero.
What can be wrong here?

Also, I have the same Problem as stated in the post from 07.12.15:
- Battery Management Studio version 1.3.45 errro in Chemistry tab
The "chemistry"-window is empty, allthough I made the "Chemistry Update" under "Help"-menu.

The Dashboard shows the chip with message "bq34z100G1" and "0100_0_06".
Is the last one the Firmware Revision? Is it up-to-date?

What I finally need, is a configuration for a 4-Cell NiMh package.

Is there a User Guide, how to program the bq34z100G1 step-by-step for such a package ?
We have to find a solution to replace the existing bq2060A by your bq34z100G1.

Can you please provide us some help?

Reinhard, 

We have drivers to support 64-bit Windows and the EV2300. You can download them from this site.

You are running the old firmware on the bqStudio platform and they are compatible. You can download the bq34z100-G1 firmware from the product website and program it with bqStudio. You should also update bqStudio, if you are not running v45. 

If your stack voltage exceeds 5V, then you will need to use an external resistor divider and set the VOLTSEL flag to 1. You will set the Number of Series Cells to 4 in either case. 

Tom

Hello Tom.

I'm using too the BQ34Z100-G1 and it doesn't work with the bqSTUDIO.

This morninig I try to download again the bqSTUDIO and the link doesn't work.

My laptop uses a WIN7 with 64bits.

Now I'm testing the BQ34Z100-G1 with the "BQ GASGAUGE EVALUATION SOFTWARE" that I had installed before in my laptop but I suppose that the bqSTUDIO must be better.

Can you help me.

Thank you.

Tom,

the firmware update of the bq34z100-G1 solved some Problems !!

I can read the current and see many battery chemistries, as well.

Unfortunately, I can´t find my batteries in the chemistry list.
We use 4 Panasonic Eneloop NiMh-cells of Type BK-3MMC in series.

see also
lygte-info.dk/.../Eneloop AA BK-3MCC 1900mAh (White) UK.html

Can you provide us a suitable chemistry file ?

Thanks
Reinhard

Reinhard

We have not characterized that cell, so you will need to use the GPCCHEM tool to try to find a match. The instructions and tool can be found at this link. I have found that it is better to run the discharge profile at a C/20 rate, instead of C/10, for PbA and NiMH cells.

Tom

The bq34z100-G1 is not supported by the older bqEVSW program and you must use bqStudio with the device. I checked the link this morning and it is working.

www.ti.com/.../bqstudio

Hi Tom,
I download it again but the result is the same.

When I start the program,
the autodetection device that apears is: 0100_0_06.

When I select between 0100_0_15_bq34z100G1.bqz and 0100_016_bq34z100g1.bqz in both cases the result is this message:

Proceed?
? The detected device is not compatible with this application!
Some actions could cause the device to lose communication permanently and enter
an unrecoverable state
Proceed at your own risk.
Select Ok to continue. Cancel to close the application.

The first time I continue with the application, but the values that I changed in the dataflash weren't agree with values that appear in the register window, for example "Cycle Count".

Can you tell me something?

Thank you.

If the bqStudio program shows 0100_0_06 on the Dashboard, then the firmware has not been updated. It should show 0100_0_16 after the firmware has been updated. The other issues that you report could also be caused by the old firmware. Can you try programming the firmware again?

Perfect. Now it's working.
Thank you very much.