(Edited to fix error with 0x1DB byte field description)
Had a little time to play with the CAN codes today;
Based on turbo2ltr's hints and some info from Groundloop, Gary, Robert and others, looked at the ID 0x1DA.
Bytes D4 & D5 behave like RPM, when scaled. I logged data while on a drive. plotted the "RPM" field. Since the LEAF is a direct drive EV, we can go from RPM straight to MPH or even use it as an odometer as I show in the plot below.
Integrate the time-tagged, "RPM" field (blue curve) and scale to the gear ratio and tire dimensions to get miles traveled (red curve). Compares perfectly with odometer reading for this trip.
Putting the LEAF in reverse works too, RPMs go negative.
Next I looked at ID 0x1DB:
Three things of interest. This field seems to commutate through 0,1,2,3 identifiers. I wonder if this is identifies different battery pack "strings". The numbers track pretty well with some leading and lagging during high loads. But, I may be reading too much into the 0,1,2,3 thing.
A portion of the 8 bytes behave like current to/from the battery edit:(D1D2); positive when charging and regen and negative when sitting with car "ON" or driving. "Volts" seem to reside in Byte D3 and the upper 2 bits of D4.
Direct correlation with acceleration/deceleration as shown in plot. I plotted a short segment of a drive where I got on the freeway and then took the next exit off.
My scaling for current and Volts is a total guess. First plot is "Amps" second is "Volts". Notice the 1/RC exponential voltage sag during regions of high power draw and voltage recovery during regen... seems plausible.
Still looking through the IDs for more hints... too much data...good times.