Part Number:BQ34110

My application is to monitor the fuel gauge information of a 10-cell NiMH battery pack. I have read the bq34100 datasheet and technical reference manual and "using I2C comms with gas gauge". But I am still confused about the steps of how to configure this chip, as there are so many registers and calibrations. Which ones need to setup first to get it going? Right now, I can send a I2C message and get some bytes back. But please send me some basic steps needs to done for using this chip. Any application examples please? I am using a STM32 arm microcontroller. I used "HAL_I2C_Master_Transmit" and "HAL_I2C_Master_Receive" functions, not sure whether it is the best way. I have got both my circuit and bq34110 demo board for hardware. I ordered a EV2400, have not received it yet.

Thanks and best regards,

Part Number:BQ40Z50-R2

Hi,

in the product folder on TI.COM we have battery fuel gauge and battery monitor, protection& authentication solutions,

both can achieve cell balancing, right? like BQ40Z50-R2 vs. BQ76925.

My understanding is that if the customer need to know the accurate Coulomb he will need gauge, otherwise battery monitor AFE is enough.

So gauge is in fact battery monitor with some algorithm inside the device and thus generally more expensive, right?

And can we put the gauge in a battery pack?

Do we need 2 devices to do cell balancing when the battery pack is 3 series and 2 parallel?

Part Number:BQ35100

Dear all,

my customer is going to use the BQ35100 with the primary battery : SAFT LS17330.

The database of the chemistry in the BQ Studio software does not contain the chemistry SAFT MH 12802.

Is it possible to add that chemistry in the DB ?

If not, how is it possible to manually add the chemistry ? Which are the required parameters ?

regards,

Domenico

Part Number:BQ78350-R1

After months of it working, the bq78350 seems to stop working. Here is the data Iv'e acquired so far:

1) bq76930 REGOUT pin is at 2.5V.

2) After button press TS1 is pulled up to 2.7V to boot AFE.

3) I see the usual change in current from 15mA to 18mA so AFE seems to boot okay.

4) PRES is pulled low.

5) KEYIN is pulled low.

6) MRST is pulled high.

7) Once VCC is applied VEN stays high and does not pulse.

8) No activity on I2C bus... it stays high.

9) PWRM stays high 1.76V (On working boards this voltage is the same but it only stays high if SMBUS is communicating).

10) ALERT goes high and stays high (On the working boards we have ALERT pulses every 1/4 second about 10-20 times or so).

Data point 10 has me worried because I thought any ALERT issue would be an "AFE thing".

It's is essential for us to pinpoint the source of the failure and why it failed because this is for a drone application.

Thanks guys,

JP

Part Number:BQ34Z100-G1

Good morning, I have a question related to the learning cycle of my fuel gauge. I am using PbA 12V, 7Ah battery. Moreover, I am using the bq34z100G1. I made some configurations since the BqStudio and using the EVM2300. One of the most important configurations are the following ones:

Taper Current = 100mA (default)

FC SET% = -1

CC Threshold = 6300 mAh

Design Capacity = 7000 mAh

Design Energy = 14000 mWh

Cell Charge Voltage T1-T2 = 2300mV

Cell Charge Voltage T2-T3 = 2300mV

Cell Charge Voltage T3-T4 = 2300mV

VOLSEL = 1 (external voltage divider)

GNDSEL = 1 (GND of circuit in PACK-)

TEMPS = 1 (external temperature sensor)

Numbers of series cell = 6

Flash Update OK Cell Volt = 1000mV

Load Select = 3

Load Mode = 1

Cell Terminate Voltage = 1750mV

Cell Term V Delta = 100mV

Qmax Cell 0 = 7000mAh

After making the configuration I program the CHEMID equal to 808, according to the battery I am using which is a YUASA 12V 7AH NP7-12. FInally, I made the calibration of this learning cycle process as follows:

Step1:

I start the process with a full charged battery (100%) and relaxed for an hour after it have been charged . I execute IT_ENABLE and then RESET command since the BqStudio. After sending this commands, RUP_DIS is enabled(red), QEN is enabled(red) too. (QEN remains in this configuration during the whole process)

Step2:

After sending IT_ENABLE and RESET. I proceed to discharge the battery to a 1A approximately, what is equivalent to C/7 (where C is the capacity of the battery). Actually, the current is variant and it changes between 900mA and 1100mA during the whole discharging process. When the voltage is high the current is 900mA and when the voltage is low, the current is 110mA. This condition takes place since the 12,8V until the 10.5V approximately. Then, the charging current decrease until 400mA approximately and it remains in this value until the battery’s voltage is 9.3V. The termination voltage is 10.5V However, I maintain this process until 9.3V because of the fact that when I disconnect the battery, the voltage increase considerably. This is a recommendation I got from the specifications of the bq34z110 chip.

Step3:

Once the battery’s voltage is 9.3V, the load is disconnected and the battery is leaved in a relaxed state. In other words, the battery is without load, or with the charger connected to to the battery. The battery is leaved in that way, until the OCVTAKEN bit is set (red). In this time, the RUP_DIS bit is disabled(green). It is recommended to leave the battery to relax 5 hours as minimum. However, I just wait until the OCVTAKEN is set to 1, and it takes just 2 hours approximately.

Step4:

I connect the charger to the battery. Previously, I configure the charger to a charging voltage of 13.8V and limiting the charging current to 1.7A. Due to the fact that I configured the chip with the FC SET% = -1, this FC bit is set (red) when it accomplish the TAPER CURRENT condition, which has a value of 100mA. The discharging process takes 9 hours and when the FC bit is set(red) I disconnect the charger due to this condition.

Step5:

After the FC bit is set to 1(red). I proceed to disconnect the charger and the battery is leaved in a relaxed state until the OCVTAKEN bit is set to 1(red). It happens after 40 minutes approximately. Although it is recommended to leave the battery to relax for 2 hours, I just wait until the OCVTAKEN is set to 1(red). As I am working with a PbA battery, in this stage of the process the maximum error continues in 100% and the Learning Status remains in 4, in other words, these values are not updated.

Step6:

The next step is to connect the load to the battery. The battery is discharged until C/7 what is equivalent to 1A. Although, this value varies between 900mA and 1100mA since the beginning of the discharge until 10.5V. (This has been already explained in the step 2). When the voltage is 9.3V, la current that the load consumes is 400mA. At this point, the load is disconnected from the battery and the battery is leaved to relax.

Step7:

The battery remains in a relaxed state until the OCVTAKEN bit is set(red). It takes 40 minutes since the disconnection of the load. At this point, the maximum error changes to 3% and the Learned Status changes to 5. I understand that when I am using a PbA battery, it is normal that those values get updated during the discharge. In the case of other chemicals, these values should be updated during the charging stage. Although. I am not so sure about it, that is what I supposed, I just have worked with PbA batteries until now.

Step8:

I repeat the steps 4 and 7 one more time until the maximum error is 1% and the Learned Status is equal to 6. In both charging processes the FC bit set(red) when the CURRENT TAPER (100mA) condition is accomplished(FC SET% = -1)

At this point I finalized the learning cycle process. The LOAD MODE parameter was configured for CONSTANT CURRENT. However, my load is a POWER CONSTANT load.

I proposed to develop the learning cycle by changing the LOAD MODE value from 0 to 1(which corresponds to POWER CONSTANT) and doing this, I get the following problem in the Step4: The FC bit never set and I dont know why, the charger current in this point is less than taper current and the SOC is 100%. I don’t know if FC bit set is a necessary condition. I have read some publications in which the learning cycle process procedure of PbA batteries doesn’t mention the FC bit during the charging stage. The procedure just looks for charging to 100% of SOC, and then it waits until the OCVTAKEN is set. I would like you to help me to solve this doubts. Thanks.

My data Memory.

(Please visit the site to view this file)

Part Number:BQ78350-R1

Hello,

I realize that some memory location are BIG ENDIAN although the documentation refer to them as LITTLE ENDIAN.

I'm talking about, for instance:

SBS Configuration Data - Manufacture Date - 0x406B (U2)
SBS Configuration Data - Serial Number  - 0x406D (H2)

I just notice that if I program them through our production software in little endian order (like we do with other bq gauges)  the related SMBus commands 0x1B and 0x1C return wrong data.
If instead we write in big endian order, everything is consistent.

Could you please explain exactly which U2, I2 etc... parameters of the data flash has to be read/write in little endian (as stated in the documentation), and which in big endian ?

It appears to be a little critical....

Thanks

Pietro

Part Number:BQ27510

Hi,

My customer is working with implementing the BQ27510-G3 into our system and had a particular question regarding the battery used with the fuel gauge. Can TI help to characterize a cell that they provide? Their Arbin tester cannot provide thermistor data so as of right now GPCCHEM does not appear to be an option which is typically recommended by TI. How can we help?

Thanks,
Soumya

Part Number:BQ34Z100-G1

SOC not accurate during NiMH charging

Hello,

I would like to ask for help configuring the bq34z100-G1. Our application is most interested in when the battery pack obtains a full-charge, whereas most application descriptions seem focused around discharge. I am confident the fuel gauge has the ability to provide the information we need, but how we go about configuring the control values is a rather intimating combination-lock that I have not yet deciphered.

Is there a technical reference manual that goes into a bit more depth in description than SLUSBZ5B
For example: 7.3.6.14     Ra Tables
Is there some place that explains the difference between R_a0 0 and R_a0x 0?..is one for discharge and the other charge? How does one find out what the values actually mean?

After completing several charge/discharge cycles I am getting reasonable predictive value calculations for discharge. Specifically SOC and AverageTimeToEmpty() seem reasonable.

However, during a charge cycle, the SOC value quickly reaches 100% while the AverageTimeToFull() is semi-reasonable. Why the quick change in SOC?

Is there a straightforward way to obtain more accurate charging predictions?

Ideally: I would like the SOC to indicate when the battery pack has actually obtained a full charge. It would also be fantastic if it could calculate NiMH self-discharge. We want to charge the pack, put it in stock and ready for field-use. The fuel gauge should indicate an accurate charged SOC so the pack can be pulled from stock and relied upon to contain enough power to finish an entire day of field work.

Attached are some example charge/discharge log files collected using:
bqStudio 1.3.86 and EV2400 on a Win10 machine along with a bq34z1xxEVM and our 7 series cell 4500mAh NiMH (ID = 6100) battery pack.

Each file contains the .log collected data and the resulting DataMemory changes recorded by the “Auto Export” feature of the latest bqStudio.

“ChargeTest3” is an example of AverageTimeToFull more accurate than SOC. During this test the thermal sensor is located on the bq34z1xxEVM board.

(Please visit the site to view this file)

“DischargeTest6” contains a good example of things working well during discharge.

(Please visit the site to view this file)

“ChargeTest6” worked fairly well, but still reached Full Charge too soon. During this test (and all subsequent tests,) the thermal sensor is placed directly in the mid-section of the battery pack.

(Please visit the site to view this file)

“ChargeTest7” is an example of AverageTimeToFull again more accurate than SOC.

(Please visit the site to view this file)

“Discharge-ChargeTest8.zip is a combined discharge/charge cycle with SOC reaching FC too fast.

(Please visit the site to view this file)

In the document SLUSBZ5B-revised July 2016, there is a section that discusses Charge Efficiency and mentions several values. I do not find anything in the Data Flash Summary related to NiMH charge efficiency…only for Pb.. SubClassID 34 offset 4.

7.3.6.16                Charge Efficiency

Charge Efficiency

Charge Eff Reduction Rate

Charge Effi Drop Off

Charge Eff Temperature Compensation

Where are these values found for NiMH?

Are the Pb values also used for NiMH? (my *guess* is YES.)

Does the “learning” process optimize these values automatically, or must they be set manually?

Any assistance in helping make this device useful for our application will be greatly appreciated.

Cheers,

-Steve

Part Number:BQ78350

Hi,

We now have a product in use, a small number of encountered problems.

The remaining capacity becomes zero after charging or discharging stops.This then causes the RSOC to go straight to zero.

Other products can be used normally, and the probability of the above problems is about 1%

Part Number:BQ40Z50-R1

 Hi team,

My customer would like to know what does the type name mean in the TRM. i guess S is string, I is int and U is unsigned... Could you please help me to know what does them exactly mean? Or where can i find the definition of them. Thanks.

S20+1? S4+1? I2? U2? F4?...

Part Number:BQ34Z100-G1

Part Number:BQ27421-G1

Hi,

Thanks Onyx. Sorry it took me a while to get back to this.

I implemented the restoring of QMax and Ra.

My implementation includes, during shut-down procedure, reading the CONTROL_STATUS register, and if bits RES_UP and QMAX_UP are set, then persist Qmax and Ra to NVM.

However, I haven't seen these bits set in any of my tests.

When do you expect this to happen? I had it running for about 1 hour, and still the bits were clear. The value for CONTROL_STATUS was 0x8E just before executing Shutdown command to the GG.

No Reset was done before this either, which could explain the bits being clear.

Please explain.

Thanks,

Moshe

Part Number:BQ40Z50-R1

Hello.

I use the BQ40z50 on the battery pack, 3P1S, 3.9V/cell. I found two problems:

1. When connected the EV2400, the PACK+and PACK- is no load.

Measured the voltage of Pack+ was the same as the BAT+, both are 3.9V.

2. Then dis-connected the EV2400, the PACK+and PACK- is no load.

Measured the voltage of Pack+ was 6.8V, the votage of BAT+ was 3.9V, they're different. and found the CHG NMOSFET turned off, the DSG NMOSFET turned on.

Was it right ?  Why the voltage of PACK+(6.8V) was higher than BAT+(3.9V) ??

3. And then, Connected the E-load on the PACK+and PACK-,but not enable the load button. the EV2400 was still disconnected. 

Measused the voltage of the PACK+, it fell to 3.53V.   

Why cannot it keep 6.8V ? 

Hi people,

I am using a BQ78350-R1 connecting to a FTDI FT232H with SMBUS.

When I try to use manufacturerBlockAccess (0x44) to read data (BlockData) it always returns wrong data,

 the data read from FTDI is 0x1717171717

also I find no matter which command and the length of the command I want to read, I always get the result 0x17.

does my command go wrong?

here is the command format I send in block write-block read process call
0x44 06 00

code:
...
buffer_T[bytesToTransfer++] = 0X44; /*Command Address*/
buffer_T[bytesToTransfer++] = 0X06;
buffer_T[bytesToTransfer++] = 0X00;// 0X0006 (ChemID)
    

status = I2C_DeviceWrite(ftHandle, slaveAddress, bytesToTransfer, buffer_T, \
        &bytesTransfered, I2C_TRANSFER_OPTIONS_START_BIT | I2C_TRANSFER_OPTIONS_FAST_TRANSFER_BYTES);


    APP_CHECK_STATUS(status);

    bytesToTransfer = 5;

    status |= I2C_DeviceRead(ftHandle, slaveAddress, bytesToTransfer, buffer_R, \
        &bytesTransfered, I2C_TRANSFER_OPTIONS_START_BIT | I2C_TRANSFER_OPTIONS_STOP_BIT | I2C_TRANSFER_OPTIONS_NACK_LAST_BYTE | I2C_TRANSFER_OPTIONS_FAST_TRANSFER_BYTES);

    APP_CHECK_STATUS(status);
...

Can you help me please?

Thanks.

Hi,

do you have products can be used for dry cells battery gauges？

battery is 3 battery in series and used in smart lock.

thank you.

Part Number:BQ34Z100-G1

the bq34z100-g1 can't be calibrated by battery management studio. it shows "can't enter the calibration mode"

Part Number:BQ34Z100-G1

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.

Part Number:BQ4050

BQ4050 temperature address is 0X08,but I can't find out TS1,TS2,TS3,TS4 address.

Part Number:BQ35100

Hi,

Trying to set design capacity 2700 Ah, when read back data flash able to get the set design capacity == 2700. Now want to calibrate voltage and current, with reference to Host System Calibration Method - SLUA640B , 

1. Able to enter calibration mode

2. CC_Offset 

a. When started Control Status value = 0x04

b. Polling... after some time CCA bit is cleared and saving offset with 0x000B

3. Board_Offset

a. When started Control Status value = 0x08

b. Polling... after some time BCA bit is cleared and saving offset with 0x000B

4. Current calibration

a. obtain raw calibration data , after averaging I am getting 0xCC == 204 mA  (Don't know if this is correct ? ... how to verify this ?)

5. Voltage calibration

a. obtain raw calibration data , after averaging I am getting 0xD1A == 3354 mV  

Please let me know the steps followed are correct ?

Thanks and Regards,

Dileep

Part Number:BQ27750

Hi  E2E community,

Got a question regarding "ManufacturerAccess/ControlStatus()" register readings.

When reading this register I got wired value which I cannot explain anyhow.

So getManufacturerAccess : 0x020C, I'm trying to figure out why I can't access to flash values and this thing rubs me 

a bit i a wrong way, It appears that security bits (SEC1 SEC0 [14 and 13]] ) are "00" which is "reserved" state, is it something wrong with IC, or 

It's just me - doing something in a wrong way ??

Thanks !