PCM Diagnostics & Tuning HP Tuners | Holley | Diablo
Sponsored by:
Sponsored by:

What Happens When the VE Table Doesn't Agree With the MAF?

Thread Tools
 
Search this Thread
 
Old 07-02-2006, 10:56 PM
  #1  
TECH Fanatic
Thread Starter
iTrader: (9)
 
Josh's Avatar
 
Join Date: Feb 2002
Location: West Lafayette, IN
Posts: 1,061
Likes: 0
Received 0 Likes on 0 Posts

Default What Happens When the VE Table Doesn't Agree With the MAF?

It seems that every tuning document I've read mentions that one of the functions of the VE table is to provide a comparative value for the reported MAF reading. I've not been able to find, though, an explanation of what happens when the VE table thinks the MAF is wrong. Particularly, which of the two values is used to determine fueling?

I realize this shouldn't be an issue if the car is tuned properly, but just for the sake of discussion, I would be interested to know.

Thanks,
Josh
Old 07-02-2006, 11:05 PM
  #2  
8 Second Club
iTrader: (16)
 
soundengineer's Avatar
 
Join Date: Jul 2003
Location: Chicago IL
Posts: 4,651
Likes: 0
Received 9 Likes on 9 Posts

Default

IF VE is correct and MAF is wong...it mucks up the tune for any part that uses the MAF
IF the MAF is correct and teh ve is wrong..then it mucks up the tune where the VE is wrong...

basically when any part is wrong..it mucks up the tune
Old 07-03-2006, 11:16 AM
  #3  
TECH Fanatic
iTrader: (12)
 
txhorns281's Avatar
 
Join Date: Jan 2004
Location: Houston, TX
Posts: 1,869
Likes: 0
Received 0 Likes on 0 Posts
Default

i also believe if the disparity b/w the two airflow calculations meets a particular threshold, the PCM will immediately fall back on SD operation (as that is supposed to be the more conservative, secondary system by original intention and setup). This disagreement would usually happen when the MAF electronics fail in some way, causing the two calculations to conflict greatly with each other and would be followed by a MAF DTC. If the MAF and VE were tuned so distantly in error, I'm not sure if the PCM sets a condition for a warning of some sort, but I rather doubt it would need to since the car would most likely be running like total crap and you definitely would notice. The range in which is acceptable b/w the two calculations is probably pretty lenient (at least lenient enough to allow +- 15-20% disparity as we can see that trims are allowed to swing b/w +25 and -25), so the difference b/w the two would have to be waaaaaaaaaay off either intentionally, or by idiocy... I've never cared to wander that far to find out

Last edited by txhorns281; 07-03-2006 at 11:22 AM.
Old 07-03-2006, 02:43 PM
  #4  
8 Second Club
iTrader: (16)
 
soundengineer's Avatar
 
Join Date: Jul 2003
Location: Chicago IL
Posts: 4,651
Likes: 0
Received 9 Likes on 9 Posts

Default

it takes about +/- 25 in LTFT before it gets to that point of thowing a code from being out of whack...
or there are also a few tables that compare to various MAP values vs MAF amounts that can get too far as well and throw a code....(this is usually teh problem vette guys run into when they ask about reduced power mode)
Old 07-03-2006, 07:36 PM
  #5  
TECH Fanatic
Thread Starter
iTrader: (9)
 
Josh's Avatar
 
Join Date: Feb 2002
Location: West Lafayette, IN
Posts: 1,061
Likes: 0
Received 0 Likes on 0 Posts

Default

Good info, thanks, guys.

Josh
Old 07-04-2006, 09:28 AM
  #6  
TECH Fanatic
iTrader: (10)
 
redtail2426's Avatar
 
Join Date: Aug 2004
Location: Rochester,Ny
Posts: 1,433
Likes: 0
Received 0 Likes on 0 Posts

Default

i noticed the other day on my car that my lower ve values(10-20% throttle/under 2000 rpm)were way to low and what would happen is the car would run smooth and then all of the sudden jerk and hesitate a bit.The jerking was from the computer jumping down to that lower ve value which in turn puts you at a much lower spark advance on the spark tables.Bottom line,the car wont run as smooth as it should.




All times are GMT -5. The time now is 11:40 PM.