Can you maybe restate your point?
OK, to re-restate the obvious: You were willing to pay $1500 more for the
same car, despite it being older and having more miles on the battery, simply because its CAC number was higher by 7 AmpHours. Clearly, CAC is not an accurate number, and its calculation to hundredths is silly. One should not spend more money on cars solely on the basis of reported CAC values.
To give this post some new relevance, if I were buying a used Roadster, I'd want as many of the log files from the car as are available and run the VMSParser on them. That would show me:
A) How long the battery spent at very low or very high SOCs
B) How long the battery spent at very high temperatures, and what the maximum temp was.
C) What the average lifetime temperature of the pack is.
D) How balanced the pack is (brickahmin, brickahave, and which brick).
If the previous owner didn't collect logs, or doesn't want to share them, you'd still be able to pull the latest log and run
VMSParser on that, which would still be better than relying on CAC alone.
For instance, today my CAC is 149.69 at 39,378 miles. I have a OK log file history of 5.5 years with 166 days missing (mostly from when I first got the car).
A) My SOC has been below 18% only for about 13 hours, never exceeded 96%, and was above 90% for only 107 hours total.
B) My battery temperature never exceeded 41° C (and was there for only 13 minutes), and was never below 4° C.
C) My battery's lifetime average temperature is 21.08° C.
D) The worst brick has varied a lot over the 5.5 years I've owned the car - there's not just one or two bricks that are bad relative to the others.
The largest difference between brickahmin and brickahave was 4.38, with the average difference being 1.21 and median difference 1.26.
Brick 54 was historically the worst brick most of the time (705 days), but most recently it's been oscillating between bricks 88, 32, 35, 54, and 81. So, no big worries there.