Differences between EvoScan and Tactrix cable?
Evolved Member
iTrader: (7)
Joined: Sep 2004
Posts: 1,457
Likes: 0
From: South Beach, FL / Miami, FL / Pt. St. Lucie, FL / NYC
I think the EvoScan 1.3U cable works fine with the lastest version of ECUFlash. Like stated on the Evoscan site the cable has the does include the ECUFlash serial licence
im having the opposite problem as the OP. My ecuflash (latest version) works fine, but Evoscan wont connect to log. Using evoscan/limitless 1.3u cable.
im gonna pull my hair out.
b
im gonna pull my hair out.
b
i have a similar problem
i bought a 1.3u just a month ago from limitless.nz
when i try to read my ecu it gives me this
[00:08:08.953] Version 1.28.716
[00:08:08.953] 8 memory models read.
[00:08:09.218] 71 ROM metadata models read.
[00:08:09.218] checksum module "subarudbw" loaded.
[00:08:09.218] flashing tool "wrx02" loaded.
[00:08:09.218] flashing tool "wrx04" loaded.
[00:08:09.218] flashing tool "sti04" loaded.
[00:08:09.218] flashing tool "sti05" loaded.
[00:08:09.218] flashing tool "mitsukernel" loaded.
[00:08:09.218] flashing tool "mitsukernelocp" loaded.
[00:08:09.218] flashing tool "mitsubootloader" loaded.
[00:08:52.281] sending init sequence 1 (0001)
[00:09:04.578] sending init sequence 1 (0001)
[00:09:19.953] sending init sequence 1 (0001)
/ PePeeePP\ P = pin e = empty
/ PeePPePe\
white harness only has 1 wire
now on evo pin 79 which is green white , i used 4g64 pin 113 which is light green
evo pin 62 which is orange on 4g64 pin 85 which is red white
when i put my key at on , the check engine light comes on
but my battery was dead 2 days ago , its been charging for about 28 hours
anyway can anyone plz help
i tried the Ecu unlocker with version 1.28 didnt work
tried version 1.29a and version 1.45 ( new released ) and didnt work
they are all giving me the same error
the 1.3u looks like its installing correctly, it appears in my system info as com5 serial port
in the options of version 1.28 i did change the port to 1.3u , and version 1.45 mentions the cable when it tries to read the ECU
could it just be a bad ground on my ecu wiring or not enough voltage ( optima yellowtop )
i bought a 1.3u just a month ago from limitless.nz
when i try to read my ecu it gives me this
[00:08:08.953] Version 1.28.716
[00:08:08.953] 8 memory models read.
[00:08:09.218] 71 ROM metadata models read.
[00:08:09.218] checksum module "subarudbw" loaded.
[00:08:09.218] flashing tool "wrx02" loaded.
[00:08:09.218] flashing tool "wrx04" loaded.
[00:08:09.218] flashing tool "sti04" loaded.
[00:08:09.218] flashing tool "sti05" loaded.
[00:08:09.218] flashing tool "mitsukernel" loaded.
[00:08:09.218] flashing tool "mitsukernelocp" loaded.
[00:08:09.218] flashing tool "mitsubootloader" loaded.
[00:08:52.281] sending init sequence 1 (0001)
[00:09:04.578] sending init sequence 1 (0001)
[00:09:19.953] sending init sequence 1 (0001)
/ PePeeePP\ P = pin e = empty
/ PeePPePe\
white harness only has 1 wire
now on evo pin 79 which is green white , i used 4g64 pin 113 which is light green
evo pin 62 which is orange on 4g64 pin 85 which is red white
when i put my key at on , the check engine light comes on
but my battery was dead 2 days ago , its been charging for about 28 hours
anyway can anyone plz help
i tried the Ecu unlocker with version 1.28 didnt work
tried version 1.29a and version 1.45 ( new released ) and didnt work
they are all giving me the same error
the 1.3u looks like its installing correctly, it appears in my system info as com5 serial port
in the options of version 1.28 i did change the port to 1.3u , and version 1.45 mentions the cable when it tries to read the ECU
could it just be a bad ground on my ecu wiring or not enough voltage ( optima yellowtop )
08:59:28.828] Using interface OpenPort 1.3 Universal TX27XeHm39c1f4d53c43cca6c18bdebbdf14777d4bf1c331
[08:59:31.812] sending init sequence 1 (0003)
[08:59:32.843] got 0x05 response
[08:59:32.843] sending init sequence 2
[08:59:32.859] got 0x1B response
[08:59:32.859] sending init sequence 3
[08:59:33.234] entering bootloader
[08:59:33.250] sending kernel size (4420)
[08:59:33.281] sending kernel load address (0xFFFF7000)
[08:59:33.296] uploading kernel
[08:59:34.015] verifying kernel checksum response
[08:59:34.015] kernel valid
[08:59:34.234] kernel get version
[08:59:34.234] rkrv: preamble 1 error
[08:59:34.250] reading kernel comm buffer size
[08:59:34.468] reading kernel flash buffer size
[08:59:34.687] interface close
this is what i get on ecuflash any insight on this?
[08:59:31.812] sending init sequence 1 (0003)
[08:59:32.843] got 0x05 response
[08:59:32.843] sending init sequence 2
[08:59:32.859] got 0x1B response
[08:59:32.859] sending init sequence 3
[08:59:33.234] entering bootloader
[08:59:33.250] sending kernel size (4420)
[08:59:33.281] sending kernel load address (0xFFFF7000)
[08:59:33.296] uploading kernel
[08:59:34.015] verifying kernel checksum response
[08:59:34.015] kernel valid
[08:59:34.234] kernel get version
[08:59:34.234] rkrv: preamble 1 error
[08:59:34.250] reading kernel comm buffer size
[08:59:34.468] reading kernel flash buffer size
[08:59:34.687] interface close
this is what i get on ecuflash any insight on this?
Thread
Thread Starter
Forum
Replies
Last Post
evoscan
Evo X Engine Management / Tuning Forums
52
Jun 20, 2017 01:46 AM




