I purchased an OBD-II scan tool from AutoEnginuity for use with the Evo. Basically I'm looking for feedback from other owners with respect to their experiences with this product.

To date I have been unable to get the tool to connect quickly with the car. The manufacture is looking into this matter, so it would be best to let this issue play out. What are your results related to how long it takes for the tool to find the car?

Second AutoEnginuity supplies a tool known as SpeedTracer that is an OBD-II based version of the "road dyno". This is similar to other implementations that are available from other vendors, typically PDA based. Attached are two images from the tool. The first is the setup screen. I used parameters based upon historical postings in this forum pertaining to the road dyno. The numbers are consistent with the published Mitsubishi data for the Evo. (Note that the extra weight accounts for the passengers and fuel.)

The second screen is the results for a third gear pull, or 85 HP and 69 ft-lbs. While the manufacture of the tool admits that AWD cars induce an error with the algorithms employed, these numbers are just wrong. Can anyone see what might be wrong with the setup? What are your results with SpeedTracer?

 

Any more feedback on this, freedom? Are you using USB or old fashioned serial port? PC or Pocket PC?

I'm looking into getting a scan tool for my Evo, and AutoEnginuity was the first one I came up with. Looks good from the descriptions, but what kind of timeframe are you talking about in connecting "quickly with the car"?

l8r)

 

The vendor released a fix for the connection timeout issue, so that is no longer a problem.

With respect to serial vs. USB I have used the tool with both configurations with zero problems. Normally I connect the Xede to a standard serial port and let the AutoEnginuity deal with a USB/serial adapter that I picked up at BestBuy.

So as a scan tool I would give a strong thumbs up to AutoEnginuity.

With respect to SpeedTracer I have not checked if a new version of the SW was released to resolve measuring AWD performance. The vendor knows that this is an issue and claimed that he has a different algorithm for AWD vehicles, but has yet to implement the code. I will email the guy and see where this stands.

 

When was the fix released? I got mine it it takes its time on a pocket pc, I have to use iso9141-2 or will not connect.

 

The PC version was fixed some time ago.

With respect to SpeedTracer the author comments that he has not been able to get an AWD algorithm working.

 

Any new updates on this unit? I would like to get one for my Garmin ique 3600 pda. Are the issues resolved.