Part Number:BQ20Z75

Hi,

We are using a .senc file with chemical ID: 0252 that is specific for the Sanyo UR18650A cell.  The default .senc file for the BQ20z75 has chemical ID: 100.  Per the above instructions if we use the .senc file that comes with a virgin BQ20z75 chip and then load the golden gg file on top, the battery will return chemical ID: 100 if queried via Manufacture Access code 0008.  Is this a don't care and the golden gg file contains all cell chemistry specific data?  If so, then what is the purpose of having .senc files with different chemical IDs?  Any help will be greatly appreciated.

Part Number:BQ27541

Need help, can somebody share information on the calibration steps for BQ27541-xxx

I am currently working on a project with BQ27541 and need to write the code for Calibration to automate the process.

I cannot find any document regarding calibration steps and formula for BQ27541-xx.

Part Number:EV2400

The first EV2400 stops working after an accidental short circuit in the BQ76940 eval board (the short was not on the EV2400).

The second one stop working after a disconnect/connect USB cable.

I check my grounds, and I cannot measure any ground loops. I work with several interfaces on my bench, and I never had a problem like this.

I just discover that several people reported very similar issues in previous posts.

Since I spend a lot of money in these tools (($207.00 x 2)+ $260.00 of the eval board), I would like to know:

1. Is there any way to replace or repair this unit (EV2400)?

2. Is there anything that I can do to avoid this problem in the future?

Thanks for your help.

Part Number:BQ34Z100-G1

We have been developing a prototype system and have been struggling with the SOC readings on our BQ34Z100-G1.

It is difficult to see the value add of this chip and we are thinking that perhaps it was not a good choice for our application.

We are working with 3 lead acid batteries in series.  The batteries are meant to operate as a UPS.  When we lose power, they kick in.

We use the fuel gauge chip to check the health and welfare of the batteries.  If the SOC is too low, we shut down the system.

The SOC readings from the fuel gauge chip are very flakey.  Starting with a fully charged battery, we  see the SOC number @100%.

We then run the system off of battery for a period of time.

The SOC slowly decreases  as we would expect.

When it gets about 90% SOC we power off and then power back on (sending a reset to the fuel gauge).  We now read  back an SOC of  either 0% or 100%

In a separate experiment we do the same thing - battery At 90% and we send a reset.  It will now read 100%

I would expect a more accurate SOC.  Where did we go wrong?

Thanks!

Part Number:BQ40Z60

Dear TI Expert,

My customer is debugging their own board of BQ40Z60, the max charging current they use is 1.3~1.4A, however, the BQ40Z60's temprature is very high, some region reach 100 degree.

Could you kindly help to review the sch and pcb layout? Thanks a lot.

(Please visit the site to view this file)

(Please visit the site to view this file)

Part Number:BQ27441-G1

Hi There,

I Have used this  fuelgague library ->> https://github.com/sparkfun/SparkFun_BQ27441_Arduino_Library

and done some modification related to battery detection using software instead of bat_detect pin.

I use ITPOR flag to detect ehether gauge is already configured or not if configured then i do not configure it again.

problem A)

         1 -> Setup is like, battery is not connected to my device, i plug in usb power to power up my device, device starts runing and first checks for ITPOR Flag in fuelgauge and in this case it shows fuelgague was power on reset which is expected then i configure design capacity, design energy, terminate voltage, tapper rate.

2 -> Configured opconf register to disable Battery Detection over BIN PIN Status, instead i read current value if it's zero battery is not connected and then i write BAT_REMOVE to make BAT_DETECT flag =  0 command and if current is not zero i write BAT_INSERT command to make BT_DETECT = 1.

3-> i now connect battery to device.

4-> now software read battery soc, before reading battery soc software checks for battery insertion logic. in this case battery is connected and software writes BAT_INSERT command. and it shows 100% which is in correct, below are the logs.

STEP1

PAL: Initialization Success
ADF: Rf_Ver = 7, Rf_Freq = 673000000
GPS: $PMTK220,100*2F
GPS: $PMTK314,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0*28
GPIO: GPIO INTR/TLMM Registered
GPIO\LED: LED Registered
ADC: ADC Registered
PWM: PWM Registered
HSU: HSUART Registered
HSU\SMODEM: Ubiik module Registered
I2C: I2C Registered
I2C\TEMP1075: Temperature Sensor Registered
I2C\GPIO_EXP: GPIO Expander Registered
I2C\USB_PD: USB PD Registered
I2C\BCG: Battery Charger Registered
I2C\IMU: IMU Registered
I2C\FUEL_GAUGE: fuelgauge Registered
SPI: SPI Registered
SPI\RF_SYNTH: RF Synthesizer Module Registered
WLAN: WLAN Registered
Net: Net Registered
FwUp: Firmware Upgrade Registered
GPS: GPS Registered
BLE: BLE Registered
FS: FS Registered
I2C\FUEL_GAUGE: FG: OP Config Data=25f8
I2C\FUEL_GAUGE: FG: Control Status=c
I2C\FUEL_GAUGE: FG: flag = 127
I2C\FUEL_GAUGE: FG: Flags Status=127
I2C\FUEL_GAUGE: FG: Init FG For First Time : ITPOR Is Set
I2C\FUEL_GAUGE: FG: Init FG For First Time : Battery Capacity Is Set To 1340
I2C\FUEL_GAUGE: FG: Set Capacity = 10500(2904), msb = 29, lsb =4
I2C\FUEL_GAUGE: FG: Set Energy = 38850(97c2), msb = 97, lsb =C2
I2C\FUEL_GAUGE: FG: Set Term Volt = 3300(ce4), msb = C, lsb =E4
I2C\FUEL_GAUGE: FG: Set Tap Rate = 913(391), msb = 3, lsb =91
I2C\FUEL_GAUGE: FG: Sealed Status = 0
I2C\FUEL_GAUGE: FG: #2 Step To Send SET_CFGUPFDATE
I2C\FUEL_GAUGE: FG: #3 Step To confirm CFGUPDATE mode by Flags Register :
FUEL_GAUGE: FG: flag = 137
I2C\FUEL_GAUGE: CFGUPMODE Flag IS up.
I2C\FUEL_GAUGE: FG: #4 Write 0x00 Using BlockDataControl() Command (0x61) To Enable Block Data Memory Control.
I2C\FUEL_GAUGE: FG: #5 Write 0x52 using the DataBlockClass() command (0x3E) to access the State subclass (82 decimal, 0x52 hex) containing the Design Capacity parameter.
I2C\FUEL_GAUGE: FG: #6 Write the block offset location using DataBlock() command (0x3F).
I2C\FUEL_GAUGE: FG: #7b Read Block And Calculate Checksum, FG: Old Caclulated Checkcsum : 172(AC).
I2C\FUEL_GAUGE: FG: #7a Read the 1-byte checksum using the BlockDataChecksum() command (0x60), FG: Read Old CheckSum :172(AC).
I2C\FUEL_GAUGE: FG: #8 Read both Design Capacity bytes starting at 0x4A (offset = 10):
I2C\FUEL_GAUGE: FG: Current Design Capacity = 1340(53C)
I2C\FUEL_GAUGE: FG: Current Design Energy = 4960(1360)
I2C\FUEL_GAUGE: FG: Current Design Term Vol = 1340(53C)
I2C\FUEL_GAUGE: FG: Current Design Tap Rate = 3200(C80)

I2C\FUEL_GAUGE: FG: #9 Write both Design Capacity bytes starting at 0x4A (offset = 10).
I2C\FUEL_GAUGE: FG: New Caclulated Checkcsum : 136(88).
I2C\FUEL_GAUGE: FG: New Caclulated Checkcsum : 192(C0).
I2C\FUEL_GAUGE: FG: New Caclulated Checkcsum : 60(3C).
I2C\FUEL_GAUGE: FG: New Caclulated Checkcsum : 218(DA).
I2C\FUEL_GAUGE: FG: New Caclulated Checkcsum : 211(D3).
I2C\FUEL_GAUGE: FG: New Caclulated Checkcsum : 43(2B).
I2C\FUEL_GAUGE: FG: New Caclulated Checkcsum : 52(34).
I2C\FUEL_GAUGE: FG: New Caclulated Checkcsum : 35(23).
I2C\FUEL_GAUGE: FG: #10 Read Block And Calculate Checksum, New Caclulated Checkcsum : 35(23).
I2C\FUEL_GAUGE: FG: #11 Write Newly Calculated Checksum.

STEP 2 - > opconf updated to disable BIE and( manually detect battery using current consuption).
I2C\FUEL_GAUGE: FG: OP Config Read Only Data=25f8
I2C\FUEL_GAUGE: FG: Read Old CheckSum :106(6A).
I2C\FUEL_GAUGE: FG: Old Caclulated Checkcsum : 106(6A).
I2C\FUEL_GAUGE: FG: Current OpconfigB Settings =0xf
I2C\FUEL_GAUGE: FG: Current Opconfig Settings =0x25f8
I2C\FUEL_GAUGE: FG: Set Opconfig Settings =0x5d8
I2C\FUEL_GAUGE: After Set Opconfig Setting =0x5d8
I2C\FUEL_GAUGE: FG: #10 Read Block And Calculate Checksum, New Caclulated Checkcsum : 170(AA).
I2C\FUEL_GAUGE: FG: #11 Write Newly Calculated Checksum.
I2C\FUEL_GAUGE: FG: #12 Exit CFGUPDATE mode by sending SOFT_RESET subcommand, Control(0x0042).
I2C\FUEL_GAUGE: FG: #13 Step To confirm CFGUPDATE mode by Flags Register :
FUEL_GAUGE: FG: flag = 117
I2C\FUEL_GAUGE: FG: flag = 0
I2C\FUEL_GAUGE: FG: Timeout = 1
I2C\FUEL_GAUGE: FG:#14 Step If the device was previously SEALED, return to SEALED mode by sending the Control(0x0020) subcommand.
I2C\FUEL_GAUGE: FG: FG Config Is Done

>>>>> "Battery Detection Logic Based On Current Consuption at this moment battery is not inserted, as it can be infered from log"
I2C\FUEL_GAUGE: FG: Battery is not Charging and not Discharging
I2C\FUEL_GAUGE: FG: Battery Removed

Command List:
Commands:
0. Ver
1. Help
2. Exit
3. Heap
4. CPU
5. Stack
6. Reset

Subgroups:
7. GPIO
8. ADC
9. PWM
10. HSU
11. I2C
12. SPI
13. WLAN
14. Net
15. FwUp
16. GPS
17. BLE
18. FS

> 11

I2C> 19

I2C\FUEL_GAUGE> 8 5

I2C\FUEL_GAUGE: I2c FuelGauge Control status Reg 0x06 = 200c
I2C\FUEL_GAUGE: I2c FuelGauge Control VOK = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control RUP_DIS = 1
I2C\FUEL_GAUGE: I2c FuelGauge Control LDMD = 1
I2C\FUEL_GAUGE: I2c FuelGauge Control Sleep = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control Hibernate = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control INITCOMP = 0 ->> due to  BAT_REMOVE command.
I2C\FUEL_GAUGE: I2c FuelGauge Control RES_UP = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control QMAX_UP = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control BCA = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control CCA = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control CALMODE = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control Sealed State = 1
I2C\FUEL_GAUGE: I2c FuelGauge Control WDRESET = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control SHUTDOWN = 0

I2C\FUEL_GAUGE> 8 4

I2C\FUEL_GAUGE: FG: flag = 0 -> means no battery detected

I2C\FUEL_GAUGE> 8 3

I2C\FUEL_GAUGE: I2c FuelGauge opConfig Reg 0x3A = 5d8
I2C\FUEL_GAUGE: I2c FuelGauge opConfig Temperature Source = 0
I2C\FUEL_GAUGE: I2c FuelGauge opConfig Battery Low status = 0
I2C\FUEL_GAUGE: I2c FuelGauge opConfig RM set status= 1
I2C\FUEL_GAUGE: I2c FuelGauge opConfig Sleep enable/disable = 0
I2C\FUEL_GAUGE: I2c FuelGauge opConfig GPOUT active high/low = 0
I2C\FUEL_GAUGE: I2c FuelGauge opConfig Pullup Resistor internal/external = 0
I2C\FUEL_GAUGE: I2c FuelGauge opConfig Battery Insertion enalbe/disable = 0

Battery Is Connected Now

I2C\FUEL_GAUGE> 8 2

I2C\FUEL_GAUGE: FG: Battery is Charging
I2C\FUEL_GAUGE: FG: Battery Inserted
I2C\FUEL_GAUGE: FG: Bat % - 100%
I2C\FUEL_GAUGE: FG: Bat Temp Kel - 302.20K
I2C\FUEL_GAUGE: FG: Bat Temp Cel - 29.05C
I2C\FUEL_GAUGE: FG: Bat Current - 182mA
I2C\FUEL_GAUGE: FG: Bat Voltage - 4187mV
I2C\FUEL_GAUGE: FG: Bat Avail Cap - 9126mAh
I2C\FUEL_GAUGE: FG: Bat Rem Cap - 10500mAh
I2C\FUEL_GAUGE: FG: Bat Full Cap - 10500mAh
I2C\FUEL_GAUGE: FG: Bat Design Cap - 10500mAh
I2C\FUEL_GAUGE: FG: Battery is Charging
I2C\FUEL_GAUGE: FG: Battery Inserted
I2C\FUEL_GAUGE: FG: Bat % - 100%

I2C\FUEL_GAUGE> 8 5

I2C\FUEL_GAUGE: I2c FuelGauge Control status Reg 0x06 = 208e
I2C\FUEL_GAUGE: I2c FuelGauge Control VOK = 1
I2C\FUEL_GAUGE: I2c FuelGauge Control RUP_DIS = 1
I2C\FUEL_GAUGE: I2c FuelGauge Control LDMD = 1
I2C\FUEL_GAUGE: I2c FuelGauge Control Sleep = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control Hibernate = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control INITCOMP = 1
I2C\FUEL_GAUGE: I2c FuelGauge Control RES_UP = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control QMAX_UP = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control BCA = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control CCA = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control CALMODE = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control Sealed State = 1
I2C\FUEL_GAUGE: I2c FuelGauge Control WDRESET = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control SHUTDOWN = 0

I2C\FUEL_GAUGE> 8 4

I2C\FUEL_GAUGE: FG: flag = 88
I2C\FUEL_GAUGE: I2c FuelGauge Flags Reg 0x06 = 88
I2C\FUEL_GAUGE: I2c FuelGauge Flags Discharging Detected = 0
I2C\FUEL_GAUGE: I2c FuelGauge Flags SOCF = 0
I2C\FUEL_GAUGE: I2c FuelGauge Flags SOC1 = 0
I2C\FUEL_GAUGE: I2c FuelGauge Flags BAT_DET = 1
I2C\FUEL_GAUGE: I2c FuelGauge Flags ITPOR = 0
I2C\FUEL_GAUGE: I2c FuelGauge Flags OCVTAKEN = 1
I2C\FUEL_GAUGE: I2c FuelGauge Flags Fast Charging allowed = 0
I2C\FUEL_GAUGE: I2c FuelGauge Flags Full charge detected = 0
I2C\FUEL_GAUGE: I2c FuelGauge Flags Under Temp Detection = 0
I2C\FUEL_GAUGE: I2c FuelGauge Flags Over Temp detection = 0

Second observation 

now i remove usb power and from below command current direction is changing means it is drawing power from battery. and tried to read battery soc multiple time but it shows 100%

I2C\FUEL_GAUGE> 8 2

I2C\FUEL_GAUGE: FG: Battery is Discharging
I2C\FUEL_GAUGE: FG: Battery Inserted
I2C\FUEL_GAUGE: FG: Bat % - 100%
I2C\FUEL_GAUGE: FG: Bat Temp Kel - 301.90K
I2C\FUEL_GAUGE: FG: Bat Temp Cel - 28.75C
I2C\FUEL_GAUGE: FG: Bat Current - -72mA
I2C\FUEL_GAUGE: FG: Bat Voltage - 4021mV
I2C\FUEL_GAUGE: FG: Bat Avail Cap - 9126mAh
I2C\FUEL_GAUGE: FG: Bat Rem Cap - 9154mAh
I2C\FUEL_GAUGE: FG: Bat Full Cap - 9155mAh
I2C\FUEL_GAUGE: FG: Bat Design Cap - 10500mAh
I2C\FUEL_GAUGE: FG: Battery is Discharging
I2C\FUEL_GAUGE: FG: Battery Inserted
I2C\FUEL_GAUGE: FG: Bat % - 100%

now even when battery is connected i fired BAT_REMOVE command and then BAT_INSERT Command Manually.

I2C\FUEL_GAUGE> 10

I2C\FUEL_GAUGE: FG: Battery Removed
I2C\FUEL_GAUGE: FG: flag = 80

FUEL_GAUGE: I2c FuelGauge Flags Reg 0x06 = 80
I2C\FUEL_GAUGE: I2c FuelGauge Flags Discharging Detected = 0
I2C\FUEL_GAUGE: I2c FuelGauge Flags [BAT_DET] = 0
I2C\FUEL_GAUGE: I2c FuelGauge Flags [ITPOR] = 0

FUEL_GAUGE: I2c FuelGauge Control status Reg 0x00 = 200c
I2C\FUEL_GAUGE: I2c FuelGauge Control Sleep = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control Hibernate = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control [INITCOMP] = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control RES_UP = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control QMAX_UP = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control Sealed State = 1
I2C\FUEL_GAUGE: I2c FuelGauge Control SHUTDOWN = 0

FUEL_GAUGE: I2c FuelGauge opConfig Reg 0x3A = 5d8
I2C\FUEL_GAUGE: I2c FuelGauge opConfig Temperature Source = 0
I2C\FUEL_GAUGE: I2c FuelGauge opConfig Battery Low status = 0
I2C\FUEL_GAUGE: I2c FuelGauge opConfig RM set status= 1
I2C\FUEL_GAUGE: I2c FuelGauge opConfig Sleep enable/disable = 0
I2C\FUEL_GAUGE: I2c FuelGauge opConfig GPOUT active high/low = 0
I2C\FUEL_GAUGE: I2c FuelGauge opConfig Pullup Resistor internal/external = 0
I2C\FUEL_GAUGE: I2c FuelGauge opConfig Battery Insertion enalbe/disable [BIE] = 0

I2C\FUEL_GAUGE> 9

I2C\FUEL_GAUGE: FG: Battery Inserted
I2C\FUEL_GAUGE: FG: flag = 188

FUEL_GAUGE: I2c FuelGauge Flags Reg 0x06 = 188
I2C\FUEL_GAUGE: I2c FuelGauge Flags Discharging Detected = 0
I2C\FUEL_GAUGE: I2c FuelGauge Flags [BAT_DET] = 1
I2C\FUEL_GAUGE: I2c FuelGauge Flags [ITPOR] = 0

FUEL_GAUGE: I2c FuelGauge Control status Reg 0x00 = 200e
I2C\FUEL_GAUGE: I2c FuelGauge Control Sleep = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control Hibernate = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control [INITCOMP] = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control RES_UP = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control QMAX_UP = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control Sealed State = 1
I2C\FUEL_GAUGE: I2c FuelGauge Control SHUTDOWN = 0

FUEL_GAUGE: I2c FuelGauge opConfig Reg 0x3A = 5d8
I2C\FUEL_GAUGE: I2c FuelGauge opConfig Temperature Source = 0
I2C\FUEL_GAUGE: I2c FuelGauge opConfig Battery Low status = 0
I2C\FUEL_GAUGE: I2c FuelGauge opConfig RM set status= 1
I2C\FUEL_GAUGE: I2c FuelGauge opConfig Sleep enable/disable = 0
I2C\FUEL_GAUGE: I2c FuelGauge opConfig GPOUT active high/low = 0
I2C\FUEL_GAUGE: I2c FuelGauge opConfig Pullup Resistor internal/external = 0
I2C\FUEL_GAUGE: I2c FuelGauge opConfig Battery Insertion enalbe/disable [BIE] = 0

Read Control Status Just to check INITCOMP =1 before reading soc

I2C\FUEL_GAUGE> 8 5

I2C\FUEL_GAUGE: I2c FuelGauge Control status Reg 0x06 = 208e
I2C\FUEL_GAUGE: I2c FuelGauge Control VOK = 1
I2C\FUEL_GAUGE: I2c FuelGauge Control RUP_DIS = 1
I2C\FUEL_GAUGE: I2c FuelGauge Control LDMD = 1
I2C\FUEL_GAUGE: I2c FuelGauge Control Sleep = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control Hibernate = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control INITCOMP = 1
I2C\FUEL_GAUGE: I2c FuelGauge Control RES_UP = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control QMAX_UP = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control BCA = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control CCA = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control CALMODE = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control Sealed State = 1
I2C\FUEL_GAUGE: I2c FuelGauge Control WDRESET = 0
I2C\FUEL_GAUGE: I2c FuelGauge Control SHUTDOWN = 0

Now  I read Battery SOC and it show correct value

I2C\FUEL_GAUGE> 8 2

I2C\FUEL_GAUGE: FG: Battery is Discharging
I2C\FUEL_GAUGE: FG: Battery Inserted
I2C\FUEL_GAUGE: FG: Bat % - 93%
I2C\FUEL_GAUGE: FG: Bat Temp Kel - 300.40K
I2C\FUEL_GAUGE: FG: Bat Temp Cel - 27.25C
I2C\FUEL_GAUGE: FG: Bat Current - -69mA
I2C\FUEL_GAUGE: FG: Bat Voltage - 3981mV
I2C\FUEL_GAUGE: FG: Bat Avail Cap - 8437mAh
I2C\FUEL_GAUGE: FG: Bat Rem Cap - 8437mAh
I2C\FUEL_GAUGE: FG: Bat Full Cap - 9126mAh
I2C\FUEL_GAUGE: FG: Bat Design Cap - 10500mAh
I2C\FUEL_GAUGE: FG: Battery is Discharging
I2C\FUEL_GAUGE: FG: Battery Inserted
I2C\FUEL_GAUGE: FG: Bat % - 93%

Question 1: When To configure fuel gauge? based on ITPOR bit or based on Battery detection?

Question 2: In any case if i configure fuelgauge while USB power is on and BATTERY connected, soc always reads 100%, is this correct behaviour? if not how to avoid this?

Part Number:BQ40Z60

Dear TI Expert,

My customer is designing a 3S pack with BQ40Z60, this is the first time they design gauge + charger solution, and they don't know how to set the OCC protection.

For example, if the charging current is set to 2A,  and set OCC to 3A, does it make any sense since max charging is 2A and OCC never happen?

If it does make sense to prevent charger damage, then how to test OCC works? Re-set max charging current to above 3A or break the charger circuit and add a external high-current charger?

Or they just need to set OCC to equal to the max charging current? Thanks a lot.

Part Number:BQ28Z610

Hi, team!

I use the BQ28Z610 in the control board of the 2S Li-ON battery(mini-UPS) and the chip is in a sealed state. I do not have neither EVM or i2c BQ programmer - only my microcontroller (atmega328 with the Arduino bootloader).

When I reading the data block for the unseal key(0x0035), the data is returned from the previous successful MAC read (e.g. OperationStatus 0x0054) and it means that I can not read the unseal key in sealed mode.

I successfully read from standard registers and MACdata, but I can not normally configure the chip because it is sealed. I learned this forum on similar topics of unlocking BQs and I find out that I need default unseal keys for transferring the chip to unseal mode. I saw in some topics that many who encountered this problem were recieve a key by email.

Can you also send me a default unseal key?

My email: niskorodnov@lanit.ru

As I understand it is necessary to write a unseal key (4 bytes) to the register 3E with the command 0x0035 with a checksum, or another procedure? I write the program in the Arduino IDE environment on a C ++ similar language using the standard Wire library.

For MACdata block read, I do this:

- Open connection with BQ i2c address and send 0x3E(allManAcces) and command bytes(LSB, MSB) - first transaction with closing connection.

- Open connection with BQ i2c address and send 0x3E(allManAcces) and read MAC block(36 bytes) - second transaction with closing connection.

What transfer procedure should be used to transfer the chip from SEALED to UNSEALED mode and UNSEALED to FULL ACCESS?

Unfortunately, the manual(SLUUA65B) does not very clearly explain what specific operations you need to perform, and there is nowhere in the datasheets an understandable structure for data transmission (for example, for the BQ24725A that I use in the project - there the query structure is shown superbly). I read it across and in the part of the security modes, but still the procedure is incomprehensible for transferring to UNSEALED mode, there is only an example for replacing the keys, which only works if the chip works in unseal mode.

PS: Why do we need such big difficulties with unlocking the device and all these keys? Why not specify a default keys in datasheet/tech guide?

Part Number:BQ20Z95

From where I can download BQ20Z95 (ev2300) for the evaluation software?

Part Number:BQ27546-G1

Dear TI Experts,

My customer is evaluating BQ27546, and they need firmware. Could you kindly help to provide the firmware? Thanks a lot.

Part Number:BQ27320

Hi Team,

Is there any application note that refers about process flow of programming golden file at system production?
If the answer is yes, I would like to confirm it for supporting customer.

Best Regards,
Yaita

Part Number:BQ76940

I have checked the datasheet of BQ76940, and found for the hardware protection features, 76940 only could give protection when battery discharge, and I want to know, for the charge condition, overcurrent and short circuit, BQ76940 could give protection?

Part Number:BQ35100

I use EV2400  to communicated with my PCM by bqstudio.

I send the command 07 to read the terperature as following picture shows.

And I read the waveform with a logic analyzer  as following picture shows.

I know that the last five sets of data represent  07, 0B ,14, 10, 01. But the first data is not represent  AA .

And who can tell me the reason of this issue?

Part Number:BQ28Z610

Hi,

do we have the TRM available for FW16?   The rev C version has register settings that don't apply to FW16.   Since we're still using FW16, we'd like the TRM that corresponds.   Is that SLUUA65B?   Is there a copy of this TRM still on-line?

Thanks,

Sal

Part Number:BQ34Z100

The datasheet says that the AD for internal and external temperature measurement is 16 bits, and the measurement range is 0-6553.5 ºK.

For the actual simulation test, the external temperature measurement was used, the open circuit temperature resistance was -39 °C, and the short circuit temperature resistance was shown to be 123 °C.

Can we adjust the temperature display range to at least -55~125°C or higher? (The temperature probe is actually used as 103F3435, which is very close to the AT103 parameter recommended in the specification. The parameter list is given as -55~125°C)

Hiiii,
We are designing a power bank with 4S li-po battery pack. So we need a stand-alone fuel guage for 4S pack that can drive 4 or 5 led`s. As we are focusing on low BOM, wedon't need any communication interface.  So kindly suggest some fuel guage for 4s pack that shows battery level when the battery is idle/charging/discharging.

Thank you.

Part Number:BQ27220

help me to check the programe? why can not change the design capacity?

Part Number:BQ40Z50-R1

Hi,

one of our customers has inquired if there are any differences to be expected by the different Hardware IDs of BQ40Z50-R1. Is there anything a customer should be aware of?

In particular, customer has received devices Hardware IDs 0x01, 0x03, and 0x0B.

Thanks and best regards,
Phil

Part Number:BQ34Z100-G1

I use the EV2300 customer development kit VB software to program an SREC file into fuel gauges such as the BQ78350, how do I get it to work for the BQ34Z100-G1?  Does the ProgramFromSrec function only work on the SMBUS interface?  if so can I connect the BQ34Z100 to this interface and use this function?

Thanks.

Part Number:BQ3050

Hello
Is the SN8765 a complete analogue of the BQ3050
In particular, I'm interested in Data Flash Values for SN8765. I can not find the Technical Reference on SN8765 anywhere.
I try to repair my home battery from the laptop in which, after replacing the elements, the maximum capacity is reset and calibration is not performed.
I work with the LPT programmer.
I would really appreciate any help!