• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 63 subscribers
  • Views 775 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.

Timeout on balancing in bq76940 AFE

Jessica Riley1
Intellectual 280 points

Hello,

I am concerned about the case where we've enabled balancing on a cell in the AFE, then communication is lost for some reason.  Is there any kind of time-out on balancing if comm is lost with the AFE?  Or will it balance the cell indefinitely until it is fully discharged?

Thanks for your help,

Jess

  • 0
    TI__Expert 6085 points
    Hi Jessica,
    On the STACK device has its own independent scheduler and not sync to one another. The scheduler is responsible for controlling start, stop of voltage measurements, Coulomb counting, cell balancing and stacked die communications. when cell balancing is ENB, each cell is measured 12.5ms as well temp in the first 250ms period of the 2sec period. Now per your question on communication disruption, this could be happening due to spurious current spike on SRN/SRP node. make sure CC_GFG is programmed with 0x19. hope this helps out. thanks vish
  • 0 in reply to Vish Nadarajah
    Intellectual 280 points
    Thanks for the quick response.

    I'm actually concerned about the case where we lose communication with our host controller. If the host controller were to set the AFE to balance a cell, then for some reason lose communication with the AFE (could be the host controller loses power), would the AFE turn off the balancing outputs at any point?

    Thanks,
    Jess
  • 0 in reply to Jessica Riley1
    TI__Expert 6085 points
    In the case of host controller setting up the AFE to Balance , and to loose communication with AFE, the AFE's scheduler and CB1, CB2, CB3 registers will be active( not cleared) and executing to the internal register value until hitting Vshut threshold or Vporz limits.
  • 0 in reply to Vish Nadarajah
    Intellectual 280 points

    Thanks for the clarification!