knochgoon24
DSM Wiseman
- 6,135
- 97
- Jan 29, 2008
-
Troy,
Michigan
So what makes it only for on 98-99? I'd go out and test it now on my 97, but the weather here absolutely stinks right now. Ice/snow mix... 

Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
For 1990-1999 Mitsubishi Eclipse, Eagle Talon, Plymouth Laser, and Galant VR-4 Owners. This is where the DSM platform history is documented and archived. Log in to help us in our mission, and to remove most ads from the browsing experience.
This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.

Definitely. I've tested your software with a '98 ECU already and it works fine.
FWIW, ECMLink uses 15625 baud as well for both the 1G and 2G ECUs. So I definitely know it works. And, yes, we use the FTDI 232R chipset.
BTW, if you have *any* interest at all in adding MUTT support to the ECMLink application instead of writing a new one from scratch, let me know. It will eventually be added to ECMLink anyway as a free download, but if someone else is already deep into it, might as well share the burden. We've got the graphing and data management pieces covered already. You would just need to add the communications layer.
Thomas Dorris
So what makes it only for on 98-99? I'd go out and test it now on my 97, but the weather here absolutely stinks right now. Ice/snow mix...
Would this support the 420a motor?
95-97 use a slightly different protocol and init sequence than 98-99.
98-99 use "true" MUT like the EVOs.
95-97 use "hybrid" protocol and have a lot of extra bytes in their requests and replys, like OBD2. Thats why the 95-97 have sample rate similar to OBD2 rates.

So basically what this tells me is that when you do get it working for the 95-97 Ecu's it will be just as slow as EVOSCAN? If that is the case I wouldnt even bother with doing all of the work. Evoscan is so slow with my 95 ECU that it is useless for tuning
I use EvoScan on my car right now. It's a 97 Eagle Talon Tsi AWD with a 4/97 build date, and I can log ~80 sample per second with it in Mitsubishi mode, not the hybrid mode. That's plenty to tune with. If it works in Mitsubishi mode, it should work with your program? Right?
I'll try to try your software out on my car later.
Do you happen to know your ECU's case Id? MD326328 would be a 97 AWD.
I'm not sure when they switched protocols, and I don't own any 97 ECUs.
I'd be interested to know if it works with your 97.
I have a 98 ecu that can do all three protocols; MUT, Hybrid and OBD2.

I noted you could output to XML, but a normal .txt file would work fine. Just make a data stream that dumps it all (neatly) into a file. Make it so that every time your start a new data log, it makes a new file. Just name it the current time and date. EvoScan does it this way and it's convenient.when are you going to have it working for us 95 eprom guys i need a logger bad..........also would you know what needs to be done to get evoscan v2.5 to connect......... i am running a elm323 cable through a serial convertor !
I am also anxious for you to say you finally got it working for poor "fogotten" us '95 guys. When do you think you will have it working for 95's or is there any hope at all? Screenshots look amazing...
+1 for us '95 guys!
I need to come up and visit you so I can look over your shoulder and see how you do this stuff.
. subscribedAny updates?