MHIScan: New free DataLogger for DSMs

[dsmoverboosted]

Other options will come up when you plug the cable in.
Does the computer recognize the cable?

Not right now but I have just read that I need to use a usb driver to make it a virtual com port.

I have downloaded the driver from ross-tech so I am hoping I am ready to go.

I guess mhi scan will see an extra com drive when the cables setup properly.

 

[j_eclipse96]

Hi there, guess I'm signing up as a beta tester as well.

I bought this cable: (USB Cable KKL 409.1 VW/AUDI OBD2 OBD OBDII VAG COM 409:eBay Motors (item 370188399754 end time May-15-09 12:06:24 PDT))
a couple weeks ago, and am having the same initialization problems as the other guys. I've messed around with drivers (openport 1.3 and the like) and tried pretty much everything I can think of to get it to connect, but no luck.

Difference is, I can't get this cable to link up to ANY of the OBDII programs I've tried. MitsuLogger, OBDIIBaseScan, EcuFlash; all fail to initialize via timeout. One thing I've noticed is that no matter what the driver's name is on the COM port, all the programs recognize it by the name of "USB <-> Serial," which is the name of the USB controller itself in the device manager, which seems to have only one driver option, no matter if its from the software CD or from Windows. From all the screenshots I've seen for these programs, it always reads as "OpenPort 1.3 Mitsubishi" or something similar, and I cannot for the life of me get mine to recognize as that.

So I started to think, maybe the cable is the problem? I was browsing around the aktive matrix forums, and found this thread: (The Aktive Matrix - View topic - VAGCOM KKL OBD-II w/ FTDI Chip WORKS with Mitsulogger)
For those of you without usernames there, this is what the first post by malibujack reads:

As promised,

I just ordered a VAG-COM FTDI based cable and will be testing it with Mitsulogger. This is a diagnostic cable ONLY, and will **NOT** Flash an ECU (You will need a tactrix cable)


UPDATE: CABLE RECIEVED, TESTED And WORKS with Mitsulogger v1.6b3 and later!! Not tested with earlier versions, but it should work if its the only FTDI Device.

OBD-II Scantech does not work with this cable. But its obviously programmatical as its init function works differently. I will work on a mode that works with this.

However I wanted to test an alternative data logging / OBD-II cable for Mitsulogger and OBD-II Scantech since its about $20 shipped from Hong Kong. A bargain if you dont need to flash.

I am planning on supplying these cables and my software to my Tuning Clients who don't need the reflash ability, but the logging capabilities only.

If this cable works, I will order a bulk of these cables for resale.

When I can determine if this cable works with the loggers, you can search E-BAY For these cables using the search terms "VAG KKL FTDI" if you get no hits, check the "Search descriptions" checkbox and search again.

There are 2 versions of this cable, one uses an unknown chipset, and another uses an FTDI chip. The unknown chipset should create a vitrual com port, and should also work with OBD-II Scantech on the com port it detects, but it won't currently work with Mitsulogger.

The cable I'm testing is a newer design using an FTDI Chipset.

I know the cable I bought said nothing about having that chipset in the description. Is it possible we received cables that had this "unknown" chipset, and that could be the root of our problems? Or did I just funk something up somehow?

Sorry for the long post, just trying to be descriptive. I'm gonna try a system rollback to before I first tried installing the cable and go from there.

Cheers, and keep up the good work Ceddy. Also, thanks for the reply to my thread about my timing issues on here, ironically I'm waiting on a logging program to figure that whole thing out

Edit: Cracked open my cable housing, and it is indeed the FTDI 232BL chipset. Also rolled back my system, and messed with all the drivers again to no avail. Going to try on my roommates computer. Any ideas for mine?

 

[Ceddy]

The Ebay 409.1 cable will not work with EcuFlash, that program is written so only cables sold by Tactrix will work with it.

It should work find with Mitsulogger. I suggest using the Drivers that comes with EcuFlash or the FTDI website. Use the FTDIUNIN.exe to uninstall your old drivers.

Also in Control Panel -> Device Manger check your cables baud rate and set to the highest. That shouldn't matter though.

USB <-> Serial is just the cables name. It has no bearing on anything.

Hi there, guess I'm signing up as a beta tester as well.

I bought this cable: (USB Cable KKL 409.1 VW/AUDI OBD2 OBD OBDII VAG COM 409:eBay Motors (item 370188399754 end time May-15-09 12:06:24 PDT))
a couple weeks ago, and am having the same initialization problems as the other guys. I've messed around with drivers (openport 1.3 and the like) and tried pretty much everything I can think of to get it to connect, but no luck.

Difference is, I can't get this cable to link up to ANY of the OBDII programs I've tried. MitsuLogger, OBDIIBaseScan, EcuFlash; all fail to initialize via timeout. One thing I've noticed is that no matter what the driver's name is on the COM port, all the programs recognize it by the name of "USB <-> Serial," which is the name of the USB controller itself in the device manager, which seems to have only one driver option, no matter if its from the software CD or from Windows. From all the screenshots I've seen for these programs, it always reads as "OpenPort 1.3 Mitsubishi" or something similar, and I cannot for the life of me get mine to recognize as that.

So I started to think, maybe the cable is the problem? I was browsing around the aktive matrix forums, and found this thread: (The Aktive Matrix - View topic - VAGCOM KKL OBD-II w/ FTDI Chip WORKS with Mitsulogger)
For those of you without usernames there, this is what the first post by malibujack reads:



I know the cable I bought said nothing about having that chipset in the description. Is it possible we received cables that had this "unknown" chipset, and that could be the root of our problems? Or did I just funk something up somehow?

Sorry for the long post, just trying to be descriptive. I'm gonna try a system rollback to before I first tried installing the cable and go from there.

Cheers, and keep up the good work Ceddy. Also, thanks for the reply to my thread about my timing issues on here, ironically I'm waiting on a logging program to figure that whole thing out

Edit: Cracked open my cable housing, and it is indeed the FTDI 232BL chipset. Also rolled back my system, and messed with all the drivers again to no avail. Going to try on my roommates computer. Any ideas for mine?

 

[dan2288]

I cant get mhiscan to work with the vag cable. Does evoscan work with the vag 401.9 cable?

 

[Ceddy]

I cant get mhiscan to work with the vag cable. Does evoscan work with the vag 401.9 cable?

Mine does, open up your cable and check if the chip says FTDI 232BL. The VAG 409.1 is the same as EvoScans 1.4 cable.

Your pretty close to me, if you want to test your cable on my setup, you could sometime.

 

[Bender]

I have the ebay cable, and I can get it to work with scantech, but on the new version of mhiscan I get an 00 00 error code. I then tried it on the first version of mhiscan, and it would connect, but after 1 second, the Windows Vista pop up that says I have to close the program comes up. I then tried it on my other car, and the same thing. One car is a 97 gst spyder, and the other one is a 97 gsx.

 

[j_eclipse96]

Tried it on a friends computer (nice dell, only a year old with vista pro) and although I got the drivers to install correctly, it still reads the same way in mitsulogger and mhiscan, 'Serial <-> USB', and I get the same initialization issues, as if the cable isn't there. Completely out of ideas here.

 

[ryanman]

Well i got the driver downloaded and everything. I click on all the stuff i want it to log but when i click to start logging it will send the signal and the next sequence says "sending f7" then it will show the f7 in red under it like it did when it first connected to the ecu and then it freezes. I tried using the debug on there and i even tried using the 97 ecu.. Nothing i did helped it...

Mine is doing the same thing, can't figure it out...

 

[Ceddy]

I haven't had a lot of time lately to work on MHIScan, been concentrating on making a definition for the Flashable ECUs.

Also sold off a lot of my different year ECUs for funds for some new parts.

I will try to get the Init Sequence problem fixed soon, if you need a logger check out: EvoScan, MitsuLogger, and Scantech. I posted info about them previously in this thread.

 

[joey17]

cmon dude you cant let us down . i went and bought a laptop just for your logger program i need to start logging and i cant get any of the loggers to work

 

[rEclipserGST]

cmon dude you cant let us down . i went and bought a laptop just for your logger program i need to start logging and i cant get any of the loggers to work

+1

After I get this 14b swap & external wastegate installed... its logging & street tuning time. Hopefully you get those kinks out. Read up on some Einstein stuff, I'm sure he did some out of the ordinary things to give his genius mind a break in order to bake a break through

 

[brian9397gsx]

im having troubles with his software to i bought a laptop running xp and it keeps saying it failed to initialize. has anyone else ran into this problem? were you able to fix it? i downloaded it to my desktop with vista and it works so i have no clue. id really like to run this over the others so i can log knock thanks.

 

[delta448]

Ceddy, not sure how much of the code on 97+ ECUs you've dissected, but can you verify and list any of the differing requestIDs for those of us with the later ECUs? The big one I think everyone's wanting to know are the different requestIDs for logging knock.

 

[Ceddy]

Ceddy, not sure how much of the code on 97+ ECUs you've dissected, but can you verify and list any of the differing requestIDs for those of us with the later ECUs? The big one I think everyone's wanting to know are the different requestIDs for logging knock.

KnockSum on a 95-97 the RequestId should be 3E
KnockSum on a 98-99 the RequestId should be 26

I haven't have time to work on MHIScan lately, I've been concentrating on the 98/99 Flashable ECUs, they have amazing potential.

Anyone who needs a logger I highly recommend EvoScan, its a great logger for $25.

97-99 guys can use any of the Evo Loggers out there.

Some good software to check out:
EvoScan
ScanTech OBD
MitsuLogger
MUTMonitor
Innovate LogWorks with MUT or OBD2 plug-in

 

[matthewdesigns]

I've tried all of these loggers, with the exception of Mitsulogger. I cannot seem to download the file in it's entirety, and have tried many times. I don't end up with a .zip file, what I get is a file which is not recognized/usuable at all.

Can someone with a working copy of Mitsulogger please PM me, so that I can get it from you by email? Thanks!

 

[giovanniv]

I've tried all of these loggers, with the exception of Mitsulogger. I cannot seem to download the file in it's entirety, and have tried many times. I don't end up with a .zip file, what I get is a file which is not recognized/usuable at all.

Can someone with a working copy of Mitsulogger please PM me, so that I can get it from you by email? Thanks!

I am having trouble also but with mhiscan. I have tried time after time to download but it doesn't work. Can anyone pm me with how they downloaded it?

 

[rocafellafw]

I'm also having problems running the .exe file I end up with it. Somehow it works on my desktop but not my laptop.

 

[the_mork]

We'll need more information than that to help you. What operating system are you running on your laptop (xp/vista/windows7)? Is there any error message? What exactly happens when you try to run the executable?

 

[rocafellafw]

Windows XP, this is what I get:

You must be logged in to view this image or video.

 

[the_mork]

Honestly this is Ceddy's realm. I have no idea what the actual problem is but in general if this were on my computer I would start by moving the executable to the desktop and trying again. If that didn't work I would right click and "run as administrator". There may be something I'm missing but it is maybe worth trying.

 

[giovanniv]

Why the hell does this only work when I download it onto my desktop and not onto my laptop?!? This is so frustrating!!!!

 

[Ceddy]

Why the hell does this only work when I download it onto my desktop and not onto my laptop?!? This is so frustrating!!!!

I am no longer supporting or developing MHIScan.
I've posted multiple times some good alternatives.

KnockSum on a 95-97 the RequestId should be 3E
KnockSum on a 98-99 the RequestId should be 26

I haven't have time to work on MHIScan lately, I've been concentrating on the 98/99 Flashable ECUs, they have amazing potential.

Anyone who needs a logger I highly recommend EvoScan, its a great logger for $25.

97-99 guys can use any of the Evo Loggers out there.

Some good software to check out:
EvoScan
ScanTech OBD
MitsuLogger
MUTMonitor
Innovate LogWorks with MUT or OBD2 plug-in

 

[giovanniv]

Is there anyother free software that allows you to monitor knock?

 

[zhjiln]

didnt like this program... could not save my logs when i press the "save xml"

ill stick to mitsulogger because my evoscan is being a PITA and not working

 

[the_mork]

I am no longer supporting or developing MHIScan.
I've posted multiple times some good alternatives.

Ceddy has made it quite clear that he isn't interested in finishing this project so those features will likely never develop. There was never a stable or finished release so no don't expect it to be fully functional. At this point Ceddy is doing IMO much more important work with maintaining and expanding the definitions and capabilities of the 98/99 DSM ecu.