new $EE tuning thing!

[dzidaV8]

I'd like to put my 2 cents into this discussion, after using this program for tuning a few f-bodies. Great work and it really makes life easier!

For me it would make tuning even easier if the Analyzer result tables could be simply copied and pasted. Another thought is to make the tables resolution match the resolution of PCM tables.

I have made a little spreadsheet to interpolate data from EEhack analysis for VE table adjustment, but entering the values by hand is a major PITA...

There is the spreadsheet attached, maybe it will be useful for someone. To use it you must instal excell interpolation add-on from http://xongrid.sourceforge.net/

[steveo]

I'd like to put my 2 cents into this discussion, after using this program for tuning a few f-bodies. Great work and it really makes life easier!

For me it would make tuning even easier if the Analyzer result tables could be simply copied and pasted. Another thought is to make the tables resolution match the resolution of PCM tables.

I have made a little spreadsheet to interpolate data from EEhack analysis for VE table adjustment, but entering the values by hand is a major PITA...

There is the spreadsheet attached, maybe it will be useful for someone. To use it you must instal excell interpolation add-on from http://xongrid.sourceforge.net/

i totally understand what you're saying.

i tried to make the VE and MAF analysis tables match the scale of the ones in $EE, but when subjected to ordinary datalogs it tended towards a really noisy unusable correction map, because the analysis that eehack does is fairly primitive and doesn't smooth/spread/interpolate anything, it just averages into the appropriate cell, and by that time i didn't feel like making a more complex analyzer.

the weird thing is i thought i had copy/paste working. at the very least, i'm going to get that going for you in the next version.

i wont spend more time on the analyzer itself, since i'm writing a far superior one right now that is more general purpose and will do everything you want. it'll be an external tool, but will easily work with eehack's data.

[dzidaV8]

Thanks, the resolution is not so much of an issue, because as you wrote there would still need to be some smoothing added. Just a thought.

But being able to copy the tables would be great :)

[steveo]

i think i'll just put a copy to clipboard button right below the ve and maf correction tables for you. i can't see any need to select/copy ranges for this use case.

[Terminal_Crazy]

Hi Steveo:

Just been looking through a log and wondered on the best way to filter out erronous logs.

At 5500 rpm I let off the throttle and map drops to say 20 , afr hits 11.5 briefly due to the lag in the data log. I'm currently averaging this into my figures.

How would you filter that out, say every log should be with 10% TPS of the previous log? or only use logs within 10% of the target AFR ?


Mitch
Terminal_Crazy

[steveo]

noise like that is usually rejected or at least softened by your averaging if you have enough data.

if your analysis algorithm allows you to reject surrounding records you could just say reject all records within a few rows of map < 25 or something.

[fbody_Brian]

Just wanted to drop in here and say thanks again.
I compiled the latest version on linux. Seems to work fine, no issues to report as of now.
Haven't been doing much with the car because driving without 3rd and 4th gear puts a damper on things.
Got a new transmission in and ready to drive this thing!