Kane Tunes My car
#128
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?
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?
Last edited by myriadshalaks; 06-04-2009 at 12:17 AM.
#131
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.
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.
Last edited by myriadshalaks; 06-04-2009 at 07:06 PM.
#132
Illudium Q-36 Space Moderator
iTrader: (1)
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.
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.
#137
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.
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.
Last edited by myriadshalaks; 06-04-2009 at 10:14 PM.
#141
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"
duh. lol.
i said "this the data needed" not "this is the table needed"
Last edited by myriadshalaks; 06-05-2009 at 01:04 PM.
#145
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.
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.
Last edited by myriadshalaks; 06-05-2009 at 02:53 PM.