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.

BQ76PL455A-Q1: BQ76PL455A-Q1:communication error when test on car

Part Number: BQ76PL455A-Q1
Other Parts Discussed in Thread: BQ76PL455A

We use 6PCS bq76pl455a-Q1 series to connect 96 cells in same PCB,for HEV BMS application,daisy chain connect witih  Cap isolate(2nf).

When test on car,it is easily to get interference,make the uart communication error ,even when the car motor work,it will be worse.

Usually, the desired amount of data cannot be received.

we need help to solve,thanks!

  • Hello user,

    bq76pl455's daisy chain is data pass through architecture, not reclocking as our newest bq79606a, so in noisy environment,

    its communication might be affected. Please follow up app note-SLUA791_bq76PL455A Design Recommendations about recommendation on daisy chain.

    It is also recommended to implement several SW workarounds such as multiple broadcast read, if still failed, then issue communication clear, then software reset.

    it is also recommended to break down the whole daisy chain into one or two daisy chains to make communication more robust.

    Thanks!

    Andy

  • Hello user,

    I will close this thread.

    You can open it if you still have question.

    Thanks!

  • Thank you for reply.

    When design we  follow up app note-SLUA791_bq76PL455A Design Recommendations about recommendation on daisy chain.

    • Besides these, are there any other solutions.

  • Hello user,

    I provide all comments.

    Maybe you can do below test step by step to verify signal integrity: only 2 455s in daisy chain, and then 3,4,5.

    If part of them daisy chained work, then you need to break down one daisy chain into two.

    Thanks!

    Andy

  • Dear Customer,

     

    we haven’t heard from you in a while, I assume you’ve been able to resolve your issue” …, then manually change the thread status to “Closed” in Thread Tracking Toolkit to avoid “Dropped thread” flag J.

     

    Thanks!

     

    Andy