MAF not dialing in

[domestic rice]

Anyone have this problem. I set up the histogram copy and paste with mult% but for what ever reason after doing this 3 times back to back it does not appear to be getting much better. Am I doing something wrong here or is this a 20 time process here?

[flame]

Not sure if you have a wideband, standard or pro interface or what procedure you have been following. The MAF is fairly straight forward to dial in. This may help you out http://www.hptuners.com/forum/showpo...9&postcount=26

[domestic rice]

Not sure if you have a wideband, standard or pro interface or what procedure you have been following. The MAF is fairly straight forward to dial in. This may help you out http://www.hptuners.com/forum/showpo...9&postcount=26

That was what I did exactly. Numbers were all in the teens and after copy and pasting using the multiply % feature 3 times it does not appear to be moving too much. Not sure whats wrong with it. I do have a WB02 and standard

[Asylumwarp]

watch this video to get your wideband setup correctly. It maynot be the model you are using, but it goes into detail on the histrogram stuff you maybe having trouble with.

http://www.thetuningschool.com/downl...p_wideband.wmv

And use flames JPG to setup the maf correctly. If the wideband isnt reading i dont think it will show up in the maf table.

[domestic rice]

I will go ahead and try his hist set up. When I dialed this in way back in the day I though I just copy & paste special-mult % to the MAF airflow vs freq table. Why would this not be working now? I didnt even need the WB02 last time to do this.

I just looked to set it up and I think that is what I was already logging. Look how high the MAF hz is getting with the same results. I looked at some other MAF settings from others, and mine are way high. Something has to be not set up right or busted.

[Asylumwarp]

Do you have it in the chart also? MAF HZ? post a cfg your using and your last log so i can see whats going on..

[domestic rice]

Here is the confg

[5_Liter_Eater]

That tune has the MAF failing at 1400 Hz, which you're exceeding at idle. You have yourself and SD tune there. And it may not be apparent because you have the P0103 set to MIL on second error so it will only fail every other ignition cycle.

[domestic rice]

That tune has the MAF failing at 1400 Hz, which you're exceeding at idle. You have yourself and SD tune there. And it may not be apparent because you have the P0103 set to MIL on second error so it will only fail every other ignition cycle.

Damm I didn't even notice that. No wonder. Well after this help and the hours asylum spent helping me out last night I hope to get this dialed in in no time!

Thanks guys!

[Asylumwarp]

You know this whole time working, i've never really checked over your actual tune to make sure its setup correctly, and thats why i missed the 1400hz fail also DOH! Get that fixed before messing with MAF tuning or your chasing your tail....

did the config work??!?! post a log/tune/config we made.. lemme check it out im curious is to how the 3 hours spent went last night..

[Asylumwarp]

I just glanced over your tune, and i see alot of stuff to address..

[domestic rice]

Something is still not right. The histo we made are not working and the upper hz are way jacked up.

[Ben Charles]

You need to log MAF HZ in the table, I don't know what config your using, but when I plugged mine it, it didn't show anything.

[flame]

You are not in MAF only. Look at the pic and change that to 0.

[Asylumwarp]

i need your cfg file posted so i can look it over.. Whenever you post a log post your cfg file too so we can see your log with a working config. without a config for your log, we are blind.

[Asylumwarp]

Got your config working so i could see your log..
But remember as Flame pointed out, you were only tuning your MAF at 4k and above, using your VE/MAF tables below, showing me your VE tables might be off too. Someone else point anything in out in the jpgs were missing? Is dynamic air your VE tables calculated air? And MAF lb/min is how much its getting via MAF? If thats the case, the log points out a very big difference and i believe we are working to try to make these as close as possible so the transition from VE/MAF is as smooth as possible correct? If this is true, something is miscalibrated, and by looking at the log, the MAF is OFF, the VE is also off. But get the MAF on first, then the VE next. I would add 10 percent to the MAF table from the looks in those areas in the pic on your tune, smooth the rest from there up. The log seemed to work for me after i fixed a few things. Its hard for someone to jump in and say do this/that when they dont know how we set it up.

[Asylumwarp]

And heres your VE table...
Heck heres the config file i used to get your log working if that helps you.

[domestic rice]

here is the config

[Asylumwarp]

look at this

[5_Liter_Eater]

Why do you need a user defined PID for AFR Error?