EvoScan v2.6 And New EvoScan GPS/Logger/Reflashing Touchscreen Review
Newbie
Joined: Feb 2010
Posts: 62
Likes: 0
From: Australia
as a heads up to those who are working with Hamish towards the final 2.7; the newest beta drivers for the tactrix OP 2 cable are not compatible with EvoScan. Under the Device manager it no longer shows up listed as a com port. it is now in its own new group "Vehicle PassThru Interfaces"
Newbie
Joined: Feb 2010
Posts: 62
Likes: 0
From: Australia
http://www.tactrix.com/downloads/ecu...1_win_beta.exe
it goes EvoScan -> op20pt32.dll -> usbser.sys -> op2 -> ecu
now
EvoScan -> op20pt32.dll -> op2 -> ecu
I'm sure EvoScan will still work.. its just a new firmware on the op2, and a new op20pt32.dll, evoscan uses the op20pt32.dll from what I can tell. so really, the new op20pt32.dll on first use will upgrade the firmware on the op2 cable. just means you can't use that op2 cable on another computer without the latest op20pt32.dll
--1.10.2938
* IMPORTANT - the OP2 now uses a custom driver I wrote for better speed and stability than the Microsoft usbser.sys driver. This allows for reduced latency and a cleaner installation as well. *** This means that initially you must do a full EcuFlash and J2534 / driver install so that all of these components will work together. OLDER ECUFLASH AND OP20PT32.DLL VERSIONS WILL NOT WORK WITH THE DRIVER. **
* IMPORTANT - the OP2 now uses a custom driver I wrote for better speed and stability than the Microsoft usbser.sys driver. This allows for reduced latency and a cleaner installation as well. *** This means that initially you must do a full EcuFlash and J2534 / driver install so that all of these components will work together. OLDER ECUFLASH AND OP20PT32.DLL VERSIONS WILL NOT WORK WITH THE DRIVER. **
now
EvoScan -> op20pt32.dll -> op2 -> ecu
I'm sure EvoScan will still work.. its just a new firmware on the op2, and a new op20pt32.dll, evoscan uses the op20pt32.dll from what I can tell. so really, the new op20pt32.dll on first use will upgrade the firmware on the op2 cable. just means you can't use that op2 cable on another computer without the latest op20pt32.dll
Evolving Member
Joined: Aug 2009
Posts: 284
Likes: 21
From: Hokkaido, Japan
Hello,
After starting to use EcuFlash1.43beta to avoid blue screen which often occur on my XP SP3, I've never been able to use EvoScan2.7beta5(last open beta released about 6 monthes ago) and other J2534 loggers. Because I'm not one of the lucky closed beta tester of EvoScan 2.8beta.
I'm looking forward to getting a 2.8 open beta or release as soon as possible.....
After starting to use EcuFlash1.43beta to avoid blue screen which often occur on my XP SP3, I've never been able to use EvoScan2.7beta5(last open beta released about 6 monthes ago) and other J2534 loggers. Because I'm not one of the lucky closed beta tester of EvoScan 2.8beta.
I'm looking forward to getting a 2.8 open beta or release as soon as possible.....
Evolving Member
Joined: Aug 2009
Posts: 284
Likes: 21
From: Hokkaido, Japan
found a solution of my problem
I found a solution of this.
EvoScan has another copy of op20pt32.dll in its own folder. As you know, current folder has the highest priority to search and execute a requested dll.
Solution:
1. Install EcuFlash1.43beta. New version of op20pt32.dll driver is installed into your windows system folder(likely windows/system32/).
2. Just remove or replace op20pt32.dll in EvoScan folder. EvoScan 2.7beta5 will be executable again.
BTW, After solve that, I've taken a test drive for some hours. No blue screen was showed. I can't say 'absolutely' yet, but it may be disappeared. Thanks to develop new driver!
EvoScan has another copy of op20pt32.dll in its own folder. As you know, current folder has the highest priority to search and execute a requested dll.
Solution:
1. Install EcuFlash1.43beta. New version of op20pt32.dll driver is installed into your windows system folder(likely windows/system32/).
2. Just remove or replace op20pt32.dll in EvoScan folder. EvoScan 2.7beta5 will be executable again.
BTW, After solve that, I've taken a test drive for some hours. No blue screen was showed. I can't say 'absolutely' yet, but it may be disappeared. Thanks to develop new driver!
Last edited by crimson red; Mar 22, 2010 at 12:58 AM.
The new driver should definitely fix any blue screens - that's why I wrote it!
I found a solution of this.
EvoScan has another copy of op20pt32.dll in its own folder. As you know, current folder has the highest priority to search and execute a requested dll.
Solution:
1. Install EcuFlash1.43beta. New version of op20pt32.dll driver is installed into your windows system folder(likely windows/system32/).
2. Just remove or replace op20pt32.dll in EvoScan folder. EvoScan 2.7beta5 will be executable again.
BTW, After solve that, I've taken a test drive for some hours. No blue screen was showed. I can't say 'absolutely' yet, but it may be disappeared. Thanks to develop new driver!
EvoScan has another copy of op20pt32.dll in its own folder. As you know, current folder has the highest priority to search and execute a requested dll.
Solution:
1. Install EcuFlash1.43beta. New version of op20pt32.dll driver is installed into your windows system folder(likely windows/system32/).
2. Just remove or replace op20pt32.dll in EvoScan folder. EvoScan 2.7beta5 will be executable again.
BTW, After solve that, I've taken a test drive for some hours. No blue screen was showed. I can't say 'absolutely' yet, but it may be disappeared. Thanks to develop new driver!
Evolving Member
Joined: Nov 2006
Posts: 223
Likes: 0
From: vienna,austria/scotland