• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 65 subscribers
  • Views 1203 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

BQ40Z50 qmax passed value is negative and soc stays at 100%

Naveenkumar Rajaram
Prodigy 40 points
Other Parts Discussed in Thread: BQSTUDIO, BQ40Z50

Hi,

     I have connected BQ40Z50EVM and BQ24735EVM. I can see charging and discharging cycles happening but SoC stays at 100% irrespective of charging/discharging state. Also I see Time to full and Time to empty also stays at 65535.

Is there any settings that I need to look at to get proper SoC %?

Thanks

  • 0
    Prodigy 80 points
    I have very similar behaviour: Gauging is turned on, I'm taking the battery through charging and discharging with TCA and TDA in BatteryStatus, but 0xD SOC is always 100%. What else must be done?
    For example, my driver is fetching the following:

    D/battery_jni( 4437): VOLTAGE 0x1D93 7571
    D/battery_jni( 4437): CURRENT 0xFFFFFD1F -737
    D/battery_jni( 4437): TEMPERATURE raw 0x0BB2 2994, 26.3°C
    D/battery_jni( 4437): SOC 0x0064 100
    D/battery_jni( 4437): SOCERR 0x0064 100 (cmd 0x0D)
    D/battery_jni( 4437): AVG_TIME_TO_EMPTY 0x0000 0
    D/battery_jni( 4437): AVG_TIME_TO_FULL 0xFFFF 65535
    D/battery_jni( 4437): CHARGING_VOLTAGE 0x20D0 8400
    D/battery_jni( 4437): CHARGING_CURRENT 0x0FA4 4004
    D/battery_jni( 4437): STATE_OF_HEALTH 0x0064 100
    D/battery_jni( 4437): BATTERY_STATUS 0x03C0 960
    D/battery_jni( 4437): CYCLE_COUNT 0x0001 1
    D/battery_jni( 4437): SAFETY_ALERT 0x00000000
    D/battery_jni( 4437): SAFETY_STATUS 0x00000000
    D/battery_jni( 4437): PF_STATUS 0x00000000
    D/battery_jni( 4437): OPERATION_STATUS 0x00000187
    D/battery_jni( 4437): CHARGING_STATUS 0x000410
    D/battery_jni( 4437): GAUGING_STATUS 0x0118E0
    D/battery_jni( 4437): MANUFACTURING_STATUS 0x0018
    D/Battery ( 4437): 7571mV -737mA 26.0°C 100% SOC, 100% SOCErr, 0min Runtime, 65535min Fulltime, 100% SOH, 0x3c0 status, 1 cycles, 8400mV Desired, 4004mA Desired, 0x0 safetyAlert, 0x0 safetyStatus, 0x187 opStatus, 0x410 chStatus, 0x118e0 gaugeStatus, 0x18 manufStatus
  • 0 in reply to Gregory Fung
    TI__Genius 10235 points

    Can you please generate a log file showing the behavior you are experiencing? You can download bqStudio (www.ti.com/.../bqstudio) if you already haven't. A log can be generated from the Registers screen. Also, please export a GG file from the Data Memory section so we can review the data flash settings.

  • 0 in reply to Chase7071949597
    Prodigy 80 points

    Chase7071949597 said:
    Can you please generate a log file showing the behavior you are experiencing

    I'm getting these results on my own linux user space driver, directly talking to the i2c/SMBus.  What you see are confirmed actual register responses.  Do you need any more registers read out?

  • 0 in reply to Gregory Fung
    Prodigy 80 points
    Here is some more info which I read at the beginning of my test program.

    D/battery_jni( 3384): MAC SAFETY_ALERT result 6: 0x400000
    D/battery_jni( 3384): MAC SAFETY_STATUS result 6: 0x000000
    D/battery_jni( 3384): MAC OPERATION_STATUS result 6: 0x000187
    D/battery_jni( 3384): MAC CHARGING_STATUS result 5: 0x00410
    D/battery_jni( 3384): MAC GAUGING_STATUS result 5: 0x018C0
    D/battery_jni( 3384): MANUFACTURER_DATE 0x0021
    D/battery_jni( 3384): SERIAL_NUMBER 0x0001 1
    D/battery_jni( 3384): SPEC_INFO 0x0031
    D/battery_jni( 3384): BATTERY_MODE new: 0xE080
    D/battery_jni( 3384): FULL_CHARGE_CAP 0x0000 0*10mWh
    D/battery_jni( 3384): DESIGN_CAP 0x0804 2052*10mWh
    D/battery_jni( 3384): MAC MANUFACTURING_STATUS result 4: 0x0018
    D/Battery ( 3384): MANUFACTURER_DATE Y1980 M1 D1, 1 serNr, 0x31 specInfo
  • 0 in reply to Gregory Fung
    Prodigy 80 points

    To be clear, I am developing with only the BQ40z50 and my android target over i2c/SMBus.  This thread was started by someone else, and I put my question here as it seemed similar.

  • 0 in reply to Gregory Fung
    TI__Genius 10235 points
    Greg,
    We really need to see the data flash settings in the gauge. If FCC is 0, then there are likely issues with the settings in the fuel gauge. As I mentioned previously, you should install bqStudio as this will allow you to read out the data flash settings and it will give us a snapshot of the current behavior of the gauge.
  • 0 in reply to Chase7071949597
    Prodigy 80 points

    I tried to download bqStudio but the export release form is not functioning properly.



    But, I assume this is some kind of PC software that is expecting to talk to some kind of microcontroller evaluation board or SMBus interface board?  I don#'t have such hardware.  Must I buy something?  do you have any programs or scripts that i can run in ARM linux on iMX6?

  • 0 in reply to Gregory Fung
    TI__Guru 73830 points
    Gregory,
    I tried the download and it is working properly. The file is a .zip file, so you will need to extract the setup program from it. You do have to use the EV2300 to communicate with the bq40z50 using the PC. We do not support scripts to communicate with the device using other tools.
    Tom