[Zasquatch]

UPDATE: Plans for a big update are taking longer to implement due to new puppy... Putting it back up for all to enjoy! Remember to support the developer

You have to love the ease of use of the COBB AccessPORT, and the great logs you can record with it. What I've hated is the process of plotting these logs. My timing for wanting to do so never helps either, and the Mrs. tends to get a little "loud" after 15 minutes of me sitting at the computer while she is standing at the door ready to go....

I decided to make a MS Excel program to make life easier. It has gone through quite a bit of testing and development on the 'other site' so this latest version should be bug free and ready to go. Check out the screen shots below!

A few notes:
-The values in the left hand column are the typical options a user should log.
-If you wish to clean up the data, i.e. delete all the 'noise' before and after you went WOT, you MUST have logged Accel Pedal Pos.
-If you select any monitors to plot that weren't actually logged, they will automatically be de-selected.
-You can graph as many or as few monitors as you would like, although the tidyness of the graph may suffer the more you add.

Shoot me a PM if you have any bugs or questions!

SYSTEM REQUIREMENTS: MS Office (Excel) 2007/2010 (Windows), 2011 (OSX Lion)
When you open the file, make sure you select ENABLE MACROS.
Sorry.... No Openoffice or Libreoffice...

If you love this spreadsheet and feel I deserve a reward, I will gladly accept donations for my hard work
Paypal donations can be sent to zasquatches@gmail.com !

v1.7 now available, featuring support for ATR/ATP datalogs, and a timing analysis feature that highlights rows with excessive timing drops - very useful for those making their own maps! Also Boost Leak/ WG Solenoid logic, Multiselect, and Auto-name!

[Zasquatch]

UPDATE 06/28/12: Added email link for faster communication and file transfer, and a donate button for people to use if they please

UPDATE 06/29/12: Updated to v1.4, incorporating reworked code and the ability to graph RPM within your plot!

UPDATE 08/03/12: Uploaded v1.5, incorporating new .xml code and a new ribbon interface, as well as a more widely compatible .zip compression on all files.

UPDATE 08/10/12: Added a routine to zero out all AFR data greater than 18 to prevent the y-axis from autoscaling to the hundreds.

UPDATE 08/15/12: Added support for ATR/ATP Datalogs and high-level timing analysis

UPDATE 09/03/12: Added Boost Leak/WG Solenoid logic, multi-file selection, autonaming, and NEW user interface.

[BMWsky]

This is fantastic. Thank you!!!

[E90SoFlo]

I will try..

Is it only work on Office or is there a Mac alternative?

Thank You!

[Zasquatch]

Originally Posted by E90SoFlo

I will try..

Is it only work on Office or is there a Mac alternative?

Thank You!

It will work in MS Office 2011 for Mac... Just make sure you save the correct version of the file (the OSX one).

Previous mac versions of office did not have VBA support, so it will only work with 2011.

[vasillalov]

Nicely done! I'd have to poke around and make one for LibreOffice so that us Linux fans can roll "Zasquatch style" too! LOL

[Zasquatch]

Originally Posted by vasillalov

Nicely done! I'd have to poke around and make one for LibreOffice so that us Linux fans can roll "Zasquatch style" too! LOL

LOL thanks man!

On a side note, I did attempt OpenOffice but soon realized I'm not patient enough to learn a new coding language

[Hisam135i]

Very cool !

[cn555ic]

Great job and the community thanks you

[Zasquatch]

Thanks fellas, I'm hoping this will help improve the quality of posted logs! Let me know if anyone runs into any snags or unexpected resuts... or if it works perfect

[BlackBB6]

Anyone try it out? Thanks for doing this.

[Dr_Dirt]

Originally Posted by Zasquatch;115****1

You have to love the ease of use of the COBB AccessPORT, and the great logs you can record with it. What I've hated is the process of plotting these logs. My timing for wanting to do so never helps either, and the Mrs. tends to get a little "loud" after 15 minutes of me sitting at the computer while she is standing at the door ready to go....

I decided to make a MS Excel program to make life easier. It has gone through quite a bit of testing and development on the 'other site' so this latest version should be bug free and ready to go. Check out the screen shots below!

A few notes:
-The values in the left hand column are the typical options a user should log.
-If you wish to clean up the data, i.e. delete all the 'noise' before and after you went WOT, you MUST have logged Accel Pedal Pos.
-If you select any monitors to plot that weren't actually logged, they will automatically be de-selected.
-You can graph as many or as few monitors as you would like, although the tidyness of the graph may suffer the more you add.

Shoot me a PM if you have any bugs or questions!

SYSTEM REQUIREMENTS: MS Office (Excel) 2003 (Windows), 2007/2010 (Windows), 2011 (OSX Lion)
When you open the file, make sure you select ENABLE MACROS.
Sorry.... No Openoffice or Libreoffice...

Home Screen:


Navigate to .csv log file:


Name the datalog (this will be the name of the created tabs/graph):


A graph is created:


Due to upload limitations on this forum, I have renamed the .zip files to .pdf. Right click and save as - after you download the files YOU MUST RENAME TO .ZIP prior to extracting.

This is awesome, any chance it will work on NUMBERS(MAC) ?

[Fundahl]

Thank You! I was having trouble finding a graph "maker" that I liked.

[Zasquatch]

Originally Posted by Dr_Dirt

This is awesome, any chance it will work on NUMBERS(MAC) ?

Nope, you need VBA, which is part of MS Office. You would have to get Office 2011 for Mac. That's what I'm using 90% of the time

[Zasquatch]

Originally Posted by Fundahl

Thank You! I was having trouble finding a graph "maker" that I liked.

You're welcome! Let me know if you have any problems or have any suggestions

[AU335i]

awesome tool Zasquatch!

suggestion: idk how to change the script but RPM isn't graphed automatically or is an option to be graphed. not sure if that's really important on a datalog or not though...i'm assuming it is though.

[Dr_Dirt]

Nice it works!
Here is my COBB Stage 1+ Aggressive, not sure why boost dropped, can anyone tell?
http://www.e90post.com/forums/attach...1&d=1332641512

[zeenon53]

I'm going to give this a shot tomorrow.

[Zasquatch]

Originally Posted by AU335i

awesome tool Zasquatch!

suggestion: idk how to change the script but RPM isn't graphed automatically or is an option to be graphed. not sure if that's really important on a datalog or not though...i'm assuming it is though.

I don't typically graph RPM as it makes the scales so big that all the other data is hard to read. I'll usually note the data point in question, switch over to the table and see what RPM it was at.

I can add RPM easily enough though, I'll put it on the list to update.

[Dr_Dirt]

Originally Posted by Zasquatch

I don't typically graph RPM as it makes the scales so big that all the other data is hard to read. I'll usually note the data point in question, switch over to the table and see what RPM it was at.

I can add RPM easily enough though, I'll put it on the list to update.

Is that mph along the bottom?

[AU335i]

Originally Posted by Zasquatch

I don't typically graph RPM as it makes the scales so big that all the other data is hard to read. I'll usually note the data point in question, switch over to the table and see what RPM it was at.

I can add RPM easily enough though, I'll put it on the list to update.

i tried searching but is there any way we can have the RPM go along with the bottom axis?

[Zasquatch]

Originally Posted by AU335i

i tried searching but is there any way we can have the RPM go along with the bottom axis?

Why would you want that? The graph would get messy, as RPM is not generally linear. Data starts looking weird and skewed when graphed against a non-linear scale. From my experience, RPM typically isn't of that much concern when looking at logs... more of a reference point. I usually just note the x value of the point, go to the data table, and see what RPM was at that data point.

But again, if there is enough desire it can be added.