I decided to make a confluence page as I validated the BMS carrier rev 1.1, so here it is. I’ll be following the validation guide (Validation - BMS Carrier ).
Before Starting
Inspected the board thoroughly for solder bridges and bad solder joints, and fixed up a few.
Gave the board a good clean with a toothbrush, ethanol (rubbing alcohol) since I didn’t have any isopropyl alcohol, water, and a cloth.
Made sure the controller board that I was going to use works by running the booard validation scripts (Board Validation ).
LEDs were checked for the correct polarity.
LED5 (which is actually a duplicate of LED4), the fan indication LED was installed backwards.
At this point, the isoSPI ICs are not populated, nor are the micro fit connectors for the HV relays, killswitch, or fans. We will add them as necessary as we go through the test. This board has already been powered up and some testing done - 12V was initially connected backwards, so there could be more issues on this board.
Power Validation
GND, 3V3, 5V, and 12V test points are all isolated from each other, tested with the multimeter continuity test.
Removed R23. This is a 0 ohm resistor between the Current Sense output of the load switch and the input of the MCU for measurement. Why do we need to remove this (Liam Hawkins)?
Without the controller board connected, 12V tested good. Installing the controller board, both 3V3 and 12V are good!
5V does not seem to be powering on. It slowly rises to 1.8V, and then stays there. I was artificially turning on EN with another power supply connected to wires I had soldered to R3. I realized that the wire also touched R2, and caused this behaviour. Fixing this, the 5V converter works and we get 4.935V.
86mV Vpp on no load, 20mV Vpp for both 1A and 2A loads. Oscilloscope was set to AC coupled, triggering on rising edge.
^ No load
^ 1A Load
^ 2A Load
Now I need another working controller board to complete the validation.