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?

 

[interex]

does EvoScan allow you to manually set values and tune the ecm/car ? I have a KeyDiver3 here I bought off a kid but dont know anything about it either. . I'd be interested in EvoScan if it did anything like DSMLink does.

 

[VPrime]

does EvoScan allow you to manually set values and tune the ecm/car ? I have a KeyDiver3 here I bought off a kid but dont know anything about it either. . I'd be interested in EvoScan if it did anything like DSMLink does.

No, its strictly a logger.

 

[oh_what_up]

thats what I'm trying to say. v2.3 does work. I'm running it right now with my 95 eprom ecu. So if you guys are still interested I'd definately recommend it.

 

[ferruchnuts44]

You still get the same cable from them right? then just download the new version from them? Damn I might be ordering up my cable asap.

 

[interex]

This seems like a total waste really. Why waste the money for all this just to "log" ? You can buy OBD/II diagnostic readers and loggers on ebay for cheap. And I've already shown how to MAKE that cable so you can easily make it and use it instead of paying for one that is $90+ and plus the wait time. I saw a "not so bad" OBDII datalogger by googling and says to work with all OBDII ECM/ECU Systems. It was only $65

 

[mikyrc]

How many of those let you read knock and IPW and much more on 2G's?
And also how many of those using just ONE software (and 2 differen cables of course) do work either with 1G's and 2G's?

That's the good thing with that software.

 

[interex]

It isnt worth it to me really. I think it would be easier to just make the cable yourself just to "LOG" But if you have money to just throw away thats cool too

 

[logic]

EvoScan's real claim to fame is that it's a MUT-III logger on supported vehicles (Multi-Use Tool, Mitsubishi's protocol for doing anything interesting with their late model ECUs; the fact that it operates via a physical ISO 9141-2 interface is an implementation detail, much like Subaru's SSM). That fact gives you the ability to log arbitrary memory locations (and do so at a higher data rate, at least compared to OBD-II), if you combine it with some basic reflashing and a little knowledge. On my Evo, EvoScan or Mitsulogger are pretty much indispensable tools in combination with something like EcuFlash. Actually, I'd expect Mitsulogger ought to work on a 95-99 DSM, although I've never tried it. (And it's tough to beat free, plus the cost of a cable.)

It looks like the 1999 ECUs can also be reflashed via MUT-III (EcuFlash reports support for the EM2364 ECU ID, which the XML description claims is a 1999; I haven't tested with the '99 ECU I have on the shelf, so I can't confirm that). However: there's no table data defined in EcuFlash's definition for it, so you'd have to figure that part out yourself. I'd guess that 1997 through 1999 ECUs should be able to be modified in this manner (or you could use an EPROM 1995 ECU and flash it yourself with a Willem burner or something similar). See the DSM-ECU mailing list archives for most of the public (and usually closely-held) information about the 2g ECU ROM layout.

Personally, on my 2g I'll stick with DSMLink. But I'm generally happy to hack our 1g and Evo myself.

 

[interex]

I'm going to use KeyDiver for now till I can afford DSMLink. With the cost of this 4088 or equivalent I'll hold off on the DSMLink

 

[skyrone]

so would there be anyway to have a cable that would work for dsmlink and evoscan??

 

[VPrime]

Why would you want to do that?
If you have DSMlink it can do every thing evoscan can do (logging wise + tune) so why bother with evoscan at all?

 

[interex]

exactly

 

[PieEyedPiper]

EvoScan's real claim to fame is that it's a MUT-III logger on supported vehicles (Multi-Use Tool, Mitsubishi's protocol for doing anything interesting with their late model ECUs; the fact that it operates via a physical ISO 9141-2 interface is an implementation detail, much like Subaru's SSM). That fact gives you the ability to log arbitrary memory locations (and do so at a higher data rate, at least compared to OBD-II), if you combine it with some basic reflashing and a little knowledge. On my Evo, EvoScan or Mitsulogger are pretty much indispensable tools in combination with something like EcuFlash. Actually, I'd expect Mitsulogger ought to work on a 95-99 DSM, although I've never tried it. (And it's tough to beat free, plus the cost of a cable.)

It looks like the 1999 ECUs can also be reflashed via MUT-III (EcuFlash reports support for the EM2364 ECU ID, which the XML description claims is a 1999; I haven't tested with the '99 ECU I have on the shelf, so I can't confirm that). However: there's no table data defined in EcuFlash's definition for it, so you'd have to figure that part out yourself. I'd guess that 1997 through 1999 ECUs should be able to be modified in this manner (or you could use an EPROM 1995 ECU and flash it yourself with a Willem burner or something similar). See the DSM-ECU mailing list archives for most of the public (and usually closely-held) information about the 2g ECU ROM layout.

Personally, on my 2g I'll stick with DSMLink. But I'm generally happy to hack our 1g and Evo myself.

I'm itching to see if ECUflash works with the 98-99 ECU's, if thats the case I'll buy both EvoScan and ECUFlash on the spot.

 

[VPrime]

ECU flash (Or was it openECU..) can read the 98/99 ECU but cant write to it.
This a thread about it on dsmtalk.

 

[98GSXtreme07]

Ah, I love v2.3! I had a intercooler pipe blow off and had to drive 15 mph, b/c thats all my car could do, making me run rich for about a mile. Well later that night a CEL comes on. When I get back from the movies I loaded up EvoScan and it was able to pull the code P0170 code. Just so happens I have a brand new 02 sensor from the wrecked car and after some heavy wrenching the new 02 sensor was on and the CEL was off. Of course I could have just gone to Autozone but I love the fact I can check CEL's myself!

 

[mnetwork]

You can do this with DSMLink and a pocket logger as well... I just love the fact that you can log knock, but I just decided today to ditch the S-AFC2 and buy DSMLink so I guess I'll never get to use this app....

 

[soldave]

You can set up gauges (and make your own too) so that they can be used to display perameters in real time. Or you can graph in real time also. Both of which can be used to replay your logs. No it doesn actually detect knock. Only DSMLINK can do that. But it is a good alternative. The only problems I have had with it is my sample rates were slow. About 4 per second sampling 15 data items. I thought it was because of the laptop (p3 600) so I switched to my main laptop (core 2 duo t7700 (2.4)) it was the same. I think it was because of vista ultimate. I bought another laptop ( p4 2.4ghz) and using a keyspan multiport adapter and sampling all available data items and I get 8 samples per second. So Im going to trim some of the fat and see what sample rat i get. I emailed them about the issue and they were stumped. They said I should be getting somewhere around 70 - 80. Im going to play with the serial port settings to see if I can speed things up. Anyone else running evoscan with higher sampleratee then me please chime in.

So by that are you saying that Pocketlogger can't log knock also?

 

[VPrime]

Not for a 2G.

 

[soldave]

My situation is a little different from most of yours, in that I own an Evo 1. But my Pocketlogger is giving me knock counts which seem to increase and decrease with tuning. Should I take it from that that the knock logging on Pocketlogger is working?

Sorry for what might be a dumb questionn; am just trying to work out if it would be worth going from Pocketlogger to Evoscan.

 

[blackrosenova40]

How many of those let you read knock and IPW and much more on 2G's?
And also how many of those using just ONE software (and 2 differen cables of course) do work either with 1G's and 2G's?

That's the good thing with that software.

Have you logged with evoscan on your 1g yet mikyrc. I have and my timing advance logged reads very low and a bunch of other things seem to be off like coolant temp.

If you notice, evoscans equation for timing advance is differant then mmcd's

http://mmcdlogger.sourceforge.net/#Protocol

Timing Advance 0x06 x - 10=deg

Ive changed it to this, if I remember correctly evoscans stock equation was x-20=deg and I think that it is wrong.

 

[mikyrc]

Not yet sorry. Just after i got the evoscan and did the connection test I started the rebuilding process of the engine and tranny. So 'till I have the car back running I can't test it.

 

[Fox1486]

EvoScan's real claim to fame is that it's a MUT-III logger on supported vehicles (Multi-Use Tool, Mitsubishi's protocol for doing anything interesting with their late model ECUs; the fact that it operates via a physical ISO 9141-2 interface is an implementation detail, much like Subaru's SSM). That fact gives you the ability to log arbitrary memory locations (and do so at a higher data rate, at least compared to OBD-II), if you combine it with some basic reflashing and a little knowledge. On my Evo, EvoScan or Mitsulogger are pretty much indispensable tools in combination with something like EcuFlash. Actually, I'd expect Mitsulogger ought to work on a 95-99 DSM, although I've never tried it. (And it's tough to beat free, plus the cost of a cable.)

It looks like the 1999 ECUs can also be reflashed via MUT-III (EcuFlash reports support for the EM2364 ECU ID, which the XML description claims is a 1999; I haven't tested with the '99 ECU I have on the shelf, so I can't confirm that). However: there's no table data defined in EcuFlash's definition for it, so you'd have to figure that part out yourself. I'd guess that 1997 through 1999 ECUs should be able to be modified in this manner (or you could use an EPROM 1995 ECU and flash it yourself with a Willem burner or something similar). See the DSM-ECU mailing list archives for most of the public (and usually closely-held) information about the 2g ECU ROM layout.

Personally, on my 2g I'll stick with DSMLink. But I'm generally happy to hack our 1g and Evo myself.

Honestly, I own a 99 and would be willing to help out in any way possible to make the ECU flashable. I know there have been discussion on openecu and dsmtalk about it. They are getting closer. My 99 is my DD but if all that's needed is to send a copy of the stock image I would be more than willing to send it to someone. Anymore info would be great. I feel as though ecuflash may be closer to reflashing these than the evoscan is.

 

[98GSXtreme07]

Yay! v2.3 is out!

 

[VPrime]

Yup got the email as well..... bah I want my car to run to test it!

 

[joyfil2001]

it works i tested it on my 95. its really slow for me though. any one else try it?