• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 62 subscribers
  • Views 251 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.

BQ76PL536A: Connection order issue

Torsten Dense
Prodigy 20 points
Part Number: BQ76PL536A
Other Parts Discussed in Thread: BQ79616

Hello

we got some issues with connection of battery pack with BMS configured with three stacked BQ76PL356 front ends in following configuration: 6/5/3 cells (in sum 14S configuration). Actually the connection order is BAT_MINUS --> Top_Cell --> Cell1_to_13. All cells and input are protected with 5.2V Z-Diodes.
Somewhere in connection process the top front end with 3 cells gots defect and drwas significant current from the top three cells even in sleep mode. All measurements and communication is running well.

I am aware that the recommended connection order is from bottom to top, nevertheless I would like to understand what could went wrong with this oder.  Is there any protection diode inside the front end which could get broken in plugging moment? Is there any issue when working only with three cells on one front end?


Thanks

Torsten

  • 0
    TI__Genius 17370 points

    Hi Torsten,

    For this device its possible to be more susceptible to this kind of event, is there any reason you are using this device instead of bq79606a or bq79616? These devices are much more adept to handle hotplug transients with fewer external components.

    Regards,

    Taylor

  • +1
    Prodigy 20 points

    Hi Taylor,

    the design is well introduced in market so we do not have the chance to change front end in short term. We only wanted to understand the issue reason, and what really is the problem with this.

    Thanks

    Torsten

  • 0 in reply to Torsten Dense
    TI__Genius 17370 points

    Torsten,

    Understood but this device was actually designed long ago and is more susceptible to this kind of transients than our newer devices, and there is not as many support resources to diagnose an issue like this. If you are following our recommended external components and still see this behavior, I recommend submitting a return so we can have some analysis performed.

    Regards,

    Taylor