This is also the reason why (e.g. with 18650 this is often done) that individual cells are fused. I have yet to see anyone doing this with these LiFePO4 cells, but I have this nagging feeling that this would not be a bad idea.
I'm not too concerned about that aspect. I've got the communication with all my devices running over RS485, most of them using Modbus.
I have extensive background in embedded development, software engineering and electrical engineering, and this is a fun side project for me. If this ever gets more 'generic' I don't know.
It seems as if the single-cell failure scenario while are fairly rare has such a high impact, it becomes a primary factor in a risk assessment for these Lithium battery systems. This has raised my awareness about the physical configuration of the compressed battery pack and how to insulate individual cells from the others while at the same time providing for compression ( to allow for expansion) but eliminate as much as possible electrical post stresses on the individual cells. This process is underway for a DIY solution. Quick question,m what are you doing for compression and how long have your cells been in service?
I looked at your blog and background. Nice cabin; it seems like a very nice off-the-grid retreat. You also have an impressive background; it is hard to imagine you have much time to act as an administrator here.
My background in Electrical Engineering and Systems theory (optimization, controls, and estimation) and is primarily in the US DoD, first on the contractor side and then on the government side. Obviously, complexity is recognized as increasing in everything, and there is a whitewater of activity with strong focuses on model-based development, agile processes, and agile enterprise-level business processes (e.g. SAFe).
Recognizing this (based on frustrations with program performance working in the government side), in about 2014-15 I started a project called SimPADS (for parafoil guidance systems with support from NPS) which had the stated goal to develop an integrated end-to-end toolchain for mixed development (Windows simulations targeting ARM platforms) applicable to small UAV programs which would be coming under higher levels of scrutiny by the FAA. Essentially this was a C++/UML/OOD modernization of the process I have spent about 10 years developing during the 1990's.
Quite surprisingly there were some fundamental theoretical findings on the structural global optimality of OO inheritance models/stacks that I discovered. So I started with Hann-Banach Dual Space optimization and jumped off into set theory, model theory, and even deeper into modal analysis and modal collapse. The objective is to confirm theoretically what this global optimality looks like and why it is so. Ultimately it is about models the correctness of which can only be demonstrated if they work.
In 2019 I completed and posted this preprint as a test of the theoretical proof (you may recognize the topic).
PDF | In this analysis, we develop and bind two abstract models of computation. The first is a set-theoretic model for the Computable Universe... | Find, read and cite all the research you need on ResearchGate
www.researchgate.net
Based on comments received, I realized I needed to formalize what I call a Constructability meta-model (the basis for all optimal minimal constructions) all of which is what got me into model theory and ultimately a model of modal collapse. I never thought I would go so far afield into abstract mathematics and logic (it is all far different than engineering or even applied mathematics). But as it turns out there is as much if not more controversy in these areas as in systems engineering and probably software engineering as well (although my sense is the SWE is coalescing faster by necessity).
Here is a sample of an abstract, and I'm using UML to organize even this formal proof (again you may have heard of the topic before).
Shared with Dropbox
www.dropbox.com
Thanks for your time reading my posts.