MHIScan: New free DataLogger for DSMs

[logic]

Ceddy, since you've stopped development on MHIScan (and for good reason, you've obviously got more interesting stuff going on with the later H8 ECUs), would you be willing to do a release of the source for v3 (or whatever intermediate state the code is in at this point), so that someone else could step up and continue work?

(You never know until you ask. At the very least, it would be a shame to see the effort you put into working out the hybrid protocol stuff disappear.)

 

[Ceddy]

Ceddy, since you've stopped development on MHIScan (and for good reason, you've obviously got more interesting stuff going on with the later H8 ECUs), would you be willing to do a release of the source for v3 (or whatever intermediate state the code is in at this point), so that someone else could step up and continue work?

(You never know until you ask. At the very least, it would be a shame to see the effort you put into working out the hybrid protocol stuff disappear.)

The Hybrid Protocol or MUT over OBD, is an extension of the OBD2 protocol.

It uses the standard ISO OBD2 Init sequence, but instead of the 1-10 OBD modes it uses mode A0. Then it does a MUT Table Lookup using using the OBD RX and TX sequences.

Because it uses the OBD2 pause between bytes and pauses between messages its limited to about 10 samples per second.

If someone was interested in continuing the project I would share my source, but I wouldn't call my code clean.

 

[logic]

Because it uses the OBD2 pause between bytes and pauses between messages its limited to about 10 samples per second.

Ew. Suddenly, the aversion to MUT-over-OBDII is very clear to me, and I see why a replacement protocol was such a high priority for Tom and Dave.

Is that seriously how a MUT tool talks to those ECUs? What a shame. Do you know offhand if the H8 ECUs support hybrid mode (or a variation of it)?

If someone was interested in continuing the project I would share my source, but I wouldn't call my code clean.

I don't think anyone has any misconceptions about code cleanliness; everyone who does these kinds of projects does them as a side thing, and "doing it the right way" is always a feature for the next version.

(You should see what my hacky SH2 disassembler looks like right now; your head would explode. But as soon as I've got it tracking register JSRs properly and producing output that can be fed to gas, it's getting released. )

 

[Ceddy]

Ew. Suddenly, the aversion to MUT-over-OBDII is very clear to me, and I see why a replacement protocol was such a high priority for Tom and Dave.

Is that seriously how a MUT tool talks to those ECUs? What a shame. Do you know offhand if the H8 ECUs support hybrid mode (or a variation of it)?

The DSM H8s support:
OBD2,
Hybrid: MUT over OBD2
and MUT3.


They also have:
1953 baud setting like the 1G ALDL protocol,
and 62500 baud like CAN.

I'm not sure if these are ever used, they might be part of a generic serial communications library or something.

 

[logic]

I knew they'd do MUT-III, just wasn't sure about the hybrid protocol; thanks for confirming! It means my '99 ECU might work for some testing if I get motivated enough to get a bench configuration set up. (Winter is coming, and I'm not going to be sitting in the Evo just to test comms and code changes. )

 

[95Eclipse]

I know that Ceddy has moved on to new plans. But can somebody that got their MHIScan working help me get mine running. I'm trying to do it myself but I don't know how...
I Downloaded the MHIScan and also the .Net framework file and got the MHIScan opening on my computer, I got the blue Ebay cable Ceddy mentions. But I don't know hot to incorporate it to the MHIScan. He says to install a driver, That's where I got lost I didn't know how to do that.

Can somebody show me how to do that with a little more details, am I supposed to go to the Ross-tech web site and download a specific file too?

Thanks for the help. I really want to give this logger a try.

 

[Hubbard 0]

If you guys are looking for another free logger for mitsus, then get MitsuLogger.

It's setup for Evo's but I've used it numerous times. One thing you will want to change is the knock address, which should be 38 on a DSM.

 

[SpawnedX]

Does anyone have a version of this software they can send me? [email protected]

I am in the midst of writing my own logger for 2Gs both 4G63 and 4G64 motors as well as adding native support for 420As going forward.

I would love if the OP could just send me his files and I will just take the project from there, but I will settle for a copy of this software to try out. I am new to OBD2 programming so could use a good example of a VB built one.

 

[jeffo]

He says to install a driver, That's where I got lost I didn't know how to do that.

Did you download the FTDI v2.0 driver for the cable:
FTD Inc. | Home
Ceddy's program only works right now with the 1997+ 2G ECU's.
For the 1995/96 ECU's I recommend EVOSCAN:
http://www.limitless.co.nz/EvoScan/