Tuning VE table with LM1 issues/questions
06-29-2007, 10:13 PM
#1
Launching!
Thread Starter
iTrader: (2)
Join Date: Jan 2007
Location: Los Lunas NM
Posts: 234
Likes: 0
Received 0 Likes
on
0 Posts
Tuning VE table with LM1 issues/questions When I paste special multiply by % my AFR Error into my VE Table the values go dangerously low.
Am I doing something wrong?
I followed the steps exactly and my wideband and HPtuners are within .1 AFR.
Thanks for your help guys.
Fil131
Pictures here: http://www.hptuners.com/forum/showthread.php?t=13036
Am I doing something wrong?
I followed the steps exactly and my wideband and HPtuners are within .1 AFR.
Thanks for your help guys.
Fil131
Pictures here: http://www.hptuners.com/forum/showthread.php?t=13036
07-02-2007, 09:41 AM
#5
Moderator
iTrader: (11)
Join Date: Mar 2002
Location: East Central Florida
Posts: 12,605
Likes: 0
Received 6 Likes
on
6 Posts
That sure is a funky donut. But what you want to bear in mind
is, computers is stupid and garbage in = garbage out. The WBO2
is nice and all, but it still responds to exhaust oxygen and not
the -real- in-taken mixture. With a cam at low RPM you must
expect the reading to be corrupted by intake air shooting or
being drawn through to the exhaust pipe. This is a lean error
that drives NBO2 fuel trimming to the rich side and will make
the WB indicate that the VE needs bumping up when it does
not (necessarily). Going into DFCO is another way-lean mode
that needs to be discarded from the data set. You might want
to validate any filtering (or apply some if there ain't).
Personally I've always preferred to do things "the hard way"
because I trust my eye more than I trust statistics. You
can use the histograms but you want to not ever trust them
over your mental model of what VE is really about, or likely
to do.
is, computers is stupid and garbage in = garbage out. The WBO2
is nice and all, but it still responds to exhaust oxygen and not
the -real- in-taken mixture. With a cam at low RPM you must
expect the reading to be corrupted by intake air shooting or
being drawn through to the exhaust pipe. This is a lean error
that drives NBO2 fuel trimming to the rich side and will make
the WB indicate that the VE needs bumping up when it does
not (necessarily). Going into DFCO is another way-lean mode
that needs to be discarded from the data set. You might want
to validate any filtering (or apply some if there ain't).
Personally I've always preferred to do things "the hard way"
because I trust my eye more than I trust statistics. You
can use the histograms but you want to not ever trust them
over your mental model of what VE is really about, or likely
to do.
07-02-2007, 11:57 AM
#6
Launching!
Thread Starter
iTrader: (2)
Join Date: Jan 2007
Location: Los Lunas NM
Posts: 234
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by NoGo
It looks like you boofed on the copy/paste.
Your VE table looks high though. Is your IFR table correct?
Only the very racy-race stuff gets over 100% VE on a single valve head.
Your VE table looks high though. Is your IFR table correct?
Only the very racy-race stuff gets over 100% VE on a single valve head.
If you have any other advice let me know, thanks for the input.
Fil131
07-02-2007, 12:54 PM
#7
I've always been a big fan of 'If it works don't fix it'. So, if your car is running right, I wouldn't sweat the higher than normal VE values.
However, if you notice your gas mileage being low, or odd A/F ratio's on transients you may want to look into what could cause your VE to calculate high.....Bad wideband, exhaust leak, wrong fueling values, low fuel pressure etc...
However, if you notice your gas mileage being low, or odd A/F ratio's on transients you may want to look into what could cause your VE to calculate high.....Bad wideband, exhaust leak, wrong fueling values, low fuel pressure etc...
