ECUflash Evoscan Basics

[woodnbronze24]

Well, thanks to some help on here I finally got evoscan working on my 95. I was advised to download v2.5 and that worked for me.

So I'm connected and I'm getting readings and about 8 samples/sec with my vag-com cable.... I don't know a ton about logging, especially with evoscan. So what should I do to get going? What should I monitor to make sure my fuel, timing, knock etc is where it should be for my current set up?:

Stock motor
E316g
Rewired evo 8 fuel pump
fmic
(other bolt ons listed in my profile)

I think my goal for now would be to find a boost level that doesn't make me too rich or lean until I get some 650s and fuel control as well as a wideband O2 and to be able to use this program well enough so when I get my tuning parts, I will know what the hell I'm doing.

Any tips on base numbers or anything else about mapping, graphing, logging etc would be greatly appreciated.

 

[jjgrizz73]

Best thing to do is select everything useful in evoscan and do a few good 3rd gear pulls and the cruising. Since you dont have a wideband moniter your knock closely but before you can even really do anything you're going to NEED a WB as well as the SAFC if you plan on larger injectors. Then you can start kicking up the boost and recording the RPM/AFRs to give you a nice tune to w/e boost you plan on running stock motor E3 with 93 octane can bring up into the 20s but its better to start out alittle rich and lean it out.

 

[woodnbronze24]

Im just not sure how to view the graphs of my logs and compare things like rpm and knock. Using the playback feature at 8 samples/second seems like its missing a lot of info from the sensors. The numbers take large leaps and are odd to try to compare that way.

 

[jjgrizz73]

When you are in evoscan, go to Logging > Open File in Graph. Then u can select w/e you want and look at say knock and RPM in the same graph to show you where you have knock when you have the WB you can compare the AFRs

 

[casperfast]

Well, thanks to some help on here I finally got evoscan working on my 95. I was advised to download v2.5 and that worked for me.

no prob its not difficult, just open the program and start playing

 

[the_mork]

The fewer items you log the more samples you will receive. Start with load, RPM, and knock count. It is worth noting that the request for knock count is different from a 2g to an evo so you will need to look up what the knock count request is. I think Knockgoon may be the person who originally noticed this so look for posts about evoscan from him.

 

[woodnbronze24]

I just changed the ID for knocksum to 3E as stated in the post. Thanks for that.

 

[casperfast]

as did i, thanks for that info

 

[woodnbronze24]

How do you check trouble codes and CELs?

 

[knochgoon24]

The fewer items you log the more samples you will receive. Start with load, RPM, and knock count. It is worth noting that the request for knock count is different from a 2g to an evo so you will need to look up what the knock count request is. I think Knockgoon may be the person who originally noticed this so look for posts about evoscan from him.

I didn't notice it. I was just the one that made a big deal about it once I was told.

How do you check trouble codes and CELs?

There's a button. Bottom right corner of the program. "Display DTC"
I can't remember if v2.5 has option to select which ecu to scan for DTC. If it does, make sure "OBDII EFI" is selected.

8 samples per second? Ouch. Is that logging via MUTII or OBDII? Try both options and see which gives you the better result.

To get the absolute fastest readings, turn off logging to screen, don't show a realtime graph, and don't use the custom gauge displays. 8 samples/sec almost isn't even worth it.

 

[the_mork]

I would be almost certain that that is logging MUT over OBD2. Its just life and its what people have dealt with in 2gs for years, we're just spoiled ever since somebody developed a true MUT logger and it just happened that 2gbs could use it properly and we're even more spoiled with the evo8 ecu.

 

[jeff24680]

Here is a link to some quick info on how I obtained my CEL codes by trial and error.

http://www.dsmtuners.com/forums/newbie-forum/352607-many-error-codes-log.html

 

[woodnbronze24]

Thanks. Are there any good maps out there that I can compare my numbers to so I get an idea of what is off and where these values need to be? ie timing advance etc.

Well I did a log...

3E as a request ID doesnt seem to be working. Im only getting single knock counts at 6500 rpms as well as my timing advancing to 38 degrees! What the heck is that all about? Bad front O2 sensor? Also, the program wont connect when I try to read my trouble codes...

 

[Ceddy]

thanks. Are there any good maps out there that i can compare my numbers to so i get an idea of what is off and where these values need to be? Ie timing advance etc.

Well i did a log...

3e as a request id doesnt seem to be working. Im only getting single knock counts at 6500 rpms as well as my timing advancing to 38 degrees! What the heck is that all about? Bad front o2 sensor? Also, the program wont connect when i try to read my trouble codes...

95-96 Ignition Map

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

38* at 6500 rpms is normal if you are still in vacuum.

Make sure the DTC tab is set to OBD2 not MUT, sometimes I need to try two or three times in a row for it to connect.