The Top DSM Community on the Web

For 1990-1999 Mitsubishi Eclipse, Eagle Talon, Plymouth Laser, and Galant VR-4 Owners. Log in to remove most ads.

Please Support STM Tuned
Please Support ExtremePSI

ECUflash EvoScan and EcuFlash tuning

This site may earn a commission from merchant
affiliate links, including eBay, Amazon, and others.

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.

Just thought I should give an update as to how I solved my issue regarding AEM Wideband logging in EvoScan using Vista 32Bit edition


  1. I uninstalled all versions
  2. Installed version 2.6
  3. Updated to version 2.7 Beta 5
  4. Made sure drivers for USB 2 Serial Adapter were installed
  5. Configured COM settings based on AEM WB manual
  6. Selected COM Port and AEM WB from EvoScan drop down menus.
  7. Started logging

I also have the full release of 2.7 however I could not get it to work for me, so as of right now this is how I am currently logging. This also works with Ceddys data.xml file for the evoscan, no conflicts.


Cheers:thumb:
 
It seems I'll start repairing my '96 car soon, and since there is 1 '97 engine block that's being sold/parted out, I am starting to wonder if I should swap CAS on my car, since '96 CAS is making heavy detonation and knocking with plastic ECU.

What's involved if I'm about to replace the CAS?
 
So from what I've read, EvoScan 2.6 doesn't really work well with logging an AEM wideband. Since 2.7 doesn't have the traditional data.xml and 2.5 doesn't support the OP 2.0 cable, I'm going to wire up my AEM wideband to the rear O2 sensor.

Should I use the blue serial output wire or the white 0-5v wire? From what I've gathered, it's as simple as connecting the proper wideband wire to the correct pin on the ecu, then changing the formula for the rear O2 sensor in evoscan to reflect proper AFRs.

Can I get some input on that?

Also, simply out of curiosity. Has anyone messed with making their own gauges in EvoScan? It seems overly confusing.
 
Hubbard 0,

I will be adding support for the new EvoScan .xmls, since only the newest EvoScan 2.7 private beta supports MapTracer for the H8 DSMs. Just waiting for a public final release of EvoScan to make sure my .xml is fully compatible before I release it.

The new MapTracer is very nice, you can edit your Fuel and Timing maps in EvoScan. Just MapTrace Knock, and lower timing in the cell where knock appears.
 
Hubbard 0,

I will be adding support for the new EvoScan .xmls, since only the newest EvoScan 2.7 private beta supports MapTracer for the H8 DSMs. Just waiting for a public final release of EvoScan to make sure my .xml is fully compatible before I release it.

The new MapTracer is very nice, you can edit your Fuel and Timing maps in EvoScan. Just MapTrace Knock, and lower timing in the cell where knock appears.

Cool, I guess I'll hold out then. Any idea on a time frame for this?
 
So from what I've read, EvoScan 2.6 doesn't really work well with logging an AEM wideband. Since 2.7 doesn't have the traditional data.xml and 2.5 doesn't support the OP 2.0 cable, I'm going to wire up my AEM wideband to the rear O2 sensor.

Should I use the blue serial output wire or the white 0-5v wire? From what I've gathered, it's as simple as connecting the proper wideband wire to the correct pin on the ecu, then changing the formula for the rear O2 sensor in evoscan to reflect proper AFRs.

Can I get some input on that?

Also, simply out of curiosity. Has anyone messed with making their own gauges in EvoScan? It seems overly confusing.

Like I just mentioned Hubbard my EvoScan is logging my AEM fine.
 
Like I just mentioned Hubbard my EvoScan is logging my AEM fine.

I'm having issues with mine. It displays my wideband reading for a second or two, the freezes on that value for the rest of the log.

I thought this was odd since it used to work for me a long while back, but while searching on EvoM I read that someone is having a similar issue.

I still intend to go over my wiring again, but I like the idea of having one less cable to run to the laptop for logging/tuning.
 
Hubbard 0,

I will be adding support for the new EvoScan .xmls, since only the newest EvoScan 2.7 private beta supports MapTracer for the H8 DSMs. Just waiting for a public final release of EvoScan to make sure my .xml is fully compatible before I release it.

The new MapTracer is very nice, you can edit your Fuel and Timing maps in EvoScan. Just MapTrace Knock, and lower timing in the cell where knock appears.

Ceddy, do You know if map tracer also works on a 1G?
 
I'm having issues with mine. It displays my wideband reading for a second or two, the freezes on that value for the rest of the log.

I thought this was odd since it used to work for me a long while back, but while searching on EvoM I read that someone is having a similar issue.

I still intend to go over my wiring again, but I like the idea of having one less cable to run to the laptop for logging/tuning.

True, I just know that the digital output is much faster than the analog output which is what I believe you need to use if you wire it to you ECU.

I used to have the same problem you did but after I did what I mentioned in the above posts it now logs fine.

I believe this issue will be taken care of in the next release however your point about one less cable is good. I have my serial/usb cable router under my steering wheel behind center console and into my glove box. When I need to use it I simply open my glove box pull out the length of cable needed then close the glove box to support the cable, when I am finished I simply tuck the cable back into the glovebox.

Cheers!:thumb:
 
True, I just know that the digital output is much faster than the analog output which is what I believe you need to use if you wire it to you ECU.

I used to have the same problem you did but after I did what I mentioned in the above posts it now logs fine.

I believe this issue will be taken care of in the next release however your point about one less cable is good. I have my serial/usb cable router under my steering wheel behind center console and into my glove box. When I need to use it I simply open my glove box pull out the length of cable needed then close the glove box to support the cable, when I am finished I simply tuck the cable back into the glovebox.

Cheers!:thumb:

Ooo, I like that idea. I'll reroute mine that way when I get to it. right now it dangles by the dead pedal and taps on my shoe when I drive. Might as well run a long usb cable to the glove box for the 2.0 cable too.

As for the outputs, my main concern is if the ecu can handle a 5v signal especially if it is designed/used to a 1v signal from the stock O2 sensor.
 
Cool, I guess I'll hold out then. Any idea on a time frame for this?

v1.93 seems to have all the bugs worked out, and I have the 2.7 .xml done. Just waiting on EvoScan. May release this weekend regardless.


Ceddy, do You know if map tracer also works on a 1G?

You have no way to load the rom with a 1G.
 
Ooo, I like that idea. I'll reroute mine that way when I get to it. right now it dangles by the dead pedal and taps on my shoe when I drive. Might as well run a long usb cable to the glove box for the 2.0 cable too.

As for the outputs, my main concern is if the ecu can handle a 5v signal especially if it is designed/used to a 1v signal from the stock O2 sensor.

I routed mine into my center console compartment and I like it like that.
 
You have no way to load the rom with a 1G.

Don't get what Tou mean. :coy:
I know You can't flash the ecu with the openport cable like late 2Gs but for map trace is it a requirement?
I use an ostrich if that does help, isn't quite similar to flashing the 2G ecu?
 
It has nothing to do with the ecu. He means that maptracer would be useless for a 1g ecu because you can't load the rom into evoscan. Without being able to load the rom into evoscan evoscan can't populate the load and RPM rows so you would get some fairly meaningless maptraces. The only possible solution would be to use a evo or H8 rom and rescale the timing/fuel tables to what the 1g scaling is assuming you're using a burned chip and not something that would not at all benefit from this sort of tool such as an SAFC.
 
By ROM You mean the eprom code?
I have the .BIN files I'm using on the ostrich so I could load them to the program if that's the case.
And yes, no SAFC, just custom ECU code.
With a regular logger (MMCD for PALM for example) I can log RPM, Load row position, timing and AFR (wideband atached to EGR-T input).

So with all this data available I don't see why wouldn't be possible to fill the tables easily.
What do You guys think?
 
It wont support your .bin file without a fair amount of work. You may be able to create a definitions file for it if you know the addresses of your timing and fuel maps but I think it would be easier just to create a definition file from an evo or 2gb that matches your scaling and just ignore the extra rows. Whenever I've seen a 1g map the load columns don't correspond to how they are displayed with the newer ecus but I imagine that is likely just a matter of the displayed numbers (x100 IIRC) so it would work that way. Evoscan then wont display your map below the maptracer but having dealt with Tephra roms that weren't immediately supported by evoscan I can assure you that that is no big deal so if you want to do it then go ahead, it should work with some cobbling.
 
Ok, I'll play with it a bit and see if I can make it work.
Thanks a lot.
 
Hi all,

Recently installed Aeromotive FPR set to 43psi with vacuum line disconnected after warming up the car. Supra pump. and EVO III Intake manifold with a 1g TB with and ISC and TPS from a 2g.

Problem:

Before the installation when cruising and IN gear, when I would let off the throttle it would cut fuel to the injectors and my WB would go all the way past 18. This is fine as this was a feature included to save gas.

Now after my installations it does not do this. In fact when I let off throttle it goes rich to about 11 until I press the throttle again. This is regular driving not in boost. Idle AFRS are fine 14.7 cruise AFRS are fine 14.7.

My first thought is possible a TPS problem maybe it is not sensing the throttle closed, however in evoscan it shows the throttle at 9% when I have my foot off of it(previously showed 12% on old IM and TB).

Slight idle surge and sometimes it even stalls when I take it out of gear. I would just like to know if there is something else that controls injector cut off when you have your foot OFF the throttle. If not I will try adjusting my TPS


I have included a log. It is saved a a word document because you cannot post excel docs. Change the format to .csv after you have downloaded it.
 

Attachments

  • EvoScanDataLog_2010.09.15_18.49.57.doc
    155.9 KB · Views: 120
You have to correctly adjust the TPS as it say on the DSM manual. (using a feeler gauge)
I would say the problem is the internal iddle switch, on the tps itself not being correctly set.
 
Guys, anyone has the EvoScan 2.7? I got e-mail for upgrading, but I cannot log on to their download site :( Their support hasn't replied for a week now :(

Can anybody send me the installation version. I got my serial and everything...
 
Guys, anyone has the EvoScan 2.7? I got e-mail for upgrading, but I cannot log on to their download site :( Their support hasn't replied for a week now :(

Can anybody send me the installation version. I got my serial and everything...

You have to register to their site to be able to download it. Even if You already have an user and serial for the program.
 
I did this. Nomatter what I do I cannot log in. I also tried the forgotten password option and when trying to post the token they send I just get "expired token" message...
 
Support Vendors who Support the DSM Community
Boosted Fabrication ECM Tuning ExtremePSI Fuel Injector Clinic Innovation Products Jacks Transmissions JNZ Tuning Kiggly Racing Morrison Fabrications MyMitsubishiStore.com RixRacing RockAuto RTM Racing STM Tuned

Latest posts

Build Thread Updates

Vendor Updates

Latest Classifieds

Back
Top