• State
  • Locked Locked
  • Replies 11 replies
  • Subscribers 63 subscribers
  • Views 270 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-R2: BQ40z50 R2

Sadatan Vashistha
Prodigy 100 points
Part Number: BQ40Z50-R2
Other Parts Discussed in Thread: BQSTUDIO, , EV2400

Tool/software:

I am using BQstudio to monitor my battery pack which is a 4S2P battery pack using bq40z50-R2 IC inside it.

Now I have two queries:

1. Will I be able to get DCIR values during charging and discharging of battery

2. Also when I am logging the data I am getting some errors "ERROR : Please check Log file\Trial7 Charge Discharge-LV2017.log.err". Why I am getting these errors

  • 0
    TI__Mastermind 28480 points

    Hello,

    Sadatan Vashistha said:
    1. Will I be able to get DCIR values during charging and discharging of battery

    The gauge calculates and updates the resistance table for each cell while in discharge, however they do not update in charge.

    Sadatan Vashistha said:
    2. Also when I am logging the data I am getting some errors "ERROR : Please check Log file\Trial7 Charge Discharge-LV2017.log.err". Why I am getting these errors

    Can you please share this file so we can look into the error?

    Regards,

    Anthony

  • 0
    Prodigy 100 points

    Hi Anthony,

    Please find attached error file for your reference. When ever this error occurs value of some of the register bit changes .

  • 0 in reply to Sadatan Vashistha
    Prodigy 100 points

    Please find below error file data for your reference. Whenever this error occurs value of some of the register bit changes.

    "
    Wed Nov 27 20:15:58 IST 2024

    Time,LogCaption,Error Code,Error String
    2024-11-27 20:15:58,MaxTurboCurr,772,No acknowledge from device.2024-11-27 20:45:58,NoLoadRemCap,772,No acknowledge from device.2024-11-27 20:46:00,TrueRemQ,772,No acknowledge from device.2024-11-27 21:16:13,ChgCurr,772,No acknowledge from device.2024-11-27 21:45:56,@TimeFull,772,No acknowledge from device.2024-11-27 21:46:25,QMax1,772,No acknowledge from device.2024-11-27 21:46:25,QMax2,772,No acknowledge from device.2024-11-27 23:25:41,MaxTurboCurr,772,No acknowledge from device.2024-11-27 23:34:24,TempRange,772,No acknowledge from device.2024-11-27 23:34:34,MaxTurboCurr,772,No acknowledge from device.2024-11-27 23:34:34,SusTurboCurr,772,No acknowledge from device.2024-11-27 23:42:55,SafetyStatAB,772,No acknowledge from device.2024-11-27 23:42:55,SafetyAlertCD,772,No acknowledge from device.2024-11-27 23:42:55,SafetyStatCD,772,No acknowledge from device.2024-11-28 04:24:38,TempRange,772,No acknowledge from device.2024-11-28 04:24:38,ChgStat,772,No acknowledge from device.2024-11-28 04:24:38,GaugeStat,772,No acknowledge from device.2024-11-28 04:24:38,ITStat,772,No acknowledge from device.2024-11-28 04:24:38,MfgStat,772,No acknowledge from device.2024-11-28 04:37:27,SafetyStatAB,772,No acknowledge from device.2024-11-28 04:37:27,SafetyAlertCD,772,No acknowledge from device.2024-11-28 04:37:27,SafetyStatCD,772,No acknowledge from device.2024-11-28 04:37:27,PFAlertAB,772,No acknowledge from device.2024-11-28 04:37:27,PFStatAB,772,No acknowledge from device.2024-11-28 05:57:29,BattMode,772,No acknowledge from device.2024-11-28 17:24:54,NoLoadRemCap,772,No acknowledge from device.2024-11-28 17:24:54,TrueRemQ,772,No acknowledge from device.2024-11-28 17:24:56,TrueRemE,772,No acknowledge from device.2024-11-29 20:15:24,ManufAccess,772,No acknowledge from device.2024-11-29 20:15:24,RemCapAlarm,772,No acknowledge from device.2024-11-29 20:15:24,RemTimeAlarm,772,No acknowledge from device.2024-11-29 20:15:24,@Rate(@),772,No acknowledge from device.2024-11-30 05:22:35,PFAlertAB,772,No acknowledge from device.2024-11-30 05:22:37,PFStatAB,772,No acknowledge from device.2024-11-30 15:31:41,PFAlertAB,772,No acknowledge from device.2024-11-30 15:31:41,PFStatAB,772,No acknowledge from device.2024-12-01 03:04:21,SafetyAlertAB,772,No acknowledge from device.2024-12-01 03:04:21,SafetyStatAB,772,No acknowledge from device.2024-12-01 03:04:21,SafetyAlertCD,772,No acknowledge from device.2024-12-01 03:04:21,SafetyStatCD,772,No acknowledge from device.2024-12-01 07:30:27,AvgTimeFull,772,No acknowledge from device.2024-12-01 07:30:27,ChgCurr,772,No acknowledge from device.2024-12-01 07:30:27,ChgVolt,772,No acknowledge from device.2024-12-01 07:30:27,CycleCnt,772,No acknowledge from device.2024-12-02 02:07:49,@TimeFull,772,No acknowledge from device.2024-12-02 02:07:49,@TimeEmpty,772,No acknowledge from device.2024-12-02 02:07:49,@RateOK,772,No acknowledge from device.2024-12-02 02:07:49,Temperature,772,No acknowledge from device.2024-12-02 02:07:49,Voltage,772,No acknowledge from device.2024-12-02 04:30:46,NoLoadRemCap,772,No acknowledge from device.2024-12-02 04:30:46,TrueRemQ,772,No acknowledge from device.2024-12-02 08:01:11,IntTemp,772,No acknowledge from device.2024-12-02 08:01:11,TS1Temp,772,No acknowledge from device.2024-12-02 08:01:11,TS2Temp,772,No acknowledge from device.2024-12-02 17:58:44,PFAlertAB,772,No acknowledge from device.2024-12-02 17:58:44,PFStatAB,772,No acknowledge from device.2024-12-02 17:58:44,PFStatCD,772,No acknowledge from device.2024-12-02 17:58:44,CellVolt1,772,No acknowledge from device.2024-12-02 17:58:44,CellVolt2,772,No acknowledge from device.2024-12-02 17:58:44,CellVolt3,772,No acknowledge from device.2024-12-02 18:29:55,BattStat,772,No acknowledge from device.2024-12-02 18:29:55,MaxTurboPwr,772,No acknowledge from device.2024-12-02 18:29:55,SusTurboPwr,772,No acknowledge from device.2024-12-02 18:29:55,MaxTurboCurr,772,No acknowledge from device.
    "
  • 0 in reply to Sadatan Vashistha
    TI__Mastermind 28480 points

    Hi Sadatan,

    "No acknowledge from device" means there was an issue in the communication between the EV2400 and the device. How often is information being polled from the device? Is the device in normal mode at this time and not in shutdown?

    Regards,

    Anthony

  • 0 in reply to Anthony
    Prodigy 100 points

    Hi Anthony,

    The time set in the BQstudio for logging the data is 4 Sec. And these errors are coming when we are running the charging and discharging profile and logging the data in the log file.

    Regards,

    Sadatan

  • 0 in reply to Anthony
    Prodigy 100 points

    Hi Anthony,

    The time set in the BQstudio for logging the data is 4 Sec. And these errors are coming when we are running the charging and discharging profile and logging the data in the log file.

    Also, is there any operating temperature range for EV2400 as we need to put it in temperature chamber.

    Regards,

    Sadatan

  • 0 in reply to Sadatan Vashistha
    TI__Mastermind 28480 points

    Hi Sadatan,

    What temperatures are the EV2400 being applied to in this testing?

    Regards,

    Anthony

  • 0 in reply to Anthony
    Prodigy 100 points

    Hi Anthony,

    Testing will be done from 0 to 60 Degree Celsius.

    Also, what do you think could be the reason for the error issue which I have shared before. Is it because of communication failure, if yes what could be the reason?
    For your information, we are using 2 battery and using 2 instances of BQ studio to read data from these two batteries at a time.

    Regards,

    Sadatan

  • 0 in reply to Sadatan Vashistha
    TI__Mastermind 28480 points

    Hi Sadatan,

    The EV2400 was designed to function at room temperature, so I believe implementing it in high or low temperature scenarios can affect the performance of it.

    Sadatan Vashistha said:
    For your information, we are using 2 battery and using 2 instances of BQ studio to read data from these two batteries at a time.

    For clarification, are you communicating with two batteries to one EV2400 or two EV2400s? If there is a EV2400 for each device there should not be an issue running two instances of bqStudio on one computer.

    Regards,

    Anthony

  • 0 in reply to Anthony
    Prodigy 100 points

    Also, there are few instances where we are getting random values for the registers and register bits and a blank in Log status instead of "SUCCESS" and there is no error logged for that time stamp in the error file? Do you think this is also due to the communication failure at that time stamp (instance)?

    It is shown in the green highlighted row.

    Regards,

    Sadatan

  • 0 in reply to Sadatan Vashistha
    TI__Mastermind 28480 points

    Hi Sadatan,

    Was this instance taken while the EV2400 was being used not at room temperature? Also, what is the current rate that the EV2400 is polling information from the device?

    Regards,

    Anthony