I see the same question a lot on here, "What logger should I get for my 2G?".
Thats hard to answer because there isn't really a good logger for us 2G guys.
So I decided to fix this and write my own freeware logger.
Its called MHIScan and it uses the MUT protocol.
MUT is better than OBD2 because it allows you to knock and other good stuff, and its sampling rate is ten times faster.
This is my first beta release, and right now it is only working on 98-99 cars.
If you have any feedback, or always wanted something in a logger, let me know.
For people who are looking for cables:
Tactrix no longer sells OpenPort 1.3 cables. They have switched to the 2.0 cable which uses Pass-Thru for new CAN-BUS cars.
EvoScan still sells 1.3 type cables.
ECMTuning's cable works.
DSMChips has cables. -> dsmchips.com/cables.html
I have only tested an OpenPort 1.3U cable. But any cable that can function as Virtual COM Port and supports 15625 baud will work.
This is my first beta release and it has limited functionality, some of the log items may have wrong conversions and give you bad info.
Compete correct item list will be added in the future, as well as support for more cars.
This software is freeware for personal use.
But is owned by me, that means you can't sell it or bundle it with things you sell.
Thanks for everyone's interest.
Last edited by Ceddy; 04-04-2009 at 10:14 PM.
Advertisement
To browse the forums without the advertisements above, Login/Register
Is a pocketlogger cable at all compatible with this? I did see you recommend the open port 1.3
BTW, very ambitious of you to make something like this. I hope that you get a good following from us 2g guys.
EDIT : just played around with it, I like it so far!
Im guessing since I have the 95 Eprom ECU in my 98 that it wont work. I look forward to trying it when It does. I have used evoscan but it is way to slow with that ECU to use it for tuning
Subscribed. Just keep us updated on when it will work with diffrent year ECU's. Thanks
I''m interested in this, also would like some information about what cable to use and where to get said cable?
I use the Alex PepperOBD-II stuff on customer cars right now and have been looking for something with a faster sampling rate which is my only real complaint (and lack of knock monitoring, but i always just watch timing )
I have a customer's 96 talon just waiting on some parts then a tune. It would be nice to give this a whirl on his car if it was working on those model years.
Is a pocketlogger cable at all compatible with this? I did see you recommend the open port 1.3
BTW, very ambitious of you to make something like this. I hope that you get a good following from us 2g guys.
EDIT : just played around with it, I like it so far!
Don't think the PocketLogger cable will work.
The MUT protocol uses 15625 baud, which is a odd ball speed.
Pocketlogger uses OBD2 which is 10400 baud.
Any cable that uses the FTDI chip should work, like the OpenPort 1.3.
OpenPort 2.0 won't work.
I've seen some cheap cables on ebay for VAG cars, I might order one and see if it works.
VAG use K-Line like us.
Any idea if this works on evos (or DSMs using evo ecus)? I assume that an evoscan cable will work just fine since an openport 1.3 cable will work or am I wrong? Do you need to have the second port connected or is that only for reflashing?
Otherwise I am very pleased with the idea of this even though I wont be able to play with it until spring.
I know there are some great programs out there for the 1g already. But the most used Laptop Software from TMO is really outdated and is lacking in some areas. Plus, there is no support for it anymore. It would be great once you get this ironed out for the 2g that you would think about developing a copy for the 1g cars. And while MMCD is fine, using it through a laptop blows.
____________________________
Kletke - Jackal Controlled 16g Car @ 27psi on Meth
Its called MHIScan and it uses the MUT protocol.
MUT is better than OBD2 because it allows you to knock and other good stuff, and its sampling rate is ten times faster.
This is my first beta release, and right now it is only working on 98-99 cars.
Can you clarify something for me about this?
This allows you to log knock on the 98-99 2g's and achieve a sampling rate 10x what a normal logger allows? If so, you are the effin' man!
If I'm reading this right, your logger uses the MUT-II protocol that previously only the dealers had access too?
Will your program allow you to alter settings in the ECU? I know back when I had problems with my ECU resetting all the emissions monitors I ended up having to pay the dealer an ungodly sum of money to force the monitors to set. They told me they hooked up their MUT-II and increased the sensitivity and forced them to set.
Also, do you mind this being distributed in other forums, citing you as the developer, of course?
This allows you to log knock on the 98-99 2g's and achieve a sampling rate 10x what a normal logger allows? If so, you are the effin' man!
That appears to be the case and I suspect that it will also log evo ecus beautifully if that matters. I also suspect that even if it hasn't been tested 97 ecus should be able to do some of these things too but at a lower sampling rate but the 97 ecu is kind of a bastard child so results might be iffy.
If I'm reading this right, your logger uses the MUT-II protocol that previously only the dealers had access too?
The dealers and evoscan which is certainly not free. This appears to be the first free program that can do it.
Will your program allow you to alter settings in the ECU? I know back when I had problems with my ECU resetting all the emissions monitors I ended up having to pay the dealer an ungodly sum of money to force the monitors to set. They told me they hooked up their MUT-II and increased the sensitivity and forced them to set.
As of this moment it isn't really possible. The 98/99 ecus require 16 volts applied to the reflash port in order for the ecu to go into a mode where it can be flashed. This is almost the same system as later Mitsu ecus except that the later computers generate this voltage internally whereas the H8 ecus need the full voltage supplied by the cable. We would need new hardware to be developed as well as a system to control it. Unfortunately just having new software isn't going to do the trick here.
Also, do you mind this being distributed in other forums, citing you as the developer, of course?
I just wanted to say again that I really appreciate someone putting together a project like this.
That appears to be the case and I suspect that it will also log evo ecus beautifully if that matters. I also suspect that even if it hasn't been tested 97 ecus should be able to do some of these things too but at a lower sampling rate but the 97 ecu is kind of a bastard child so results might be iffy.
That would be awesome. Hopefully Ceddy will pop in and confirm that fact.
Quote:
Originally Posted by brainlessher0
Anyone have any other sources to purchase a cable that would work with this program?
Tom with ECMTuning gave a link a couple posts up to their cables that will work with the program, unless you were looking for a different vendor.
FWIW, I always had plans to add MUTT logging and control functions to the free ECMLink software too. I just haven't gotten around to it. The software design is abstracted from the device layer. So you can basically "plug in" code for whatever device (MUTT, OBD2, ECMLink, etc.) you want to communicate with and you get the entire logging and other framework stuff for free. You basically just implement the communication layer.
And the plan is to release the source code the V3 laptop application too, but again, I just haven't gotten around to bundling that up yet.
As for the cable, $75 for a native USB OBDII cable is not a bad price... Keep in mind our cable is a nice, clean custom molded solution with full opto-isolation and all surface mount components.
FWIW, I always had plans to add MUTT logging and control functions to the free ECMLink software too. I just haven't gotten around to it. The software design is abstracted from the device layer. So you can basically "plug in" code for whatever device (MUTT, OBD2, ECMLink, etc.) you want to communicate with and you get the entire logging and other framework stuff for free. You basically just implement the communication layer.
And the plan is to release the source code the V3 laptop application too, but again, I just haven't gotten around to bundling that up yet.
As for the cable, $75 for a native USB OBDII cable is not a bad price... Keep in mind our cable is a nice, clean custom molded solution with full opto-isolation and all surface mount components.
Thomas Dorris
Does your cable use a FTDI chip? FTDIs are the only ones I found that can support 15625 baud.
Does your cable use a FTDI chip? FTDIs are the only ones I found that can support 15625 baud.
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.
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
Thats a interesting proposition. I'll have check out your software. I'll PM you.
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...
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.
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
