So who wants their ECU's "Chromed"?

[GTWHOA]

I'm sitting at the 20psi mark on e85 and it's smooth as silk up top. Haven't touched the timing yet. What numbers should I see for 2byte load logging I'm used to load figures that correspond to the timing and fuel maps.

[Greg E]

They do correspond to the load and timing maps. The number you see in evoscan is the number the ecu is looking up in the axis.

With 9Bs pushing 16psi on a stock car, I see 210ish engine loads.

I remember Brett's car with 19Ts at 20psi peaked around 265 load. That ca put down 375ish on the Dyno.

Toni car was only seeing 190 load when it put down 425 on the Dyno. That tells me the MAFT numbers are waaaay off. Still was able to tune for it though.

[Stealth_RT]

Eventually, this setup will be on my car using billet DR650s, 264 cams, stage 2 heads, etc., with the MAFT Pro setup running speed density. Who know what load numbers it'll be seeing, lol. Maybe someday, we'll be able to do speed density w/o a MAFT Pro piggyback.

[GTWHOA]

They do correspond to the load and timing maps. The number you see in evoscan is the number the ecu is looking up in the axis.

With 9Bs pushing 16psi on a stock car, I see 210ish engine loads.

I remember Brett's car with 19Ts at 20psi peaked around 265 load. That ca put down 375ish on the Dyno.

Toni car was only seeing 190 load when it put down 425 on the Dyno. That tells me the MAFT numbers are waaaay off. Still was able to tune for it though.

I must have missed something my 2 byte load values are up around 7000 lol. Yes I have the correct version of ES and the datafile. I don't want to put any more time into this version though knowing the release is just around the corner.

[Greg E]

What's the address of inside MUT00 and MUT01 in the file flashed to your car?

Also, what's the evoscan scaling for 2byte load.

[VR4GUY]

Tactrix cable is on it's way, evoscan and ecu flash have been installed. Is there a working link around for the latest chrome version? also should I be using evoscan 2.6 or 2.9 at this point? Can't wait to start learning and playing with this myself.

[Greg E]

I'll send you the latest chrome v2 XML so you can play with your tune.

Use evoscan 2.6 for now. I'm working on getting the 2.9 done by the end of next week.

[fridayda13th]

If you need anything tested out, I can help. I have a 93 stealth 98ecu. Installing my wideband and lcd this weekend. Just pm me and ill send you my number.

[JonB]

Ok so I have spent the last 2 1/2 days reading this thread from start to finish! I think my brain is mush now!

I bought a 98 sl ecu and harness form blackstealth over the winter and installed it on my 92 Stealth TT along with:

AEM FPR
EVO 560 injectors (actually flow closer to 600)
Walboro 255 and hotwire
new plugs, etc.
as well as some other odds and ends

Car also has:
15G turbos
MBC
AEM UEGO
AEM Boost Gauge

Now since installing it I have been fighting with it trying to get all the CELs to go out. After reading the thread I am going to try Adam's peripheral setup and see if that does the trick. I think I have the chrome V1.0 for ECUflash and am eagerly awaiting V2.0! Now I know I don't have the file for EVOscan so I will need to do that. I have been using V2.7. Can I use the chrome file with this version or do I need to go V2.6? I am using windows 7 so I will probably have to do a re-install under a different folder as stated in the thread.
My next question is about the CAS lag time on the first gens. I need to adjust my timing map to compensate for this?
I was kind of wondering if Greg would be willing to do me a quick tune for my setup and I can tweak it from there. I would be willing to make a separate donation for this
I am new to tuning and am learning lots and lots over the last couple of weeks! You guys have done an amazing job on this!

Thanks!

[Monster Stealth]

I have the correct version of ES and the datafile.

Where did you install Evoscan? If you are under Vista or 7 and installed to the "Program Files" directory, user account control locks down the files in that folder. Long story short, even if you have your data.xml in the correct folder, Evoscan will not read it and defaults to something else. Always install Evoscan to the root of the drive (ala C.