Nevermind, I realized you can change the formula in Evoscan.

 

I ordered mine Monday and got it in Today. Already installed it and made the changes. Total process took less then 30 minutes.

time to go do some logging to see how it compares to my ZT-2 boost.

 

Sorry for the newb question, but what does the EGR test do? Is it ok to leave it enabled rather then disabling it?

Thanks

 

Its supposed to test whether the EGR system is working properly. Its up to you whether you disable it. I would expect that some emissions test stations expect to see an EGR system test, so it should be enabled for those tests.

 

Great thread! Are these instructions for a specific version of ECUFlash or should they work with any of them? It didn't say in the first post. Also, I've seen that the latest version of ECUFlash is v1.34, but many people still seem to prefer v1.29a as the most dependable? Lastly, if v1.29a is the way to go, where can I get it? I checked the OpenECU site and AktiveMatrix, but neither have anything but the most recent version. Thanks!

 

I have 1.34 and it worked with no problem.

 

v1.34 is fine if you can get it to work with your cable. Some people are having problems with older cables working with newer versions of ECUFlash. ECUFlash will only work with genuine Tactrix cables. At least one batch of genuine cables were not setup with a proper internal ID, and they are not recognized by newer versions of ECUFlash. There is a software fix available from Tactrix. For the rest of the people who don't have a genuine cable, its ECUFlash v1.29a:

ftp://se30.dyndns.org/evo/

login: guest
pass: monster

 

I got it to work with v1.29a. The strange thing is that while I got logging to work, I somehow broke my boost control ... it used to boost 25 psi and taper to 24 at redline; after installing the JDM MAP sensor and flashing the ECU with the modified ROM, I can't get over 12 psi, both according to the log and my boost gauge, and of course the car feels like a wet rag. I don't know if the problem is software or hardware yet. I'll try to do a leak check tomorrow to rule out hardware for starters.

 

Very odd. The area of the code that I modify to log boost has nothing to do with the boost control code.

 

I spent all day looking for boost leaks but did not find anything. Finally I gave up, installed the original MAP sensor, and flashed it back to the ROM before the install. No change (still no boost) ... so whatever it is, it has nothing to do with the logging mod, just seemed to have happened at the same time. I'll figure it out eventually ...

 

Do you have a CEL? If you have a CEL that trips the low-boost table, you will be restricted to 56% duty cycle or something like that, or maybe 64%, can't remember off the top of my head now.

Did you log your BWDGC?

 

what low boost table?

 

I'm pretty sure he means boost table #3 which kicks in above the BCLS.

 

But nothing todo with CEL hehe

 

No cell, I did some more logging last night and included WGDC this time. At this point my best guess is an ignition problem (I've ordered new plugs and wires) or a leak I haven't found yet. I did notice that the o-ring on the JDM MAP sensor is a little chewed up, but since swapping in the USDM one didn't make any difference I don't think that's it. Thanks for the help!