Maybe you can try MUT_50
scaling is
OBDII_LTFT => ((MUT_50/4 - 32) * 100/128
at least in CT9A

 

Your fuel trims look okay to me, I've seen alot of stock Evos running aftermarket intakes or filters that have similar fuel trims. The 0 in the begining is because the logging of the fuel trims take a little longer to start than the rest.

BTW, the fuel trim seems to be about 10% off meaning if actual is 2.00% (on OBD2 software), it shows as 1.80%.

 

Thanks for sharing! Is your car stock? Is the tune stock? You seem to have much lower IPW than I do. Just trying to learn more about the differences...

 

My car isn't quite stock - I have an HKS drop in and upper intercooler pipes, and I'm using a generic 90 octane map from the other forum that has JDM mivec and some other minor changes. Looks like I need to back off the timing in a couple spots just a little still.

 

Ah, no wonder it looks different than a stock log If you pull 1 to 2 degrees of timing where you're knocking in the low end, it will probably help. It's interesting that you seem to be running higher boost than stock, but are hitting lower peak load cells than some stock cars. It seems to hold boost better though. Are you running with 90 octane gas?

 

I'm running 91 octane - the highest I can get in NM - and it was about 85 degrees outside last night when I did the logs.

 

Just for some reference, here's what a log looks like on a Dominator 2.0 & Cos MX1 Cams @ 24 psi (low boost mode) in 3rd gear. You can see it only spools around 250 RPM later than stock. Sorry, I'm hiding my IGN timing numbers The boost holds pretty steady across the entire range and this car puts out around 445whp/418tq when the boost is set to 26 psi (hi boost mode).

 

So it looks like the MAP cap has been taken off too in this logger?

.......awesome.....

 

Works great! Much easier than using PCMScan/Evoscan combo as I was doing previously

The only thing it's lacking is WB support, if we had that, I wouldn't ask for anything more

 

So Tephra, what is involved with finding all the other groovy loggable items like we have with Evo 8/9 like Load Error, WGDC correction, etc?

 

You can use most of the MUT tables from the 9.
If I'm not mistaken, Load Error should be: MUT8A 0.15625*x-20

So in the config.txt it should look like this on the 52680018:
LoadError:0x8086FB:1:x,0.15625,*,20,-:2

 

Oh and WGDC Correction is MUT8B 0.5*x-64

So in the config.txt it should look like this on the 52680018:
WGDCCorrection:0x80876D:1:x,0.5,*,64,-:2

 

what is this basically..sorry didnt read 6 pages.... does this program allow us to log with the stock ecu and need nothing else? or what exactly?

 

Yup well we log the ADC signal from the MAP sensor - which is uncapped.

I think the cap is only if you log through regular OBD (mode 1 or mode21). It doesn't actually affect the running of the car.

So yeah you have the full 3bar worth of log

With WB02 I will be looking at hooking the signal wire upto the rear02, just like we did for CT9A, then you can log the rear02 in this logger.

Stay tuned for that thou

 

Mate - 6 pages is nothing... Some of my threads get upto 60+ pages hehehe

To answer your question.

This logger allows you to log the stock ECU with a very minor change.

See the first post for what changes you need to make - most USDM ECU's are catered for so its just a matter of making the change and then running the program with the right config.txt file.

You still need an OP2.0 cable