16-cell BMS

16-cell BMS

The goal of this BMS is to use mostly decade old components to create a 16 channel cell voltage meter. It uses a very accurate sigma/delta ADC for superb resolution. It can drain about 100mA from a cell or charge it with 50 mA via the DC/DC converter. The ability to both charge and discharge cells speeds up balancing despite the low balancing current.

When turned off it drains no current from the connected cells at all.

On the low voltage side it features two inputs for temperature sensors and one input for a 5V current sensor, differential or single ended.

It can be cascaded to be used with more than 16 cells and has an automatic addressing scheme to forgo the use of jumpers or DIP switches. All communication is done via CAN. Supply voltage is 12V with about 20 mA draw when not balancing.

The software is not yet finished, see forum for progress

The boards can be bought in the shop.

Pinout

The pinout is also written to the bottom silkscreen.

On the left side you see 17 inputs. The first one is connected to the negative pole (GND) of your (sub)pack, the subsequent ones to the positive poles of up to 16 cells. At least the lower two cell inputs must be connected. When cascading modules the positive-most input of module n is also the GND of module n+1, so must be spliced to connect to both.

On the top right is the vehicle interfacing or low voltage connector. From top to bottom it is low voltage GND, 12V, enable_in, enable_out, CANH, CANL. GND, 12V, CANH, CANL are connected to all modules in parallel whereas enable_out is chained to enable_in of the next module. The first enable_in must be connected to 12V whenever the BMS should become active, e.g. when charging or driving. The module with 12V on the enable_in auto-detects as "main" module, collects data from the subsequent modules and sends more high level CAN messages

On the bottom right is the temperature sensor and current sensor input. Top to bottom it is tsensor1+, tsenseor1-, tsensor2+, tsensor2-, 5V, CUR+, CUR-, GND. A single ended current sensor is just connected to CUR+.

Right now the current sensor is only supported on the main module and only one temperature sensor is supported.

Communication

All configuration, queries and firmware updates are done via the CAN bus. There is no independent web interface like known from e.g. the inverter. However there is a solution to connect an ESP32 via CAN and then have the known web interface or you can use Dave Fiddes "oic" tool for the command line. It is important to know that the main module has node-id 10 and the subsequent ones 10+i (i index of submodule, so 1st submodule has node-id 1). The base node id can be configured to start at something else than 10.

All info given here is preliminary and will likely change!

Apart from that the modules output periodic CAN messages depending on their role. The base address for cyclic messages defaults to 0x1F4 and can be changed by modifying pdobase on the main module. pdobase is ignored on the sub modules.

All modules output on ID 501 (0x1F5) + i

start	length	item	description
0	13	umin	minimum cell voltage of module i
16	13	umax	maximum cell voltage of module i
30	2	counter	counts from 0-3 (anti-freeze)
32	13	uavg	average cell voltage of module i
48	8	tempmin	Minimum temp +40 on module i
56	8	tempmax	Maximum temp +40 on module i

The main module does not output its local accumulated values but accumulated values over all modules.

In addition the main module outputs on id 500 (0x1F4)

start	length	item	description
0	11	chargelim	maximum charge current in A
11	11	dischargelim	maximum discharge current in A
22	10	soc	Pack soc in 0.1%
32	16	idcavg	Averaged current reading of last 1s in 0.1A - signed!
48	10	utotal	Total pack voltage in V
62	2	counter	counts from 0-3 (anti-freeze)

Reading individual cell voltages

Cell voltages are only available via CAN SDO from the module that measures them. So voltages 1-16 must be queried from the first (main) module, 17-32 from the 2nd (1st submodule) and so on. With Dave Fiddes tool this translates to:

oic -n 10 dumpall #dumps all values including cell voltages from 1st module
oic -n 11 dumpall #same for second module
oic -n 11 read u0 #Read first cell voltage of second module

For querying voltages say in your arduino sketch you'll need to acquire every voltage separately by sending and receiving SDO messages

0x60A#0x40 idhigh 0x21 idlow 0 0 0 0

idhigh and low are the bytes of the internal ID. The id of the first cell voltage is 2006 (0x7D6) so for querying the 1st cell voltage of the first module you send

0x60A#0x40 0x07 0x21 0xD6 0 0 0 0

And you will receive the reply

0x58A#0x43 0x07 0x21 0xD6 0xD0 0xED 0x01 0

0x0001EDD0 is the voltage value which decodes to mV x 32. So 0x1EDD0/32 = 3950.5 mV.

The next cell would be on 0x7D7 and the last on 0x7E5. The next 16 voltages are then queried from node id 0x60B.

Configuration Parameters

There is currently a limited set of parameters which will be extended as the software grows. This table always reflects the latest git commit. Check the page history for previous versions.

These are the parameters of v0.16.B

Name	Unit	Min	Max	Default	Description
BMS
gain	uV/dig	1	1000	586	Scaling factor from ADC digits to mV
correction0	ppm	-10000	10000	-1250	The first two and the last channel have slightly different topology and need their own correction factor
correction1	ppm	-10000	10000	1500
correction15	ppm	-10000	10000	1000
numchan		1	16	16	Number of cells connected to the module
balmode		0	3	0	Balancing mode 0=No balancing 1=Only bump up low cells 2=Only dissipate high cells 3=Do both
ubalance	mV	0	4500	4500	Voltage above which top balancing is started
idlewait	s	0	100000	60	Number of seconds to wait after stop of current flow to measure unloaded cell voltage und start balancing
Battery Characteristics
dischargemax	A	1	2047	200	Maximum discharge current
nomcap	Ah	0	1000	100	Nominal capacity
icc1	A	1	2000	50	Maximum charge current of empty battery
icc2	A	1	2000	30	Maximum charge current of roughly half-charged battery
icc3	A	1	2000	20	Maximum charge current of rather full battery
ucv1	mV	3000	4500	3900	First constant voltage set point. Transition to next one when dropping below icc2
ucv2	mV	3000	4500	4000	Second constant voltage set point. Transition to next one when dropping below icc3
ucellmax	mV	3000	4500	4200	Third constant voltage set point and maximum cell voltage
ucellmin	mV	1000	4500	3300	Minimum loaded cell voltage. Discharge limit is dropped to stay above this value
chargeXsoc	%	0	100		Percentage of charge current at soc X. In between two points charge current is interpolated
Sensor Setup
idcgain	dig/A	-1000	1000	10	Gain (or actually division factor) of current sensor
idcofs	dig	-4095	4095	0	0A offset
idcmode		0	3	0	Current sensor mode 0=Off, 1=Single Ended ADC, 2=Differential ADC, 3=ISA current shunt
tempsns		-1	3	-1	Temperature sensor -1=Off, 0=JCurve, 1=KTY81, 2=PT1000, 3=LeafBMS
Communication
pdobase		0	2047	500	base COB Id for cyclic messages. Main module uses pdobase and pdobase+1, 1st submodule uses pdobase+2 and so on
sdobase		0	63	10	base node ID for SDO queries. Main module uses sdobase, 1st submodule sdobase+1 and so on

Operation

Calculating current limits

Limiting charge and discharge current are the only means of this BMS to protect the battery. It has no means to turn off the current flow by itself but instead relies on the connected components to obey the calculated current limits that are sent out via CAN. The current limits are calculated in a number of steps.

Charge Curve

The initial approach was to assign a certain charge current to points in the SoC curve. This method can be skewed if the SoC calculation is off for some reason. The new method deploys 3 CC/CV regulators. This was copied from oberving VWs charge curve of the MEB cars. The first regulator has the highest charge current and aims for a voltage typically around 3.9V for many NMC chemistries. When current drops below the CC value of the second regulator then that one is used, aiming for a higher voltage of typically 4V. And finally the 3rd regulator takes over aiming for the charge end voltage of typically 4.2V. When setting all 3 to the same values a simple CC/CV curve is generated.

Voltage limits

Voltage limits are enforced via a P-regulator. I.e. as we approach the upper or lower voltage limit current is cut back to stay away from the limits until it reaches 0A. The upper and lower limit is configurable

Temperature limits

These are not enforced yet. High temperature will cut back both charge and discharge current whereas low temperature will only cut back charge current.

Energy limits

Not enforced yet. Some OEM BMSes cut back charge current after a certain amount of energy has been put into the battery. E.g. When starting charge at 50% charge rate will end up higher at 70% than if we start charging at 10%.

Calibration

As every instrument the voltage measurement needs to be calibrated to cancel out tolerances in the involved components. There are 4 parameters for calibration.

• gain : The translation ration between the ADC digits and mV. This applies to all channels
• correction0, 1 and 15 : This allows special tuning of said 3 channels because they use a slightly different current path and thus need a small gain correction

Calibration procedure

First we determine the general gain. Pick any of the voltages between u2 and u14 which share a common gain factor. Use a good multimeter to measure the physical voltage of your reference channel. Now tune the gain parameter until your multimeter and the BMS voltage read the same value +-0.5mV. Now all channels from 2-14 should read correctly.

Then for channels 0, 1 and 15 also measure the physical voltage input and tune the respective correctionX parameter until multimeter and BMS report the same voltage. The correction factors can be negative if a channels reads too high.

Save your parameters to flash to make the calibration permanent.

Flashing firmware

If like me you have sourced the BMS boards from an alternative source then you will need to flash the bootloader and firmware onto the BMS. This is a relatively straightforward process once understood but took me a while to get it to work.

Firstly you will need an STLink dongle, I used this one but I believe any will do.

I used STM32CubeProgrammer on Linux to flash my board and also (prior to flashing) upgrade the STLinkdongle to the latest firmware (might not be necessary but felt it was wise to do so).

Once you've got STM32Cubeprogrammer installed you're probably best erasing the STM32 Chip to ensure you're starting from a clean board. Navigate to the "Erasing & Programming" tab on the left and connect to your STlink dongle (if you havent already). Once connected, (you can also update the firmware on the dongle at this point on the "Memory & File Editing" tab), connect the dongle to the BMS board via the VDCG pins...

(V = Voltage 3.3V, D = SWDIO, C = SWCLK, G = Gnd)

and perform a "full chip erase".

Once thats complete head over to Github to download the Bootloader and download the hex file (you may need to be logged in to download the files).

Once downloaded, in STM32CubeProgrammer, navigate to the "Memory & File Editing" tab and open the hex file you just downloaded, once opened you can use the "Download" button to flash the bootloader to your BMS board.

You can now repeat the above process of opening the hex file and "downloading" to the BMS board for the main BMS firmware which is available from the BMS Github repository .

Once all that is done, you can move onto the Web interface. You'll need the "Can Backend" version of the ESP32 Web Interface available here (click the green code button and download zip)

Once downloaded download Arduino IDE 1.8.19 (you'll need this version, nothing beyond version 2 as this does not support SPIFFS flashing as far as I'm aware) and set it up for flashing to ESP32 boards and also flashing ESP32 Spiffs .

To setup the Web interface Arduino sketch, you'll want to unzip and (IMPORTANT) RENAME the folder to "esp32-web-interface" to match the ino file within the folder, if you don't do this you'll have problems further down the line. Once unzipped and renamed, open the esp32-web-interface.ino sketch file and upload it to your ESP32 dev board. when this completed you'll also need to upload the SPIFFS image, you can do this by going to Tools and "ESP32 Sketch Data Upload" and choosing SPIFFS. once this is complete, you can connect your ESP32 to your BMS board via CAN and power them and they shuld work (note you'll need the 12V enable in line connected also).

Once on the Web interface, select Node ID 10 and a speed of 500kbps and you'll have all your wonderful BMS spot values and params ready to go.

Operating Limits

• Max voltage for the board is 70v
• Max number of cells is 16