The Central Hub for DSM Community and Information

For 1990-1999 Mitsubishi Eclipse, Eagle Talon, Plymouth Laser, and Galant VR-4 Owners. This is where the DSM platform history is documented and archived. Log in to help us in our mission, and to remove most ads from the browsing experience.

MHIScan: New free DataLogger for DSMs

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.

I never could get this program to work with the ecmlink v3 cable, but thomas sent me a beta program that worked awesome for logging my 97 gs-t
 
what are the minimun laptop requirements to use this. I'm about to buy a cheap laptop It worked for dsmlink would it work for this?
 
I just got a netbook and I absolutely love it. It's a 10" Asus EEE PC. The model is 1000HA. They are only 300 and some bucks. 1.6GHz processor, 160GB hard drive, 1GB of ram, Windows XP. Or you can go with the 8.9" screen and get one for 200 something, but have a keyboard that sucks to type on. Mine is great even for everyday use, and the battery lasts like 5 hours browsing the internet on wireless.
 
If a laptop works for dsmlink it should probably work for this.

I'm running evoscan on an old Toshiba laptop with a 366mhz processor and windows xp. It boots extremely slowly and is sluggish with everything I do but logging itself is actually just as fast as my regular notebook.

As far as I can tell MHIscan is lighter on resources than evoscan.
 
I got my cable and started messing with it. I connect to the ecu then i get to this spot where it says"sending f7" then the cursor moves once then blah.. freezes up and says program not responding...
 
I can't get it to work either with the ebay vag com cable and i installed the driver for the cable. mine says.

"Microsoft .NET Framework"

unable to load DLL FTD2XX.DLL

System.DllNotFoundException: Unable to load DLL 'FTD2XX.DLL': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at MHIScanner.D2XX_Unit_NET.FT_GetNumberOfDevices(Int32& lngNumberOfDevices, String& pvArg2, Int32 lngFlags)
at MHIScanner.D2XX_Unit_NET.GetFTDeviceCount()
at MHIScanner.Form1.Form1_Load(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
MHIScanner
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/MHIScanV03/MHIScan%20v0.3/MHIScanner.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
 
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...
 
For everyone having problems, I'm working on a newer version that handles the initialization sequence better, as well as a interrupt driven RX/TX routine. Every year ECUs programming is a little different, and my current system doesn't handle the variations in timing well.

People having driver issues, I may do a driver installer, but its pretty easy to install the driver yourself.


I'm actively working on MHIScan in my free time, and should have a new release soon, but want to have everything working perfect before I release it.


For people who need working logger now, here are my suggestions for free or low cost loggers:

1G -> MMCD or TMO Logger

95-96 -> ScanTech from aktivematrix.com for OBD2
or EvoScan(Small Fee) for Hybrid Logging

97-99 -> Can use any of the EVO loggers, there are bunch of them. MitsuLogger from aktivematrix.com is a good one.
 
What logger can i use with the VAG cable i have besides yours LOL???
 
What logger can i use with the VAG cable i have besides yours LOL???

The OpenPort and VAG 409.1 cables operate identically.
Most programs designed to use the FTDI chip will work.

EvoScan
ScanTech OBD
MitsuLogger
MUTMonitor
Innovate LogWorks with MUT or OBD2 plug-in
 
The questions is will it work with the 95 ecu??
 
Ceddy your the MAN if you haven't heard it lately. Keep up the good work!

waiting for my cable to come from china.... :-(
 
I don't know if this was incorporated in the original design or not, but a lambda conversion would be very useful. Especially if the input to convert was selectable from narrowband / wideband.
 
I don't know if this was incorporated in the original design or not, but a lambda conversion would be very useful. Especially if the input to convert was selectable from narrowband / wideband.

Also, if the scale is selectable/programmable. That way you can get a direct AFR without having to convert the voltage using a formula the logger could easily do for you.
 
ceddyyyyyyyyy! hook us up with an update...
 
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.

Download link ->
Newest Version 0.3 http://www.ceddy.us/MHIScanV03.zip
Version 0.1 http://ceddy.us/MHIScannerV01.zip

Screen shots ->
You must be logged in to view this image or video.

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

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


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.

will this work for my 97 gsx? and where can i buy a datalogger from and cable?
 
Last edited by a moderator:
will this work for my 97 gsx? and where can i buy a datalogger from and cable?

I just look through this thread one more time. I've posted the answer to your question... several times. And yes, it does work. Quite well actually.
 
I am driving out to help a friend who owns the 2g and I got a couple questions about setting up mhiscan to work with a usb vag-com cable just to make sure I can get it all going the first time.

First I noticed there are only 2 options for cable ports on mhiscan, com1 and com3. No usb option. Will it automatically detect the cable on usb and give me a third option when its hooked up?

Second Do you guys install the vag-com driver? I did and the vag-com programe that comes with it says it cannot detect the cable on usb, is this something I should be concerned about?

Thanks Alot
 
I am driving out to help a friend who owns the 2g and I got a couple questions about setting up mhiscan to work with a usb vag-com cable just to make sure I can get it all going the first time.

First I noticed there are only 2 options for cable ports on mhiscan, com1 and com3. No usb option. Will it automatically detect the cable on usb and give me a third option when its hooked up?

Second Do you guys install the vag-com driver? I did and the vag-com programe that comes with it says it cannot detect the cable on usb, is this something I should be concerned about?

Thanks Alot

Other options will come up when you plug the cable in.
Does the computer recognize the cable?
 
Add Value - Be Respectful - No Trolling - No Misinformation - Participate Often!
Support Vendors who Support the DSM Community

Latest Classifieds

Back
Top