Logging Evoscan 2.6 for DTC (CEL) with newer ecuflash

[Chris@Rvengeperformance]

As many of you may know evoscan 2.9 doesn't read our diagnostic trouble codes correctly. The solution for now is to use evoscan 2.6 to pull DTCs. The issue is I found I couldn't connect after updating ecuflash to the latest version. I found the issue and the solution on openecu.rg

"Although be forewarned that installing this new version screws up EvoScan 2.6's ability to use the OpenPort V2.0. This is due to a new implementation of the

DLL now use OP2 driver for improved performance and reliability (see below for details) 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. *

The solution though is easy, Just delete the OP20PT32.DLL which resides in your EvoScan 2.6 directory. Then all will be well."

Deleting the dll allowed me to read the cel with 2.6 without an issue.

On my computer the file was here:

C:\Program Files (x86)\EvoScan\EvoScan v2.6

your paths may vary

[Jesters Deadd]

Thanks

[Chris@Rvengeperformance]

A little update to this... If you are running a modern version of windows then deleting this dll may only work until the next reboot. Windows will put the file back as part of their system restore system. Now, you can disable the system restore feature, but it is a good feature to have.

System Protection - Turn On or Off in Windows 8 (http://www.eightforums.com/tutorials/4688-system-protection-turn-off-windows-8-a.html)

You don't have to turn it off. Delete the file or any files you want and then use the "Delete all restore points for this drive"

Now reboot your machine and the file is still gone.

[Toni]

Thanks I'll have to try this out. I just updated to 2.9 along with all the firmware updates and neither 2.6 nor 2.9 worked. Glad there is a work around.

[LeRoyDL]

I just installed my ecu and am getting a j2534 error no matter what I do. I did install 2.9.0023 is it expected that I can't get any communication to work? (dataloging, read ecu, solenoids dtc etc.)?

I've uninstalled and reinstalled several times, should i try complete uninstall and go to 2.7?

[Chris@Rvengeperformance]

It is been some time since I messed with this, but you may want to uninstall everything, restart the computer, then plug in the tactrix and let it find the drivers. Then install ECUflash and go from there.

Also, be sure openport 2.0 is selected in evoscan.

[CoopKill]

And after uninstall, before reboot go into the program files folders, and delete any evoscan/ecuflash folders left, if any are.

[LeRoyDL]

When i first installed the drivers / evoscan / ecuflash i was getting an dll error in ecu flash so i went and found some other driver that cleared the error. Perhaps this hurt more then helped. This was a week or so ago, yesterday was first time i tried to communicate with the ecu. Do a complete removal and reinstall this afternoon.

[LeRoyDL]

So i tried installing this: Download Drivers + J2534 DLL (http://www.tactrix.com/index.php?option=com_content&view=category&layout=blog&id=38&Itemid=61)

and now can atleast compare rom to ecu:


152835996 EcuFlash Version 1443721
152835996 OS Version Windows 7
152835996 Qt Version 480
152836011 63 memory models read
152836011 scanning for metadata models in C/ecu/OpenECU/EcuFlash/rommetadata
152836198 612 ROM metadata models scanned
152836198 checksum module subarudbw loaded
152836198 checksum module mitsucan loaded
152836198 checksum module mitsuh8 loaded
152836199 patch module Subaru CAN Enhanced RAM Parameter Logging loaded
152836199 patch module Mitsu CAN RAM Parameter Logging loaded
152836201 flashing tool wrx02 loaded
152836202 flashing tool wrx04 loaded
152836204 flashing tool sti04 loaded
152836206 flashing tool sti05 loaded
152836206 flashing tool mitsukernel loaded
152836206 flashing tool mitsukernelocp loaded
152836206 flashing tool mitsubootloader loaded
152836206 flashing tool shbootmode loaded
152836207 flashing tool shaudmode loaded
152836209 flashing tool subarucan loaded
152836211 flashing tool subarucand loaded
152836213 flashing tool mitsucan loaded
152836225 J2534 API Version 0404
152836225 J2534 DLL Version 1003721 Jan 9 2013 172459
152836225 Device Firmware Version 1123688
152836225 Device Serial Number TA$1ZuBJ
152836225 interface close
152836245 J2534 API Version 0404
152836245 J2534 DLL Version 1003721 Jan 9 2013 172459
152836245 Device Firmware Version 1123688
152836245 Device Serial Number TA$1ZuBJ
152836245 interface close
152836265 J2534 API Version 0404
152836265 J2534 DLL Version 1003721 Jan 9 2013 172459
152836265 Device Firmware Version 1123688
152836265 Device Serial Number TA$1ZuBJ
152836265 interface close
152849699 131072 byte image read
152849699 using metadata XML ID 23862006 from file C/ecu/OpenECU/EcuFlash/rommetadata/mitsubishi/23862006xml
152852769 J2534 API Version 0404
152852769 J2534 DLL Version 1003721 Jan 9 2013 172459
152852769 Device Firmware Version 1123688
152852769 Device Serial Number TA$1ZuBJ
152854789 sending init sequence 2
152854789 got 0x11 response
152854789 sending init sequence 3
152855149 entering bootloader
152855149 sending kernel size (2029)
152855179 sending kernel load address (0x0000F000)
152855189 uploading kernel
152855519 verifying kernel checksum response
152855519 kernel valid
152855719 kernel get version
152855729 kernel version is OpenEcu Mitsubishi H8/539F Kernel V107
152855729 reading kernel comm buffer size
152855739 comm buffer size set to 256
152855739 reading kernel flash buffer size
152855739 flash buffer size set to 1024
152855759 -- comparing ECU flash memory pages to image file --
152855759 seg start len ecu CRC32 img CRC32 same?
152855909 LB7 00010000 00003000 18023FFE 1EFDA5D6 NO
152855929 SB0 00013000 00000200 D90A49D9 D90A49D9 YES
152855959 SB1 00013200 00000200 614E4403 614E4403 YES
152855979 SB2 00013400 00000200 9C5C2520 9C5C2520 YES
152855994 SB3 00013600 00000200 9D0A5827 9D0A5827 YES
152856001 SB4 00013800 00000200 529496AA 529496AA YES
152856021 SB5 00013A00 00000200 AB1E2EDA AB1E2EDA YES
152856031 SB6 00013C00 00000200 01D43F34 01D43F34 YES
152856051 SB7 00013E00 00000200 BD7BC39F BD7BC39F YES
152856251 LB6 00014000 00004000 570329C0 570329C0 YES
152856441 LB5 00018000 00004000 5363B41F 5363B41F YES
152856641 LB4 0001C000 00004000 D4CD69CA D4CD69CA YES
152856841 LB3 00020000 00004000 5E12815E 5E12815E YES
152857041 LB2 00024000 00004000 968D0FC7 968D0FC7 YES
152857241 LB1 00028000 00004000 BFC27FD9 BFC27FD9 YES
152857431 LB0 0002C000 00004000 8F3E818E 8F3E818E YES
152857461 interface close


Still not luck with evo scan. Im going to try another computer here shortly.

[LeRoyDL]

want to add, i also can't get the car to start nor do i hear the fp prime at power up :(

Ive verified the harness like 5 times, im not real sure whats going on :(

ignore this, i am certainly getting fuel pressure while cranking, verifying spark next.