And you guys are driving me in-sane.....


LOL - PS Brettus I am pretty sure it is Calculated Load.

I had the Dashhawk and my logger set-up and it seemed that Calc Load was the one putting out the right info.

 

yes it's Calculated Load

 

I found doing a chart like this to be very worthwhile ...

 

Absolute.

 

you confuse me MM . Sometimes you are tighter than a fishes **** for information and other times very free with it .
Que pasa ?

 

I'm never tight with information.
I virtually give it away.
I just refuse to give away answers to stuff that is so unbelievably obvious that it is painful.
Just ask anyone that has learned the "secret" of the dwell settings.

Reading threads like this one mostly makes me fear for the welfare of the human race.
But sometimes there are questions (like yours) that are simple clarifications for some point that might not be obvious or not worthy of much further investigation.

 

......

 

Yeah this with load would be perfect IMO; since the Target Lambda varies based on load.... unless your hand keying them.

 

No one insults quite like Jeff......

 

Its a lost art.

 

A cheeky turn of phrase and all that jazz.....



You missed your calling man - you shoulda been a diver; you would have fun I would imagine. Right about the time your filling someones wall locker with cement you realize you'd fit right in....

 

I probably would have enjoyed that!
I sink like a rock, so I probably would have made a pretty decent diver.
Getting back to the surface is another matter, I suppose.

I guess that's a metaphor somewhere...

 

LOL - hey 50% of the job isn't all bad. Just kinda makes it hard to have a repeat performance.


Getting a bit more on topic: Chase; with Load, Target AFR, MAF volts, g/sec, and Actual AFR - all in one snapshot averaged over a few hundred data-points - scaling these little bumps in your tune should be a snap - now I just gotta get to work.

I am sitting on at my desk procrastinating......

 

I read the target values off the load vs rpm map and manually loaded them so yes load is accounted for in the chart .

 

I am doing the same thing...... just automatically - HAHAHA; trying to finish now...

 

Graphing the logged AFR/MAF against the known map targets is relatively easy to do in Excel, once you get the hang of using the functions. Quickest way is to take your .csv log file and convert it to .xls format. Then add another worksheet to the spreadsheet. Then cut and paste your AFR or MAF map from Access Tuner or other software onto the new worksheet. Back on your datalog worksheet create a new column for "Target MAF/AFR". To calculate the Target MAF you then use the HLOOKUP function. An example...

=HLOOKUP(F2,'MAF Calibration'!$A$2:$AV$3,2,TRUE)

F2 - your logged MAF Voltage value
'MAF Calibration' - name of the worksheet where you put the MAF map. If you don't rename it you'll probably see 'Sheet2' or similar.
$A$2:$AV$3 - this is the cell range of the MAF lookup table. It should include the header row with MAF Voltages.
2 - this is the 'nth' row in the MAF lookup table containing the values you want to find. For the MAF map it will always be "2".
TRUE - just means you aren't expecting to find an exact match of MAF Voltage.


For TARGET AFR you use the INDEX and MATCH functions. An example...

=INDEX('AF Gear 1-3'!$A$2:$R$19, MATCH(G2,'AF Gear 1-3'!$A$3:$A$19,1), MATCH(A2,'AF Gear 1-3'!$B$2:$R$2,1))

'AF Gear 1-3' - name of the worksheet where you put the AFR map
$A$2:$R$19 - this is the cell range of the AFR lookup table. It should include the RPM header column and Load header row.
G2 - your logged RPM value
$A$3:$A$19 - this is the cell range containing the values of the RPM header column.
A2 - your logged Calculated Load.
$B$2:$R$2 - this is the cell range containing the values of the Load header row.
1 - means you aren't expecting to find an exact match.

Once you have entered in one formula, you can just drag to copy it to all cells in the new "Target MAF/AFR" column. The "$" before each lookup table cell location is required to establish an Absolute cell reference rather than a Relative cell reference. I'm definitely not an Excel power-user, I just found how to do this off of Google because I knew the program could do 2D and 3D table lookups without using add-ons. My example spreadsheets where done in Excel 2003. My copies of Open Office 2.4 on FreeBSD and Ubuntu also have these functions, but I didn't test them on those machines cause that's obviously not where my ATR race is installed.

Graphing Target AFR-MAF.zip

 

cool . What happens to values midway between 4 marker values ?

IE say 3750rpm and 145% load

 

Jesus.... just wait like 2 hours!

 

For the 2D MAF map it looks up values in a "less than or equal to" manner. For the 3D maps (eg AFR) it does the same, but I realized that the way I posted needed to be amended. Where I had...

=INDEX('AF Gear 1-3'!$A$2:$R$19, MATCH(G2,'AF Gear 1-3'!$A$3:$A$19,1), MATCH(A2,'AF Gear 1-3'!$B$2:$R$2,1))

should really be...

=INDEX('AF Gear 1-3'!$B$3:$R$19, MATCH(G2,'AF Gear 1-3'!$A$3:$A$19,1), MATCH(A2,'AF Gear 1-3'!$B$2:$R$2,1))

with an explanation of...

$B$3:$R$19 - this is the data range of the AFR lookup table. It should NOT include the header column and row.


Graphing Target AFR-2.zip

 

that's cool, atl8. nicely done. still looks hard. lol.

just got off the phone with kane. the new baseline is on its way shortly.

i'll have to make some more logs and key some stuff in to it, but this time sunday or monday, i should have the most perfect tune available to me given the equipment i have on hand. i'm shooting for a flat 12.5 from about 5k to 9k. is that too ambitious? i think NO! well, maybe a little.