Stuck the MAF back in to test bucking at takeoff
#1
Stuck the MAF back in to test bucking at takeoff
Well that #$%^!@ MAF is back in.
Pros:
1) Appears to have fixed bucking at takeoff
Cons:
1) Screwed up LTFTs, even with the Holden table (not surprised)
2) That stupid bucking at steady cruise is back
3) WAY down on power, even at part-throttle, I definitely had to lay into the pedal more at cruise
As soon as my MAF ends get here I will rebuild the MAF table. I think that may fix the bucking at cruise when it matches the VE table more. I did turn proportional idle back on, so that may be what is hurting me though. We shall see....
Pros:
1) Appears to have fixed bucking at takeoff
Cons:
1) Screwed up LTFTs, even with the Holden table (not surprised)
2) That stupid bucking at steady cruise is back
3) WAY down on power, even at part-throttle, I definitely had to lay into the pedal more at cruise
As soon as my MAF ends get here I will rebuild the MAF table. I think that may fix the bucking at cruise when it matches the VE table more. I did turn proportional idle back on, so that may be what is hurting me though. We shall see....
#4
Originally Posted by cablebandit
you guys love a needless headache. Leave the maf on and let the pcm do all the work
#7
Originally Posted by TwoFast4Lv
Yes I must admit It makes me LOL to see people tossing there MAFs again
Trending Topics
#8
I decided to update my MAF table today, because my trims are way too far off to stick ported ends on the MAF. It could have maxed out the LTFTs for sure. The MAF frequency to 0 thing certainly did the trick. I made an interesting observation. The MAF table was almost exactly one cell off all the way down the table. (shifting them to the left)
#10
Originally Posted by Scooter70
You better change that avitar...
So did you get the MAF table nailed down so that your trims with MAF match the ones you were getting SD?
So did you get the MAF table nailed down so that your trims with MAF match the ones you were getting SD?
#11
Launching!
Join Date: Mar 2004
Location: Dallas Texas
Posts: 233
Likes: 0
Received 0 Likes
on
0 Posts
#13
TECH Enthusiast
Join Date: Mar 2004
Location: Australia
Posts: 647
Likes: 0
Received 0 Likes
on
0 Posts
In circumstances like this I will go back to the stock MAF cal, Idle airflow and all other airflow calcs and retune. Its hard to hit a target when you don't know where it is. Change one thing at a time. By all means keep your current tune safely stored. Use it when you have isolated the problem.
It is unquestionably fuel related caused by dodgy airflow calcs, but without knowing much about your car (cam etc.) it could be anything. I knwo its obvious, but check your O2 sensors and log your airlfow readings at idle and into moving closed loop.
It is unquestionably fuel related caused by dodgy airflow calcs, but without knowing much about your car (cam etc.) it could be anything. I knwo its obvious, but check your O2 sensors and log your airlfow readings at idle and into moving closed loop.
#14
Originally Posted by MNR-0
In circumstances like this I will go back to the stock MAF cal, Idle airflow and all other airflow calcs and retune. Its hard to hit a target when you don't know where it is. Change one thing at a time. By all means keep your current tune safely stored. Use it when you have isolated the problem.
It is unquestionably fuel related caused by dodgy airflow calcs, but without knowing much about your car (cam etc.) it could be anything. I knwo its obvious, but check your O2 sensors and log your airlfow readings at idle and into moving closed loop.
It is unquestionably fuel related caused by dodgy airflow calcs, but without knowing much about your car (cam etc.) it could be anything. I knwo its obvious, but check your O2 sensors and log your airlfow readings at idle and into moving closed loop.