Graphing AP Data Logs in Excel

[LuczOr]

I've been working on a little something for the community. Hal was bitching about not liking to view data logs in a spreadsheet and I told him to make a fucking macro. Well he told me that I was a useless sack of shit and haven't done anything for this community so I should do it.

Here are the results.

Make no mistake, this shit was way more complicated than I thought since data logs contain a lot of different parameters that need to be graphed on different scales. Excel makes it even more difficult since they only allow two different scales on a single chart. This excel spreadsheet scales and stacks the parameters on their own axis.

The spreadsheet can graph up to 19 parameters (I intended to do 20 but I fucked up and was too pissed to fix it). 19 should be fine though since most people only tend to log 15-18. You can graph up to 300 data points of each parameter.

To use this, just copy and paste your AP data log into the TOP LEFT of the "Data Paste" sheet. The graph will be on the "Chart Page". Do yourself a favor and don't fuck with the Additional Data pages.

NOTE: The left most parameter in Data Paste MUST BE TIME! All of the parameters are graphed against time, just like they show up in the data log. Also, try to make sure the time starts at zero, otherwise your graph will be a crunched and moved to the right. You can actually change the numbers for time and start them at 0 and count up by 1 till you reach the bottom of your data since the chart just uses it as a counter anyway.

I will warn you that this IS a first version. I'm sure something will be fucked up, but let me know and I will try to fix it.

ONE MORE THING, The chart uses an add-in for excel that references cells to make custom labels for the chart. I'm not sure if you need it, but you will know if you have no axis labels or some type of error. If that is the case, you can download the add-in here:
XY Chart Labeler
Install it, then follow the path to where you installed it and run the XYChartLabeler.exe to add it into excel

AND FINALLY, note that if you have any parameters that are populated entirely with zeros (like KR for instance, because your tune is that baller) it will end up all the way on the bottom of the graph. Luckily it doesn't get in the way of any other parameters so just ignore it.

AND, this will probably only work on Excel 2007.

Here is an example of the finished product using some noob's log.

[LuczOr]

FUCK here is the attachment, format was wrong on first one.

[86AmishMs3]

Pretty cool, but I prefer to do it myself, but i'm sure the excel illiterate people would like.

What about making the x-axis rpm though, then you have to worry about 1 less y-axis as well. Shouldn't be too hard

[silvapain]

Originally Posted by 86azms3 Pretty cool, but I prefer to do it myself, but i'm sure the excel illiterate people would like. What about making the x-axis rpm though, then you have to worry about 1 less y-axis as well. Shouldn't be too hard

If for some reason you let off the throttle in your log and the RPM drops, it'll fuck up your graph. Time is a good base as it always increases in the log.

[aaronc7]

some guys might be datalogging cruise or other conditions, so i see why the time thing makes more sense on the x axis for something like this.

[Bucker]

Does not work on Open Office. My latest log graphed:

[thatguyinms]

Originally Posted by LuczOr AND, this will probably only work on Excel 2007.

update to a very old post.. Confirmed that this continues to work to Office 365 with no macro editing.

[nindoja]

Shameless self-plug: Alternatively, upload your log to https://www.revisionsrus.com and get an interactive view of all your data, with mouse overlays for all the logged values at that specific point in time.

Here's an example log. https://www.revisionsrus.com/logs/634

[MSMS3]

Not sure there was any reason to bump this what - eight old thread?

Regardless, I think most of us prefer to look at the actual data points for the particular PID(s). Scaling and axis of the graphs can be confusing and misleading.

Data is data. Graphs are secondary depictions of the data.

[nindoja]

Originally Posted by MSMS3 Not sure there was any reason to bump this what - eight old thread? Regardless, I think most of us prefer to look at the actual data points for the particular PID(s). Scaling and axis of the graphs can be confusing and misleading. Data is data. Graphs are secondary depictions of the data.

Data is useful, and why I include it in the display on the site, albeit hidden. That said, graphs are great for quickly picking up patterns or trends in data. Sure, you can spend some time building a template or macros that colorize your data, but if you don't want to do that graphs are great.

[MSMS3]

It you know what the data means, you will always use it directly. Just show me the rows and columns and the time line, as many frames per second as possible.

You have to be very careful with scaling and the values in each axis of charted data or it can be very deceptive and misleading.

I'll stick with the raw data in csv format. Colorize data? No. Just columns, fields and numerical values, time-stamped as close together as possible.

Not saying that charts have no value, but for serious diagnostic and tuning work I want to see the data. A lot of really important, sometimes critical, engine destroying events can happen in a tenth of a second.

A drop in fuel pressure or a sharp instantaneous lean out in AFR sufficient to point to impending zoom, zoom, boom is not likely to show up on a chart scaled to show a full 3,000 rpm to red line WOT pull would never be noticed. It happens too fast and recovery is too quick.

I caught impending high pressure fuel pump failure on a data log, seeing very quick transient drops and recovery lasting only a tenth of a second. Pump internals were replaced before anything bad happened.

By the time a trend shows up in a chart type log, the damage may have already happened.

For the same reason, most instantaneous real time gauges, analog or digital have little value except for maybe boost and rpm.

[aaronc7]

not sure why I'm in the 8 year old thread either, but.....

I use MegalogViewer HD. Log viewer/plotter, scatter plots, histograms and table generators.