MHIScan: New free DataLogger for DSMs

[MY1GDSM]

I Was gonna check it out But I keep getting a "MHIScanner has encountered a problem and needs to close" message

 

[Ceddy]

I Was gonna check it out But I keep getting a "MHIScanner has encountered a problem and needs to close" message

What car was this on? Only works on 97-99 now.

Make sure requestid.xml was in same directory as MHIScanner.exe.
And that you have .NET 3.5 installed.

More informative error handling will be added in newer versions.

 

[MY1GDSM]

What car was this on? Only works on 97-99 now.

Make sure requestid.xml was in same directory as MHIScanner.exe.
And that you have .NET 3.5 installed.

More informative error handling will be added in newer versions.

I was gonna just take a look at it...I don't have a 2g

 

[jrohner]

I have completely switched to the FTDI D2XX DLL. This allows a lot more things to be done and should be a little faster. This also allows more than one FTDI cable to be plugged in, with VCP having more than one cable screwed things up.

So we can use the VAG KKL FTDI cables that are easily found for like 15 bucks? They are said to work with programs such as Evoscan & Mitsulogger.

Do you mean you could log to two separate programs or PC's at the same time just by having a Y adapter to plug two cables into the diagnostic port at the same time? That would be nice for having a screen in the car that shows some data, kind of like the screen on myrollingroad.com, and still log to your PC at the same time.

 

[Ceddy]

So we can use the VAG KKL FTDI cables that are easily found for like 15 bucks? They are said to work with programs such as Evoscan & Mitsulogger.

The cable I got was: USB Cable KKL 409.1 VW/AUDI OBD2 OBD OBDII VAG COM 409
Works perfect so far. Don't know how the chinese do it, the parts alone cost more than 30 bucks.

Do you mean you could log to two separate programs or PC's at the same time just by having a Y adapter to plug two cables into the diagnostic port at the same time? That would be nice for having a screen in the car that shows some data, kind of like the screen on myrollingroad.com, and still log to your PC at the same time.

Some new laptops don't have serial ports. So if you had a USB Diagnostics cable and a USB to Serial converter to hook up your WideBand there would be driver conflicts.

I think the ECU would get mixed up if two loggers where talking to it at the same tome.

 

[MY1GDSM]

must be the .Net framework ... I tryed to install 3.5 and my laptop got pissed off...

 

[JMiller]

This the cable you talking about for $15 shipped that works?
eBay Motors: USB Cable KKL 409.1 VW/AUDI OBD2 OBD OBDII VAG COM 409 (item 250386355221 end time Mar-18-09 14:06:19 PDT)

 

[SpoolinTalonAWD]

Fantastic work.
The DSM camp has needed something like this for a while now.

Here's hoping for 1G support.

 

[95Eclipse]

This the cable you talking about for $15 shipped that works?
eBay Motors: USB Cable KKL 409.1 VW/AUDI OBD2 OBD OBDII VAG COM 409 (item 250386355221 end time Mar-18-09 14:06:19 PDT)

+1 on this. I would like to know so I can go ahead and order mine.... Delivery times for Hong Kong KILL ME

 

[jrohner]

I just ordered one last night for like $13.88 with free shipping.

 

[snooopy365]

I'm making some good progress, when I have free time.

The Hybrid protocol for 95-96 is ugly and unnecessary complicated and has slowed things down a little. The Hybrid protocol is wrapped up inside the OBD2 and Emissions junk. The protocol is what they call "Designed by Committee", they make things complicated so you have to buy their datasheets and manuals.

I could not control the inter-byte and inter-message timing that OBD2/Hybrid is picky about with the .NET VCP driver. So I have completely switched to the FTDI D2XX DLL. This allows a lot more things to be done and should be a little faster. This also allows more than one FTDI cable to be plugged in, with VCP having more than one cable screwed things up.

I also got some info from Innovate Motorsports about their WideBand's protocol. I will probably add support for their WideBands in the future.

Also I have found a source for some dirt cheap cables, but I want to test them out a little more.


Progress Report:
Transitioning program from Virtual Com Port to FTDI Driver.
97-99 DSM is done.
95-96 DSM Init Sequence is done, as well as some simple requests.
I have about 8 to 10 hours of work before my next release which will support 95-99 DSMs.

I would like to add support for 1Gs, if anyone has a ECU and harness plugs they would like to donate it would help out a lot.



Also IRL today, I stripped three exhaust manifold studs. If anyone in the Reading, PA area wants to help a brother out, and has a right-angle drill I could borrow for a day, that would be awesome.

what kind of info do you need for 1G?
works the ping pong way, (2G seems to be nearly the same?)
basic adresses and formulas are shown here:

http://mmcdlogger.sourceforge.net/

 

[Ceddy]

what kind of info do you need for 1G?
works the ping pong way, (2G seems to be nearly the same?)
basic adresses and formulas are shown here:

http://mmcdlogger.sourceforge.net/

The 1G stuff is very well documented. But you shouldn't trust everything you read 100%

It helps having an actual ecu, to test my own code for mistakes.
And to try to speed up the protocol by decreasing the delays between messages.

 

[BkzProblem]

Any news on the 96 ecu's?? Once Again, what you are doing is greatly appreciated...

 

[knochgoon24]

The 1G stuff is very well documented. But you shouldn't trust everything you read 100%

It helps having an actual ecu, to test my own code for mistakes.
And to try to speed up the protocol by decreasing the delays between messages.

Do you think you could make that dynamic? Or maybe have the user enter in the delay as an option? I've heard that some ECUs can read faster from one car to the next. I'd like to push it as fast as it will go until I start getting I/O errors or jumbled data.

PM me when you need it tested on the '97 again. And the wideband support would be nice. I have plenty of time in the evenings to test it.

Any idea when your next update will be out?

 

[ZenkaiRacerDsM]

Man this is bad ass! I just bought a pocketlogger not too long ago but its kind of a pain trying to tune on a PDA, and most importantly no knock logging!

Is that blue cable on ebay thats linked the one that works? If so Ill order one asap! And just to be sure, my pocketlogger cable wont work?

You are the man! Are you taking donations? You should!

 

[19BLACKGST98]

If you log less items, you will have more resolution per item.

You should get at least 15 samples a second.
Log RPM, AirFlow and KnockSum only and they will update 5 times a sec.
WideBand is logged separate from other items.

RPM, AirFlow, KnockSum and WideBand is all you should need for WOT tuning.

Your only options for a faster sample rate are a ecu swap or a complete ems.


Also if you are using EvoScan to log KnockSum on a 95-97 the RequestId should be 3E not 26.
KnockSums address is different between 95-97 and 98-99.
Address 26 will always read zero on a 95-97.

I have a 98 with a 95 ECU so what does my requestID need to be? I did a pull and it showed one count of Knock (without me changing anything).

 

[v8killer]

still waiting for the release for the 95 guys, will this work with my elm 323 cable or will i have to get one of those vag com cables off ebay !

 

[jrohner]

I have a 98 with a 95 ECU so what does my requestID need to be? I did a pull and it showed one count of Knock (without me changing anything).

Then you go by what he says about a 95.

 

[rEclipserGST]

+1 for 95 models

 

[joeyzaza]

Thanks for this software

Works great on 97 GSX! I'm using the cable I bought from EvoScan.

 

[jrohner]

Would it be possible to just get the logging code from a 1g on to a 95 EPROM? I love the logging on a 1g; the TMO Logger is great.

How about otherwise the logging from an Evo 8? Maybe Tephra or MrFred on EvolutionM would know how the code works well enough to be a help on porting it over to a 95.

 

[Ceddy]

Would it be possible to just get the logging code from a 1g on to a 95 EPROM? I love the logging on a 1g; the TMO Logger is great.

How about otherwise the logging from an Evo 8? Maybe Tephra or MrFred on EvolutionM would know how the code works well enough to be a help on porting it over to a 95.

The problem swapping the Evo code is the newer ECUs use the H8 processors, which have a totally different Assembly Language.

A 1G logger swap is possible, but thats a few hundred lines of code.

I have the 95-96 protocol done, just have to finish a few things, then I'll put out my next release. Mitsu wrapped the 95-96 Hybrid protocol inside OBD2 so it is slow like OBD2.

Jeff from DSMChips said he might do a feature thats speeds up the protocol, problem is the Emissions/OBD2 part of the code is so cryptic the top DSM code guys have trouble figureing out what Mitsu was trying to do.

 

[-TunedDSM-]

Looking forward to the release of the 95 update, thanks again for all of your hard work.

 

[knochgoon24]

If you log less items, you will have more resolution per item.

You should get at least 15 samples a second.
Log RPM, AirFlow and KnockSum only and they will update 5 times a sec.
WideBand is logged separate from other items.

RPM, AirFlow, KnockSum and WideBand is all you should need for WOT tuning.

Your only options for a faster sample rate are a ecu swap or a complete ems.


Also if you are using EvoScan to log KnockSum on a 95-97 the RequestId should be 3E not 26.
KnockSums address is different between 95-97 and 98-99.
Address 26 will always read zero on a 95-97.

I'm going to have to try this out. I haven't changed anything in Evoscan (both v2.5 and v2.6 beta 7) and I know I don't get a continuous reading on 0 on my 97. It fluctuates betwee 0 and 1 under load. And judging by my timing curve, I'm not getting any timing retard due to knock.

 

[BkzProblem]

Cant wait for the 95+ release.... Im coming up to p.a. within the next two weeks so free luch and beer on me for your hard work....