Have you talked to Colby (EcuFlash) or Hamish (EvoScan)? Hamish might not be too willing to share, as he has a commercial product to sell, but Colby might be more willing to discuss specifics. Also, MalibuJack (MitsuLogger) on AktiveMatrix had a MUT3 scantool at one point, if memory serves?
____________________________
-Ed
Advertisement
To browse the forums without the advertisements above, Login/Register
Have you talked to Colby (EcuFlash) or Hamish (EvoScan)? Hamish might not be too willing to share, as he has a commercial product to sell, but Colby might be more willing to discuss specifics. Also, MalibuJack (MitsuLogger) on AktiveMatrix had a MUT3 scantool at one point, if memory serves?
I talked to them a little, they are all Evo guys and are more interested in the newer stuff.
Thats the main reason I started MHIScan, to support older cars.
I tried the cable on my Eclipse today. It was running around 10 samples per second in Evoscan on Hybrid mode. I tried the EC95 Brazillian code -- I couldn't get a connection with Mitsu or Hybrid in Evoscan. I also unsuccessfully tried Mitsulogger, MHI Scan, and MUT Monitor.
Does your cable have pins 1 and 4 grounded together?
Quote:
On the EVO4/5/6 you have to short pins 1-4 together so the ECU let you initialise it.
My VAG 409.1 cable doesn't have them grounded together.
My OpenPort 1.3 cable doesn't even have a pin 1.
I'm trying find in the service manual, what on the OBD2 plug is connected to the ECU.
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.
Quote:
Originally Posted by knochgoon24
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.
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.
____________________________
Wes - '97 Talon Tsi AWD
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.
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.
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
