Evoscan logging on my 99vr4 with Tactrix.

[ICPREY]

I recently bought Evoscan (2.9),Chrome,and a Tactrix cable(2.0) to datalog my 99 vr4. I've loaded all the chrome files per the instructions to Evoscan and ECUflash. I plan on using chrome to make sure the CEL goes away even with my cats/EGR/EVAP removed. I want to get comfortable data logging first prior to doing any flashing.
I've been playing around with the Evoscan and my laptop in the garage with the car idling and it will connect, but it randomly stops working. No consistency on when it disconnects. It acts like it locks up and then it gives me an error code J2534 Read Error - 16. Do I have to change the settings to make sure it doesn't lock up? I read that if you turn off "log data to screen" if will make it faster..is that the answer? Do they have Firmware up dates for the Open port? Maybe try Evoscan 2.6 instead? I've used Scan XL Pro on my Viper and Viper truck with no issues, to bad I can't use it on my 99. Any help would be appreciated!:biggrin: I've attached what the log report says.

Info: Battery 12.177V
Info: Initialize Vehicle ECU...
Info: Initializing At 5 baud...
Info: Timer: 2122.407ms
Info: Initialization Complete...
Info: Waiting for INIT Response...
Info: ECU ID: E6AE
Info: Connection successful...
Error: J2534 Read Error - 16
Info: Datalogger Ended.

[ICPREY]

Took the car out today and I was able to log two runs of approx 5-10 minutes each, so I guess it works. I did turn off "log data to screen", but I don't know if that makes a difference. I read somewhere the 1.3 cable is better to log. Anybody know where I can get an affordable one? Do I really need it?How do I tell if the download speed of the cable is good enough?
I was also able to log with the scan XL pro software and cable, but it didn't display knock or some of the fuel trims like the Evoscan. I do like how it displays the data in graph form in real time and recorded form. I was also able to clear the CEL for the EGR/EVAP with it (till next start).

[Chris@Rvengeperformance]

I do all my logging with just the 2.0 cable. no problems. usually if you can't connect it is a driver thing.

[ICPREY]

Do you log data to screen? Do you use the live trace feature?

[Chris@Rvengeperformance]

I guess I'd have to look to know what you mean. If you mean I show live numbers on the screen or utilize the gauges then yes.

I'm not sure, but isn't the live trace used to trace out where you are at in a rom? Probably not going to work for us.

[ICPREY]

Yea I mean showing live numbers or gauges while logging. I need to experiment more with the logging software to feel comfortable with it. Thanks for the the reply.