EvoScan - Does anyone use it??

[mnetwork]

I was looking at Evo tuning.. I was bored... and I stumbled across something that they use a lot as a logger. It is called EvoScan. I went on the web site: http://www.limitless.co.nz/#SupportedVehicles, and it actually says it works with our cars too and any mitsubishi up from 94 using the "MUT/MUT-II/MUT-III protocol" for the logging... This logger logs everything including knock sum.. would it be possible that because this logger uses the Mitsubishi protocol and not the generic obd protocol that it can log things that the other generic obd2 loggers can't?

 

[m_0ney_pit]

hold on, according to what I've read injector scaling should be below the injector size. The value of 513 corresponds to 560cc evo injectors so the value for scaling for our ecus should be below 450.

I currently have my value set to 412.3 but I'm not sure if this is correct.

 

[Ceddy]

m_0ney_pit the Injector Scaling value will have no effect on fuel trims.

All calculations for fuel trims are done inside the ECU which outputs a hexdecimalish number.
These values are usually multiplied by .78 to get a decimal number.

I don't know why evoscan is using the formula (0.1961*x)-25.
If your fuel trims seem wacky I would try .78*x

 

[m_0ney_pit]

I emailed evoscan support about injector scaling and they are unsure about the value for 2g dsm's.

If you want to see your OBDII fuel trims and only have a tatrix cable you can download "OBD scan tech generic" , its available on aktivematrix.com.

The good thing is that so far from what I can see, using a scaling of 410 the output fuel trims from evoscan for low and mid are in line with what OBD scan tech is giving. They are ~1% higher than OBD scan tech.

the big question to me is...if 2g's only have a stft and ltft then why is a value being retrieve for low,mid, and high trim(always appears as .180%) by evoscan which is in line with an OBDII logger?

Does this mean 2g doesn't actually have a high trim?

 

[Ceddy]

Attention 95-97 Hybrid Beta Testers Needed

I was looking at my disassembly of the 95 ECU last night and came across the logger table.
Decided to add what I could figure out to EvoScan.

So far I have found 47 new items that can be logged.

A lot of them are not that useful, like if the AC switch is on, or if the CEL is on.
But some good ones I found are:
Coil energization time, and
Injector deadtime.

If you are running a 95-97 ECU and would like to help me test these out you can download this file -> http://ceddy.us/data.xml

Then replace the file data.xml in: Program Files\EvoScan\EvoScan v2.5\DataSettings\

Be sure to make a backup of your old data.xml, in case you would like to use it again.

All of the new items I added have a _ in front of them. And have detailed info in the notes section.

If you find any items that are not working correctly, please PM or email me to keep this thread clean. I would like to compare the new KnockSum I found to the old one, and see if all other items are working correctly.

One major problem I found with EvoScan is they use one file for all the protocols, when all the protocols are not the same. For example the 1G converts Inj DeadTime at one unit = 24 uSec, and the 2G one unit = 15 uSec.

There are a total of 128 items in the 95-97 Logger Table, I hope to find them all, if you would like to help me test them it would help out a lot.

I'm not sure if these new items will work with the 98-99 ECUs, but I think most will.

 

[m_0ney_pit]

I tried the knocksum with request 3E on the 99' ecu and it returns a wide range of data. value changes from 5 counts to 45 counts. Maybe its the unfiltered signal?

Tried dead time also and the value changes with throttle position but I don't know what it means.

 

[redtsi252]

Does any body that has Evo scan had Dsmlink before?.....Im curious as to how it compare...I have a 95 eprom

 

[logic]

I've used both. EvoScan is purely a logger; it gives you a view of what the car is doing, but that's it. DSMLink gives you both a logger and the tools needed to make fuel and timing adjustments.

Basically, I view EvoScan as half of a tool. On the Evo side of the house, the other half of the tool is EcuFlash; 97-99 DSM ECUs should be reflashable via MUT (just like an Evo), but I can't say as I know if anyone has put much time into the EcuFlash definitions for them.

For DSMs, I'd still consider DSMLink far and away the superior product. On Evos, EcuFlash+EvoScan is pretty compelling.

 

[98GSXtreme07]

With EcuFlash, so far only 98-99 ECU's are "readable", meaning you can pull an image but that's as dar as it goes. Still haven't figured out if or how you can do anything with the image.

 

[m_0ney_pit]

ECUflash is grabbing the whole rom from the ecu, but it doesn't know how to display the timing/fuel maps because there is no xml definitions written that tell it what address to read when its looking at the hex file.

So to write a proper xml rommetadata file for the 98-99 ecu we need to know the adresses are for the fuel maps, timing maps ect.

I copied the data from an evo7 xml file and added it to the xml written for the 1999 gsx ecu but none of the addresses match.

 

[_Madman_]

UPDATE ON '96 ECU.

I purchased the EvoScan yesterday and today borrowed a generic OpenPort 1.3 Universal cable to try it out.

Tried to connect to my ECU and no go (EvoScan v2.5). It just retries infinitely. Tried setting longer timeouts, slower data rates, nothing.

There was kind-of-successful connection via Mitsubishi/OBDII settings, with low baud rate, but it just connected and timeouted in a timeout period. The screen goes green, voice says 'aight' and after timeout it disconnects. If I set timeout to 9999 it waits 10 seconds but doesn't log anything. I wasn't able to get any parameters at all.

Then again I have an Eclipse that is for Japanese domestic market (I got hieroglyphs all around, air filter, timing belt cover, ABS warnings etc.). And the ECU has "Enginnering sample" written on it.

I will update the status when I get the original cable with one of the pins removed.

 

[mikyrc]

Did you install ecuflash so you can install the drivers that come with it?

 

[_Madman_]

Don't know... I just ran EvoScan setup, then, after running it once to register, I started it up the second time, connected laptop to car and unknown device went up 2 times. I selected choose driver, navigated to EvoScan folder and there was a x86 and x64 drivers somwhere in the folder. I installed the correct ones and the cable was recognized as OpenPort 1.3 Universal.

I think drivers that came with EvoScan should suffice. There is a ton of tweak able parameters though, maybe they should be changed.

I will wait for the real cable and try other open source programs to connect to my ECU.

 

[_Madman_]

Does anyone have a 98/99 ECU ROM image? I would like to take a look... PM if you have.

 

[m_0ney_pit]

Does anyone have a 98/99 ECU ROM image? I would like to take a look... PM if you have.

why don't you download it from your ecu? you have the tatrix cable right, just install ecuflash.

 

[_Madman_]

No the tetrix cable is still coming from New Zealand, and it will take a whole lot of time with our Republic post offices. And as I said I have an "Engineering sample" ECU right now which can't be logged or read from. 98/99 ECU is on it's way from states and I will have to figure out how to solve CAS problems when it's here.

I had a chance to borrow a cable for a few minutes to test my ECU, but I don't have it right now.

While I'm waiting I would gladly take a look at the ROM itself.

 

[knochgoon24]

If I order a cable from evoscan, should I ask for one with no 9 pin?

EvoScan HighSpeed Mitsubishi/Subaru USB Datalogging Cable
(also known as OpenPort 1.3U or 1.3B Universal Cable)
Datalogging and ECUFlash Reprogramming Cable.
High quality and high performance 12pin + 16pin datalogger/reflash cable, capable of extreme high speeds.
Perfect for EvoScan, StiScan, EcuFlash, OBDII software.
Specifically supports 1994-2007 Mitsubishi vehicles for EFI, AYC and ABS systems. Bonus! allows reprogramming of Subaru WRX/Sti ECUs and Mitsubishi Evo factory ecus via EcuFlash (included reflash connector) Also Supports 1999-2007 Subaru SSM-II vehicles for datalogging. For Mitsubishi ABS/AYC support - put in the comments box on the next page that you want a cable without pin9.

My car has ABS. I think the AYC thing is for newer Mitsubishi cars. Does the "ABS support" offer something along the lines of disabling the ABS or what?

 

[_Madman_]

Ok, I finally got the cable, 98/99 ECU and managed to do some tougher testing.

The original ECU of my car is weird, see here -> http://www.dsmtuners.com/forums/newbie-forum/307384-injector-plug-swap.html and I was unable to connect to it whatsoever.

The 98/99 ECU is fantastic as far as logging goes, and it's super easy to work with when you use the EvoScan software.

What bugs me, though, is the values and adjusted values. You can log both of them and don't know if they are accurate and which one are correct ones. But then again, I didn't had a lot of time to test and read manuals, so that is my fault

And since I have some problems with injectors right now I will have to fix that first.

Then the not so good news.

We had a DSM club meet today, and I tried to log 95' EEPROM ECU of 2G GSX, 94' 3000 VR-4, 97' 3000 VR-4. I don't know what ECUs those cars had, but I was unable to read the DTCs with default settings on none of those cars even with CELs on. I only managed to connect to GSX and 97' VR-4, and the log graphs were basically horizontal lines with values like idle sitting at 3300 rpm while the real values were below 1000. So the older ECUs need either some adjustment or they might not work, I cannot tell you for sure as of now.

Concerning extras, they work just fine!

The cable I got is EvoScan one and you can see it in attachment. I said without pin 9 and it doesn't have one, if this is correct -> OBD Diagnostics, Inc. - OBD2 Cable

With 98/99 ECU I was able to connect to ABS extra easy, although 2 of 4 wheels were displaying weird values while standing still. 134 and 24 km/h. Then again My ABS is buggy lately with ABS light being on more often than not, so 99% that EvoScan reads everything right.

All in all, if you have 98/99 ECU, EvoScan is awesome, maybe some vales will have to be tweaked but it's super easy for logging. If you have older ECU, then I cannot say anything for sure. Maybe I'll manage to find some time for tougher testing later.

BTW, I don't know if knock count value is correct for DSMs. And yea, EvoScan has actuators to test different things like injectors and fuel pump.

 

[astanovoy]

Hi Madman,

I have JDM Eclipse 2g GST too and no problems at all with logging and diagnostics for Japaneese Eclipses and US eclipses in our local DSM Club St-Petersburg.

Try to use different protocols with Evoscan (2.5 latest version for September 08)- Mitsubishi, 1G/OBDIALDL and Hybrid DSM/3000GT/Eclipse.

One of this should work with ANY mistu ECUs supported by Evoscan, because you have right cable 1.3 Openport.

Cheers from Russian DSMers

 

[_Madman_]

Well, I got the new ECU in, and it logs incredibly fast compared to those old ones I came across. So I'm happy. Maybe I'll do some more testing with other cars later, but for now I got to get a new transmission as this one was blown during the testing of the new ECU.

Anyway, I wanted to ask how do you retrieve the .rom from 98/99 ECU. Do you need both connectors? Which ECUFlash version do you have to use, which settings?

I tried to read the .rom with just the obd2 cable and I couldn't. I had an older version of the ECUFlash, though, and it had only EVO/x/x/x/x and Subaru/x/x/x/x/x options, none of them worked.

 

[linksys42]

this video will guide you step by step.

YouTube - How-to flash your Evo ecu using ecuflash

 

[_Madman_]

That's what I tried, but I am unsure about if I need to connect the second plug somewhere and what vehicle I must choose, there wasn't DSM option on the list. All Others failed.

 

[Ceddy]

Does anyone have 97-99 ROM image they could send me?

I'd like to compare the Fuel and Timing maps to my 95.

I was playing with EcuFlash, making a definition file shouldn't be that hard.
Just the Immobilizer stuff is a little confusing, do the 97-99 even have the Immobilizer?

Anyone working on getting EcuFlash working for us?


If someone could send me their flash image, it would be much appreciated.
(email - [email protected])

Thanks.

 

[_Madman_]

Tell me how and I'll send you ROM from my 98/99 ECU.

AFAIK, they don't have immobilizers. I swapped from 96 ECU and everything works just fine (aside from the fact that my car lacks bunch of emission related equipment from factory and has 6 CELs http://www.dsmtuners.com/forums/newbie-forum/309609-ecu-going-emisson-mad.html ).

 

[Ceddy]

Tell me how and I'll send you ROM from my 98/99 ECU.

Hook both connectors on your cable up.
Turn on EcuFlash.
Do ECU->Read From ECU
Then File->Save ROM

 

[_Madman_]

Well, I tried but with no success. I used EcuFlash 1.34 or something.

Do I need to connect the white connector of Tectrix cable too? I couldn't find a socket for it.

And which car do you have to chose, it has Evo's and STI's only

I downloaded EcuFlash 1.38 today, I will try to read the ROM again tomorrow.

Which drivers did you used?