87 Vette Owner

I'm currently running a slightly modified APYP bin for my '87 vette (using AutoProm / TunerPro RT). What a difference between 160 baud and 8192!!!

I am in the initial stages of tuning, so I am concentrating on fueling for idle and part throttle. Timing is stock APYP for now.

I recorded my first data log on Monday and downloaded it into an Excel file. My questions are:

1. How long do you typically drive around for each session of data logging? I know I need to vary the rpms, load, throttle, etc in order to hit most / all of the BLM cells, but what have you found to be a good length of time?

2. Re: Fueling - for those that use Excel, once you've opened up your data log (in Excel), what parameters do you prefer to focus on and do you have any specific method of looking at the data? (For example, using "Autofilter" to only look at the data for BLM cell 3, or sorting the MAF grms/sec data to see if anything jumps out?).

As a beginner, I'm just curious about what methods everyone uses.

Thanks!!
Dan

Slow89Iroc-Z

I use datamaster to log and typically drive around under varing conditions untill I get about 25k-30k data points. I like to hit a bit of highway cruise, stop and go, and I hit a few hills using varing throttle positions and speeds through it all. For all the logging I lock the BLM's at 128 and tune with the INT. If I am tuning just fuel I then export RPM, MAP, and INT. I created an excel spreadsheet that will take my current VE tables and using my new data automatically create a more accurate set of VE tables. I then chart these new tables in excel and smooth them out so there are no big/odd changes in the VE. I then run the car with the new tables using this process about 4 times and I get all of my INT's to 126-132 range. Goes pretty quick..the spreadsheet makes it easy....

ashman5

i, for one, would like to see a 'how to' analyze data from tunerpro with screenshots.

87 Vette Owner

Thanks for the info, Slow89! My last data log, I think I only collected about 7.2k worth of data, which didn't seem to be enough to capture a good representation.

Ashman - it will definitely vary depending on what you are trying to accomplish / what part of the tune you are working on. There is a TON of information in the data log, but you don't need all of it at once (at least I don't, anyway ).