This is still a proof of concept & a discussion on how to implement the acrive balancing. Take a look to the original v4 version.
Iām using a bigger general purpose micro controller, the fact that to keep the boards the same size of the v4 I had to make some decision:
1.Active balancing require a lot of discrete stuff, using an external dedicated IC require less space. Discrete solutions require multiple opamps, mosfet drivers, mosfets, ?..
2. The current solution is cheaper. the IC require fiew passives.
3. Implementing the DCDC Buck boost on the FW require a ālotā of resources that during initial phase of the development were not available (Initially I wanted to use the same AtTiny)
But Yes, youāre right I would prefere to have only a programmable chip with FOSS instead of a proprietary solution.
Thanks, things are looking better now!
This in my opinion could reduce the community ability to change and improve the software for their needs. That is why Iāve chosed to work with the Arduino/Platformio. (the initial debug code is for arduino)
An STM32 could also be another good alternative.
The problem to implement the ETA3000 is the fact that we need three differential ADC channels to measure the local cell and the next cell to properly know if we can dump power to the next cell. One of which is used to monitor the balancing current.
Right now I donāt have a schematic for that, the connection is the same of V4, but you also have a sense cable that connect the cell balance of cell N to the positive of cell N+1 to read itās voltage and provide the power if we need balancing.
Yes the V5 code has been tested on the 328P variant (except the sleep mode see below).
Take a looks that you cannot put the IC in complete sleep due to a lack of Serial RX wakeup ISR on the 328P variant but the PB have it but the AVR studio C library have a bug:
This is another reason Iāve put on hold the project.
Why you say so? Instead of loosing the energy we move the power to the adiacent cell. Both UP and DOWN. This can be done on both charging and discharging process.
Iām open to suggestions, the fact the you want to keep the DIYBMS make sense. Even if this is a directly derived project. In fact as you requested Iāve also implemented your protocol. (We could mix and match modules - THIS REQUIRE TESTING)
Suggestions for the name are OPEN.
To sum up the current status:
Once I get some time for the project I will order the components that are missing and Iāll show you a prototype.
Batteries, MCUs, Connectors, Passives, and PCBs are here.
I have created an Arduino Uno based prototype and used a scope/logic analyzer to troubleshoot the code and it was fine (The sleep wakeup from Serial was not tested due to HW limitation. Also the active balancer section is missing on that prototype.)