Notices
ECU Flash

96530006 can't logg trims

Thread Tools
 
Search this Thread
 
Old Apr 14, 2009 | 09:18 PM
  #1  
japanevo's Avatar
Thread Starter
Evolving Member
iTrader: (2)
 
Joined: Jan 2007
Posts: 124
Likes: 0
From: Las Vegas
96530006 can't logg trims

i just switched back to 9653 for various reasons. the most important being that it will pas emissions. i just got my car fixed and after driving it for a day i tried to log the trims because things were a little off. for the most part everything seems to be working except the fuel trims, short and long both just show up as .1008 . the only change i made was to the ROM itself was patching it to get rid of the rear O2 heater. guess i can try changing it back and see if it goes back to normal.
Old Apr 14, 2009 | 10:01 PM
  #2  
tephra's Avatar
EvoM Guru
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 66
From: Melbourne, Australia
either you did the patch wrong.

or you didn't leave the car run for long enough so the trims start working.

also sometimes you can get a "bad" flash - try changing the fuelmap and then reflashing, then changing the fuelmap back then reflashing again.
Old Apr 14, 2009 | 10:51 PM
  #3  
japanevo's Avatar
Thread Starter
Evolving Member
iTrader: (2)
 
Joined: Jan 2007
Posts: 124
Likes: 0
From: Las Vegas
Originally Posted by tephra
either you did the patch wrong.

or you didn't leave the car run for long enough so the trims start working.

also sometimes you can get a "bad" flash - try changing the fuelmap and then reflashing, then changing the fuelmap back then reflashing again.
actually i need to retract that statement about patching the rear heater. i did do the patch but not until after i tried logging. but i did try it again after words and got the same readings. i put well over 60 miles on the car before i tried logging so i don't think that would be the problem especialy considering the STFT showed .1008 as well. i just reset the ecu after i made a change to my Maft, i had the input and out put all jacked up from when i was troubleshooting and the car was running lean, so i will try the flash then reflash tomorrow on my way home from work. it is about 20 miles one way.
Old Apr 15, 2009 | 05:28 AM
  #4  
fixem2's Avatar
Evolved Member
iTrader: (30)
 
Joined: Dec 2003
Posts: 929
Likes: 0
From: USA
I believe that is the default reading, aka = zero. Check your front sensor O2 connection.
Old Apr 16, 2009 | 06:07 PM
  #5  
japanevo's Avatar
Thread Starter
Evolving Member
iTrader: (2)
 
Joined: Jan 2007
Posts: 124
Likes: 0
From: Las Vegas
front o2 is showing in evoscan as of yesterday. i tried the re-flash trick last night, went back to a version of my ROM without the rear o2 patch, and i have put another 50 miles in the car and still no LTFT, low mid or high.... i might try flashing the 9055 ROM i was using before just to see if it is my ROM or what.
Old Apr 18, 2009 | 01:18 PM
  #6  
SEEnoEVO's Avatar
Evolved Member
iTrader: (21)
 
Joined: Dec 2006
Posts: 544
Likes: 1
From: D
I am having the exact same issue. I switched from 011 to 006 and it isnt logging my FTs as well. I also noticed that the RPM it is logging is incorrect. It is reading almost twice what it actually is. Someone help please!!!!
Old Apr 18, 2009 | 01:32 PM
  #7  
fixem2's Avatar
Evolved Member
iTrader: (30)
 
Joined: Dec 2003
Posts: 929
Likes: 0
From: USA
Never saw this when I converted. Try going back to the original ROM and verify it works correctly. THen convert using minimal map conversion from 0011 to 0006 and immobilizer disabled. This would verify that it is the ROM and not the car.
Old Apr 18, 2009 | 02:09 PM
  #8  
SEEnoEVO's Avatar
Evolved Member
iTrader: (21)
 
Joined: Dec 2006
Posts: 544
Likes: 1
From: D
I got the RPM and the rest of the numbers working correctly with the help of fixem2, but the trims still are not logging. My AFR's at idle dropped from 14.7 to 11.0.
Old Apr 18, 2009 | 02:38 PM
  #9  
SEEnoEVO's Avatar
Evolved Member
iTrader: (21)
 
Joined: Dec 2006
Posts: 544
Likes: 1
From: D
Can anyone explain why the AFRs at idle seem so rich at least? I am really struggling with all these different issues.
Old Apr 18, 2009 | 06:58 PM
  #10  
tephra's Avatar
EvoM Guru
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 66
From: Melbourne, Australia
did you copy your injector settings (scaling+latencies)?
Old Apr 18, 2009 | 07:33 PM
  #11  
SEEnoEVO's Avatar
Evolved Member
iTrader: (21)
 
Joined: Dec 2006
Posts: 544
Likes: 1
From: D
I actually installed FIC 1000's and have an extremely rich idle. I switched from the 011 to the 006 while upgrading injectors.
Old Apr 18, 2009 | 11:36 PM
  #12  
japanevo's Avatar
Thread Starter
Evolving Member
iTrader: (2)
 
Joined: Jan 2007
Posts: 124
Likes: 0
From: Las Vegas
well mine have started working and hopefully i have all my other issues fixed so i can start causing other problems now. i had to back track a few ROM changes to get everything working, at first i was having issues with the not logging trims, so i back tracked a few changes then trims started working but started getting P0125. think i have the 125 code fixed now hopefully the only CEL code i have is fro the rear O2. i am going to give it a couple of days to make sure the 125 is gone then i am going to try applying Mrfred's rear O2 patch again and see how it goes.
Old Apr 18, 2009 | 11:49 PM
  #13  
fixem2's Avatar
Evolved Member
iTrader: (30)
 
Joined: Dec 2003
Posts: 929
Likes: 0
From: USA
If you are using a Tephra ROM then the Rear O2 simulator is included.
Old Apr 19, 2009 | 08:06 AM
  #14  
japanevo's Avatar
Thread Starter
Evolving Member
iTrader: (2)
 
Joined: Jan 2007
Posts: 124
Likes: 0
From: Las Vegas
i was referring to the parch to get rid of the CEL for the heater circuit. i tried the 10K ohm resistor mod and that didn't work. i haven't tried the 2-3 50 ohm resistor mod yet. but if i cant get my car running right then that will be next.
Old May 13, 2009 | 07:46 AM
  #15  
SEEnoEVO's Avatar
Evolved Member
iTrader: (21)
 
Joined: Dec 2006
Posts: 544
Likes: 1
From: D
Originally Posted by japanevo
well mine have started working and hopefully i have all my other issues fixed so i can start causing other problems now. i had to back track a few ROM changes to get everything working, at first i was having issues with the not logging trims, so i back tracked a few changes then trims started working but started getting P0125. think i have the 125 code fixed now hopefully the only CEL code i have is fro the rear O2. i am going to give it a couple of days to make sure the 125 is gone then i am going to try applying Mrfred's rear O2 patch again and see how it goes.
What was your fix for the P0125?


Quick Reply: 96530006 can't logg trims



All times are GMT -7. The time now is 08:19 AM.