My service engine light came on coming home from work and every time I try to read the codes with EvoScan it gives me different answers. Finally it gave me all of the codes at once:

Updated: 19:01:46
Vehicle speed sensor
Barometric pressure sensor
Knock sensor
EGR sensor

The only one that throws a red flag to me is the knock sensor which is odd because i am not knocking at all according to my logs. The rest...I dunno...any ideas about what would cause them? I was having an overboost which was since resolved and the codes were cleared. Are these just stored? If so, how to rid myself of a pesky stored code? I tried using Scan Tech II to pull and clear the codes but for some reason it keeps timing out even though I have it set to the JEFF Protocol and correct com port.

Assistance please?

 

Evoscan's DTC/CEL tool doesn't work on the Evo8 and Evo9 (USDM Models that I know of)

The codes your getting aren't what the light really is, you'll have to use OBD Scantech with your Tactrix cable, or a regular scan tool to retrieve and clear the code.

 

Download the free Scantech tool.

 

If you read my original post I am trying to use ScanTech, also. I have changed the JEFF Protocol and have the Comport set to the one designated by my laptop. However, when I look at the table it says codes NO and if I try to pull the code it comes up with a timeout error box or can't connect. Ideas on how to resolve this with ScanTech?

 

Can anyone answer my questions, please?

 

Same thing in here! I had a P0172 code and the Scantech Tool connected fine to the car and was reading live data.... but was giving me no codes.... when in fact I had one.

Had to use my standalone OBD2 Scanner!

 

I don't know how that was possible, if it connects fine and reads live data in Scantech, then everything works..

I do know some people have trouble getting it to connect, 90% of the time its just a matter of adjusting the protocol settings a bit until it connects, mostly trial and error.

I had one occasion where no matter what I did, it wouldn't connect, this was with older OpenPort drivers (ones prior to ECUFlash v1.29a) and I had several Driver versions installed that may have been giving me trouble.

I do keep a standalone OBD-II scanner around though, because I do think its a good idea to have one.

 

There are other settings for the protocol too, in another tab you have to set the Slow Init protocol, and no attempt to try other protocols, not sure why, but if you cycle through all of them it won't connect properly.

You need to connect first before you can retrieve the codes, but I understand the problem your having.

Sorry I missed that you had tried this in the original post, But the software does work once you get all the settings dialed in.

When I get a chance, I'll set it up so in the future, all the defaults will be pre-set to work with the tactrix cable, as the other cables are easier to get working.

 

scantech works fine for me, set it on com1, it was a bit stubborn but works perfectly, even diagnosed other evo's..

Wael

 

Worked on 4 Different cars so far.

 

It finally worked for me after installing and uninstalling the drivers lik 3-4 times so that it saw the USB as a VCP (Virtual Comm Port). Now it works fine on any obd-II car

 

Yeah so far the data that has been gathered from you guys is the com port portion of the new drivers doesn't install 100% properly. Most of the time its due to old FTDI drivers clobbering something. But the tool does work. The funny part is according to some "in the know" on OpenECU's forum, it really "Shouldn't" work.. But it does..