(((Mitsubishi MUT-II/MUT-III Datalogger)))

[markoverclock]

Originally Posted by SeekNStrike

my shit does not work. He said he is working on it about a month ago.

what yr is your car?

[markoverclock]

does anyone have the 2.2 v i have the 2.1 and would like to try out the 2.2 so if anyone is beta testing let me know by via pm.

would like to see if it fix something.

[SeekNStrike]

Originally Posted by markoverclock

what yr is your car?

96

[tfw a-ok]

Originally Posted by SeekNStrike

96

There's a known problem with '96 (myself included) as the first year of OBDII mitsubishi's MUT version was a little "different" than the other years. This according to the developer affects some '95 cars as well.

[jba3]

Originally Posted by maddux317

Went back to 2.0 and it works...... this is some really buggy software either way, it locks up pretty often (using Vista... what a POS OS). 2.1 didn't work at all. It was connecting with the ECU and receiving data, but it wasn't doing the conversion to give me readings...... When using 2.0 the baud rate somehow set itself to 0 and that had me messed up for a while trying to figure that out. I set it to 15525 or something along those lines and its working pretty decently....... now just to figure out why I'm having to use 0 correction on my afc with 550cc injectors to get .94-.96v at WOT lol.

On another note, when you guys have this cable connected do your door locks randomly lock then unlock themselves?

I've had issues with it under Vista. Lots of issues, but also with Vista in general. I "downgraded" to XP. No issues, 2+ months without a single lock-up. However, that's using the same app on my evo.

Originally Posted by ideffect

So, will this product work properly for a 95 Hybrid ECU (specifically my 95 Stealth TT)? It seems like it will and is the correct cable the "16pin SSMII/MUTII/OBDII+12pin Evo Reflash Connector"? It looks like a very impressive tool!
Thanks you.

I was not able to get it to read my 95, but I emailed the author and he said it's an issue with my cable. The cable/software works on my evo just fine, but not on my 95 spyder. I had a friend try his copy of evoscan and his cable, with no luck either. I believe there are specific cables you need for the hybrid ECU, not just a standard tactrix? Can anyone with it working on a 95 confirm this?

[Hannibalzero]

Maddux/jba - did you try changing the properties of the executable so that it runs in XP compatibility mode? Also, did you try running the application as the administrator to see if the problems continued?

[jba3]

Originally Posted by Hannibalzero

Maddux/jba - did you try changing the properties of the executable so that it runs in XP compatibility mode? Also, did you try running the application as the administrator to see if the problems continued?

Nah, this was on my old laptop under XP natively. Also running as administrator. Same thing on my friend's laptop. Hamish (the writer of evoscan) said people have it working on the 95s, but they use the home-made cables.

[mikesx4911]

But overall the HHH is better than than this one right?

[Hannibalzero]

Originally Posted by mikesx4911

But overall the HHH is better than than this one right?

It depends. If it will read knock, I'd say this will better for anyone with an OBDII car, even if some of the other features don't work.

[mikesx4911]

Wow I just noticed that the HHH is like 63 buxs US money, that seems like a lot this is only 25 buxs haha. Im gonna give this thing a try