PCM Diagnostics & Tuning HP Tuners | Holley | Diablo

Negative LTFTs at WOT, Fix???

Old Jun 7, 2006 | 01:21 PM
  #1  
6speeder's Avatar
Thread Starter
On The Tree
iTrader: (25)
 
Joined: Mar 2004
Posts: 140
Likes: 0
From: Dayton ohio
Default Negative LTFTs at WOT, Fix???

Hi, I'm trying to figure out why my 402 is randomly going lean. I noticed that my Long Term Fuel Trims are going from 0 to -15 at WOT and this is when the car starts to go lean. You can actually watch the injector duty cycle go from 66% down to 53% when the LTFTs drop. How can I fix this?

I can email anyone the graph of this taking place as a powerpoint file if this would help. Thanks, Brian
Reply
Old Jun 7, 2006 | 06:58 PM
  #2  
joecar's Avatar
TECH Senior Member
20 Year Member
Photogenic
Photoriffic
Shutterbug
 
Joined: Apr 2002
Posts: 6,080
Likes: 17
From: So.Cal.
Default

Negative LTFT means engine is running rich and PCM is reducing fuel.

What are your HO2SB11 and HO2B21 voltages at WOT...?
Reply
Old Jun 7, 2006 | 06:58 PM
  #3  
jimmyblue's Avatar
Moderator
iTrader: (11)
 
Joined: Mar 2002
Posts: 12,604
Likes: 7
From: East Central Florida
Default

-15 trims at WOT is abnormal, it should clip at zero. I've
never seen this myself, seems like the computer has lost
its mind (or still thinks it's in closed loop).
Reply
Old Jun 7, 2006 | 07:01 PM
  #4  
joecar's Avatar
TECH Senior Member
20 Year Member
Photogenic
Photoriffic
Shutterbug
 
Joined: Apr 2002
Posts: 6,080
Likes: 17
From: So.Cal.
Default

I agree with jimmy....

At WOT, if LTFT is negative PCM uses zero, if LTFT is positive PCM keeps positive (or richer of LTFT and PE).
Reply
Old Jun 8, 2006 | 07:59 AM
  #5  
Fran D's Avatar
TECH Regular
20 Year Member
iTrader: (5)
 
Joined: Nov 2001
Posts: 422
Likes: 0
From: Washington Crossing, PA
Default

Yes, this sounds more like you are never getting to open loop at WOT. You should log the FTC at WOT and make sure that it's 15 or 22 (more likely, the latter). If not, then you need to dig into what switch is keeping it out of open loop (e.g., TP%, Engine Temp, etc.).
Reply
Old Jun 8, 2006 | 08:17 AM
  #6  
6speeder's Avatar
Thread Starter
On The Tree
iTrader: (25)
 
Joined: Mar 2004
Posts: 140
Likes: 0
From: Dayton ohio
Default

Originally Posted by Fran D
Yes, this sounds more like you are never getting to open loop at WOT. You should log the FTC at WOT and make sure that it's 15 or 22 (more likely, the latter). If not, then you need to dig into what switch is keeping it out of open loop (e.g., TP%, Engine Temp, etc.).

I looked at all the sensors that I can think of would cause this and they look great. What gets me is that when this takes place all the sensors stay the same so it makes me think it is tuning related, but I don't know. I notice my lights dim when I go WOT. Could this have anything to do with the negative LTFTs? I think it is from my belt slipping on the alternator.
Reply
Old Jun 8, 2006 | 08:30 AM
  #7  
Fran D's Avatar
TECH Regular
20 Year Member
iTrader: (5)
 
Joined: Nov 2001
Posts: 422
Likes: 0
From: Washington Crossing, PA
Default

Originally Posted by 6speeder
I looked at all the sensors that I can think of would cause this and they look great. What gets me is that when this takes place all the sensors stay the same so it makes me think it is tuning related, but I don't know. I notice my lights dim when I go WOT. Could this have anything to do with the negative LTFTs? I think it is from my belt slipping on the alternator.
Have you confirmed that you are in FTC (fuel trim cell) 15 or 22 at WOT? This is not a sensor value; it represents what fuel lookup table your car is in.

The dimming at WOT, I think, is a separate issue (unless, of course, the controller supply droops below 4 volts, but I think the car would just shut off then). That's odd... in and of itself. Perhaps a slipping belt.

Please check the FTC at WOT.
Reply
Old Jun 8, 2006 | 06:11 PM
  #8  
SmokingWS6's Avatar
TECH Fanatic
iTrader: (1)
 
Joined: Jun 2004
Posts: 1,795
Likes: 2
From: St. Louis MO
Default

Check your tps% at WOT. If the TPS is messed up it may not know your at wot.

Also check the PE enable table. Always possible a wrong value has been entered forcing it to stay in closed loop.
Reply
Old Jun 9, 2006 | 07:02 AM
  #9  
6speeder's Avatar
Thread Starter
On The Tree
iTrader: (25)
 
Joined: Mar 2004
Posts: 140
Likes: 0
From: Dayton ohio
Default

Ok, I think the dimming is coming from the alternator slipping because there is rubber next to the pulley on the alternator, but it still does drop to 11.4 volts as soon as I get on it. I logged it last night and the cell it was in for the most part was 22 at WOT.
Reply
Old Jun 9, 2006 | 08:23 AM
  #10  
Fran D's Avatar
TECH Regular
20 Year Member
iTrader: (5)
 
Joined: Nov 2001
Posts: 422
Likes: 0
From: Washington Crossing, PA
Default

Originally Posted by 6speeder
Ok, I think the dimming is coming from the alternator slipping because there is rubber next to the pulley on the alternator, but it still does drop to 11.4 volts as soon as I get on it.
Weird.

Originally Posted by 6speeder
...I logged it last night and the cell it was in for the most part was 22 at WOT.
That qualification is a little troubling. If the TP% showed 100, you should expect the FTC to be 22. You do need to be careful in interpreting the data from some scanners. If you are just running synchronously (ask for PID, get it, ask for next PID, etc.), then there can be some latency in the readings (especially during WOT when things are changing quickly) depending on the data rate the scanner is operating under. Therefore, it's possible that at the top of a gear at WOT, during a shift, one may close the throttle slightly before going to the next gear. Depending on the mode and speed of the scanner, it's possible to catch a TP% reading of 100, while by the time it gets to logging the LTFT it's already showing -15 due to the throttle closure on a shift. But, perhaps I'm repeating something you already know.

If you have a contiguous stream of data with TP% at 100 and the FTC is not steady at 22 (without being in a "transition" region, i.e., shift), then there's something that is overriding the PE Enable TP% vs. RPM table. That's probably the first place to check. Have you done something with the tune, recently, to cause these issues? However, if you have a contiguous stream of data with TP% at 100, FTC at 22 and LTFTs at -15, that's a problem that would extend beyond the capabilities of any tuning software, that I know of, to deal with. There may be a problem with the PCM. I hope that's not the case.

I hope all this rambling is helpful and not confusing. Good luck!
Reply


Thread Tools
Search this Thread

All times are GMT -5. The time now is 11:21 AM.