View Full Version : 96-97 Fuel control
RealMcCoy
06-01-2013, 12:42 PM
I feel a little dumb asking because I should probably remember this myself.... (we'll just blame old age...lol)
I was e-mailed a log from a 97 to help another member diagnose an issue, and the front fuel control has what looks like garbage data.
So the question is: Is the separated front/rear bank fuel control something that started with the 98-99? and there is only one bank of control on the 96-97?
striker2
06-01-2013, 02:19 PM
all OBD2 vehicles should have separate fuel control as part of the emissions standards for OBD2, so anything from 96+. Easy way to confirm is to hook up a standard OBD2 scan tool that shows live data and look for B1 and B2 LTFT.
many manufacturers had split fuel control on their OBD1 computers if they had sequential port injection (instead of TBI). Im pretty sure Mitsu did on their US models (no reason to spend the money on the extra O2 sensor otherwise).
RealMcCoy
06-01-2013, 02:58 PM
Not buying that... Almost all monitor the banks separately, but to see separate bank control and trims is pretty rare... Most cars that I see (even much newer than these cars) only have LTFT/STFT and BI/B2 trims are not supported.
I don't have a 96-97 here at the shop to check, so I can't verify it one way or the other.
striker2
06-01-2013, 03:45 PM
The only OBD2 vehicles that might not have separate bank control (aside from the obvious I4 engines) are those that only have a single cat after the exhaust merges. many vehicles (including the 3S) have pre-cats, one per bank, plus the main cat and the PCM has to be able to adjust the banks individually to keep the pre-cats functioning properly (and from burning them up).
RealMcCoy
06-01-2013, 05:29 PM
The only OBD2 vehicles that might not have separate bank control (aside from the obvious I4 engines) are those that only have a single cat after the exhaust merges. many vehicles (including the 3S) have pre-cats, one per bank, plus the main cat and the PCM has to be able to adjust the banks individually to keep the pre-cats functioning properly (and from burning them up).
I agree that would be the ideal method, but in reality it's seldom the case... While a large portion of the cars out there fall into the category you mentioned as merging into one monitored cat, there are many out there that have separate monitored cats, but don't support separate fuel trim data.
I don't believe OBDII mandates HOW the manufacturers control the fuel and cat efficiency, just that they do it, and set codes for failure... It's up the the manufacturer to meet the emissions standards of the model year being produced in any way they can.
OBDII was also quite slowly phased in and modified in the early years... It's pretty common to see very different standards for a 96 car than a 98...
But none of this theory positively answers my question... I have a log with both displayed, but complete garbage on the front bank, and relatively normal readings on the rear. I'm theorizing that it's just garbage on an unused PID, but it would be very nice to confirm it for sure one way or another..
vr4tune
06-01-2013, 05:39 PM
I have a 97 and yes it has separate fuel controls as well as stft and ltft for both banks. I had a cracked front manifold and only my front bank went rich. It may be the scan tool.
RealMcCoy
06-01-2013, 05:49 PM
I have a 97 and yes it has separate fuel controls as well as stft and ltft for both banks. I had a cracked front manifold and only my front bank went rich. It may be the scan tool.
Awesome, thank you... I agree now that I have that info. He's using evoscan 2.9. I told him it was broken, and to download an earlier version, I don't think he believes me yet...
Greg E
06-01-2013, 06:36 PM
91 to 99 Turbo cars have separate bank fuel trim control. Hence there being 2 o2 sensors. ;)
Later NA cars switched to dual bank control too.
RealMcCoy
06-01-2013, 06:42 PM
91 to 99 Turbo cars have separate bank fuel trim control. Hence there being 2 o2 sensors. ;)
Later NA cars switched to dual bank control too.
Few know the code like you do, so I won't argue... But I will submit that "contol" does not equate to available scan data... There is no separate right and left trims output in scan data for a first gen...
Greg E
06-01-2013, 09:30 PM
Few know the code like you do, so I won't argue... But I will submit that "contol" does not equate to available scan data... There is no separate right and left trims output in scan data for a first gen...
It's because Jeff was the first person to discover it. Somehow this detail eluded all the software designers all these years. I think I'm the first person to trace the entire MUT table after Jeff got me started.
RealMcCoy
06-01-2013, 09:51 PM
Are you saying that with a correctly designed scan tool that info could be extracted from a 1G ECU?
Also, do you concur that I should consider data from a 2.9 log suspect when it appears to be garbage? I'm trying to gather enough evidence to condemn it, but the car owner has talked to "other people" that claim 2.9 is the shit to have...
striker2
06-02-2013, 12:55 AM
I dont have any problems logging with 2.9, but I am using a 99 Chrome ECU. Im not sure how well it interacts with the 96-97 ECUs.
Greg E
06-02-2013, 08:55 AM
Are you saying that with a correctly designed scan tool that info could be extracted from a 1G ECU?
Also, do you concur that I should consider data from a 2.9 log suspect when it appears to be garbage? I'm trying to gather enough evidence to condemn it, but the car owner has talked to "other people" that claim 2.9 is the shit to have...
Just because you're seeing garbage results doesn't mean anything other than the trims are located in a different request.
Maybe one day I'll disassemble a 1G rom and trace all the requests to make a logger that actually works with our cars. 2.9 file I created only works with Chrome. Many requests are custom. The next version will really separate my setup from stock as many of the simple requests like load and RPM will return garbage if not used with chrome.
RealMcCoy
06-02-2013, 01:46 PM
Just because you're seeing garbage results doesn't mean anything other than the trims are located in a different request.
Maybe one day I'll disassemble a 1G rom and trace all the requests to make a logger that actually works with our cars. 2.9 file I created only works with Chrome. Many requests are custom. The next version will really separate my setup from stock as many of the simple requests like load and RPM will return garbage if not used with chrome.
I didn't consider that He may have gotten his hands on your 2.9 file... I assumed he just downloaded the original directly. Any way I can identify it from the logs he sent?
I've also seen posts here about code gathering issues... In one of those threads I remember you saying 2.9 was broken. If that hasn't been resolved I'm hesitant to believe any code information he sends me.
I never upgraded from 2.8 because I kept hearing about issues with 2.9, so I wouldn't have any first hand experience.
Greg E
06-02-2013, 03:12 PM
I didn't consider that He may have gotten his hands on your 2.9 file... I assumed he just downloaded the original directly. Any way I can identify it from the logs he sent?
I've also seen posts here about code gathering issues... In one of those threads I remember you saying 2.9 was broken. If that hasn't been resolved I'm hesitant to believe any code information he sends me.
I never upgraded from 2.8 because I kept hearing about issues with 2.9, so I wouldn't have any first hand experience.
The file Hammish created (the one that comes with evoscan by default) is supposed to be a general file for all mitsubishis from that generation. Truth is there's no such thing. It's based on the old mitsulogger files and is tailored to the 4 cyl cars.
2.9 does have issues reading codes but that's the only issue. Still debating what to do about this... It's one of two issues left to tackle before the next version of Chrome is released.
RealMcCoy
06-02-2013, 03:44 PM
The file Hammish created (the one that comes with evoscan by default) is supposed to be a general file for all mitsubishis from that generation. Truth is there's no such thing. It's based on the old mitsulogger files and is tailored to the 4 cyl cars.
So this may be the issue I'm seeing with the front bank data...? I haven't ruled out the possibility that his ECU crapped out, but I'd like to see if we can get some codes... Hopefully I can get him to try a different logger. Trying to help someone fix a car from 3000miles away is difficult enough without crap data to work with...
RealMcCoy
06-04-2013, 01:36 AM
Got more of the story, and everything makes sense now... He had purchased an ECU from Adam, and was running Chrome, but put the stock ECU and injectors back in to try and troubleshoot a problem. So was in fact trying to log with the Chrome 2.9 file.
Adam's ECU is back in it now running Chrome, and the data lakes sense again, so I think I may actually be able to help him out now...
Wish I could get and trust codes though...
Greg E
06-04-2013, 08:21 AM
Show the guy how to get codes using a test light. The procedure is in the manual.
Greg E
06-04-2013, 12:00 PM
If I knew anything about the protocol i would write my own code reader program....
If I knew anything about how the timers in the stock ROM worked I'd make a chrome mod that would blink the CEL codes.
Powered by vBulletin® Version 4.2.3 Copyright © 2026 vBulletin Solutions, Inc. All rights reserved.