I am emailing a CSV export from an autocross now, but Excel will only load about 65K lines of it.

 

I got it. I was able to extract the following WOT 2nd gear run from it. It starts at 5000 rpm and ends at 8500 rpm. Two impressions:

http://www.sr20deracing.com/S2000/gernby.xls

1. That is one damn FAST logger. Holy crap is it fast. We are talking 196 frames every second. This is AMAZING and this is with all the parameters getting logged. If you disable some parameters it will become even faster than this.

2. When do you have Vtec set to engage? If it is stock then, when Vtec engages at ~5900 rpm, there is a drop in timing advance by about 3* BTDC. Is there any reason why Honda designed the tune this way? If we change the Vtec engagement point to a lower rpm would the timing pull also hold or do we have to tune it in ourselves?

3. I am impressed that you can get knock count on a per cylinder basis. In the Evo/Subie loggers that I use you can only get it for the entire engine block.

4. As Hondata mentioned, you can see that knock retard changing, but there is no change in the Knock count. Knock count is the one to worry about.

I would like to see a WOT pull in 3rd gear from 3000 rpm to 8500 rpm on a stock tune. Can you do that and send it to me gernby? I will post it for everyone to see.

This is so exciting. It makes me feel the same when I first started tuning Evos and Subies.

 

I believe the datalog is coming via CAN bus, with a transfer rate of over 900 frames per second. I don't think the datalogger allows you to turn off any parameters, but you can tell it to "listen" slower. However, the data is a constant stream on the CAN bus, so it isn't like the OBDII communications where the data has to be requested.

My VTEC engagement is at 5500 RPM's. I really don't feel comfortable adjusting ignition timing yet, so I'm using the timing map from Hondata's optimized stock tune.

I have lots of WOT pulls from 3K to 8.5K datalogged. I'll sent one shortly.

 

this is some great information. With just intake and exhaust, the injector duty was in the high 80s. I guess the fuel system on the stock S is limited. If you can post up the 3rd gear log, that would be helpful 2nd gear goes by pretty quick I would imagine.

I'm considering getting this as I heard that running a testpipe will make the car run lean. This would elvate the problem. Also the upped rev limiter is helpful But then again, I need to upgrade clutch cause the stock POS presure plate is crap. It slips so bad.

 

can you enlightment me on this suggestion made by the software. "Suggested fuel change from the lamba value"

what can you explain that in a little more detail? when you hit the suggested fuel change, the number in there is the percent to change. For example in the low fuel map in 3500/10, the program suggest a 3 percent increase in that field. So make a 3 percent increase in that field?

where is the suggestion being made by? is it going off the corr A/F or the A/F?

 

What I've learned during this process is that you really need to split the part throttle datalog from the full throttle datalog, and make both datalogs complete. The datalogs that you have above are very incomplete since you didn't hit many of the target cells

Basically, for a full throttle datalog, you should hit the datalog button just before you push the pedal to the floor in the 3rd gear at 1500 RPM's on a road where you can accellerate all the way to fuel cut without lifting, then hit the datalog button again to end it.

For part throttle, I just posted a long suggestion in another thread about that.

Since there seems to be such a huge difference in fuel curves between 80% throttle and 100% throttle due to harmonic characteristics, it seems to be very hard to merge part throttle and full throttle tunes. I wish the professional tuners would chime in about this ...

If I missed the point of your question, let me know...

 

yeah i got you on the logging suggestion. I went out and did a 1500 RPM at 3rd gear and 2000 RPM in 4th gear. But it ddn't hit all the cell?

 

It looks like it hit as many cells as a full throttle run would hit. Ignore the suggestions in columns 5-8, since this is a full throttle pull. Columns 9 and 10 are where the full throttle tuning will occur. The reason why you didn't hit all the cells in column 9 and 10 is because the RPM indexes are outside the usable range.