like this? 2nd gear WOT maf in g/s to maf voltage

how can i tell what's best?

and what's going on at 3.8 volts?

 

DO a MAF + Load + AFR graph like that.... see where the AFR's are off the target in your MAP

 

i'll try that on the next one.

this one is the maf calibration i did with baseline overlayed with the output from 2nd and 3rd wot.

this one seemed useful. maybe i should have the grid lines on though.

what does this mean?

 

best i can do. the scale is off when you try to overlay them.

 

I don't understand the target MAF and actual MAF thing....

I was talking about a graph time based with load, AFR, target AFR and MAF

 

the first one is the maf calibration copied from the map. the y is g/s and the x is voltage. the actual maf is what i logged at wot.

i don't understand the second maf chart either. it's a chart of the maf reading in g/s at a certain load. so if the load is .98, the target maf reading is whatever it is on the calibration map and the actual map is from my data logs. it was a pita to put together, and it's not very illuminating. i guess it sort of helps to see the load under which the MAF reading is not what it should be given the map. But there's really not enough data to fill it in all the way. So it looks all jiggity jaggity.

the afr at load chart seems interesting though.

i can do time based. i didn't think of that.

 

Wait huh?

MAF is a 2D map - fuel target AFR is the one with Load and RPM that matters.... IE if you target afr at a load of 1 and RPM of 6000 is 9% off; you need to know the MAF voltage and the g/sec at that point in order to see where on the MAF curve you need to scale....

Make sense or am I leading you in circles? Call a brother if you need to B.

 

right, i was trying to find out where the maf is at, say, at load 1. that's what the chart is supposed to represent. but it doesn't.

i can do better.

 

if i had the target afr from the map with the percent difference on the first chart, would that be what i'm looking for?

the scale is too large to have them all on one graph. i could put load and maf on one though.

 

okay, to hell with the charts.
this is the data needed to tweak the maf scale, correct?

 

Without the deviation for standard (aka Target) that graph doesn't help a whole lot....

 

yeah, to hell with the charts. see above.

so it's clear, at this point i think i'm just neurotically trying to get things as perfect as i can with what i have for lack of anything better to do.

i got what i was looking for working backwards. now i want to try it the right way. but the data is all slippery.

thanks for indulging me.

 

Wait for the new MAF Baseline.... I think this will solve your problem.

Maybe I can get it done this weekend.

 

sweet. that's what i've been angling for anyway.

still, i think i did figure out a way to make a line out the target afr data that would overlay with the actual afr data. if it works, i'll post it later. any excel gurus are welcome to jump in here.

 

That table doesn't tweak your MAF scale.....that's the open-loop AFR table

 

but next to it is the maf and afr logged data. i'm trying to find out where in the open loop afr log the afrs from the map table are not lining up .. and by how much they're not lining up ... so i know where and by how much to tweak the maf scale.

duh. lol.

i said "this the data needed" not "this is the table needed"

 

With a few cold ones, anything is possible.

 

the only problem to solve is my neurosis.

 

I tried logging target afrs yesterday and got a bunch of numbers that were totally out of whack - just sayin

 

i think if you go by the rpms and the load, you can find a comparison line from your AP data logs.
SO look at the data log, look at rpm and load, and find an afr. then look at the table, find a comparable rpm and load, and write down the target afr. then divide the bigger afr from the smaller afr. that should give you the percent deviation from target at that spot. i think you can make two lines out of that.

i'm going to try tonight.

but it's a pita. i considered just having a slot for every rpm from 0-9000

column 1 will be rpm, coulmn 2 would be data log afr at that rpm, and column 3 would have the afrs from the map table at that rpm AND with a load comparable to the load the afrs from column 2 are logged at. there won't be an axis for the load, it's up to the charter to make sure the loads line up. hence, pita.

 

/\ that's what i've done before . I'm just surprised the target afr's seem to be unloggable

 

i hear ya. someone needs to write a program that would make this easier. oh wait, someone is. lol.

 

rhymes with pain ?

 

and david blaine.

 

BTW - anyone know what load is the one used by the pcm . Is it calculated load or absolute load ?