Flying ADC 16 channel BMS 96S test

[mario]

@Mario How did you diagnose Q5? I have some possibly unrelated issues with my boards but looking for ways to test different components to identify issues.

Johu described this earlier... Measured source vs drain pin with multimeter in diode test mode... It should show about 0.5V if it's ok. Mine was shorted.

[Jacobsmess]

Ah of course, when shorted what shows on your multimeter? Im a little confused as my Q5 shows around 0.7v on both working and non-working boards...

[mario]

Ah of course, when shorted what shows on your multimeter? Im a little confused as my Q5 shows around 0.7v on both working and non-working boards...

It shows continuity - it beeps.

[Jacobsmess]

Ok thanks, I can only really assume mine are OK....

[mario]

@johu I tracked it down to Q5 being defective and replaced it.
All the other components look fine, and I’ll connect the BMS back to the battery.

Do you have any recommendations to avoid stressing or burning components on startup?
Would it make sense to disable balancing before power-up, or is there a better approach?

After that, I tested again:
Powered the boards without the battery and board #4 reports BALANCER_FAIL with errinfo 218.
Then I connected the battery and, per earlier instructions, manually set enable to ON... all channels on board #4 read correct values.
I tried restarting boards few times and the board #4 reports BALANCER_FAIL but with different errinfo codes (338, 540, 347, 386).

For now, I’ve disabled balancing on board #4 and left the others in balancing mode Both.
All the other boards work as expected.

@johu, since all channels read correct values on board #4, is your request to measure input on ADC still relevant?
What else I can do to address BALANCER_FAIL error?

[johu]

The balancer test basically disconnects all mux channels and then enables the balancing FETs Q15 and Q14. Then it expects to see 5V on the ADC input. ~500 digits means it only sees a small fraction. Maybe balancing FETs broken?
You can also disconnect the battery, set testchan to 0 and testbalance to Additive. You should then see 0V on the gate of Q15 and 5V on Q14. On the ADC input you should also see 5V.

[maiks]

Hello,

Based on the documentation, the BMS uses a shunt as one of its current sensors.
The shunt communicates via the CAN bus, using the CAN_H and CAN_L lines.

Could you please clarify where I should connect the shunt’s CAN communication lines (CAN_H and CAN_L) on the main board?

Thank you in advance!

[johu]

uh oh, that's not currently implemented but will add it. Which shunt are you using?

[maiks]

Thanks for the update
I use Isabellenhuette Current Sensor Shunt w/Connectors IVT-S-1K-U3-I-CAN1-12/24 ISA
That l purchased from ebay https://www.ebay.com/itm/335212904644

[maiks]

uh oh, that's not currently implemented but will add it. Which shunt are you using?

I have two v2.2 boards running firmware v0.23B.
I’m attempting to update both to the latest firmware, but the upload process consistently fails at around 3% (see attached image).

I’ve retried the update multiple times on 2 boards with the same result

Could you please advise what might be causing this or suggest troubleshooting steps?

Thank you!

[Jacobsmess]

Delete any .json files from the files section

[maiks]

Delete any .json files from the files section

l have only one file in the location and thats .bin file

[manny]

On the web interface

[maiks]

On the web interface

firmware failure.png

thank you . l had only 1 .json file deleted it but no change

[johu]

Are you running 500k CAN Baudrate?

[maiks]

Are you running 500k CAN Baudrate?

I’m running it on a 500k baud rate.
I applied 12V to the BMS ENA_IN pin for about 4 seconds, and the board powered on (LEDs started lighting).
Next, I set the node ID to 10, and it successfully displayed the current BMS firmware version.

When I proceeded to update the firmware, I clicked Install, selected the firmware file from my PC, and confirmed. The installation began, but after reaching 3%, the BMS powered off (lights went out), and the update process froze at 3%

[johu]

ok, try keeping ena_in powered during update.

[maiks]

ok, try keeping ena_in powered during update.

Yes, it worked — thank you so much. However, one of the boards tried to update and then stopped midway. The indicator lights went off permanently. I’ve tried power cycling it, but it still won’t light up. I’ve checked all the wiring, and everything seems intact. What could be the problem?

[johu]

just connect it to the CAN bus alone without the other module. Of course there will be no parameters. Just start the update anyway and it should go through

[maiks]

just connect it to the CAN bus alone without the other module. Of course there will be no parameters. Just start the update anyway and it should go through

It has worked . Thanks alot