SOC data: 281-based, New-Bars

My Nissan Leaf Forum

Help Support My Nissan Leaf Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
So just to be clear here.. How does one tell if they have the new software? I'm assuming I am updated as I just got the car 3 weeks ago.. The "old" bars are those expressed in the LSN of byte 3 in 0x5bc? (toggling between 12 and some mystery bar level that is usually higher than what's displayed on the dashboard)... presumably the "new" bars/range are set to give more of a reserve than the original design? Drove the car down to 4 on the SOC# (starting from 278 full) and had reduced performance mode kick in rather dramatically (detailed in a post on the turtle discussion in a another sub topic)... I was kinda shocked that it would give me full power one minute then seconds later go to extreme RPM and eventually cut power completely (after about 1/2 mile in RPM).. It must have been an abnormally low cell on a still not completely balanced pack (278 instead of 281 full). I'd like to think the phases from full power to no power would be more gradual..
-Greg
 
I did some additional testing with the prototype SOC meter, focusing on the range of charge from 1 bar down to the Very Low Battery warning. The motivation for this experiment was the consistent finding that a reading of 1 bar of remaining charge corresponds with a SOC percentage of about 25% on the SOC meter. At a recent breakfast meeting, we were discussing this unexpected finding.

Question at hand: If the SOC meter is going to be useful near the bottom of the range (which IMHO is the range where it is most critically useful), is the burn rate from 25% to 5% similar to the burn rate for the majority of the range of charge, or does the burn rate increase, i.e., does SOC "fall off the table" rapidly below 25%, leading a person using the SOC meter to overestimate their remaining charge, and therefore their remaining miles, at this point?

I started the experiment on July 20 at 1 bar and 25% SOC on the prototype meter. I drove around my neighborhood, in D mode, headlights on, AC off, on local highways and residential streets, stopping at lights and stop signs, and reaching perhaps 50 mph at times. This was not a steady speed run by any means. I recorded the SOC% and SOC number at every half mile and at the Low Battery and Very Low Battery alert points.

I've shown below the data that I already reported for my July 2 run, which was a smooth freeway run, along with the data from my July 20 run. I realize that the driving speeds and burn rate are different on a freeway run than with slower stop-and-go driving, with some regen happening at stop lights, etc.

I did a rough plot using Excel. The slope of the burn rate from the July 20 run from 1 bar down to Very Low Battery, appeared slightly steeper than the slope of the burn rate from the freeway run from 100% charge down to 1 bar, but it wasn't very much steeper. Of course, there might still be a faster burn rate from 1 bar down to 5% charge, but it was masked by the fact that I was driving stop-and-go with some regen.

Someone with better plotting skills than mine might want to plot this data and calculate the slope of the line from the two runs to see if we can draw any conclusions from it.



Code:
Miles	Pct	SOC#	Alert and bars
0	  99	279	12 bars
4.4	92	257	11 bars
9.2	84	236	10 bars
13.9	78	219	9 bars
20.8	71	199	8 bars
25.8	66	186	7 bars
35.1	58	163	6 bars
40.8	51	143	5 bars
51.7	36	102	3 bars
56.6	31	88	2 bars
61.8	26	73	End data collected July 2 (1 bar showing)
--------------
65.5	25	72	Begin data collected July 20 (1 bar showing)
66	  25	71	
66.5	25	70	
67	  23	67	
67.5	22	64	
68	  22	62	
68.5	21	59	
69	  19	55	
69.5	17	50	
69.7	17	49	Low Battery (last bar disappears, miles display starts flashing)
70	  16	47	
70.5	16	45	
71	  15	42	
71.5	14	41	
72	  13	39	
72.5	13	37	
73	  11	32	
73.5	10	30	
74	  10	29	
74.5	10	28	
75	  9	27	
75.5	8	25	Very Low Battery
76  	7	22	
76.5	7	20	
77	  6	18	
77.2	5	16	LEAF parked
 
Boomer23 said:
I started the experiment on July 20 at 1 bar and 25% SOC on the prototype meter. I drove around my neighborhood, in D mode, headlights on, AC off, on local highways and residential streets, stopping at lights and stop signs, and reaching perhaps 50 mph at times. This was not a steady speed run by any means. I recorded the SOC% and SOC number at every half mile and at the Low Battery and Very Low Battery alert points.

Good data! Clearly you were the right man for the prototype unit!
 
looks like the only real conclusion has to be averaged on several runs. there is an obvious delta here on display changes. there is simply too much variance in distances traveled from one bar change to another. its easy to understand it on a "street" run, but even the freeway numbers are all over the place. but that means that there is changes to conditions which could mean direction (wind effects) elevation, etc.
 
SOCvsMiles.png


Only a slight bending of the curve.
 
Note:
The one-channel (one CAN buss) SOC meter is ALSO programmed to send all the CAN-messages back to a PC to be Logged, Graphed, etc.

The messages are being sent out the SOC-Meter's unused 9-pin "D" connector, which is an RS232 serial port. This "Logging" port is not normally connected to anything when using the "Meter" to view SOC, but simultaneous logging of the entire EV-CAN buss message-stream is relatively easy, and inexpensive.

You need:
1. a portable Windows PC that can run my free CAN-Do program (XP, Vista, Win7),
2. some may need an "automobile" 12v power adapter (often $10 to $20) for their PC for longer recording sessions,
3. the CAN-Do program (free) downloaded from http://www.wwwsite.com/puzzles/cando/
4. an RS232 Serial port on the PC, or an inexpensive (about $5) USB-to-RS232 adapter and a USB port.

I have a bunch of these adapters that APPEAR to be fine for CAN-Logging at 115,200 baud, but are just "not quite sufficient" for consistant "flashing" of the AVR-CAN board itself.

So, for a few dollars and very modest effort, you can actually LOG and GRAPH this data.

I have just started a new thread named "SOC-Meter for One-CAN Logging & Graphing".
 
Boomer23 said:
Code:
Miles		SOC#	Alert and bars

69.7		49	Low Battery (last bar disappears, miles display starts flashing)

75.5		25	Very Low Battery

I remember a previous post that had SOC# at 48 and 24 at the respective alerts.

So, 5.8 miles from Low to Very Low. Sure wish you had gone to turtle for another data point ;-) I predict that you were very close.

Code:
DATA POINT-----A------B------C-----D-
BatteryLow----11.0---8.6---13.6---6.7
VeryLow--------6.7---5.5----8.4---5.2
-------------------------------------
Total2Turtle--17.7--14.1--22.0---11.9
-------------------------------------
VeryLow/Low----61%---64%---62%----77%
 
The real question is how much usable energy YOUR car's battery
has after its LBW, not how much energy the average LEAF had.

I suspect (do not know) that there is significant variation in the "low end"
energy, depending primarily upon the condition of the specific battery, what
Nissan's "SOC" reports, and how the LEAF uses that (and other) information.
 
garygid said:
The real question is how much usable energy YOUR car's battery
has after its LBW, not how much energy the average LEAF had.

I suspect (do not know) that there is significant variation in the "low end"
energy, depending primarily upon the condition of the specific battery, what
Nissan's "SOC" reports, and how the LEAF uses that (and other) information.


And why gathering data helps to figure those things out, hence the cumulative data of Battery Warning to Turtle.

I'd like to see if the Warnings are indeed at data points 48/49 and 24/25 for all cars. And if a coherent ratio of data can be used to somewhat accurately say that if I drive 10 miles with LowBatteryWarning, then I will most likely be able to drive an additional 60% of that number at the same speed/conditions, or 6 miles, until I hit turtle.

Not even a tiny percentage of people will intentionally drive their cars to turtle to determine what their specific car might do, and even if they did, they are too many variables for that single data point to be accurate at, perhaps, years down the road when they REALLY need it.
 
In turbo2ltr's early work on the EV-CAN buss, I believe he determined that the Bars, Battery Warnings, and Turtle "events" were tied to the "broadcast" SOC value. He did this, as I recall, by sending his own messages TO the EV-CAN buss, and observing the "events" on the LEAF's dashboard.

Of course, I might have not understood properly, or have forgotten.

Apparently the VCM translates SOC levels to Display-Bars, since it was only (we think) the VCM's firmware that was re-written by the "A/C Fix" April 2011 Update.
 
evnow said:
SOCvsMiles.png


Only a slight bending of the curve.

If these cells were actually charged all the way to 4.21 volts (aka, true 100%), you would see a bend at the start as well. interesting....
 
The SLOPE of the curve is important. The flatter slope represents more miles per bar.

It looks like the slope at 175 (raw) SOC is only half of the slope below 50 SOC. Therefore TWICE as many miles per bar in the middle than at the low-SOC end.
 
rainnw said:
If these cells were actually charged all the way to 4.21 volts (aka, true 100%), you would see a bend at the start as well. interesting....

Thats crazy talk, 4.15v is really pushing it.
 
Both of you are just guessing, right?

I have not seen any exact high-end (or low-end) data on these Nissan-produced cells, just guesses based on other Li-ion chemistries.

Different (even quite similar) battery cell micro and macro structures, and the exact chemistries of all of the elements can produce cells with VERY different characteristics.
 
Every time I've watched my car charge, the charge terminates at 394V or 394.5V "100%"
(ie 4.10v/cell) even though RAhC has only hit 280 max.. Once I saw it climb to 281 but then while still charging reset back to 280.. Incidentally, "80%" is only 4.05v/cell.

Can someone with logging capabilities generate a graph during charge of pack voltage, current and RAhC?
 
PS I think we'll need to dither the current and Vpack... It's got a fast refresh rate but only 0.5A resolution... So for example if it reports 8.0A 80% of the time and 8.5A 20% of the time (within a matter of seconds), I'd take that as 8.1A
 
Try looking at the EV-CAN 6-hour charging Log
(6 million CAN-messages) with the CAN-Do program available at:
www.wwwsite.com/puzzles/cando/

CAN-Do can graph what appears to be the SOC and the Pack Voltage.
 
Back
Top