Notices
ECU Flash

o2 trim freezing up, trims not recording...

Thread Tools
 
Search this Thread
 
Old Oct 22, 2010 | 12:58 PM
  #16  
Jack_of_Trades's Avatar
Evolved Member
iTrader: (17)
 
Joined: Jun 2007
Posts: 3,523
Likes: 2
From: Opelika,AL
Something is up with your STFT signal. I graphed it out since it looked like a pattern.



So its either your Front O2 sensor needs replacing or you are somehow logging the wrong item in the logger.

What REQUEST ID's do you have listed for your STFT (O2 Feedback) in Evoscan? Are you running a Tephra patch?
Attached Thumbnails o2 trim freezing up, trims not recording...-o2.jpg  
Reply
Old Oct 22, 2010 | 01:10 PM
  #17  
05blue8's Avatar
Thread Starter
Evolved Member
iTrader: (28)
 
Joined: Mar 2007
Posts: 843
Likes: 5
From: Austin, TX
RequestID is 0F and I've tried a second o2 sensor, no codes thrown with either, car runs the same with both. I know when I unplug the o2 the car runs like crap and also when it is disabled it runs like crap. Could it be going bad? It has a tephra mod on it, 96530706...here's a screenshot. Thanks for your help Jack...when this is resolved I'm going to send you some cash for your assistance.
Attached Thumbnails o2 trim freezing up, trims not recording...-trims.jpg   o2 trim freezing up, trims not recording...-tephra.jpg  

Last edited by 05blue8; Oct 22, 2010 at 01:13 PM.
Reply
Old Oct 22, 2010 | 01:27 PM
  #18  
Jack_of_Trades's Avatar
Evolved Member
iTrader: (17)
 
Joined: Jun 2007
Posts: 3,523
Likes: 2
From: Opelika,AL
The next thing to check would be your MUT table in ECUFlash and see what value is listed on the chart for 0F.
Reply
Old Oct 22, 2010 | 01:28 PM
  #19  
05blue8's Avatar
Thread Starter
Evolved Member
iTrader: (28)
 
Joined: Mar 2007
Posts: 843
Likes: 5
From: Austin, TX
Here's the table...
Attached Thumbnails o2 trim freezing up, trims not recording...-mut.jpg  
Reply
Old Oct 22, 2010 | 01:32 PM
  #20  
Jack_of_Trades's Avatar
Evolved Member
iTrader: (17)
 
Joined: Jun 2007
Posts: 3,523
Likes: 2
From: Opelika,AL
Well thats the correct value alright,hmm...
Reply
Old Oct 22, 2010 | 01:33 PM
  #21  
05blue8's Avatar
Thread Starter
Evolved Member
iTrader: (28)
 
Joined: Mar 2007
Posts: 843
Likes: 5
From: Austin, TX
Damn it, I was hoping for a different answer
Reply
Old Oct 22, 2010 | 01:37 PM
  #22  
l2r99gst's Avatar
Evolved Member
iTrader: (2)
 
Joined: Mar 2004
Posts: 3,499
Likes: 4
From: CA
For a test, why don't you mometarily raise your idle RPM by a good amount. You may simply be running into the mimimum pulsewidth issues with that large of an injector.

If so, maybe do the mods to mess with the minimum pulsewidth.
Reply
Old Oct 22, 2010 | 01:38 PM
  #23  
Jack_of_Trades's Avatar
Evolved Member
iTrader: (17)
 
Joined: Jun 2007
Posts: 3,523
Likes: 2
From: Opelika,AL
Originally Posted by 05blue8
Damn it, I was hoping for a different answer
Im thinking lol. Those readings are too much of a pattern to be real so I doubt that is showing actual trim values somehow. Have you tried loading a FRESH 9653xxx6 rom of any sort just to see if its the same result? Sometimes ROM's can become corrupt,happens more often than you'd think.
Reply
Old Oct 22, 2010 | 01:48 PM
  #24  
Mellon Racing's Avatar
Account Disabled
iTrader: (38)
 
Joined: Aug 2005
Posts: 9,319
Likes: 1
From: Virginia Beach, Virginia
put the oem rom back on the car and btw, which nb02 sensor brand/model did you install, some don't work.
Reply
Old Oct 22, 2010 | 01:51 PM
  #25  
05blue8's Avatar
Thread Starter
Evolved Member
iTrader: (28)
 
Joined: Mar 2007
Posts: 843
Likes: 5
From: Austin, TX
It is a stock replacement, not an off brand, the factory one.

Let me talk to my tuner and have him try that. Thanks guys, all ideas are welcome
Reply
Old Oct 22, 2010 | 02:22 PM
  #26  
05blue8's Avatar
Thread Starter
Evolved Member
iTrader: (28)
 
Joined: Mar 2007
Posts: 843
Likes: 5
From: Austin, TX
I just talked to another tuner who thinks it's the min pulsewidth issue also *sigh*
Reply
Old Oct 22, 2010 | 02:25 PM
  #27  
Mellon Racing's Avatar
Account Disabled
iTrader: (38)
 
Joined: Aug 2005
Posts: 9,319
Likes: 1
From: Virginia Beach, Virginia
the 05 evo has the 96940011 rom and those v7 rom's are "universal" and used on several different evo 8 models which I've never thought was a good idea.
Reply
Old Oct 22, 2010 | 02:31 PM
  #28  
Jack_of_Trades's Avatar
Evolved Member
iTrader: (17)
 
Joined: Jun 2007
Posts: 3,523
Likes: 2
From: Opelika,AL
Are you running the stock FPR or an adjustable one? If its an adjustable one, you can try lowering the static fuel pressure to 35psi instead of the factory 43psi so you can add more IPW at idle.
Reply
Old Oct 22, 2010 | 04:46 PM
  #29  
05blue8's Avatar
Thread Starter
Evolved Member
iTrader: (28)
 
Joined: Mar 2007
Posts: 843
Likes: 5
From: Austin, TX
So another development...I swapped my omni 4 bar map sensor and rom 965 to the stock 1 bar on 0011 and it worked, all trims recorded. I did this because I looked at previous logs and my 1 bar logged trims long ago when my original 4 bar took a crap so this was a replacement. It was the only 0011 xml I had with any sort of tuning done on the 2150's. Does this indicate it is in fact not an IPW issue?

Stock FPR.

He went to that ROM for better boost control and 0011 being so limiting tuning wise.

Last edited by 05blue8; Oct 22, 2010 at 04:59 PM.
Reply
Old Oct 25, 2010 | 02:22 PM
  #30  
Mellon Racing's Avatar
Account Disabled
iTrader: (38)
 
Joined: Aug 2005
Posts: 9,319
Likes: 1
From: Virginia Beach, Virginia
Originally Posted by 05blue8
So another development...I swapped my omni 4 bar map sensor and rom 965 to the stock 1 bar on 0011 and it worked, all trims recorded. I did this because I looked at previous logs and my 1 bar logged trims long ago when my original 4 bar took a crap so this was a replacement. It was the only 0011 xml I had with any sort of tuning done on the 2150's. Does this indicate it is in fact not an IPW issue?

Stock FPR.

He went to that ROM for better boost control and 0011 being so limiting tuning wise.
fwiw I run 38psi and make 705awhp on the 96940011 so don't let anyone tell you that ROM is limited it's technically a tephra v2 ROM as it lost support after that due to space limitations for teprha's mods (which I don't really need anyway).
Reply



All times are GMT -7. The time now is 12:32 PM.