• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 62 subscribers
  • Views 433 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

EV2400: Command sequence the EV2400 uses to shutdown a battery pack

Daniel Loranger
Prodigy 75 points
Part Number: EV2400
Other Parts Discussed in Thread: BQ8050, BQSTUDIO

Hello,

I am working on a charger board issue which can only be created when using batteries that are in the shutdown state (new from factory). 

We have found that we can reliably shutdown the batteries (BQ8050 interface) using the BQ software and the EV2400 module to send the value 0x0010 to the 0x00 register of the battery, however, we need to fully automate the process of shutting down the batteries and then waking up the charger board to be able to cycle the system to get the failure to show. Currently we have to move the series of smart batteries back and forth between the charger board and the EV2400 interface to perform this shutdown.

I have tried just sending the 0x00 register the word 0x0010, not sure what I am missing to get this working as expected.

Can you share a workflow/code snip that will allow us to implement this functionality in our scripted routine?

  • 0
    TI__Guru** 102355 points

    Hello Daniel,

    Are you using bqStudio to communicate? What is the gauge/charger you're working with, can you explain what you're working with a little further?

    The EV2400 is designed to interface with our gauges and chargers using bqStudio.

    Sincerely,

    Wyatt Keller

  • 0 in reply to Wyatt Keller
    Prodigy 75 points

    Hi Wyatt,

    I am using bq Evaluation software package 1.05 with the EV2400 to shutdown the batteries.  The charger board applies voltage to wake up the batteries which is when we get into the fault condition I am working on. The pathway through our charger board is a bit of a mess (i2c muxes, multiple packs with same addresses, etc) so there is application code to read the batteries from there. That is all working fine, other than the issue where batteries are shutdown.  This is all design specific and we think we have the situation figured out, just need to cycle test to demonstrate the fix is actually a fix statistically.

    The situation I am trying to recreate is when the battery pack is removed from all that charger mess and plugged directly into the EV2400.  Using the BQ Evaluation software, by entering 0x0010 to the manufacture access field tells the pack to shut down (turn off the output fets at least).   by being able to replicate whatever the BQ/EV2400 are doing in the backend, I can return each battery to the shutdown state and repeat the power on event.

    I am using a raspberry pi to communicate with the batteries (relays to get batteries disconnected from the charger), so I have full control over the I/O connected to the batteries in case I need to write a command, clear the I/O, pulse a pin, turn the clock 3 hours ahead, whatever.  I just need to know what is happening in the backend so I can recreate it for my test.

  • 0 in reply to Daniel Loranger
    TI__Guru** 102355 points

    Hello Daniel,

    Please reference this other thread: e2e.ti.com/.../888116

    I would recommend you get in contact with your FAE so we can share more info via other means.

    Sincerely,

    Wyatt Keller