MHIScan: New free DataLogger for DSMs

[logic]

Were you using this with your ECMLink'd ECU, Ryan? If so, you're trying to talk to a '95 ECU, not a '97.

 

[Burnett03]

No ecmlink v3 is on my race car, i was trying this on my stock DD 97 gst. Stock ecu.

 

[the_mork]

No ecmlink v3 is on my race car, i was trying this on my stock DD 97 gst. Stock ecu.

This might not have anything to do with the problem but what is the build date of your car?

 

[Burnett03]

I don't know.

 

[the_mork]

It should be on the driver's door tag. If you don't mind take a look at it next time you go for a drive and report back.

 

[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 between 0 and 1 under load. And judging by my timing curve, I'm not getting any timing retard due to knock.

Ok, so I finally got my car back on a night with nice weather (g/f was using it because her car had a bent rim). I got around to trying the difference between 3E and 26 for the knock sum request. It seems, Ceddy, that you were right. I made a new item to data log called "Knock Sum 2" with the 3E request so I could compare them heads-up. Here's a graph.

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

Knock Sum uses 26 as the Request ID.
Knock Sum 2 uses 3E as the Request ID. From the way the graph looks, 3E seems like the request to use.

Thanks for pointing that out.

And I still can't wait for your next update.

 

[Ceddy]

MHIScan v0.3 Released!

You can get it here -> http://www.ceddy.us/MHIScanV03.zip

This release is still a early beta, a lot things don't work or haven't been added yet.

The main additions are:
- Can now Log 95-96s using the Hybrid Protocol. (Yes, I know the sample rate is slow.)
- Complete rewrite of everything changing from VCP to the FTDI Driver.


Thanks for everyones interest.


Also if anyone needs an free OBD2 Scanner and Code Checker.
Get ScanTechProject77.rar from The Aktive Matrix - Your Automotive Resource
There is info about it on that site.

 

[justinhill98gst]

nice work!

 

[ZenkaiRacerDsM]

Didnt work for me. It fails to load FTD2XX.DLL.

 

[justinhill98gst]

Try this link for the v0.3 http://www.ceddy.us/MHIScanV03.zip

 

[Ceddy]

Didnt work for me. It fails to load FTD2XX.DLL.

You need to install the driver that came with your cable.

or

From the FTDI site -> D2XX Direct Drivers

 

[knochgoon24]

Just 1 bug I've found so far (haven't logged with it yet):

You locked the maximum size to 800x600 but you can still shrink it smaller.

 

[ZenkaiRacerDsM]

Installed the drivers for the cable. Still the same problem. Unable to load FTD2XX.DLL. I installed .net 3.5 before trying to run it as well.

 

[ZenkaiRacerDsM]

Ok, downloaded and installed the D2XX direct drivers. The error no longer exists but nothing happens when I click on find cable.

 

[habitatguy187]

We all appreciate your work in this and bringing this to the community for free. But you should charge at least $5 for a lifetime key or something once all the bugs get worked out. You deserve it for the work you've done.

 

[ZenkaiRacerDsM]

I dont know if I installed the D2xx driver files right. Do they need to be in the windows system folder? Or the system32 folder?

The v0.1 recognizes the cable but the v0.3 doesnt. So I guess somethings up with the D2xx drivers.

 

[whiteflash]

Anyone have a link to a cable that will work with this program? Thanks

 

[Ceddy]

I dont know if I installed the D2xx driver files right. Do they need to be in the windows system folder? Or the system32 folder?

The v0.1 recognizes the cable but the v0.3 doesnt. So I guess somethings up with the D2xx drivers.

What cable are you using?
What OS?

How to install driver:
Plug cable in and wait for "Found New Hardware"
Select "I will choose file" then "Have Disk"
Find your folder that contains the D2XX drivers and select the .INF file

 

[viperlp01]

Well i just ordered the VAG.COM cable... This looks sweet. Can't wait. Can we mess with the timing and fuel tables??

 

[Burnett03]

. Can we mess with the timing and fuel tables??

No way.

 

[ZenkaiRacerDsM]

I have the VAG com cable. When it asked me for what drivers to install I installed the drivers that came with the cable. The program was still giving me the same .dll error after I did that. So then I downloaded the D2XX drivers and copied the files from the 386 folder to the windows system folder. I did this because it wasnt going to ask me for drivers for the cable again since I already installed the ones that came with the cable. Once I copied the D2XX drivers to the system folder the .dll error no longer came up, but the program doesnt recognize that I have a cable connected.

 

[the_mork]

Well i just ordered the VAG.COM cable... This looks sweet. Can't wait. Can we mess with the timing and fuel tables??

It sounds like when the openport 2.0 cable becomes available that you probably will be able to use ecuflash. I'm excited but it will take some time for any modified roms to mature.

 

[Ceddy]

I have the VAG com cable. When it asked me for what drivers to install I installed the drivers that came with the cable. The program was still giving me the same .dll error after I did that. So then I downloaded the D2XX drivers and copied the files from the 386 folder to the windows system folder. I did this because it wasnt going to ask me for drivers for the cable again since I already installed the ones that came with the cable. Once I copied the D2XX drivers to the system folder the .dll error no longer came up, but the program doesnt recognize that I have a cable connected.

What VAG cable do you have? There are like 50 different kinds.
I have a 409.1

You can't just copy drivers to the system folder. Windows needs to handle that.

Google search how to remove drivers using the control panel.

 

[ZenkaiRacerDsM]

Its the exact cable you mention on page 2 of this thread. USB Cable KKL 409.1 VW/AUDI OBD2 OBD OBDII VAG COM 409.

Ill figure out how to remove the drivers and then reinstall with the D2XX drivers and report back. Thanks for the help!

 

[ZenkaiRacerDsM]

Ok it worked, the cable is now recognized. Thanks!