Hey, I have been asking arround and so far no answer.

I have had the V2.1 Evoscan for a few weeks (2 months maybe?) and until recently it worked flawlessly. A few days ago I tried to do some logs and it connected, but all my alarm triggers activated (knock alerts, high coolant, etc) and it would read extremely weird values (knock counts 255) and the box that lights up green when connected would be green, but it would flash yellow. I hit "stop data logging" and tried to open the log, but it didnt record anything.

Think I had an issues with Evoscan, I went in an had the "repair Evoscan" done. That didnt help, so I downloaded V2.2 off the site and it wont connect. It just keeps going thru the auto connect sequence until it times out.

So after that failed, I found out how to download V2.0. Well guess what? Same thing. No connection, no recording. But on V2.0 when trying to connect the car's RPM would raise to 2200. I had to turn the car off and restart to get it to idle correctly (idle set to 1150).

After all of that, I rechecked the Tetrix cable connections, and wiggled it arround while trying to connect (to see if it connected, indicating a fault in the wires) and it didnt change. I reopened V2.1 and it magically started working perfectly. That is until the next day when I tried to open it, it said it couldnt find the directory for the installation of Evoscan V2.1 That puzzled me, so I went and had to re-reinstall it. Now it works but the other 2 versions still wont work. (individually, I am not trying to run the 3 of them at the same time. I know better)

Any ideas? V2.1 is working, going on 3 hours of no issues. Knock on wood.

 

Baudrate correct??

-E

 

I had the same problem, the only thing I could figure out was something was corrupt with the drivers. I reinstalled and it worked perfect.

 

Dont you need to un-install all other versions and shortcuts, before you re-install?

 

This happened with Evoscan .99 last year. What I did was completely delete every Evoscan file and its directory, reinstall the FTDI driver and reinstall Evoscan.

 

exactly! this is what I had to do...

 

wow, ok. I will have to do that. THank you!

 

does V2.1 have the support for the AEM UEGO? or will have have to download a different version?

 

Just checked... AEM Uego IS supported in 2.1...

Cheers-
E

 

weirdly enough. I went to rewire the cable from the wideband to usb-serial converter and all I did was disconnect and reconnect the same wires to the same places, reloaded the usb-serial driver and evoscan started recording the wideband.