Annual Battery Inspection - Seekrit Data Report

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.

Ingineer

Well-known member
Joined
Oct 15, 2010
Messages
2,742
Location
Berkeley, California
Here is a typical report of the data that's sent to Nissan after your annual battery inspection:

Code:
VIN                     BATDATE DATE    LBSOH           VCMID           LBCID           LIBSN   MILEAGE
JN1AZ0CP*BT******       201105  201203  1.028100        237D0-3NA0C     293A0-3NA0B     ******  060B4000

MAXBATTEMPRN    8       -35     35-40   40-45   45-50   50-55   55-60   60-65   65-
MAXBATTEMPRN    8       03D4    0000    0000    0000    0000    0000    0000    0000

MAXBATTEMPCG    8       -35     35-40   40-45   45-50   50-55   55-60   60-65   65-
MAXBATTEMPCG    8       00D7    0001    0000    0000    0000    0000    0000    0000

BATTEMPRN       8       -35     35-40   40-45   45-50   50-55   55-60   60-65   65-
BATTEMPRN       8       03D5    0000    0000    0000    0000    0000    0000    0000

BATTEMPCG       8       -35     35-40   40-45   45-50   50-55   55-60   60-65   65-
BATTEMPCG       8       00D8    0000    0000    0000    0000    0000    0000    0000

AVEVSP          7       -10     10-20   20-30   30-40   40-50   50-60   60-
AVEVSP          7       00DD    0096    00A6    00A5    00A5    0039    000E

AVEMOTORPOWER   9       -5      5-10    10-15   15-20   20-30   30-40   40-50   50-60   60-
AVEMOTORPOWER   9       03AA    0000    0000    0000    0000    0000    0000    0000    0000

MAXACPOWER      11      -0.5    0.5-1.0 1.0-1.5 1.5-2.0 2.0-2.5 2.5-3.0 3.0-3.5 3.5-4.0 4.0-4.5 4.5-5.0 5.0-
MAXACPOWER      11      0228    013A    0033    000F    0005    0000    0001    0000    0000    0000    0000

MAXHTPOWER      11      -0.5    0.5-1.0 1.0-1.5 1.5-2.0 2.0-2.5 2.5-3.0 3.0-3.5 3.5-4.0 4.0-4.5 4.5-5.0 5.0-
MAXHTPOWER      11      016C    0084    00B8    0051    0062    000A    000C    0012    000E    000A    000F

FMCGTORUNTIME   10      180-    160-180 140-160 120-140 100-120 80-100  60-80   40-60   20-40   0-20
FMCGTORUNTIME   10      0022    000E    0013    000B    000D    0010    000A    0008    0008    0316

NUMBEROFQCANDNC 2       QUICKCG NORMALCG
NUMBEROFQCANDNC 2       0001    00DE

FMRUNTOCGTIME   10      180-    160-180 140-160 120-140 100-120 80-100  60-80   40-60   20-40   0-20
FMRUNTOCGTIME   10      0000    0000    0000    0000    0000    0000    0000    0000    0000    0000

PKTIMEWHENHIGHSOCAFTERCHARGE    8       0-3     3-6     6-12    12-24   24-48   48-72   72-96   96-
PKTIMEWHENHIGHSOCAFTERCHARGE    8       0000    0000    0000    0000    0000    0000    0000    0000

PKTIMEWHENHIGHSOCAFTERDRIVE     8       0-3     3-6     6-12    12-24   24-48   48-72   72-96   96-
PKTIMEWHENHIGHSOCAFTERDRIVE     8       0000    0000    0000    0000    0000    0000    0000    0000

SOCATCG 8       0-20    20-30   30-40   40-50   50-60   60-70   70-85   85-
SOCATCG 8       0003    000E    001E    0032    0012    000A    0042    0019

TURTLELAMP      1       NUMBEROFTURTLELAMPTURNEDON
TURTLELAMP      1       0000
Go wild! =)

-Phil
 
Thanks for the info. Now to sit down and try to figure out what I am looking at.

looks like they track everything. # of QCs, turtle lights...
 
RN - Run
CG - Charge
FM - ? FM Run & FM Charge with units 180 max down to 0-20
QC - QuickCharge
VSP- ?
NC - NormalCharge (100% charge events?)
PK - Peak or Park ?
SOC-StateOfCharge

SOCATCG - StateOfChargeAtCharge - A histogram of when you charge the vehicle with SOC in percent

MAXACPOWER - Peak power used by Air Con 5.0 KW Max
MAXHTPOWER - Peak power used by DC heater 5.0KW Max
AVEMOTORPOWER - Average Motor Power in KW
MAXBATTEMPxx - Max Battery Temperature xx
BATTEMPxx - Battery Temperature xx (average per use?)
 
TonyWilliams said:
Only one turtle on? Awesome stuff, Phil.
That car (not mine) has had zero turtles actually. The number right past the parameter is the # of fields to follow.

Some quick definitions I've deduced:
MAXBATTEMPRN = Max batt temp hit per run (C)
MAXBATTEMPCG = Max batt temp hit per charge (C)
BATTEMPRN = Avg batt temp per run (C)
BATTEMPCG = Avg Max batt temp hit per charge (C)
AVEVSP = Avg vehicle speed (MPH)
AVEMOTORPOWER = Avg motor power (kW)
MAXACPOWER = Max A/C power consumed (kW)
MAXHTPOWER = Max heater power consumed (kW)
FMCGTORUNTIME = Unsure (maybe charge to run time ratios?)
NUMBEROFQCANDNC = # of L1/L2 and then QC charges
FMRUNTOCGTIME = Unsure (Run to Charge time ratios?)
PKTIMEWHENHIGHSOCAFTERCHARGE = # of hours parked when SOC > ? (80%?) after charge
PKTIMEWHENHIGHSOCAFTERDRIVE = # of hours parked when SOC > ? (80%?) after drive
SOCATCG = SOC when charge was initiated
TURTLELAMP = # of times for low SOC (turtle)

These are informed guesses, If you disagree, let's hear it!

I'll get the mileage constant for you soon.

-Phil
 
TonyWilliams said:
Only one turtle on? Awesome stuff, Phil.
The 1 refers to the number of parameters. The report indicates that turtle has never been reached. This doesn't look like an actual report, as fields that probably would be populated are zero.
 
TonyWilliams said:
I thought figuring out the mileage would be easy:

060B4000

Hex to decimal:

101400576 ???

If 060B4000 is really 060B4.000 then the milage would be 24,756. There is enough range in 5 hex digits, as FFFFF.000 would be 1,048,575
 
lukati said:
TonyWilliams said:
I thought figuring out the mileage would be easy:

060B4000

Hex to decimal:

101400576 ???

If 060B4000 is really 060B4.000 then the milage would be 24,756. There is enough range in 5 hex digits, as FFFFF.000 would be 1,048,575


Agreed, that makes sense. Why go to three decimal places, and then apparently not use any? I can't believe it is exactly 24,756.000 miles.
 
TonyWilliams said:
Why go to three decimal places, and then apparently not use any? I can't believe it is exactly 24,756.000 miles.
All data is 2 bytes wide (i.e. 4 hex digits), except for the milage. Two bytes would not be enough to hold enough miles (65,535), so more digits are needed. They may have gone for another 2 byte unit although they only needed one more digit. That wastes 3 digits but keeps the memory well organized.
 
FMCGTORUNTIME: from charge to run time (time sitting after charge completion before operating)?
FMRUNTOCGTIME: from run to charge time (time sitting after running before starting charge)?
 
Nekota said:
I'll take a guess at the units being metric and in 0.1 meters for 6300.7 miles.

Metric makes sense since the temps all seem to be.

But a leading zero doesn't make sense to me.

If I assume a reversed order, then the three leading zeros might make sense, then assume one digit for tenths...

4b06.0 = 19206.0 kM (11934 mi).
 
TickTock said:
FMCGTORUNTIME: from charge to run time (time sitting after charge completion before operating)?
FMRUNTOCGTIME: from run to charge time (time sitting after running before starting charge)?

Makes sense, except the report has all zeros for FMRUNTOCGTIME ..?
 
Nekota said:
I'll take a guess at the units being metric and in 0.1 meters for 6300.7 miles.
Interesting... could also be 101,400,576 feet = 19,204.6545 miles Truncating also possible but it's actually more difficult to handle 3 bytes of data than 4. They just used a 32bit INT instead of a 16bit INT.

Nubo said:
If I assume a reversed order, then the three leading zeros might make sense, then assume one digit for tenths... 4b06.0 = 19206.0 kM (11934 mi).
I've never seen hexadecimal reversed like that. At worst the byte order would be reversed (little vs big endian), not the nybble order!

06 0B 40 00 becomes 00 40 0B 06 or 4,197,126. If we assume that's meters, it works out to 2,607.97 miles. If we leave the byte order as is, then 101,400,576 meters = 63,007.3968 miles which may be possible (No clear reason to shift the decimal like Nekota did). I suspect, though, that byte order is NOT reversed. If it was then you'd expect the reversal to be used throughout - so that means he's used quick charge (QUICKCG) a total of 256 times (0100) instead of just once (0001) and a normal charge (NORMALCG) 56,832 times (DE00) instead of 222 times (00DE).

----

I converted the table into CSV and HTML versions (HTML has hex converted to decimal assuming no byte order reversal).
=Smidge=
 
Nekota said:
I'll take a guess at the units being metric and in 0.1 meters for 6300.7 miles.
That would be a little odd, but might just be true. The report has 1 QC and 222 L1/L2 events under NUMBER_OF_QC_AND_NC. This number is close to a total of 216 charging events under SOC_AT_GC. Depending on whether these charging events went to 80% or 100% SOC and using a range of 3-5 miles/kWh, the total milage should be in the 3,400-10,900 mile range. So 6,300 miles looks about right.

Using the entire width of the data block certainly makes more sense than truncating it. Given that the three least significant digits are zero, the counter probably increments in units of 1000, or about 410 m. The total milage that can be displayed would be 429,497 km. Totally reasonable.
 
Guessing unknown parameters to be time between charge complete and next time driven maybe and miles measured by tire rotations which is about like what 400 rotations per mile? Or so since that is how most cars determine distance
 
Looks like the mileage figure is KM if divided by 0x4000 (decimal 16384) or bit shifted right 14 places. Or you can divide it by 0x66F6 (26358 decimal) to directly derive miles.

So this report's 0x060B4000 = 6189 km or 3847 miles.

-Phil
 
Phil, can you say where this report came from? Would be awesome to be able to do a "self-check" for battery health using these stats. Was this extracted from the car?
 
sandeen said:
Phil, can you say where this report came from? Would be awesome to be able to do a "self-check" for battery health using these stats. Was this extracted from the car?
I understand this is from a CSV file that is created by the Nissan Consult 3 tool when the battery report is run. If you know where to look it is sitting in a subdirectory. Others smarter than me can probably extract this data from the car using other tools.
 
Back
Top