ECUflash Evoscan + 95 EPROM Ecu

[XiKeiyaZI]

So I just received Evoscan from a good friend of mine here on tuners. I've tried both 2.6 and 2.7 versions of evoscan and I keep running into the same issue. I am able to connect and log for about 1-2 seconds, and then I get an error. This is actually about what I get.

Info: Initialize Vehicle ECU...
Info: DSM Initialize...
Info: Initializing At 5 baud...
Info: Initialization Complete...
Info: DSM Connected.
Info: Connection successful...
Error: FTDI Read Error - 4
at #=qxhKYH1mFtMAh8z93zD7prqWQvv2_OfgSnHCmz2Zy3v0=.#=q4wG$BmytYsscBYbM0CQyd6dVRjbyQzgv1$pYSJHpgoA=(Int32 #=qSmYp_2_Xyy$V9QRSo0fSww==, Int32 #=qWvQwf1OY$GAyrAUDgi9A_6Fryk2D5cpro3$tGG7lzAw=)
at #=qxhKYH1mFtMAh8z93zD7prqWQvv2_OfgSnHCmz2Zy3v0=.#=qgPjsDP_xx5oij7gGqW7v3w==(Int32 #=q6DqTuA5PV1$pWADoW8iuYw==, Int32 #=q06iGv8jbiegxletYYJ2Zfprz4wFBu8dHyQ_LAuSG$kU=)
at #=qcYTi9Xx62Q46MlRsGjuPN1obrQTs8A5PdOAFjpb$dxs=.#=qcdl0rnAUma_98f$ksRzQrA==(Boolean #=qIIIQIoNWCY0W3ObcSCY5A8g48TQbJ2x4KFtJCu_3jH8=, String #=qdlx8tN28mG6zvxtZKbZXmw==, Boolean #=qHDhEvCFQv_V0O1oZAa5jUVrwieg057naUpvwjsJ9dz0=, Int32 #=qFWAUDcQAn9jFGwkqDMJZJA==)
at #=qcYTi9Xx62Q46MlRsGjuPN1obrQTs8A5PdOAFjpb$dxs=.#=qI2Bxs8jh5r0BxamKtYJJTA==()
Info: Datalogger Ended.

So it'll connect, I'll see data in the main window, and then that jumble of code will show up. Has anyone else had this issue?

BAUD was set to 10400 per what I've read on other threads and it's selected for the DSM/3000GT setup on the 1.3 Cable option.

 

[Tyeler18]

You need the 2.0 cable.

 

[rEclipserGST]

You need the 2.0 cable.

Tactrix cable correct?

 

[XiKeiyaZI]

Hm..interesting.

And yes, Tactrix Cable.

 

[Tyeler18]

Yea, for some reason my 1.3u cable works on my 98 GST even though everyone says it won't.

But it sounds like either there's something messed up in your evoscan software download, or you need the 2.0.

 

[jrohner]

You need the 2.0 cable.

No he does not. You can use the 1.3 cable or a cheap $10 vag-com cable from ebay.

I used v2.5 with my 95 ECU's, and it would occasionally disconnect, but overall worked fine (besides the ridiculously slow logging rate making it nearly useless).

Each version of evoscan seems to introduce it's own new bugs IMO; 2.7 is a joke.

 

[XiKeiyaZI]

Mind explaining what I might need to do then?

 

[jrohner]

I would find v2.5 and give that a try.

 

[XiKeiyaZI]

I've tried both 2.7 and 2.6. You think 2.5 would really make a difference?

 

[Chicken Patty]

I've tried both 2.7 and 2.6. You think 2.5 would really make a difference?

If I remember correctly v2.5 caused the same reconnect issue when I had it. But I may be wrong, give it a shot and see. Luckily my car was a 97 non eprom and worked great, logged at like 40-50FPS. EPROM cars tend to have issues logging with this software.

 

[XiKeiyaZI]

Well... damn it all.. ~__~

 

[williillii]

I used a VW scan tool on my 95 ecu. Worked better than evoscan. Even if you can get it to stay connected you will get 4-5 samples per second. Not worth it. Since you already have the cable maybe you should look into the Evo ecu swap.

 

[knochgoon24]

Honestly, at this point, if anyone is looking into the Evo ecu swap, they might as well look into just swapping to the 98/99 ecu. Ceddy has single-handedly programmed most the the Evo stuff into the 98/99 roms.

Evo Ecu's still have 3 things over the 98/99:
-Live Map (reflash on the fly)
-DMA (stupid-fast logging speeds)
-The cable is cheaper.

But put it this way, I'm thinking about swapping from the Evo 8 to the 98/99 because of a few small issues that aren't critical... just annoying.

 

[Absit]

Install 2.5 AND ECUFlash (for drivers). That should fix it.

 

[XiKeiyaZI]

I'll give the 2.5 a try. ECUflash is already installed.

I want to remind everyone that the GST is NOT a tuning car. I'm not looking for crazy tuning or anything, just basic logging abilities. The need to swap to a 98-99 or an Evo ECU is null, especially since I prefer Ostrich over anything.

 

[Absit]

Really, if you want to log, you'll need an ECU swap anyway. You're only going to see 6ish samples per second otherwise.

Have you tried contacting EvoScan support? They're very helpful.

 

[knochgoon24]

Maybe these will work?
http://www.dsmtuners.com/forums/tun.../326872-mhiscan-new-free-datalogger-dsms.html
Mut Monitor Version 2.0 Released 12/04/2009 - MyRollingRoad & South West Mitsubishi EVO Forums

You may also want to try downloading the D2XX FTDI driver from here.
http://www.ftdichip.com/Drivers/D2XX.htm

Edit: Scratch that. MHILogger was never finished for the 95-96 Ecu. And MUTMonitor is for MUT-III, so it also probably won't work.
These might though:

http://www.aktivematrix.com/forum/dload.php?action=file&file_id=27 <- Just OBD stuff
http://www.aktivematrix.com/forum/dload.php?action=file&file_id=35 <-MUT-II supported.

Links to EvoScan and ECMLink and I'd have just about every logger for the 2g all in one spot.
I don't know if you can do MUT-II though LogWorks or not.

 

[mike96]

i dont think it will log knock but have you tried using the version of evoscan to log in OBDII mode just to see what happens?

 

[XiKeiyaZI]

For the record, I'm going to try the suggested links.

As for scanning in OBDII mode, yes I have. It won't connect. When I can get it to connect through the DSM/3000GT mode, it will connect for a matter of seconds. I'm almost sure I'm simply doing something wrong.

On another note.. for the love of GOD stop suggesting that I ECU swap. That'd be a complete waste of money for absolutely nothing.

 

[knochgoon24]

You should swap to a Civic ecu and use Hondata.

Seriously, I hope you find something that will work for you.
Even the EvoScan site suggests the 10400 BAUD rate with the 95. http://www.evoscan.com/technical-vehicle-manuals/12-mitsubishi-diagnostics
Those are based on suggestions from Jeff @DSMChips. He used v2.5 when he wrote this http://www.dsmchips.com/evoscantips.html

I've also used wOBD, but that won't help you with logging knock. I don't even know if it works with the Openport 1.3U cable anyway. OBD2 Software

 

[Absit]

Did you set the data rate as suggested by EvoScan?

 

[knochgoon24]

I was talking with him on AIM last night. We pretty much exhausted all the options in EvoScan. Even changed the BAUD rate.

At this point, I'm starting to lean towards a driver issue.

 

[XiKeiyaZI]

I was talking with him on AIM last night. We pretty much exhausted all the options in EvoScan. Even changed the BAUD rate.

At this point, I'm starting to lean towards a driver issue.

That's exactly what I'm starting to think. I'll remove everything and try it once more from the top and make sure to notate everything in the hopes that it will lead to a working setup and that I'll have documentation of what I did to make it work.

 

[williillii]

I spent over 6 months screwing with the 95 ECU and Evoscan, while talking back and forth with Hamish. It is NOT designed to work with that ECU. He started to implement it but then stopped working on it from what I can tell...everyone that has that ECU is using DSMLink so it would be catering to a very small croud. Even if you can get it to work, you're going to have connectivity issues (disconnecting at 5500rpm during a pull is really annoying) and AT BEST you will be able to log 5-6 samples a second. Which is useless. You're better off with a pocketlogger.

I suggested an ECU swap because you already have the cable. So you're about $125 away from a flashable ECU. I said the EVO because you have the cable. But knochgoon24 has a point, you might find the 98/99 ECU to better suit your needs. You'd have no problem selling that cable, but the Openport 2.0 is $100 more..

And really, logging more than 5 samples a second is in no way a waste of money.


ps. Are you sure the cable is working? Confirmed on another car? Because I had a bad cable that was doing similar things to me.

 

[XiKeiyaZI]

Yes, the cable is working. Just screw the idea all together. It's lovely that software these days is catered to specific crowds and not made mass universal, and the ones that are cost $600. (Link). I'll just be more than happy driving it as-is.. socketed, with Ostrich. Feh. I get so fed up with the limitations of shit based on the amount of money that you can spend on it that it's pathetic. I mean, sure most people who have the money to spend are using Link, but where does that leave the people who aren't looking to go tune-happy, can't spare the cash, and have a 95-96 ECU? Especially Eprom? I suppose it's just "Toss it and get a new ECU! " Or " Get Link! "

That's fine. Don't need it. Thread is resolved via OP's inability to justify buying an entirely different ECU to make software work which was based around the Evo/DSM platform. The option for DSM/3000GT should be changed to 3000GT/DSM(Excluding 95 Eprom). Thanks for your time everyone, have a good evening.