ECUFlash / Evoscan / Mitsulogger Questions

Just my luck it could be the lean out by 3.0 AFR and increase timing by 10* at peak timing.
i still have the same problem with mine i am lucky if it connects for 5 mins. no help from anyone. Seems as though everything related to a evoscan problem is hardware or computer related. i didnt get any help from the support ticket either. I tried everything in the book. there is nothing wrong with my computer either. hours of reading on google with evoscan problems, i give up. no support for it either.
i still have the same problem with mine i am lucky if it connects for 5 mins. no help from anyone. Seems as though everything related to a evoscan problem is hardware or computer related. i didnt get any help from the support ticket either. I tried everything in the book. there is nothing wrong with my computer either. hours of reading on google with evoscan problems, i give up. no support for it either.
yeah it reconnects sometimes. sometimes it doesnt i always have to unplug the usb close evoscan, and reopen then plug the usb back in. there is no pattern to when it does it. I tried closing programs and all kinda other crap, reset all the com ports, restart the computer. nothing seem to help. i am using the 2.0 cable but there are a a lot of people that use that cable with success with evoscan.
yeah it reconnects sometimes. sometimes it doesnt i always have to unplug the usb close evoscan, and reopen then plug the usb back in. there is no pattern to when it does it. I tried closing programs and all kinda other crap, reset all the com ports, restart the computer. nothing seem to help. i am using the 2.0 cable but there are a a lot of people that use that cable with success with evoscan.
Did you see these posts? It seems someone at evoscan helped him. He doesn't seem to know what they did though.
Tactrix 2.0 cable on 2002 Subaru WRX
Tried Evoscan 2.7, 2.8, 2.9. Keep getting the same error.
Info: OpenPort Firmware v1.12.368
Info: Battery 14.003V
Info: Initialize Vehicle ECU...
Info: Starting Subaru SSMII Init...
Info: Received 0 Data Bytes.
Info: Connection successful..
Error: Index was outside the bounds of the array.
Info: Datalogger Ended
This error does not happen with my 1.3u cable.
RomRadier/ecuflash works with both cables fine.
Process of elimination has led me to evoscan's tactrix 2.0 driver. I tried the tip listed for 2.7 by renaming the op20pt32.dll to op20pt32.old. If I start evoscan it then reinstalls a new op20pt32.dll. Somethings is not jiving.
Any help would be appreciated.
Tried Evoscan 2.7, 2.8, 2.9. Keep getting the same error.
Info: OpenPort Firmware v1.12.368
Info: Battery 14.003V
Info: Initialize Vehicle ECU...
Info: Starting Subaru SSMII Init...
Info: Received 0 Data Bytes.
Info: Connection successful..
Error: Index was outside the bounds of the array.
Info: Datalogger Ended
This error does not happen with my 1.3u cable.
RomRadier/ecuflash works with both cables fine.
Process of elimination has led me to evoscan's tactrix 2.0 driver. I tried the tip listed for 2.7 by renaming the op20pt32.dll to op20pt32.old. If I start evoscan it then reinstalls a new op20pt32.dll. Somethings is not jiving.
Any help would be appreciated.
The baud rate is just whatever is default in evoscan. I am not familar with messing with those settings. Is there a different rate i should log at?
Hey guys
Tried reflashing a friends car. Strange issue that I'm having, I havent had an issue like this before. I can read the rom from the ecu but when I make changes and want to write it back onto the ecu, it wont let me
The battery voltage is about 12.7v which I think is sufficient, below 12v is when ecuflash wont read/write. I've also tested the equipment on another friends car and it works ok so that eliminates the cable/laptop/software. Also used ecu unlocker and that didnt work.
If the ecu was blocked/locked, I wont be able to read it either I think
Using ECUFLASH 1.44 and 2.0 openport tactrix cable.
JDM 03 evo 8 with rom id 93660005
This is what I get from ecuflash log:
[20:35:08.429] J2534 API Version: 04.04
[20:35:08.429] J2534 DLL Version: 1.00.3210 Nov 22 2010 23:18:50
[20:35:08.429] Device Firmware Version: 1.11.3209
[20:35:08.429] Device Serial Number: TA5QDZH9
[20:35:11.043] sending init sequence 1 (0001)
[20:35:12.051] got 0x05 response
[20:35:12.051] sending init sequence 2
[20:35:12.058] got 0x1B response
[20:35:12.058] sending init sequence 3
[20:35:12.392] entering bootloader
[20:35:12.394] sending kernel size (0)
[20:35:12.398] sending kernel load address (0xFFFF6000)
[20:35:12.402] uploading kernel
[20:35:12.402] verifying kernel checksum response
[20:35:12.402] kernel valid
[20:35:12.405] sending init sequence 2
[20:35:14.407] interface close
Any ideas?
*Problem solved*
Tried reflashing a friends car. Strange issue that I'm having, I havent had an issue like this before. I can read the rom from the ecu but when I make changes and want to write it back onto the ecu, it wont let me
The battery voltage is about 12.7v which I think is sufficient, below 12v is when ecuflash wont read/write. I've also tested the equipment on another friends car and it works ok so that eliminates the cable/laptop/software. Also used ecu unlocker and that didnt work.
If the ecu was blocked/locked, I wont be able to read it either I think
Using ECUFLASH 1.44 and 2.0 openport tactrix cable.
JDM 03 evo 8 with rom id 93660005
This is what I get from ecuflash log:
[20:35:08.429] J2534 API Version: 04.04
[20:35:08.429] J2534 DLL Version: 1.00.3210 Nov 22 2010 23:18:50
[20:35:08.429] Device Firmware Version: 1.11.3209
[20:35:08.429] Device Serial Number: TA5QDZH9
[20:35:11.043] sending init sequence 1 (0001)
[20:35:12.051] got 0x05 response
[20:35:12.051] sending init sequence 2
[20:35:12.058] got 0x1B response
[20:35:12.058] sending init sequence 3
[20:35:12.392] entering bootloader
[20:35:12.394] sending kernel size (0)
[20:35:12.398] sending kernel load address (0xFFFF6000)
[20:35:12.402] uploading kernel
[20:35:12.402] verifying kernel checksum response
[20:35:12.402] kernel valid
[20:35:12.405] sending init sequence 2
[20:35:14.407] interface close
Any ideas?
*Problem solved*
Last edited by NigHtcRawl3R; Jan 18, 2013 at 08:17 PM.
Hi guys I was doing some logs on my 03 Evo GSR using EvoScan and in the program says 6.7 psi at idle?? I was so confuse then the boost is set at 20 but when I do WOT in EvoScan again it says 26 psi. I switch the boost hose twice already and is reading right no boost leaks detected. Mods are Omni 4 bar, speed density, FP red, tial bov, 1200cc Pte, aem fuel rail, 450 walbro, turbo back exhaust, ets 3.5 fmic, STM ic piping, egr delete in 91 oct. If somebody knows about this I will really appreciate the help since I don't know to much about this type of stuff and I live in El Paso where there is nobody that knows about this cars.
Hi guys I'm having trouble getting my new 1.3u cable and evoscan to connect ot my car. I have tried to connect the software to my car but have been unable to get any output. I have installed both evoscan and the cable drivers. The driver shows as installed in device manager but when i click start data logging it just keeps retrying but never succeeds. I have tried obdII 96+, Mitsubishi MutIII and DSM/3000GT. None of them give any output. With the cable hooked up the dash does flash out the diagnostic codes through the engine light and the neutral light. I am trying to get data about the sensors and speed. My car is a Mitsubishi Fto, its the tiptronic gpx model. I have already tried disconnecting the battery as error code 62 was being flashed when i first hooked up the cable but now thats gone but I still cant get evoscan to connect. Any ideas?








