Personally I think you'd be better off with the logging version, and simply download the log into your PC at the end of the ride/day, and check for lows. If you use a device like the CA+analogger that also logs your throttle/speed/voltage/current/etc. you can merge the two logs so that you can see exactly when these things happen.
Then you'd not be distracted on-road with watching the data, but still have it all. Plus you can analyze it even better at your leisure without having to depend on your memory, or having to keep an eye on the display *all the time* to watch for dipping cells.
But if you did want to have a dashboard display, I would recommend one that does not use numerics, but isntead uses either bargraph or color. or both.
To use color, simply have a bicolor LED, that has red and green in the same unit, for each cell or cell group. Two comparators per LED will trigger it, so that at "full" down to some middling value, the green LED remains lit but red is not. Below that value, green remains lit but red also lights, turning the LED yellow to warn you it's getting low. At the LVC point, or just above it, the green turns off but red remains lit.
So one comparator's trigger point is at the LVC, and one is at your chosen above-LVC warning level.
Then you simply have a row or group of LEDs that you can note the color of as you glance down, and it takes far less attention and far less time than numeric displays.
In many UI situations, such as dashboards and cockpits, where attention *MUST* be prioritized elsewhere, numerics are only for precision readouts such as setting specific values when attention may be safely diverted from other things, or non-priority readouts like odometers, that you don't usually look at while driving. All of the really important information is best conveyed graphically, often with moving needles or colored gauges of some type, sometimes with "bugs" at specific setpoints so you only have to see if the needle is above or at or below that setpoint, and not process the actual numerical info.
When it is necessary to use numbers on critical displays, they are usually very large, and centered within an analog gauge that repeats the same information in a faster-to-grasp way. At least, on the better UI designs.
Anything in a UI that takes your attention from time-critical decision making is wrong, unless that item is more important than the decision you might have to make--on the road, there's not really anything more important than paying attention to what's in front of you, and next in line is what's beside and behind you. After that is maybe speed, and then battery condition somewhere down the list from there.
If battery condition is more important than any of the above, then it needs an automatic cutoff rather than a manual monitor. Knowing what your batteries are doing is definitely not more important than seeing that car that is cutting you off with zero warning, or that pedestrian that just stepped off the sidewalk in front of you.
If you are doing all this batteyr monitoring and testing away from any possible traffic or road conditions that could be hazardous, then fully-numeric displays of all the possible data would be neat to have, and useful...but on-road I wouldn't want it distracting me; at best the three-color cell display would make it to my "ultimate dashboard".
