ECUFlash 1.38 cable fix.
Jul 3, 2009, 09:01 AM
#33
Newbie
Join Date: Apr 2009
Location: Blacksburg Va (VT)
Posts: 30
Likes: 0
Received 0 Likes
on
0 Posts
I have the same issue, so here is what i do: I use the latest version of ECUFlash to open my ROM and edit the data using the latest XML, and then switch to the old 1.29 ECUFlash to read and write data.
I haven't noticed a problem using this method, I don't use 1.29 to edit anything, and all the changes I make in 1.4x seem to write fine, even bobbelbits (or whatever they are called).
Its a small pain in the *** to switch back and forth. You need to make sure to name the install directories differently to keep the copies seperated.
Maybe i'll try this hack later. Good Luck!
I haven't noticed a problem using this method, I don't use 1.29 to edit anything, and all the changes I make in 1.4x seem to write fine, even bobbelbits (or whatever they are called).
Its a small pain in the *** to switch back and forth. You need to make sure to name the install directories differently to keep the copies seperated.
Maybe i'll try this hack later. Good Luck!
Sep 24, 2009, 05:00 PM
#34
Newbie
iTrader: (3)
Join Date: Dec 2005
Location: Seattle, WA
Posts: 87
Likes: 0
Received 0 Likes
on
0 Posts
Colby
Sep 28, 2009, 04:05 PM
#35
Newbie
Join Date: Aug 2009
Location: canada
Posts: 33
Likes: 0
Received 0 Likes
on
0 Posts
i have a similar problem
ive tried ecuflash version 1.28, 1.29a , 1.45
i have a brand new 1.3u cable from limitless.nz ( unless they shipped me an old model and i need to modify it
heres the log
[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)
it keeps opening a window and saying error see log for details
could it be a bad ground or wiring ? bad obd2 port "?
i tried the Ecu unlocker , version 1.1 , didnt work
the cable is properly installed and key is at on when i press the ok button on READ FROM ECU
i read on another thread it might be a bad cable ?
any ideas plz ?
ive tried ecuflash version 1.28, 1.29a , 1.45
i have a brand new 1.3u cable from limitless.nz ( unless they shipped me an old model and i need to modify it
heres the log
[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)
it keeps opening a window and saying error see log for details
could it be a bad ground or wiring ? bad obd2 port "?
i tried the Ecu unlocker , version 1.1 , didnt work
the cable is properly installed and key is at on when i press the ok button on READ FROM ECU
i read on another thread it might be a bad cable ?
any ideas plz ?
Thread
Thread Starter
Forum
Replies
Last Post
vegasboy301
Evo Show / Shine
63
Dec 12, 2005 06:30 AM
