Hi,
More (li-ion) battery model papers with pictures.
Going back to your first, and then second, post(s) - I see no point in entering the complicated territory of charge balancing between multiple cells/packs (unless you really want/need/have to), one single cell model for a simulation to show the purpose might/will spare you from a lot of design and simulation time and/or misery, IMO. A row of battery packs will require a lot of sensing and control circuitry to balance the charging between the cells and also between the packs... Personally, I'd take the weasel-way-out and only model/include one cell, or at most two, especially as you say 'I initially intended to use many small components to simulate the functionality I wanted to achieve' - I designed a theoretically functional discrete single li-ion cell charging/discharging circuit (very, very interesting and fun to do) and it is a lot of components and a couple of workarounds to get the waveforms you need/expect to see in the simulation results. It's loads of ICs like logic, op amps and comparators, transistors, sensors, passives, the odious battery model, and so on to control: the battery has temperature limits/limitations both ends, limits on depth of discharge, requires the pre-charge current, the charge current, has a voltage cut-off at both ends. A coulumb counter would be good/vital to add realism (not just voltage has reached lower or upper limit) but that is in and of itself also a lot of parts to do discrete design. Simulating with an MCU presumably takes out a lot of the design work? Those are the reasons why I think a 'one cell proof of concept' would be the way to go with your project.