MAF based understanding
Posted: Wed Apr 18, 2012 3:06 pm
MAF Mass Air Flow
Air goes in you get a voltage or frequency output, ecu translate this from a transfer function into a known number of air mass in grams a second or pounds a minute. Personally I would stick with grams a second.
With said number the ECU can add the right amount of fuel at the various rpms and load sights, you just need to tell it what Lambda to target.
Why I prefer it is because it is a lot easier to tune and get going with a wideband then compared to trying to tune all the spots of the speed density VE table. Also the load repsents engine efficiency and corsponds with tq output while MAF follows horse power output so you have a good idea of where your tq and hp are being produced at. Plus with a little math you can figure a range that your car can be in. Also throw a map sensor in and you can tell better where you are at on turbo compressor maps. Another reason is a MAF sensor handles varying exhaust and intake setups with better ease then a speed density setup, esp if you have variable geotermy turbos or exhaust flaps or etc devices to increase engine breathing efficency. You basically tune the transfer function based on lambda output on a working car if you have no curve for it presently. car to reading to lean on the wideband, take the lambda value and multiple it with the grams a second value to get the new updated grams a second for that voltage or adc point, This method works just fine when you run at lambda 1 in your commanded fuel table.
In another post I will post up how I suggest it be implemented
Despite what people may think I don't agree on it being that much of a restriction for a normal daily driven car. The biggest objection aganist it that I can see valid is how much space a maf sensor takes to plumb in for a correct setup. the looks of one in a setup.
Air goes in you get a voltage or frequency output, ecu translate this from a transfer function into a known number of air mass in grams a second or pounds a minute. Personally I would stick with grams a second.
With said number the ECU can add the right amount of fuel at the various rpms and load sights, you just need to tell it what Lambda to target.
Why I prefer it is because it is a lot easier to tune and get going with a wideband then compared to trying to tune all the spots of the speed density VE table. Also the load repsents engine efficiency and corsponds with tq output while MAF follows horse power output so you have a good idea of where your tq and hp are being produced at. Plus with a little math you can figure a range that your car can be in. Also throw a map sensor in and you can tell better where you are at on turbo compressor maps. Another reason is a MAF sensor handles varying exhaust and intake setups with better ease then a speed density setup, esp if you have variable geotermy turbos or exhaust flaps or etc devices to increase engine breathing efficency. You basically tune the transfer function based on lambda output on a working car if you have no curve for it presently. car to reading to lean on the wideband, take the lambda value and multiple it with the grams a second value to get the new updated grams a second for that voltage or adc point, This method works just fine when you run at lambda 1 in your commanded fuel table.
In another post I will post up how I suggest it be implemented
Despite what people may think I don't agree on it being that much of a restriction for a normal daily driven car. The biggest objection aganist it that I can see valid is how much space a maf sensor takes to plumb in for a correct setup. the looks of one in a setup.