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.

BQ78350-R2-DEVICE-FW: Which parameters have to be scaled when using IPscale ?

Part Number: BQ78350-R2-DEVICE-FW

Hello Again, after investigaton a lot and reviewing all related threads i am still not sture which parameters are influenced by IPScale.

Could you please mark in the list below the items which have to be scaled by IPscale?

The documentation is really unsufficient at this point and the customer has to spend tons of hours to read through different documents...

Please help. Thanks in advance!

* Field Order: Class name Subclass name Parameter name Parameter Value Display Units
Calibration Current Deadband Deadband 10 mA
Calibration Current Deadband Coulomb Counter Deadband 38 264nV
Protections OCC Threshold 11000 mA
Protections OCC Recovery Threshold 10000 mA
Protections OCD Threshold -30000 mA
Protections OCD Recovery Threshold -28000 mA
Protections PTO Charge Threshold 2000 mA
Protections PTO Suspend Threshold 1800 mA
Protections PTO Reset 2 mAh
Protections CTO Charge Threshold 2500 mA
Protections CTO Suspend Threshold 2000 mA
Protections CTO Reset 2 mAh
Protections OC Threshold 1000 mAh
Protections OC Recovery 10 mAh
Permanent Fail SOCC Threshold 28000 mA
Permanent Fail SOCD Threshold -28000 mA
Permanent Fail VIMR Check Current 10 mA
Permanent Fail CFET OFF Threshold 5 mA
Permanent Fail DFET OFF Threshold -5 mA
Advanced Charge Algorithm Low Temp Charging Current Low 132 mA
Advanced Charge Algorithm Low Temp Charging Current Med 352 mA
Advanced Charge Algorithm Low Temp Charging Current High 264 mA
Advanced Charge Algorithm Standard Temp Charging Current Low 1980 mA
Advanced Charge Algorithm Standard Temp Charging Current Med 4004 mA
Advanced Charge Algorithm Standard Temp Charging Current High 2992 mA
Advanced Charge Algorithm High Temp Charging Current Low 1012 mA
Advanced Charge Algorithm High Temp Charging Current Med 1980 mA
Advanced Charge Algorithm High Temp Charging Current High 1496 mA
Advanced Charge Algorithm Rec Temp Charging Current Low 2508 mA
Advanced Charge Algorithm Rec Temp Charging Current Med 4488 mA
Advanced Charge Algorithm Rec Temp Charging Current High 3520 mA
Advanced Charge Algorithm Pre-Charging Current 100 mA
Advanced Charge Algorithm Maintenance Charging Current 44 mA
Advanced Charge Algorithm Termination Config Charge Term Taper Current 450 mA
Fuel Gauging Current Thresholds Dsg Current Threshold 20 mA
Fuel Gauging Current Thresholds Chg Current Threshold 20 mA
Fuel Gauging Current Thresholds Quit Current 10 mA
Fuel Gauging Design Design Capacity mAh 9000 mAh
Fuel Gauging Design Design Capacity cWh 19440 cWh
Fuel Gauging State Learned Full Charge Capacity 9000 mAh
Fuel Gauging CEDV cfg FCC Learn Up 1024 mAh
Fuel Gauging CEDV cfg FCC Learn Down 1024 mAh
Fuel Gauging CEDV cfg OverLoad Current 30000 mA
Fuel Gauging CEDV cfg Near Full 200 mAh
Fuel Gauging CEDV cfg Reserve Capacity 0 mAh
Power Sleep Sleep Current 20 mA
PF Status Device Current Data Current 0 mA
SBS Configuration Data Remaining AH Cap. Alarm 300 mAh
SBS Configuration Data Remaining WH Cap. Alarm 432 cWh
Lifetimes Current Max Charge Current 0 mA
Lifetimes Current Max Discharge Current 0 mA
Lifetimes Current Max Avg Dsg Current 0 mA
Lifetimes Current Max Avg Dsg Power 0 cW
  • Hi Andreas,

    All of the current (mA) and capacity (mAh) parameters should be scaled. You do not need to write the Lifetimes data or PF Status (these are written by the device). You may not want to scale some of the very small current parameters such as Current Deadband since it will be too small. 

    The cWh parameters should not be important unless you are setting the [CAPM] bit in the Battery Mode register to '1' (device reports some parameters in mW and mWh instead of mA and mAh).

    The Coulomb Counter Deadband does not need to be scaled. However, I've learned that a setting of '9' is the optimal setting instead of the default setting of '38'. 

    Best regards,

    Matt

  • Hello Matt,

    thank you for the very quick response!

    Unfortunately my fears came true and i have to rescale more than 44! Parameters in case i want to use IPscale = 1.

    This is a bit unconvienent, failure-prone and honestly spoken "not user friendly" ;-(

    I would expect from TI-developers that such a power full software is able to rescale all parametery by itselv when IPscale is used.

    Nevertheless, this feedback helps and i now know what to do...

    Thanks!

    Andreas