EVOscan Cannot log Fuel Trim Low

[1999RSfwd]

Hello everyone. I have a 98 GSX, with a blackbox. I have EVOscan for logging, and ECUflash for flashing.

I've owned the car for almost a year, and it runs ok, but I want to get my injectors dialed in.
For some reason I cannot log "Fuel Trim Low" or "Fuel Trim Mid" in EVOscan.
I do have a P0105 code, and a previous owner wired in a potentiometer in the barometric circuit. Could this potentiometer be my issue?
I haven't tested the maf, but I replaced the first maf with a spare I had.
Also I can clear the P0105 code while the car is running, and it doesn't come back until I turn the car off and back on.
Is there a way to turn this code off in ECUflash? Even if I could turn it off would the fuel rims log?

Any help is appreciated, and I can post logs, and do whatever is needed if someone is willing to help.

Thanks!

 

[1999RSfwd]

Here are two logs I took today. A short cruise, and idle when I got back. I cleared the P0105 code before the cruise, and it didn't show back up. The code usually comes back after I turn the car off and back on. So after idling, I turned the car off and back on, and the code didn't come back.

 

[95REGF150]

It's definitely logging but it's just returning a 0 value which means your problem is in your EvoScan definition not pointing to the correct MUT request address for your ecu's ROM.

Are you using a CeddyMods ROM or the original ROM in the ECU? If the original ROM what is your ROM ID? If using Ceddymods you need to use the EvoSacn .xml that he included in the mods .zip file. He properly defined all the various MUT request address's there for his ROM's with the proper scalings. And I can tell from the headers in the .csv you posted that you are not using his .xml

 

[1999RSfwd]

The ROMs highlighted are the ones I currently make adjustments from. And this is how EvoScan looks as well.

You must be logged in to view this image or video.

You must be logged in to view this image or video.

 

[1999RSfwd]

And this

You must be logged in to view this image or video.

 

[95REGF150]

Ok so if you open the EvoScan 2.7+ folder in CeddyMods you will find there is a file named "Mitsubishi MUTII.XML". You need to go to your documents and find the EvoScan v2.9 folder. Inside there there will be a DataSettings folder. Inside that folder you need to replace the MUTII.xml that is in there with the MUTII.xml from the CeddyMods folder.

Then when you start EvoScan select "EFI CeddyMod DSM" from the Select ECU dropdown as it will now be an option.

This will give you all of the logging values for the 2055 ROM as defined by Ceddy. A bunch of the values in the definition you are using are incompaitble with 2055. That's why your Load 1 byte is not working and it's impossible to tune without logging load.

However, the fuel trims (low, mid, high, and current) are not one of these things. By the second photo you posted they are all defined as the correct MUT address (0C, 0D, 0E, and 50) so I'm not sure why you are not getting any values for any of those requests.

Did you modify the MUT table at all in EcuFlash?

 

[95REGF150]

And you definitely need to get those working because going by your Cruise log with the one trim that is working your short term fuel trim it's pulling the max 25% out and your still running rich as hell so just by looking at that I would say you have your injectors scaled a little to small.

Have you done WOT tuning yet? How is your AFR looking in open loop under boost? What do you have your global injector scale set too right now for 750's?

 

[1999RSfwd]

I put a copy of the "Mitsubishi MUTII.XML" in the DataSettings folder. And I get this mesage now in EvoScan

You must be logged in to view this image or video.

You must be logged in to view this image or video.

Here is my MUT table, I did not modify it that I know of.

You must be logged in to view this image or video.

My injector settings right now.

You must be logged in to view this image or video.

 

[95REGF150]

You are getting that error in EvoScan because now there are multiple files with the same definition labels in them. But none of those definitions are the one you are using. EFI CeddyMods DSM is only in that file you put in there. So you can just hit ok to that error and select EFI CeddyMods DSM from the list. If you want it to stop coming up move the other .xml's to another folder.

The MUT address's in your table are correct so logging 0C, 0D, 0E, and 50 should be giving you the fuel trims. Try a log with EFI CeddyMods DSM selected and see what you get. Then we can look at other possible issues.

And as for your injector scaling, one issue right off the bat is I can see you changed the values in the Batt Voltage axis of the Latency table. I'm sure you did this to match the latency table provided with your injectors but kind of an unwritten rule of EcuFlash is don't mess with the lookup axis unless you know everywhere it is being used.

What that means is when you change the Battery Voltage values in the latency table it affects the output of data from other tables that use that axis. For instance lets say another table call it Table X had the battery voltage values in the 1st column and values 1-7 in the second column. You change the Voltage axis as you did in the latency table. But now in Table X where before 12v was an interpolation between value 4 and 5 with your rescale it now outputs almost exactly value 4. This can affect your drivability and cause problems you will never be able to track down.

So first thing change your Voltage Axis back to:
4.69
7.03
9.38
11.72
14.06
16.41
18.68

Now to get your latency values you can interpolate from the values at the voltages you were given to get the correct latency for that voltage. (i.e. you currently have 2.265ms at 7.4v and 3.570ms at 5.05v. to get the value for 7.03v you do: ((7.03-5.05)*(2.265-3.570))/(7.4-5.05) + 3.570 and you get 2.470ms.

But in my opinion looking at those values that is still way high for latency. All of the injectors I have worked with in that size range have been less than that and that may be why you are rich at cruise. What I would recommend doing is just putting the factory latency values back in and adding to all of them all at once to shift the table up for your larger injectors. Generally for 750cc you would add around 0.280ms to the values.

Lastly your global of 757cc is probably a little high for 750's. Most of the injectors I have tuned take around 5-10% lower scaling then their nominal flow rating to give correct AFR at WOT. The latency table does not really affect WOT it affects mainly idle and slightly cruise. What is your AFR under boost right now? Do you have a log of that?

 

[1999RSfwd]

Which .xml's do I need to move from the datasettings folder, in order to not get that message?

I do not see a "EFI CeddyMods DSM" on the list. I see "EFI CeddyMod Evo 5/6". Do I choose this one??

You must be logged in to view this image or video.

I changed the voltage axis back to stock, I must have accidentally changed it. And I changed my latency values back to stock and then added 0.280ms to all of them.

You must be logged in to view this image or video.

In that cruise log earlier, I did go WOT a few times. My target afr is set 10.5, but my wideband was reading around 11.5.

Thank you for all of your help!

 

[95REGF150]

That's odd its not showing up. Attached is the Ceddymods DSM .xml I use for EvoScan. I had to upload it as a .txt file since the forum does not allow .xml extensions. After you download it just change it back to a .xml extension. Then in the DataSettings remove all the other unrelated MUTII XML defiinitions. The only ones you should have in the folder are these:

You must be logged in to view this image or video.

And the Mitsubishi MUTII.xml there should be the one I have attached to this post

Now the next time you open EvoScan the "EFI CeddyMod DSM" should be available from the drop down.

Went back and looked at your log in EvoScan and I see your WOT pulls now:

You must be logged in to view this image or video.

The hard part about this is until you get your fuel trims logging you don't know if there is a trim active that is adding or subtracting fuel during this pull.

What I'm worried about for you is this part of your cruise where the STFT is stuck at -25% and your still rich:

You must be logged in to view this image or video.

So you definitely need to get tuning. I think your on the right track by changing the latency as I suggested. Now for more of my 0.02 cents.

One thing Ceddy did which I don't agree with is he changed the fuel trim control points from their factory values of this:

You must be logged in to view this image or video.

To this:

You must be logged in to view this image or video.

What this does is turn on the High LTFT that was disabled from the factory. I played hell tuning WOT with the high trim turned on because it would randomly start subtracting fuel during a WOT pull and turning the car lean which is really bad. So I put the factory values back in and now there is no trim active after 4000 RPM or so when the MID LTFT shuts off. Then if you tune in your MID trim well enough your good to go.

So for you that's where I would start. Change your control points back to stock. Then I would set your injector scaling around 680-700cc and the fuel map to 11.0 AFR under boost. Then go make some pulls. If the Wideband shows leaner than 11.0 on the log past 4000 rpm you need to drop the injector scaling some more. If it is richer than 11.0 than raise the injector scaling slightly. Once you get the Wideband matching your AFR Map then move on to adjusting your trims via your latency value.

Same thing with those. Idle trim positive 10% then add 10% to the latency table and vise versa. Once you get the idle trim within 5% or so look at your Mid trim. If it is not within 5% then you will have to modify the MAF smoothing table to bring it inline. But usually you do not have to do this.

You must be logged in to view this image or video.

 

[1999RSfwd]

Well well well, look what we have here! That new .xml file worked. Oh and no errors in Evo Scan anymore.

You must be logged in to view this image or video.

Thank you so much! This is why I love tuners, because of people like you.
I'm about to go do some tuning right now.

I do have one question though. Would my P0105 code cause my fuel trims to not populate?

 

[95REGF150]

No problem at all happy to help.

I do have one question though. Would my P0105 code cause my fuel trims to not populate?

I don't think the P0105 code on it's own would prevent the fuel trims from working. However, that code is for Baro sensor malfunction which is very important for proper fueling. Basically your MAF sensor is 3 sensors in one. An air temp sensor, baro sensor, and volume flow sensor. It uses all 3 of these readings to combine into a Mass Air Flow rate. The P0105 code means that it is not getting one of these key pieces of information. Which will throw off your Ecu Load.

That becomes a problem if you spend all this time tuning and then get your MAF fixed it will change all the loads and require a complete retune. I would get that code taken care of before you do anything else and just turning it off is not a good solution for this one. A new MAF may do it but it could also be the wiring or connector for the MAF.

 

[1999RSfwd]

A previous owner wired a potentiometer in the baro circuit, I wonder if this could be my problem. I need to test the maf, but I know all the wires look good around the connector.

 

[95REGF150]

A previous owner wired a potentiometer in the baro circuit, I wonder if this could be my problem. I need to test the maf, but I know all the wires look good around the connector.

Is the pot still in the Baro circuit? If so I would definitely remove it. Tweaking sensor input voltages is old school and for people who cannot actually tune via flashing or some other method which you now have.

You want the sensor inputs as clean as they were when the factory tuned the car.

 

[1999RSfwd]

Yes it is still there. I need to remove it, I just haven't yet.

 

[1999RSfwd]

So I just went for a cruise, came back and idled for little bit. My fuel trims still won't populate. I think it may have something to do with CEL, but I'm not sure. The car does seem to run better though, after some adjustments.

 

[1999RSfwd]

Ok, so I removed the potentiometer in the baro circuit. I reset my trims by unplugging the battery. Removing the potentiometer cured my P0105 CEL, and my fuel trims have started working!
@95REGF150 Thank you for all your help, I don't know what I would have done without you