Fuel trims and idle
Have your tried a different logging program, like Mitsulogger to log the trims?
I thought I saw people having the same problems with EvoScan where the trims would stay at .1008. At the very least, make sure the requests and formulas are correct for the version you are using. The requests should be 0C, 0D, 0E, and 0F for LTFT Lo, Mid, High, and STFT, respectively. The formula for all four should be (0.1961*x)-25.
Your STFT (request 0F) should be rapidly moving around while logging if you are in closed loop and EvoScan is working properly.
I thought I saw people having the same problems with EvoScan where the trims would stay at .1008. At the very least, make sure the requests and formulas are correct for the version you are using. The requests should be 0C, 0D, 0E, and 0F for LTFT Lo, Mid, High, and STFT, respectively. The formula for all four should be (0.1961*x)-25.
Your STFT (request 0F) should be rapidly moving around while logging if you are in closed loop and EvoScan is working properly.
Thread Starter
Joined: May 2005
Posts: 233
Likes: 2
From: Fuquay Varina NC
Download link: http://www.megaupload.com/?d=7562WSO7
Thanks
Thread Starter
Joined: May 2005
Posts: 233
Likes: 2
From: Fuquay Varina NC
Have your tried a different logging program, like Mitsulogger to log the trims?
I thought I saw people having the same problems with EvoScan where the trims would stay at .1008. At the very least, make sure the requests and formulas are correct for the version you are using. The requests should be 0C, 0D, 0E, and 0F for LTFT Lo, Mid, High, and STFT, respectively. The formula for all four should be (0.1961*x)-25.
Your STFT (request 0F) should be rapidly moving around while logging if you are in closed loop and EvoScan is working properly.
I thought I saw people having the same problems with EvoScan where the trims would stay at .1008. At the very least, make sure the requests and formulas are correct for the version you are using. The requests should be 0C, 0D, 0E, and 0F for LTFT Lo, Mid, High, and STFT, respectively. The formula for all four should be (0.1961*x)-25.
Your STFT (request 0F) should be rapidly moving around while logging if you are in closed loop and EvoScan is working properly.
Thanks for your help also.
hrmm I checked it out - everything (load/tps tables + coolant temp) looks fine for closed loop control.
something else is wrong.
can you try reflashing this ROM to your car? perhaps it got corrupted somehow?
Maybe flash back to your stock ROM, then back to this one again...
something else is wrong.
can you try reflashing this ROM to your car? perhaps it got corrupted somehow?
Maybe flash back to your stock ROM, then back to this one again...
That small snipet of the log that you posted shows your O2 sensors reading very rich and you wideband agress with it.
What have you changed recently when everything was working ok? You said you changed the O2 sensor? Did you mess with anything on your MAFT...was the MAFT tuned and calibrated correctly for your injectos? Your fuel trims should be very negative, but they aren't doing anything (assuming they are being logged correctly), so something is keeping your car from running closed loop maybe.
What have you changed recently when everything was working ok? You said you changed the O2 sensor? Did you mess with anything on your MAFT...was the MAFT tuned and calibrated correctly for your injectos? Your fuel trims should be very negative, but they aren't doing anything (assuming they are being logged correctly), so something is keeping your car from running closed loop maybe.
Thread Starter
Joined: May 2005
Posts: 233
Likes: 2
From: Fuquay Varina NC
hrmm I checked it out - everything (load/tps tables + coolant temp) looks fine for closed loop control.
something else is wrong.
can you try reflashing this ROM to your car? perhaps it got corrupted somehow?
Maybe flash back to your stock ROM, then back to this one again...
something else is wrong.
can you try reflashing this ROM to your car? perhaps it got corrupted somehow?
Maybe flash back to your stock ROM, then back to this one again...
)On a side note I still cant read from the ecu so I am not sure what getting written to it. I bought a new cable with the same result using ECU flash v1.40.
Thanks again Tephra, HAPPY NEW YEAR!
Thread Starter
Joined: May 2005
Posts: 233
Likes: 2
From: Fuquay Varina NC
That small snipet of the log that you posted shows your O2 sensors reading very rich and you wideband agress with it.
What have you changed recently when everything was working ok? You said you changed the O2 sensor? Did you mess with anything on your MAFT...was the MAFT tuned and calibrated correctly for your injectos? Your fuel trims should be very negative, but they aren't doing anything (assuming they are being logged correctly), so something is keeping your car from running closed loop maybe.
What have you changed recently when everything was working ok? You said you changed the O2 sensor? Did you mess with anything on your MAFT...was the MAFT tuned and calibrated correctly for your injectos? Your fuel trims should be very negative, but they aren't doing anything (assuming they are being logged correctly), so something is keeping your car from running closed loop maybe.
Thread Starter
Joined: May 2005
Posts: 233
Likes: 2
From: Fuquay Varina NC
yeah this is where I get out of my depth.
I *would* have thought that its better to get the injector scaling correct in the ECU rather than fudging the numbers sent by the MAFT???
What is your scaling from the 96940011 rom?
I *would* have thought that its better to get the injector scaling correct in the ECU rather than fudging the numbers sent by the MAFT???
What is your scaling from the 96940011 rom?
Also, keep in mind that after the battery died, the fuel trims were reset in the ECU. So, your fuel trims should be at 0, like they are. However, they should start responding once your coolant temp comes up and idling for a few minutes. I'm not sure how long you have waited so far, so I thought I would mention it. The coolant temps in your logs look like the car was already warmed up.
Last edited by l2r99gst; Jan 1, 2009 at 09:09 PM.
Thread Starter
Joined: May 2005
Posts: 233
Likes: 2
From: Fuquay Varina NC
I am using the factory scaling transferred it to the new rom.
Thread Starter
Joined: May 2005
Posts: 233
Likes: 2
From: Fuquay Varina NC
Well, go back and check both ROMs and make sure you didn't miss any important settings from the 0011 ROM to the 0006 ROM. As tephra mentioned, a good test would be to flash back in your 96940011 ROM and see if your trims start responding again. If so, then make sure that you didn't miss anything like the injector scaling, etc. If the MAFT is handling the injector scaling, then that shouldn't be an issue.
Also, keep in mind that after the battery died, the fuel trims were reset in the ECU. So, your fuel trims should be at 0, like they are. However, they should start responding once your coolant temp comes up and idling for a few minutes. I'm not sure how long you have waited so far, so I thought I would mention it. The coolant temps in your logs look like the car was already warmed up.
Also, keep in mind that after the battery died, the fuel trims were reset in the ECU. So, your fuel trims should be at 0, like they are. However, they should start responding once your coolant temp comes up and idling for a few minutes. I'm not sure how long you have waited so far, so I thought I would mention it. The coolant temps in your logs look like the car was already warmed up.
I had the very same issue, trims not showing up in evoscan nor mitsulogger. I knew they were ok, so I forgot about it. A couple months later I was logging and noticed everything was working. So my idea was ecu was tarded and needed to recalibrate itself or something to that affect. So I suggest unhooking the ground terminal of your battery for 30 minutes and try that. If that doesn't work and you know your trims are pretty darn close, I wouldn't worry too much about it. Drive it for a while and keep checking.
Thread Starter
Joined: May 2005
Posts: 233
Likes: 2
From: Fuquay Varina NC
I had the very same issue, trims not showing up in evoscan nor mitsulogger. I knew they were ok, so I forgot about it. A couple months later I was logging and noticed everything was working. So my idea was ecu was tarded and needed to recalibrate itself or something to that affect. So I suggest unhooking the ground terminal of your battery for 30 minutes and try that. If that doesn't work and you know your trims are pretty darn close, I wouldn't worry too much about it. Drive it for a while and keep checking.
Thanks
I will try resetting the ECU, but I still have idle issues thats why I need to see my trims



