Tesla Graphical Log Parser

My car is a year old / 6000 miles and the A-hr is still going up a bit but has been a pretty flat line (started at 157, now 160).

Great stuff!

Works fine now. Thanks!
(small bug, the year is not displayed as 11 but as 41)

Measuring battery health

Doug,
When you get a chance, would you please add the following plots to your graphical parser:

The data is from items in the Daily record of the vms_log file. (other records, e.g drive10m SOC, are not used)

• Daily Ahr capacity vs miles
• Daily Ahr capacity vs date

• histogram of Daily SOC, bounded by start/stop date interval.
• histogram of Daily SOC at a set temperature or range of temps. E.g histogram of SOC for all temps >= 30C
• histogram of daily brick max temp

• daily brick max temp brick number vs time
• daily lowest brick Ahr capacity brick number vs time

These last two plots should appear semi-random. If one brick starts to dominate, it is the weaker brick...


The above plots will allow us to better understand the health of our batteries. Since all of these plots are taken from data in the "daily" record, each vms_log has the entire history starting from the birth of the car and ending on the date of the log dump.

-Scott

Doug_G said:

Might these last two be more informative as histograms? Or are you looking to see a progression?

Click to expand...

Sure, but it's not more informative, it's less because what happend in the last month is more important than what happend in the first month. You need to plot it vs time because you need to see the "consecutive" days where the brick in question was hottest or had the lowest capacity.

Example: brick number of the lowest capacity brick
1,2,3,1,4,5,1,2,6,1 ; brick number one is a low performer.
2,3,4,5,2,6,1,1,1,1 ; brick number one will probably fail.

Both of the above data sets have the same histogram plot. We're interested in the consecutive days, not just the number of occurrences.

Doug_G said:

I have no plans to release the source code; however, the Windows executable is available for free

Click to expand...

Well, I can't argue with your choice because I've never released source code, either. But considering that I don't own any peecees, I'm going to have to write an OSX version of this. I guess I'll have to go back to Tom and Scott for the information.

Thanks anyway.

An OSX version would be very welcome. A private source code exchange perhaps? Go on Doug_G help S-2000 along!

S-2000 Roadster said:

Well, I can't argue with your choice because I've never released source code, either. But considering that I don't own any peecees, I'm going to have to write an OSX version of this. I guess I'll have to go back to Tom and Scott for the information.

Thanks anyway.

Click to expand...

I'm in the same boat. Only macs around, and a pain to dig up a PC (and wait for it to windows update).

Perhaps we could collaborate. I've also been toying with the idea of an iOS version (but wondering how to get an iPhone in disk mode with /VehicleLogs without jailbreak).

Is temperature data recorded for the PEM and motor?
I would love to be able to chart temperatures.

Might I make a suggestion that someone get an open source version of a parser up somewhere, preferably on GitHub (collaboration there works better than I've seen on other sites)? I'd contribute if i were. it would be great to keep the parser / data structure separate from the presentation, so that multiple front ends could be added quickly. I was thinking a web frontend so I could get the logs graphed on any device would be pretty slick.

Figuring out the data fields in the log file is hard. Figuring out how to present the data is hard. Figuring out how to let a user navigate through a gigantic set of data to extract out the bits they care about is hard.

If you know the data fields, writing a parser isn't hard. Even if you had a parser from someone else, you're still going to have to learn the format to understand what's in the log so you can build an appropriate user interface. Figuring out an existing parser and how to interface with it isn't a big obvious win compared to writing your own. If writing the parser is a barrier to writing a graphical app, I think you're underestimating how much work you're signing up for.

That's why I went to the work of publishing the format and data fields instead of giving away my source code. That was enough to get Doug rolling. I've thought about writing a graphical version for Mac OS X, but I find that every time I dive into the logs I want different data and charts than I did the previous times. I have a pretty good idea of how hard it is to write a robust charting engine, so there's no way I want to tackle that. As much as Excel drives me crazy, it's a nice charting package that makes it easier for me to get the charts I want than writing custom code.

Kudos to Doug for writing a graphical app for Windows. It's a big job I'm not willing to take on for my preferred platform.

markwj said:

I'm in the same boat. Only macs around, and a pain to dig up a PC (and wait for it to windows update).

Click to expand...

FYI, it runs fine under Parallels for Mac.