Ted B

iTrader: (6)

Well, I've just about had it. Tuning another forum member's factory-sized turbo car on E85 and getting all the features working and tweaked was fairly straightforward enough. We tuned it within a day, and it runs like stink. My own car however is an entirely different story.

- Made WOT runs today. Switching to 94170015 did alleviate the nagging P0300 code and misfire, but after adding Tephra's NLTS-CEL patch to the base XML, 2-byte load now reads in the thousands. I'm just too weary at this point to sift through hundreds of forum posts just to figure out where to begin.

- The car has 850cc injectors and runs 93 octane, and yet can't maintain better than 14.xx-15.xx AFR when the turbo comes on boost, and hits 100+% IDC. Go figure that one out.

- Car feels like it hits boost cut around 320 load. Boost cut timer set to something like 400,000 ms, but I can't be sure if it's actually boost cut (?) or something else.

- Idle dips to 400rpm at times, and sometimes it stalls. Nothing seems to fix that.

- And lastly (I wish), the M&W COP system is NOT directly compatible with the factory ECU, as there is a persistant low throttle angle, low load misfire. It takes its toll on fuel economy, and makes the car jerky at times. No one can seem to figure out why it doesn't behave this way with standalones.


Sorry for the grocery list of headaches, but I have invested far more time in dealing with the idiosyncracies of the factory ECU than tuning the car itself, and I'm just completely burnt out on it. When I install my new ported head, BIG cams, new intake manifold and TB, etc., I can't even imagine the frustration that awaits. I feel strongly that I am not going to let things get to that point.

(sigh)

evo_08

iTrader: (1)

ted i have a twin dli in my garage if you need it.

Ted B

iTrader: (6)

Thanks, I appreciate that. I used to have one, but that won't work for what I am going to do, which is essentially to run E85 and 35-40psi.

mchuang

iTrader: (11)

Maybe you should ask someone who has everything working properly to share their .bin file and xml file and use it as a starting point

tephra

iTrader: (6)

first lets fix 2byte load...

what have you put into MUT00 and MUT01.

What is your evoscan formula for 2byte load

Ted B

iTrader: (6)

I don't think the problem is with Evoscan. In fact, I know what the problem with 2-byte load is. Apparently, 2-byte load is not included in the 94170015 mod XML that I swapped in today. Looks like I need to go hunt down that patch for this XML file (wherever it is).

All of this is just becoming too much for me to remember.

Evoryder

iTrader: (55)

i had the same 2 byte issue with his new patch..went back to the old one with my rom he made specific. Worked fine.

tephra

iTrader: (6)

what have you put in as MUT00 and MUT01?

Ted B

iTrader: (6)

35164 and 35165

Don't ask me where I got those numbers. I've sifted through so much that I wouldn't remember for the life of me. After another session of searching, I found the code for the MUT table somewhere else. I didn't change anything in it.

I did that, but something went amiss, and I had to restart from scratch.

tephra

iTrader: (6)

Those are correct, whats you address for the MUT table.

Whats your evoscan formula?

Ted B

iTrader: (6)

Evoscan:

<DataListItem DataLog="Y" Color="" Display="Load MUT 2Byte Mod" LogReference="LoadMUT2Byte" RequestID="00" RequestID2="01" Eval="0.3125x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" ScalingFactor="1" Notes=""/>

MUT table address (from ECUflash XML): 38158

tephra

iTrader: (6)

that should work.

screenshot of the mut-table?

Ted B

iTrader: (6)

It's too big to get a clear shot at <100kb. Give me a region.

Ted B

iTrader: (6)

tephra

iTrader: (6)

in that picture MUT00 = 888F not 895C.

how did you set MUT00/01 to 2byte load?